Muskoka

I fully agree, that's the "programming" direction all sims should be heading/leaning towards in the future, if they're interested in offering a true Vr experience. The problem is there's no suitable "hand controllers" available yet, for Dcs use. Yes, the touch controllers work great in X-Plane, and Flyinsides new sim, but those simulators aren't as demanding in "reaction time" as Dcs. You can't be "fiddling" around in the Dcs cockpit, the interactions with dials, and switches, needs to be accurate, precise, and fast, or your dead. :) And whatever you end up using for interaction, it has to work with everything in that cockpit, meaning, you can't be using "something" to manipulate the stick, and "something else" for dials and switches. Everything in front of you "needs" to be manipulated with one controller, other than rudder of course. I do very much look forward to the day that I can perhaps put on a pair of gloves, or something similar, that will allow me to "completely" control the aircraft in the Vr world. No mouse, no hotas, just my hands, a set of rudder pedals, and a mic for voice interaction. Looks like there's some offerings in the near future, I hope they work as well as projected/expectations. And I'll add, they need to be affordable (gloves for example) , not the ridiculous price some are asking.

Yes, if it's even possible? Give everyone the option(s) that best suits their own needs, styles of game play.

Latest DCS version here, doesn't work that way at my end. Yes, you missed the point we're trying to convey. Mouse option not selected in Vr settings, your head moves the mouse cursor, and your hand on the physical mouse has no affect on the cursor. Bad, because I have to stare directly at what I want to adjust, no peripheral view adjustments. Mouse option selected in Vr settings, yes, your hand can move the mouse cursor, great, but so does your head movement, still. Again, bad because of reason given above. It forces you to stare at what you want to adjust, or at minimum, don't move your head a millimeter because it will "pull" the cursor away from what you want to adjust. So, yes, in this mode there is "some peripheral" adjustment allowed, but only if you keep your head completely still, not real world at all. We don't want the mouse moving at all with head tracking / movement. I'll decide where the mouse cursor goes with my hand controlling the physical mouse, not my eyes in any way, shape, or form. It's not natural in it's current offerings. With the option on, yes I can move the cursor to a switch with my hand, but my head is still "tied/coupled" to that mouse, and any slight movement of my head, and the cursor is off what I want to adjust. Hence, why, "the mouse", needs to be uncoupled from "your eyes", at all times. If they can make that an option for users that like, and, or dislike that feature, then great. But currently, "both options" move the mouse cursor with head movement, bad. So in reality, there needs to be 3 options I guess. 1. Eyes/head movement moves the mouse cursor, no mouse hand control at all, other than manipulation of switches/dials. Current option not selected. 2. Eyes/head movement, and hand, moves the mouse cursor together, or independently. Current option when selected. 3. Eyes/head movement have no control of the mouse ever, only your hand movements control the mouse. What we're looking for I believe (?, I don't speak for the others here), at least I am. This option is currently not available.

Sure, that would be great.

The "big deal" is it's "not natural" to have your hand "forced" to go where your eyes are "directly looking" , as has been pointed out by a few here already. It ruins the vr experience. You should be able to adjust things in the cockpit using your peripheral vision, just like in the real world. And most certainly, not be forced to stare at something to make adjustments to a dial, or flip a switch, that's ridiculous . It's not really hard to comprehend, to see the problem, it's simply a very poor implemention of mouse control / cockpit interaction. I suppose if someone has the whole cockpit assigned to hotas buttons, then it's not an issue. But who wants to do that when flying in vr, certainly not me. Vr is about immersion, the freedom to look around, and interact with your surroundings, just as you would in the real world. This issue, takes part of that experience away. Besides, one of the most important aspects of flying is situational awareness, and the second I'm forced to "loose focus", because I have to "stare" at something just so my hands can make adjustments, is a step backwards, not forwards. Just free the mouse from your eyes, and everything will be right in the world again.:smilewink:

It really ruins part of the vr experience. What's been implemented is "not natural" at all. Your hands are not forced to follow what's directly in front of your eyes in the real world, so why do it here? I can manipulate "things" in my peripheral view in the real world, without needing to be looking directly at something, allow the same here. Your diminishing the experience by locking our hands to our eyes. The mouse, "your hand" should not be connected to the eyes in anyway. In some cockpits it makes it very difficult to get at some switches/dials at your sides, because you really have to "crane/twist" your head/neck to get your eyes looking directly at them, it's actually annoying. If you could just look in that general direction and make adjustments, that would be the natural way of doing things. Now I have to reset my view in the headset, push myself back in the seat, further than what you'd do in the real seat, just to get at some things in the cockpit, makes no sense.

It is horrible, I don't know of a "fix". If this is a feature it really needs to go.

Agree, I don't notice it either. I'd have to stop "doing what I'm doing", and look for it, to even "notice" it's there.

What's your point/message? That means, and conveys nothing to me. That's why I say the manual is confusing to read. Where does that say that the L39 "has" to have radio presets set in the mission editor for communications to work? For a newcomer, or casual user of DCS, the way Vaicom is advertised/presented in the manual, you basically install the plugin in VA, make some configuration changes based on your needs, setup PTT, get in your aircraft, and all communications will just work. It assumes everyone knows how to use the mission editor, or cares to, and that every mission available by default in Dcs will just work with every aircraft, and that's simply not the case. What you quoted above does not address clearly that aircraft like the L39 "must have" radio presets programmed in the mission editor, or communication with "Atc" is not possible in this aircraft. I've nothing more to say on this, my points been made. Hopefully this discussion may help some newcomers, or someone who has no interest in mission editing, that get frustrated with Vaicom, and give up. Reading back through this forum group would indicate that this has happened on more than a few occasions. It was only through my own persistence, and spending a week reading everything I could from the Dcs forums, that the light bulb went off, and I finally figured out what was required to get Vaicom to work with the L39, through mission editing. It certainly wasn't as easy as install the plugin, jump in a default mission, and go.

And just to prove to myself, not that I need it at this point, I just created a simple free flight mission from Nellis without me manually changing any preset frequencies in the mission editor, and got no response from atc for "Request Engine Start". Go back to the editor, put 132.55 in the first preset, and the atc respond immediately to my "Request Engine Start". Maybe that will give you some clue as to what's wrong at my end, or how I have things improperly setup? Edit: Your message went in as I was typing this reply, yes I seem to have to define the radio presets in the L39C or atc response is very hit and miss. If I put them in, it just works. So, the way I'm doing it for the L39C is correct, and not the norm for "some" other DCS aircraft? If that's the case, that's fine, at least I know for the future. I don't recall seeing anywhere in the VaicomPro manual, that mission editing may need to be done differently for certain aircraft modules in DCS, for it to function properly. If it were in the manual, with perhaps an example, it may have saved me many hours of unnecessary frustration, and hair pulling. Just a suggestion of course.

Sorry to say it doesn't work as described at my end. I've been flying sims for a lot of years, and was a atc controller on Vatsim for awhile, so please don't assume you know anything about my level of atc flow intelligence.:smilewink: I'll admit, my knowledge of DCS, and it's inner workings is lacking, but not flows, or how to fly aircraft in general. Now that's out of the way. If I don't fill in the "Radio Presets" for the airports in the mission editor, I get nothing but crickets, or it's very hit and miss at best. Once I fill those in manually, the atc work exactly as they should, and I would expect. So, something isn't working/setup properly still at my end, and I have no idea why. I just finished a fuel tanker rocket bombing mission I created this morning, and everything worked great, including the atc. If I remove the "Radio Presets" in the mission editor, I can sit there all day long asking "Request Engine Start" at Nellis, and I get zero response from atc. Put them back in, and the atc respond immediately. Please explain why that might happen. Nothing has changed in the "atc flow", or the way the radio is used, only in the way the mission is setup. This is in the L39C, Nevada map, Easy Communications on. I'm using one PTT button on my Hotas, and currently using Tx4 "Auto", but have also tried with Tx1. I want to use one button only for all communications, ground or atc, and have no desire to set the radio frequencies myself, at least not today, maybe tomorrow. I've also tried with the rotary switch in Norm, and SNGL mode. I find the manual "very confusing", so please tell me how I can setup the L39C to fly the Nevada map, only using one button on my Hotas, for all forms of communications. I will only fly in VR, so some form of keyboard less communication is what I need. I'm still hoping VaicomPro is the answer. Edit: If it sounds like I'm irritated, you'd be correct. I've been working at this for hours a day, for the last week. Luckily I'm retired and have the time. I had no problems at all getting HCS Voicepacks setup for Elite Dangerous, or any other plugins I have for VA, yet this has turned into a nightmare, sorry to have to say that.

In the end I think it was my lack of understanding of the convoluted atc and radio systems in Dcs, more than anything else. I have always been just a casual user of Dcs, jump in and fly around. I spent far more time, and many years, in "other" flight sims. I didn't realize that the end user had to "setup" the whole atc system for every "flight/mission". As in other sims, you get in a aircraft, any aircraft, tune your radios, and away you go. Doesn't matter which aircraft, they all recognize the underlying atc network of the simulator without any input required from the user, not so in Dcs. That's my fault for not having/obtaining the required knowledge. So, I had expected VaicomPro to be just a tool to simplify my interaction with a already present atc system, in every aircraft, for every flight/mission, and I was wrong. You, the user, still have to setup the atc system every mission, manually, with no option for "saving presets", not that I can see. I'd bet that 90% of the posts in here for people wondering why atc isn't responding to their requests properly, is because the mission itself doesn't have the proper atc info in it. On the other hand, if VaicomPro is supposed to magically know what atc frequencies to use, in every mission, in whichever aircraft you choose, it's not working that way at my end. The only way I can communicate with atc at every airport on a map, is for me to setup the atc system manually, in the mission editor, for every single mission. Seems to be a rather poor implementation of a atc system to me, just my opinion. I get that every "mission" is unique, but underlying atc systems are not. Airports have frequencies that seldom ever change, so you should be able to create a mission, and have the underlying atc system automatically implemented, without any user input. Once in the aircraft, tune your radios accordingly using that aircrafts systems, to a atc system that already exists. Can't that be implemented somehow on a per "module/map" basis. Why do I have to tell the mission editor "everytime", what the atc frequencies are, for every airport on the map. Something like that should already be "baked/programmed" in. Rant over.....

Would someone kindly explain how I can setup a "simple free flight" mission so I can practice flying / landing from Nellis to Creech on the Nevada map, and most importantly "have" atc work at both ends. Right now I'm taking off from Nellis and have atc, but at the Creech end there is crickets. The request is going through properly, just no response. They are both blue coalition. All lua files are in place, and worked fine yesterday with a mission I created, that no longer seems to have atc at both ends. Think I have it figured out now, first "new" test to Creech was a success.

Decided to purchase the P51D today, and now the atc are no longer responding at destination airports in the mission I created yesterday. Nothing has changed in that mission, I'm still flying the same aircraft as yesterday, L39C, all I did was purchase/install another aircraft module for future use. This is really getting frustrating.

Not having any luck at all with Atc in Nevada. I've tried with "Instant Action", and "Create Fast Mission", and I never get any response from Atc. This is in the L39C, DCS latest. Actually, in some of the Instant Action missions atc works, in others it doesn't. Now I need to look at the missions and find out why. Ok, got it figured out. Created my own mission for Nevada, with parameters that work. Have ground, and atc working from Nellis. Still learning.:) Didn't have luck at the destination airport though, no interaction with atc at all. It "picked" the correct airport, but there was no response to repeated requests for directions to final, or requests for landing. Figured it out, just had to make the destination airport the same as me, and the departure airport, color "blue", when setting up the mission. All good after that.

Thank you for getting in touch. I tried responding in pm, doesn't look like my message went through as far as I can tell. Before I do what you suggested in pm, I have some questions. I just spent the whole day re-downloading and installing DCS, and all my modules (75 gb), so the registry entries in Windows 10 would at least be correct, for this install. Having moved my original, and subsequent installs numerous times, the registry for DCS was a mess, still is for those installs. So I still have multiple entries in the registry, but at least one of them is correct. None are OpenBeta, (see below). I have fired up the new install, and everything looks fine. I then started up Voice Attack, and the VA window log says it found DCS in the new location, great, but the saved games folder is incorrect. The new one does exist as I created a variant text file in DCS World root, my new install. How do I tell Vaicom where my new saved games folder is? I want one save folder for the old install, one for the new. I'm also seeing a reference in the log, same as before, stating "DCS World version 2.5 OpenBeta not found". Why is it even looking for that, when it already says it found the new directory where DCS is currently installed under "DCS World" on my G drive? There is no reference to the OpenBeta anywhere in my registry for DCS, that I know for sure. Because the log is saying it found one location that is correct, and continues to look for one that doesn't even exist, OpenBeta, do I need to tell the config utility where the parent folder is? Also, do I still need to do the export lua thing on page 33, if I tell it where the parent folder is? It seems to have figured that out, but the saves folder is still wrong in the log. Should I be removing Vaicom from VA, and starting fresh with it as well? I also tried by removing the "old" saved game folder, leaving the new one, just to test. Vaicom just keeps recreating the folder when starting VA, and placing a Scripts folder inside it. Started from scratch with Voice Attack, it's still looking at the wrong saved games folder according to the log. Guess I can't go any further until I hear how to get Vaicom to look at the correct saved games folder. Edit: Went with the saved games folder it was looking for. Seems to be working. Guess I need to learn more about DCS as far as radios go. Depending on what I loaded, Instant action, a mission, or a mission I created, I would get ground ok but no atc, or atc with no ground, or nothing on some. Edit2: All seems well, did a flight from Beslan to Batumi in the L39C and had no real issues with ATC. Need to work on the pronunciations some, but it all worked out in the end. Edit 3: Can't get atc anywhere on the Nevada map, but works fine with Caucasus and Normandy maps.

Still not there yet. Don't have any problem communicating with ground crews, but ATC is a no go, at all airports, on any map. Requests are being displayed correctly in VA, and in game ("Request Departure", or "Nearest Airfield....Directions to final" for example) but I never get any response back from ATC. Suggestions? I've read all the threads here, as well as the manual multiple times, nothing gives a answer as to why ground works, but atc doesn't. If one is capable of understanding, and reading back, why isn't the other? Here's the log from the VA window. Ground connects the power as they should, ATC does not respond. I've done the edit's from page 33 of the manual. I've managed to get to a place that has better internet than me (unlimited data) , doing another install of Dcs. Will see how that goes. It's still not the default install location, I can't, not enough space on drive c.

Well, out of nowhere it has started to work, I think. The log now shows it's found DCS, and then a few lines later it says it can't find it, whatever. The only thing I did was select the option "Auto-import new modules" in the config utility, and now the aircraft names are showing on the PTT screen. I've yet to try anything else, but that seems positive. I don't see anywhere in the manual that indicates this is a "required step" for initial install functionality. Perhaps because my install is not standard, the database wasn't created properly in the beginning, and selecting this triggered something? Edit: Seems fine so far, loaded the P51, asked for ground power, and it worked fine.

I get that, and I've now read every post in this thread, some multiple times, as well as the manual. I can see I'm not the first to have issues. I've no interest in creating symbolic links, just so this will operate properly. I do use them for my Xplane scenery, over multiple instances of Xplane, and it works great. But that's only to save space. I don't need this that bad, I'm just a casual DCS user. So it is what it is, and that's fine. I will seek out other options privately. Thanks to all for trying to help.

Thanks for the response, and you're correct, it's not what I wanted to hear.:) On limited internet as it is, so a re-install of DCS is not an option, and quite frankly, totally unnecessary. I find it hard to believe this has to be this difficult. There must be "a lot"? of people out there that move DCS around as they see fit after initial install, as that is a feature of the program. To think this would rely on a registry entry for install, considering the portability of DCS, makes no sense to me, I guess it does the author. I've again tried setting the parent folder path in the config utility, and it appears to just ignore the entry, and continues to look at the registry entries that do point to drive "G". DCS is currently on my "D" drive, there's no DCS on any other drive. This is quickly becoming "not worth the effort", and if possible, I may ask for a refund, if my keys for the program and chatter can somehow be "invalidated". I do appreciate you taking the time to respond.

That install is only openalpha in "folder" name only, the actual version I'm running is 2.5.3.22176 Release, and it's currently on my G drive, it's never been on C. It's also been moved to different drives numerous times, so the windows registry will not have the correct information, I've verified that by looking through the registry. I use the Updater Utility by Skatezilla. This install has been both Release, and Beta. I have no idea why the folder is still named alpha. I ran a alpha version, versions ago. Naming seems to not matter to DCS, it runs great, updates, cleans, and repairs just fine. No problems with modules either. I've pretty much read this whole thread, and it's the reason I'm here. I've read the manual, and specifically the stuff on page 33, and it makes no sense to me at all. I don't understand what your trying to do with the lua files. Simply put, the logs show Vaicom is looking in the wrong place for the DCS install. How do I correct that? I've tried changing the parent folder, no change. I don't understand the "instructions" on page 33, so at this point I'm at a loss as to what to do. Re-install of DCS seems a bit much, just to "sort out" the windows registry entries. Chatter is working fine, but the config utility never lists the name of the aircraft I'm using. I have PTT setup, and it's working, but the commands I speak don't appear to have any effect in DCS. They are being recognized by VA fine. How do I "point" Vaicom to the current location of DCS on my system? And, if I decide to physically move the DCS folder again, how do I manage that in Vaicom, basically the same question. The lua files mentioned on page 33 already exist, but in different locations of course to the manual, so I'm not sure why, or if, they need to be edited/appended in some way? When I export the files in the config utility, the export.lua script for example is exactly the same as the one that already exists in saved games, so appending that file makes no sense to me, the contents are identical. Hopefully someone will shed some light on how to correct the install issue.

I've watched a few, the 17 minute video for VaicomPro 2.5 intro tutorial doesn't help at all with the issues I'm currently having. I wish it were that simple, and I was flying instead of seeking assistance.

Just getting back into Dcs after an extended break, thought I'd buy Vaicom Pro today, and I'm not having much luck getting anything up and running. Very much familiar with VA from too much time spent in ED with HCS Voicepacks, but a complete noob to Vaicom. I'm noticing when I run the configuration utility, there's no aircraft listed in the window, it just says "Easy Communication On". Here's a screenshot of my saved games. The game save is the DCS.openalpha folder, and the Dcs folder has the Vaicom stuff in it. Is that a problem, before I start digging any further? Here's the VA window, I can see that the saves isn't correct? The rest I have no clue about. I've read page 33 of the manual for a manual install, as my install is not standard, and for the life of me I don't understand what to do. In steps 3 and 5 those folders do not exist on my system, not those locations, and it doesn't say to change to "your install" location, hence the confusion. I've also tried changing the parent folder in the configuration utility, that didn't do a thing. The logs still show it looking for a "very old" install location in the registry, which makes no sense for a program that can be freely moved at will to any location/drive you like.

Agree, this needs to be changed, somehow.