sthompson

Those two campaigns avoid the issue rather than "taking care of" it, and the fact that they felt compelled to do so shows that it really is a problem. (Their approach won't work for multiplayer in any event.) As for the rest of your post, you seem to miss that many of the people asking for some help HAVE spent a lot of time trying to learn it, DO want to learn, but have not been successful. It's really arrogant to argue that other people shouldn't have something just because you and others don't need it.

Well said. I think I will start a wishlist item asking them to stop working on the Viper so that they can focus on my pet wishes. If you don't like the Viper as is, just don't use it. Problem solved.

No one is asking for anything remotely close to that. All I want is an option for better visual cues about where the "thing" is that I need to hit, with mission planners having the ability to choose whether to permit that option or not just as they do for other options such as wake turbulence. All it would require is limiting the basket's movement a bit and perhaps enlarge a bit the region where it snaps to the probe to make the hookup a bit more forgiving. I doubt if that requires more than a tweak to parameters already in the tanker code with no changes at all to the flyable modules. And to those who say I am ignoring the complexity and resources needed to implement something I say you don't know that is true any more than I do. Only the developers can answer that question, and it isn't the purpose of a wish list to set priorities for their efforts based on the unknown to us difficulty of implementation. I realize that the OP asked for an "auto" mode option. That's not what I want, but apparently some think that it's not OK to contemplate any changes at all that would give struggling customers some help. There have been reasonable arguments for something less extreme as an OPTION. Perhaps we could focus the discussion on what would best help people overcome their limitations without going all the way to making it a pushbutton process. Advice to "practice more" doesn't cut it for many of us. Think about this: The most common advice given for how to successfully AAR in DCS is to ignore the basket and fly the picture. Is that really how the military trains? I doubt it. Is it realistic to have the basket and hose slice through your aircraft when you miss with no damage? Obviously not. And I'd be very surprised if the military would let people who can't do AAR continue to fly. Perhaps we should ban people from certain aircraft if they can't demonstrate realistic proficiency within XX hours? Or a permanent ban from flying DCS if you crash and die. That would be realistic. I just don't buy the argument that it's realistic now. I suspect it is harder than in RL in some respects and easier in others.

So you think that flying a long mission with a fixed load of 10% or 50% or 100% fuel is the same experience (apart from the actual AAR) as doing AAR (with assistance or not) and then having to worry about your weight and fuel consumption? Obviously not. Unlimited fuel totally changes the mission. Furthermore, it would have to be permitted in the mission design. That pretty much rules out most MP play as well as any mission where you do not want to peek at the mission details in the editor before flying. As for being inconsistent with the "study sim" mentality, I get that. But consider that right now mission designers can already choose to allow or not allow game modes, radio assists, tooltips, crash recovery, easy comms, padlock, unlimited fuel, unlimited weapons, immortality, unrestricted sat nav, labels, choice of avionics language, external views, various unrealistic F10 views, no wake turbulence, no birds, perfect weather, and no random failures. So there are already lots of options for permitting or not various levels of realism depending on who you are trying to please in your mission design. Adding AAR assist to that list is unlikely to change the overall experience in any big way and just might reduce frustration for some of us. I personally have been flying ED products since the Flanker 1.0 days, have purchased all of the modules (except the JF-17), almost all of the DLC campaigns, and all of the maps. So I'm pretty much the ideal ED customer from a revenue standpoint. I fly for many hours each week, and try to work in some serious AAR practice (i.e. 3-4 hours) every few weeks. I've studied all the manuals, watched all of the AAR videos, and try to fly as realistically as I can. I have decent CH HOTAS that works fine for everything I do except AAR. But I have never caught the basket even once. It's a major source of frustration. My failures are not due to insufficient "study." Perhaps my HOTAS or computer isn't good enough or perhaps I'm not good enough despite practice. I'm not going to invest additional $1,000s in hardware to find out. BTW, good luck getting developers to start putting warnings on their campaigns that say "this is very hard and you might fail." That's not going to happen even if it should.

Unlimited fuel totally changes the experience since you then carry it around for the entire mission. It's not a close substitute. Plus not an option for missions you can't edit.

I disagree. It seems that of those who voted more people want ED to put their development resources elsewhere. That's not the same thing as "not wanting this option." If ED thinks that a poll on the forum is a good way of analyzing user wants and needs then they need to sign up for a remedial class in how to do a marketing survey. People who happen to read that thread are not a representative sample of users and the poll is of questionable value. Personally, my inability to do AAR after more than 100 hours of trying with not one single successful hookup is a major factor keeping me from enjoying DCS more. And yes, I've watched all of the videos and have HOTAS that works just fine for everything else.

See Hollywood's suggestion in this thread: https://forums.eagle.ru/topic/254389-per-aircraft-ptt-buttons/?tab=comments#comment-4505760. Also Weegie has posted some good ideas about this recently, but I'm having trouble finding them. You might do a search in the VAICOM forum. (This thread is no longer the main place for such discussions.)

It could be related to the "SRS PTT Mapping" option in VAICOM even if you don't have SRS. I found that toggling this changes the radio assignments to TX nodes. With that turned off I'm getting the correct mappings in the Tomcat. Caveat: I tested this in the 14B. Is the issue only in the 14A?

https://forums.eagle.ru/topic/257727-happy-new-year/

There was a very recent change in SRS that might be causing this if you have SRS PTT Mapping enabled. I find that I get a reversal of TX1 and TX2 in the Tomcat when this is enabled. Try unchecking it on the MP tab or using the button on the PTT tab.

It doesn't do either of those things. It changes the radio frequency as if you entered a manual frequency. However, neither the UFCP nor the radio panel show any changes. And if I reselect the displayed preset channel it reverts to the original frequency, so the presets are unchanged. To be clear, if instead of using VAICOM I tune a frequency manually using the radio panel the manually tuned frequency does not display on the UFCP. Perhaps that is a feature of the real plane. However with manual tuning I can see the actually tuned frequency by glancing at the radio panel on the left hand side of the cockpit. But when VAICOM PRO changes the radio tuning that radio panel displays the old preset or previously tuned manual frequency as if nothing has changed. Ideally using VAICOM PRO a new preset channel would be selected and displayed, or a new manual tuning would occur and be displayed if the desired frequency does not correspond to a preset.

I don't fly VR but use TrackIR instead, but use the same trick. There is no return to "normal view" because the new view with your head naturally a bit further back is more normal than the "normal" one that implicitly has you leaning in all the time. The downside is that this changes your perspective on the instruments and HUD, and possibly you won't like the new view as much. But I don't think there is any way to quickly toggle between two default view positions. That's presumably why the OP was asking about snap views in the first place.

Short answer: Do exactly what it says in the pop up. Longer answer: There is more detail about the Finish step in the manual. In the current version it is on page 36. (Aside: Various places in the manual tell you to look for it on the wrong page.) Detailed answer: In your case you do not have "multipart commands" consolidated in your profile and instead are displaying each keyword as a separate line. So in the profile screen (right side of your screenshot) you first need to click the icon just to the right of the "Import Commands" box in the lower left corner. It currently appears as three horizontal lines each preceded by a dot. This will change the icon to just one line preceded by a dot, and will cause all of the "AI Communications" multipart command parts (each is a single keyword) to appear in one line rather than as separate lines. Then do the things in the popup. That is, double-click on the "AI Communications" command to open it. (It's the line directly below "Keyword Collections" that has a long list of keywords.) Within this command, highlight and delete everything on the "when I say" line, and then paste in the contents of clipboard, which will hold the new keyword list. Finally, click OK to save the new version of that command, and then "Done" to save the changes to your profile.

@Gorlow, you have quite a few VoiceAttack plugins all running at once according to the log. Have you tried removing all of them except for VAICOM? Perhaps there is a conflict. You might also turn on VAICOM's debug mode and restart to look for additional cues. Also, VAICOM PRO saves a log file (not the same as the VoiceAttack log) in folder C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Logs. There might be additional clues there. Finally, do you have this problem with the stock VAICOM PRO profile? It appears that your profile includes kneeboard commands activated by the joystick, so I assume it is not stock.

I think this must have changed. Tonight I had datalink and Tacan going at once on a MP server. However the TACAN option on the HSD page was not visible while datalink was active. I had datalink active and then tried turning on Tacan from the Tacan page. It seemed to go active, but the Tacan option was not visible on the HSD. When I turned off datalink the Tacan option became available. I selected it. TACAN cues displayed on the HSD. I then turned data link back on. The TACAN info continued to be displayed on the HSD. So I then had TACAN cues on the HSD and datalink at the same time.

I use VAICOM PRO a lot. I can use it to tune the radio with my voice, for example. However in the the JF-17 changes in radio tuning made using VAICOM PRO do not show up in the UFCP display. I can confirm that the radio tuning did change, since the tuned recipient responds. The new frequency also shows up in the SRS overlay. But the UFCP display remains out of synch with actual tuning until I change the tuning manually.

I'm trying the JF-17 in the current free-to-fly period and liking it very much. Except for the VAICOM integration. I'm having the following troubles and wondering if I'm alone: When I use "Select Tunes Radio" a select command does tune the radio, as verified by successful transmission to ATC. The frequency also shows on the SRS overlay. However the displayed channel in the cockpit does not change. I assume this is a problem with the module, not with VAICOM. It would be nice to get the cockpit display working to show the actual tuning. VAICOM' does not play nicely when SRS PTT Mapping is enabled. Symptoms include: No frequency displayed in the VAICOM window when transmitting. Only TX1 is available as a PTT even though SRS is supporting both of the module radios plus an expansion radio. No TX nodes are available at all unless the PTT switch is set to NORML or SNGL.

I also wish they were easier to find and that a collection of links to installed manuals were available somewhere. However I suggest that the place for this is not the main GUI interface. When I want to review a manual while flying I do not want to exit the mission just to open a manual. A "DCS Documentation" subfolder of the Eagle Dynamics start menu folder seems like a better place for these links. I actually keep such a folder handy already, but it needs a lot of manual updating. Alternatively there could be an entry on the Escape key menu (similar to the one for adjusting controls) that would let you open a manual from a paused game.

Yes, I do see something weird. You have the DCS install paths (both stable and openbeta) pointing to Saved Games. Is that where your installed copy of DCS lives? Usually it lives in Program Files or in a separate directory tree.

Turn on debug mode, restart VAICOM, then post your log file here so we can see if there are any issues on startup.

Where can I find that mod?

Any chance you could post the full update list? There is no news in the I-16 forum and I don't know where to find the announcement that you partially copied. I hope they finally give us a radio and kneeboard. Those are long overdue.

We had autodetect before this change. The only difference is that you can now trigger it while the game is running rather than just having it work once at startup.

The question was what you need to do after a DCS update, not a VAICOM update. After a DCS update you definitely need to restart VAICOM with DCS not running, and only then start DCS again. That lets VAICOM update the DCS lua files that may have been reset when DCS updated. You may or may not need to also delete export.lua first. I find that isn't necessary on my installation, and I've been puzzled why it is recommended so often. It only helps if the file was not set up correctly in the first place.

Does SRS work for you in the F-14 when VoiceAttack is not running? It sounds more like an SRS problem than a VAICOMPRO problem if it works in some modules but not others.