Shimmergloom667

You guys got Jester tuned on AM or FM?

In the Mission Editor I can set the CM loadout of the Mirage to 112 / 48 *without* an Éclair pod equipped (where it should be 112 / 16). With an Éclair the maximum flare loadout should be 40, for a total of 112 / 40 (or combination thereof). I found a few similar, old bug reports, but nothing point out this exactly, if I am not mistaken.

HB already has acknowledged pretty much all of these to be fixed during EA

Yes, still present on open beta 2.5.4.29585

See topic: both AI and player F-14B models show up as "UKN" on RWR, where it should be a "14".

Just grabbed it in the spring sale, can confirm: Radar Altimeter frame drop from ~80 to ~25 after a long mission still present in open beta 2.5.4.29585. Disabling radar altimeter instantly brings FPS back.

Awesome, thanks a lot!!

Wait, what - do I understand that correctly, that there won't ever be an option to use both the Jester Menu Wheel through it's hotkey *and* AI RIO? That's a shame and a few bucks wasted, for that is not usable for me. Still, thanks for the great work. :cry:

Yeah, but he shopped it up to 21:9, which is beyond my skills :megalol:

Think you could upload the source file without your menu over it? :)

Man, I *knew* I had seen that thread! Thanks, buddy! :)

So, uhm - I just grabbed me an Acer Predator X34P, and while I was fine with the F-14 title background pic on my old 24" Dell 16:10, it now looks like ass. Any of you guys got neat ultrawide F-14 pics lying around, by chance? :) Much appreciated!

That's DCS AI right there - the wingmen in every module are pretty clueless on how to keep formation without a weirdly binary throttle setting, IMHO.

Why are you yelling, pls stahp

Spent several hours flying as both Pilot and RIO w/o issue yesterday.

The scan mode is still there (as in: the Sidewinder sensor head still moving), just the diamond on the HUD is not moving. Working as intended, fixed in one of the last Hotfixes.

Hey Hollywood! Things finally settled down yesterday with all keybindings intact and the AI RIO working. While you have done a fantastic job again, I really feel the need to emphasize once more that an option for both AI RIO and the Jester Wheel is, IMHO, sorely needed. While VAICOM works very well for me and me being rather fluent in english, I am still no native speaker and from time to time voice recognition will fail me. Even with lots of training and custum recorded pronunciations it will still happen, trust me on that. With the regular comms menus this is not too bad - on one hand, it's mostly stuff you don't need *right now* in a heated combat situation, on the other hand I am still able to keep the regular comms menus bound to my keyboard as a backup for those situations where voice recognition fails. With the AI RIO, both the importance of voice commands as well as the possible problems of a failed voice recognition rise proportionally, and failing to have Jester perform essential tasks in A-A combat will be felt. On top of that I am not a big fan of the "Select" function in Vaicom. This may be subjective, so please take that with a grain of salt, but I am a friend of turning dials to tune in an ATC etc., and not just tell my plane to do something which it can't in real life. Similar situation with Jester: I want to be able to tell him which frequency to punch in manually, not just select something. Also, and here is my non-native-speaker problem again: my pronunciation of ATC names of the Caucasus region vastly differs from what voice recognition expects. In conclusion: while I understand it from reasons of immersion, I feel the Jester Menu Wheel is sorely needed as an *option*, and at a high priority. Please find attached this link to the DCS facebook group, where a similar thread is forming with another few people issuing similar concerns: https://www.facebook.com/groups/DigitalCombatSimulator/permalink/2021552227970784/ All that said: thanks for a phenomenal addon to DCS, I really love Vaicom and hope to be able to use it much more in the future! :)

After a few restarts it seems to be running w/o issue on my X56, can confirm though that the Warthog of my aforementioned buddy suffers the same problem that metzger has. It is entirely reproducable: as soon as VoiceAttack runs, starting up DCS afterwards messes up Warthog bindings (vaicom 2.5.9.4, VA 1.7.3)

After shutting down VoiceAttack and repairing DCS, the Input Categories are back. Turning Voice Attack back on also damages the input categories again.

Can confirm having problems - I now have strange problems, too: - shut down DCS & VoiceAttack - started VA as admin, updated vaicom to 2.5.9.4, shut down VA, restarted VA -> 2.5.9.4 confirmed - downloaded and installed AI RIO dll according to manual - started VA, activated AI RIO license, did NOT YET enable AI RIO extension - started DCS -> several Categories of Keybindings in F-14 module missing (e.g. "Stick", "Throttle"), see attached screenshot - shutting down VA and repairing DCS brings back categories

So far he didn't buy the AIRIO plugin, that's why he didn't enable AIRIO in EX yet. What happened so far: - start VA - auto-update vaicom to 2.5.9.4 - started DCS for the first time -> all keybindings gone (yes, with 2.5.9.4 already) - shutdown DCS & VA, repair DCS, restart DCS - standard keybinds are back - shut down DCS - start VA with 2.5.9.4 - start DCS -> all keybindings gone So you say even without RIO addin you should enable AIRIO in Ex?

So, a buddy of mine still loses all his keybinds as soon as he starts VoiceAttack with VAICOM 2.5.9.4 - any idea what to do? As soon as he deactivates VoiceAttack and repairs DCS / restores his binds all is back, so we can reproduce it atm. Is there a possibility to back up Vaicom settings for a possible reinstall? How do you actually go for a clean reinstall?

Thanks for the RIO module, instantly bought it even before reading the manual, that said: you say that Jester Menu Wheel and your Plugin are mutually exclusive. Any chance that may be added (back?) in at a later date? I really like the Menu Wheel and would love to have it as an alternative / a backup when voice recognition fails. Thanks a lot! :)

If you turn the Landing Gear lever, you are engaging emergency gear down. This depressurizes a nitrogen container to put out the landing gear in case of a hydraulics loss. Unfortunately NWS won't work afterwards and it can't be repaired on ground (yet), so you will have to restart. Better yet: don't touch the landing gear lever.

He never, ever closed the canopy for us in assisted start, he's always asking me to do it. And I've done a lot of assisted startups. :D