flyingflatfour

I pretty much tried every fix that I could find but I'll have a look at your link above ;-)

that's exactly what doesn't want to start

Well I just discovered that it does... as I perform the check-in call to the SuperCarrier, as soon as I say "marking moms" I hear the beep sound in the background and the command is sent to DCS. Indeed the SC responds when I am still talking (fuel state)

By the way, is there an option to tell Vaicom to wait until you release the PTT to send the commands to DCS?

Hi everyone, I've had some help in the VA discord channel. Turns out I had chosen the option "use installed speech platform speech engines" under the VA "system/Advanced" options tab. This is I guess because back when I installed VA for the first time, having a french version of Windows, I had no built-in engine in english. I turned it back to "use Built-in SAPI Speech Engines" and now, since I installed the US english voice and language pack under the windows settings panel, I can have access to the proper engine. I can even, from the VA "recognition" options tab, under "utilities", open up training mode and add/remove dictionary words. But I can still not launch the native MS app (the blue bar) either from the windows control panel nor from the Vaicom config panel... see images attached. Could someone please confirm that if I can access training and word editing from VA instead of the native blue bar, it still works as intended?? Thanks!

Thanks, I’ll do that

Thanks for the reply, but it seems it's not the problem. Just trying to start the speech recognition app directly from the control panel doesn't work either. Please see some screenshots of my setup. I have tried setting up a new Windows account to see if I had something corrupted in my account, but I still get the same message. I wonder if I could have deactivated a service needed for this to work? What I don't understand is that VoiceAttack still seems to work? :doh:

Hello, I have been trying to use the training mode to work, but when I click on the microphone icon under editor, this error message pops up. I have checked and English - US is checked everywhere. I tried finding a solution elsewhere on the internet, no joy.. I fear this may be due to some windows debloater program I used in the past. Any ideas?

Hi Hollywood, I have read the manual concerning keybinds but it's not that clear in my mind. I use the TM HOTAS Warthog with the CTS profile system, which is setup to be compatible with VAICOM PRO and SRS together. I have assigned VAICOM PRO nodes TX1, 2, 3 and 5 to joystick buttons DX20, 22, 23 and 21 respectively (I do not use easy comms) and have checked that they work as intended (press/release). I have checked that these are not assigned to any command within DCS controls menu. Still the problem persists... So I have tried another module, the Su-33, and there seems to be no problem there. I suspect there is a conflict with the CTS profile, which simulates the pinkie switch on the stick as a PTT when airborne, but in a non-conventional way through complex TARGET programming... I am in contact with the programmer to try to sort this out. Best regards!

Delayed commands Hi everyone, I've been having a very annoying issue lately using VA + VAICOM PRO with the F-5E (haven't tried using another aircraft): Even though the software recognizes my commands properly (as shown in VA window), they will very often be blocked from being passed right away on to DCS, when airborne. It took me some time to figure out that they would eventually be passed on when opening up the COMMS menu manually (in the F-5E, either using the throttle mic switch, the stick pinkie switch in flight or RALT+\). Strangely enough, the first press to open the COMMS menu doesn't work. The second press works and seems to "unblock" all commands that were queued up by VA+VAICOM. On the ground everything works normally and landing has the same "unblocking" effect on pending orders. Using the COMMS menu manually works everytime. In the VAICOM PRO settings I don't have the COMMS menu hidden option activated and I am using realistic comms in the DCS options. All nodes are properly showing up in the VAICOM status window and respond appropriately to joystick inputs. Using latest version of DCS stable, VA and VAICOM PRO with paid licences, under Windows 10 1903. HOTAS is Thrustmaster Warthog with CTS profile. I wonder if this has anything to do with the F-5E's pinkie switch: on the ground it acts as a NWS button, in the air as a PTT. Any help appreciated as it has been a deal breaker quite frankly :cry:

Thanks, can’t wait for the next stable release :thumbup:

Thanks

Thanks for the information, didn’t know about that. Will report further !

Sometimes the weapons release stops working, even though everyting is properly configured in the cockpit. Bombs or rockets just won't drop or fire no matter what. Restarting DCS fixes the issue... until it happens again randomly. Exiting/rejoining a MP server is not enough to clear the fault.

Sometimes the reticle settings will have no effect on it, as if it stays frozen in MSL mode. Depression doesn't affect the reticle either in MAN... This tends to happen in Multiplayer after some time in the session.

In Multiplayer, as a client, the rudder exhibits uncommanded, rapid left/right deflections when airborne, making the plane unflyable. Happens at any speed apparently. However as a host the problem seems to not exist. Very weird!

That's a negative... how do I opt-in?

Fantastic!! :clap: Next question is: when is 2.28 due :lol:

Hi Home Fries, I've been fiddling around a bit with the Su-33 lately. :wub: Concerning Air-to-Air refueling, there is a special ACS flight control mode that has to be activated by pressing RCTRL+R that helps a great deal to stabilize the bird for refuel. On Cougar, would it be possible to map this to Button 5 together with extending / retracting the refuel probe? Also, there is another feature that would be handy to have mapped somewhere: LALT+I to lower/extend the titanium air intake protections. Helpful for carrier take-offs :smilewink: Best Regards, FFF

Great, makes much more sense now :thumbup: (at least to me :D) I agree and indeed that is what I am using as a solution for the time being :thumbup:

Not sure of what you mean but as I said, what is intuitive to me is that the layout should be according to the TQS lettering shown on the layout, thus TQS VHF = arrow pointing upwards, meaning pushing the switch forward/down. The last thing I would do would be to reverse the actual VHF/UHF symbology (=lettering) on the reference layout, as it wouldn't correspond to the actual TQS anymore, adding to even more confusion... If I were you I would copy/paste the VHF/UHF/IFF lettering in the middle of the box so as to replace the Comm Switch words. Please find attached an example of what I would wish for :D Please refer to my previous post with extensive information and screenshots regarding this. After trying again it seems that SRS does pickup on Radio 1 through DX20 after all, no idea why it didn't work last time... However VAICOM pickups up on TX1 when the F-5E radio is seen by VAICOM on node TX2 so nothing happens. But what you are saying is correct: pressing TQS VHF / down triggers DX20 and UHF / up triggers DX20+DX21

May I offer my help with reworking the reference layouts? Of course, I understand. In the meanwhile, is there a way for me to edit things manually to get SRS + VAICOM working on TQS VHF / down together with the F-5E AN/ARC-164 UHF radio (SRS Radio 1 / VAICOM TX2) ? Cheers FFF

In fact it kinda depends on the position of the throttle lever. In full aft position, the Comm switch is almost horizontal, thus VHF = forward / UHF = backward. When the throttle is full forward the switch is almost vertical, then VHF = down / UHF = up. So if I understand correctly, the TQS reference layout box for the comm switch currently shows the opposite of the UHF/VHF diagram laid out on the stick just next to it. Thus, the "PTT Common" is in fact assigned to Comm switch UHF / up / backward. I don’t know if it’s just me who finds it counter-intuituve but yes I believe it would help a great deal to update the layouts by duplicating the VHF/UHF/IFF diagram inside the box for the Comm switch assignments :thumbup: Makes more sense now. May I suggest to enrich the layouts to clarify the various possibilities, for instance by using a colour code indicating what the Comm switch will do according to which options are chosen regarding VAICOM, SRS and PTT Common ? Will do, thanks :thumbup: Did you have a chance to look into the issues I was raising concerning the Comm switch for the F-5E in my previous post?

Here you go: "When encountering the situation where Windows 10 does not let TARGET hide away the physical devices, SRS may not detect the Thrustmaster Virtual Device in the Controls menu but your physical device instead. To correct this, follow the following steps: 1) run SRS client at least once, with the option "Allow More Input Devices" turned ON, then close the application. 2) navigate to SRS installation folder, locate and open the clientlog.txt file. 3) scroll down to the bottom of the file and locate the line that says: "Found Device ID:0400044f-0000-0000-0000-504944564944 HOTAS Cougar Joystick Usage: Generic Type: FirstPerson" 4) Copy and paste your conflicting device ID (just the string as highlighted in bold above) to a new, blank text file and save it in the same folder named blacklist.txt 5) Start SRS Client, this time turn OFF the option "Allow More Input Devices" 6) You should be able to bind your controls notmally now. Final remarks: if more input devices are connected and are still conflicting, follow the same procedure for those extra devices, or add the one device you want to be recognized (Thrustmaster Virtual Device) in a whitelist.txt file. Roger, got it. I have changed my SRS settings so as to remove the bindings for PTT and Intercom Modifier, and have turned ON the setting "Radio switch works as PTT". Radio 1 is bound to Joystick btn 19 / Radio 2 : btn 21 / Radio 3 : btn 22 as per CTS manual. Concerning the TQS comm switch terminology I believe there is a lot of confusion going on. Could we agree to call the physical switches according to their lettering and their corresponding directions? Do we then agree that the VHF switch position means pressing down / UHF = up / IFF OUT = left (seen from the pilot seat) / IFF IN = right ? This helps to verify wether the CTS references layouts are matching what's going on in DCS. In addition, I shall add that the CTS "Settings" page shows a "TQS CommSwitch Mapping" that uses yet another set of switch names (T2-5 / Up-Dn-Fwd-Aft) that add to even more misunderstanding, as I don't see what Aft/Fwd would mean on the TQS ? On the Warthog though that would make sense I guess. Concerning the A-10A, using this combination of VAICOM+SRS + Cougar, this is what I find for the Comm switch: - IFF OUT = left = SRS Radio 1 = VAICOM TX1 = AN/ARC-186 VHF AM - VHF = down = SRS Radio 2 = VAICOM TX2 = AN/ARC-164 UHF - IFF IN = right = SRS Radio 3 = VAICOM TX3 = AN/ARC-186 VHF FM So if this is as intended, I believe the CTS reference layout is wrong: TQS VHF / down is shown as mapped to "PTT Common" when it is actually "UHF". Wouldn't it also help to change "VHF2" to "VHF(AM)" and "VHF1" to "VHF(FM)" ? There is a screenshot attached showing the A-10A and the status of SRS+VAICOM when pressing TQS IFF OUT / left. SRS picks it up as Radio 1 (VHF AM) and VAICOM as TX1/VHF AM. Is this as intended? If I understand correctly, this is then what you call "PTT Common" in your reference layouts? If so I believe this is misleading for those who run VAICOM+SRS and therefore do not use PTT Common. I am wondering if in fact there isn't as well a misinterpretation between you and me regarding the way to read out the reference layout box for the TQS Comm switch?? This might explain the confusion with the radar range setting as well? According to my intuition, the reference layout box should be read according to the switch lettering that appears right below it on the drawn TQS. If we take the F-5E as an example here, "PTT Common" is in the upper position of the layout box, which corresponds to VHF, so that means pressing down on the physical button... ... which does not match you're describing above? Going on with the F-5E, pressing on TQS VHF / down has no effect, neither on SRS nor VAICOM. Please see attached screenshot showing the status of both when pressing that button. Isn't it because SRS sees the F-5E's sole radio as "Radio 1" and is therefore expecting a press from TQS IFF OUT (Joy btn 19) to trigger it, when we are pressing TQS VHF (Joy btn 21) instead? VAICOM sees the F-5E radio in the TX2 slot, but you said above that TQS VHF / down is mapped to TX1, and that is indeed what VAICOM sees is being triggered, but doesn't transmit in DCS since it's not on the right node. Still with the F-5E, presssing TQS UHF / up will result in TX1+TX4 being triggered in VAICOM when it should have been reserved for TS3/Discord, right ? Again the reference layout seems inverted here, showing TQS VHF / down mapped to "PTT Common" (TS3/Discord if I am following) and UHF / up mapped to "AI Comms". Looking at the VAICOM settings this makes partially sense to me, as Joystick btn 21 is assigned to TX4 which is AUTO. Still don't understand why that would trigger TX1 as well... In fact I don't understand why this binding should be left for those who use SRS+VAICOM without a PTT Common ? Wouldn't it be possible instead for those who do not use TS3/Discord with a PTT, to bind TQS UHF / up / Joy btn 21 to TX5/INTERCOM ? For the sake of troubleshooting, I have attached a screenshot of my VAICOM settings and SRS controls to verify they match the setup required by CTS. Please find attached a screenshot showing the options menu and the device analyser when pressing the H1 down. The line that is highlighted in french means "Trim - pitch down", so in my case it is indeed reversed. Keep up the good work, I hope I haven't been too hard to read but things are still not clear in my mind so I'm trying to adopt a standard terminology :thumbup:

Hi everyone, I was having a new bug: the mouse pointer won't show up anymore in DCS when playing in VR with a WMR headseat. I was running Steam VR 1.1.4 (stable) I have had this issue before but could usually solve it by either making sure the DCS window was the active one, or pressing the WMR Win+Y key combination... this key combination seems to be broken. Problem solved by switching to Steam VR beta (1.2.6.)... hope this can help!