Muskoka

Thought I'd try the VSPX processing. When selected it gives these instructions. The paste function is simply not working. Multipart commands are consolidated, I delete the existing string of commands from the box, cursor is still in the box, try to paste but nothing is there. Even if you right click with the mouse in the box, the paste function is grayed out. Also, pressing the test button in the editor does nothing. It sits for minutes on end with no update in the va window, it's not doing anything. While I'm at it, I'm finding some commands don't work. For instance the jtac command, from the manual page 48, " In addition to these there are additional commands for JTAC, such as Repeat Brief, " that command returns nothing, although it's recognized in the va window. The brief is not repeated. I've found others, but I'll start with that, as it may be due to the keywords not updating when switching to VSPX? Tried with va run as administrator, and not, no difference. I have the Vaicom Pro license, with chatter.

Thank you guys for the answers. What I'm trying to achieve seems to be working fine. As long as TAD is the SOI when I hit TMS down long, the TGP is "locking on" to the target. I can see the camera view change immediately when I hit TMS down long. After takeoff, and getting closer to the target destination, I can see the intended target on the TGP display, at least very close to it, within feet I'd say. That's all I was trying to do, get the TGP display to lock on to the target before even leaving the ground. It seems to work. I can then fine tune through the TGP as I get closer, but I was trying to find out how to lock that view on the TGP to the target prior to takeoff, and like I said it seems to be working.

Trying to learn the A10C, been at it a few days. All is going pretty well, able to hit targets with bombs in CCRP. I've just been picking targets in the Tgp. Question is about using a predefined way point in the mission editor, which would also be my intended target, and thus it's my Spi. Lets say I create a mission with a single way point, that is also the intended target. This would be done in the briefing room before I ever get in the aircraft. I know this is going to confuse you, I'm confused. I've read that China hat back long will move all sensors to the current way point, which is also my intended target, therefore I want it to be Spi. If CHBL moves all sensors to the current way point, does it them become "the target", Spi. I don't think it's working that way, at least to my eyes. If the single way point / intended target I create in the mission editor is 75 miles away, CHBL sets all sensors to that way point, how do I target it when it's 75 miles away? I can't seem to wrap my head around how to do this. I've watched a ton of videos, but can't seem to figure out something that seems pretty simple. In my mind I should just be able to "mark" the way point on the Tad page to make it Spi, while sitting on the ramp prior to takeoff, but I don't think this is how it works? There must be some way to mark your intended target before getting in the air, regardless of how far away it is? Found this thread, looks like what I need to do? https://forums.eagle.ru/showthread.php?t=159074 Once in the air everything is working fine, no problems hitting targets. Still have to hunt for the targets in the tgp though, was hoping for a different method than trying to scan a tv image for the target. Still learning....

I guess, it works, and that's what really matters in the end. Wanted to fly her for "my" country, but that's not to be.:)

This was posted under the aircraft, I've moved it here where it's probably better suited. "Guys, it's been a while since I've used DCS. I'm sure in the past, over a year ago, I could use the ZA variant in the mission editor. Now I can't seem to be able to do that, it's not available in the drop down. I've tried various things, but the only Albatros available is the C variant? I'm sure it's something I'm doing, but I can't seem to figure it out. Perhaps this should be moved to the Mission editor section." Figured it out. It can only be loaded under certain countries, why, who knows.

Moved to Mission editor. Can't see how to delete this post.

This isn't changing anything in the registry, nothing listed in that screenshot at least. All keys are the same value after running, and a reboot. Win 10 Pro ver. 2004.

Thanks for the tip, I'll commit this to memory for future use.:)

Thank you very much for the help, that did the trick. I had already set the custom path, and did the reg fix. The fix was either the repair, or deleting the export.lua

Never had much luck in the past (years) getting this going. Coming back to DCS after at least a year away, and a few installs of Win 10 on this computer. I own VA, and purchased Vaicom Pro and the chatter files back in 2017. First question, why is the aircraft I'm sitting in not listed in the PPT window in the config utility?I've setup my joystick for PTT, when I select the button it's transmitting. Let's start there.

Deleted post, sorted out the issue.

Agree, it's very noticeable. I'm usually mid to lows 50's with in game ipd, too high a number and the cockpit is way to cramped, too low and the cockpit is way too big.

My experience as well. A few emails, they paid for everything, close to 2 weeks from the day I shipped it back, until it was returned. I should add, they sent back a refurbished unit, but I was advised before hand, and basically had no choice but to accept. Perhaps my "slight reluctance" to accept a refurb was why they sent a $60 cable back, who knows.

My right speaker quit after 2 months of use, was replaced without question. They even sent a new cable back when all I had sent was the headset. A year and a half later and the left speaker is acting up. Have taped both sides now so it can't move at all. Has worked fine taped up for the last couple months.

Sent my headset back for rma replacement a year ago, infamous speaker/ribbon cable problem, and for whatever reason they sent me a cable back, that I was definitely not expecting. Lucky me, I now have a spare. They sell for $60 here in Canada.

:doh: Thank you.... Sometimes the most obvious things go unnoticed. Works as it should. Thanks again Czech6.

Hi, thanks for the response. Yes, I do have it on.

Coming back after a break from DCS, and getting the message "PTT Key not in use: check configuration". VA is setup, Joystick setup has been tested, using the test button in VA. I'm using Joystick 1, button 3. Vaicom PTT config (lctrl, lalt, c) is set to SNGL, and I use TX4 "SEL/AUTO". In the PPT section of the Vaicom profile in VA, Transmit TX4 press and release are both set to Joystick 1, Button 3. No idea why I see a message it's not setup? And when it says "check configuration", what configuration am I supposed to check? I've done the lua export from page 33 of the manual, still no luck, same message as above when giving a command. Here's my VA log window. 8:31:20 AM - PTT Key not in use: check configuration. 8:31:19 AM - Recognized : 'ground power on' 8:30:44 AM - Chatter initialized. 8:30:44 AM - Resources added. 8:30:44 AM - Adding chatter resources.. NATO 8:30:44 AM - Chatter theme set to NATO 8:30:44 AM - Adding themepack collections 8:30:44 AM - Nearest ATC: Nellis AFB. 8:30:44 AM - Player New callsign entered module L-39C Albatros, unit callsign Enfield11 8:30:44 AM - Resetting selected units. 8:30:44 AM - DCS mission | Nellis Ramp L39c 8:30:44 AM - ------------------------------------------ 8:30:44 AM - Plugin 'VAICOM PRO 2.5' initialized. 8:30:44 AM - Ready for commands. 8:30:44 AM - Startup finished. 8:30:44 AM - Chatter initialized. 8:30:44 AM - Resources added. 8:30:44 AM - Adding chatter resources.. Default 8:30:44 AM - Chatter theme set to Default 8:30:44 AM - Adding themepack collections 8:30:44 AM - Current Profile string matches database. 8:30:44 AM - No new DCS modules to import. 8:30:44 AM - Success. 8:30:44 AM - Building master labels table... 8:30:44 AM - Success. 8:30:44 AM - Building master keywords table... 8:30:44 AM - Adding 0 imported menu commands. 8:30:44 AM - Adding 0 imported ATC aliases. 8:30:44 AM - Success. 8:30:44 AM - Loading F10 menu items... 8:30:44 AM - Success. 8:30:44 AM - Loading keywords database... 8:30:44 AM - Success. 8:30:44 AM - Updating keywords database... 8:30:44 AM - Checking VA profile. 8:30:44 AM - 4/5 DCS-side files were updated. 8:30:44 AM - Reset: TabSheetBar.lua 8:30:44 AM - Reset: speech.lua 8:30:44 AM - Reset: RadioCommandDialogsPanel.lua 8:30:44 AM - Reset: VAICOMPRO.export.lua 8:30:44 AM - Unchanged: Export.lua 8:30:44 AM - Saved Games folder = C:\Users\musko\Saved Games\DCS.openbeta 8:30:44 AM - DCS World installation path = I:\DCS Open Beta 8:30:44 AM - Custom install path used for 2.5 OpenBeta 8:30:44 AM - DCS World version 2.5 not found. 8:30:44 AM - Executing automatic lua code installation. 8:30:44 AM - License: PRO 8:30:44 AM - Plugin version 2.5.8.3 (release) 8:30:43 AM - Initializing.. 8:30:43 AM - Press LCtrl+LAlt+C for config. 8:30:43 AM - VAICOM PRO for DCS World. License: PRO 8:30:43 AM - Plugin support enabled.

Great news.....

Just picked this up, went to check out the link in the first post, and get the same.

To each their own I guess, but using a "physical controller/hotas" is not "virtual reality" in its purest sense, now is it. To suggest otherwise, is dumb. Back at ya. :smilewink: Neither is using a Touch controller, so I'll give you that. More reason why some kind of glove, that becomes part of your body, is needed to be true vr in the cockpit, so you can better manipulate a virtual flight stick. Hence my suggestion to look at Vtol Vr, it's getting close. Yes, you need some kind of "external control" to manipulate things in the vr world, I get that, but my ultimate vr is using "some device" attached to my hand, or better yet a full body suit, but not a physical hotas, yoke, steering wheel, you get the point. You may not agree, but that's kinda moot to me. You enjoy what you currently have, that's great, I hope vr goes that step further. Is it a ways down the road yet, years, sure maybe, but we can all dream. I'm certainly not arguing that what we have today is the answer, far from it, but I certainly don't want it to stop developing, leaving us dependant on physical controllers, like a hotas. Read some of the reviews for Vtol Vr over at Steam (or better yet try it yourself) , most of those people "get it". It's the closest thing to a real vr experience we have today in flight sims, others are somewhat behind to say the least.

Doesn't seem dead to me, perhaps just the "Rift 2"? New and improved maybe, "Rift S"? https://www.google.ca/amp/s/techcrunch.com/2018/10/31/after-canceling-rift-2-overhaul-oculus-plans-a-modest-update-to-flagship-vr-headset/amp/ https://www.google.ca/amp/s/venturebeat.com/2018/11/01/oculus-reportedly-plans-rift-s-a-small-pc-vr-upgrade-thats-not-rift-2/amp/

I wouldn't say it totally breaks immersion, I still use my hotas, and yoke, at times, depending of course on what I'm flying. I just think "in the future", and that could be a long way off for mainstream simulators, it would be cool to not have to rely on anything other than "our hands" in a virtual cockpit. Like the way its done in Vtol Vr, which if you haven't tried, you need to have a look at. That's implemented really well, but certainly does not have the complexity of Dcs, but fun just the same.

"Trust me"... No thanks, that's why we're here looking for a better way, for us, which we have suggested. Better yet, as we've suggested, give multiple options. Doesn't that make more sense than, "my daddy is bigger than your daddy, so I'm right", just saying, and I'm sure you know what I mean. The reasons we've given why the current options are poor at best, are just as valid as anyone else's argument. There is a way to make all users happy. Make the change, give us multiple options, we're happy, your happy, everyone gets to play the way they want, and move on. :thumbup: I have zero desire to manipulate the cockpit the way you do, and vice versa, so give users the options, simple. Nobody is asking for "your style" of play to be removed.

In the vr settings there's 2 options offered for how the controllers interact, not on my computer at the moment so not sure of the exact names, but I choose the "ergonomic" option. It allows you to manipulate the yoke with your hand "anywhere" you like, so I rest my hand on my leg, and only need to "tilt" the controller slightly up, down, left, and right. I don't need to keep my hand suspended in air attached to the yoke. It takes getting used to of course, but I find it works quite well. Just need to be gentle with the movements, no heavy hands. :) Is it perfect, no, far from it, but with practice it gets easier. I look at it this way, I want a "complete" Vr experience. The only way to do that is "use your hands" in the cockpit, so I give it my best shot. I can takeoff and land, they may not be perfect, or, "by the book", but I get down in one piece, and that's all that really matters at this stage of "early" Vr development to me. The fact that I'm able to do anything in vr, fly, drive, cause mayhem in a fps, travel in space, is a life long dream for someone pushing 60, so I feel very lucky to have a chance to experience vr at all.