tanr

Changing the tanker to only be on 305.00 (removed the advanced waypoint action line that set freq 243.00) and set preset 1 for the F-15E to also be 305.00 and the tanker worked fine with normal comms. Might be some special handling for 243.00 since it's the guard channel that's causing the issue. Thanks for all your work.

I had similar blurring/trailers with a 3090, Quest Pro, and using OpenXR if I had DLAA on with Sharpening at 0.6. Leaving DLAA on but setting Sharpening at 0.0 seemed to get rid of the motion blurring and actually left things looking sharper than before. Then again, I wasn't even running MSAA before so I'm just happy to get rid of much of the jaggedness.

Checking the status of this as I'd love to try out a Loupedeck plugin with DCS. Old programmer myself, so willing to look through the code if needed.

Glad to hear that!

Waiting to see how the F-15E turns out too. I'm not expecting anything to be done on the 19 before they get the F15 out the door. Would love to see the 19 get turned around like the M2000 was. In the meantime, I'm using Munkwolf's keybinds to get some of the inputs I want (like keyboard bindings for GIK-1 Compass Course needle).

Found this thread while trying to find a mapping for the course selector knob. Adding some of these frequently asked for bindings would really be appreciated.

Any specific steps to take if moving from the release version to the beta version of SimShaker for Aviators? I'm on the 2.5.0.0 release version (and on Sound Module 2.26) and want to move to 2.5.8 Beta. I know that Beta and Stable don't share the same database, so I can import my database from the exported Stable settings, but any other gotchas? Like can I leave the Sound Module on the release version? Thanks.

I've got a track file of a flight on Growling Sidewinder, RWR is on (Search mode off). Most emitters don't show on RWR. The missile that got me actually showed up on RWR briefly before I went boom. Here's a link to the track file, which will expire Sunday. Growling RWR Trackfile (Can't upload it directly since the track file is 41MB.). I've attached a snapshot from that flight where you can see plenty of contacts on Radar and HSD, with the RWR basically empty.

Yes, please, we really need those APIs!

Can't quite tell from the dimensions if my big feet would work well with these pedals. Will these work with U.S. shoe size 15 (EU size 49, UK size 14.5) feet? For dimensions, the exterior length of my shoes is 13.5 inches = 353 mm. I could wear shorter slippers with length 12.5 inches = 317 mm to fly if needed. Quite interested in using them with dampers to switch between planes and helicopters. And just because they look gorgeous!

Nope, not using NS430 or DiCE I'm afraid!

Curious which Vaicom PTT Mode you're using for the Apache? I'm hoping the "NORM" mode will be smart enough to figure out that the cyclic RTS Left transmits on the current radio, as opposed to always changing the radio to UHF. Though I guess I could map RTS Left and Right to UHF and VHF radio select+transmit for Vaicom and leave the Apache ICS set to VOX since those FM radios won't get used much. Just trying to work out a usable system for MP till a Vaicom update for the Apache comes out.

Found a "fix" for my Vaicom "Options" breaking (suspends listening after bringing up comm menu). After many partial resets I finally did a full uninstall and reinstall of Vaicom (VoiceAttack is Steam version and Steam version of Open Beta DCS in a custom folder). I didn't add back in the AIRO and Chatter extensions. Options menu worked correctly after that. As soon as I added the extensions back in the Options menu changed back to giving a "Listening Suspended" right after "Options" (and without me releasing the PTT key button). So something in the extensions is borking it. I removed the extensions (don't need them right now) and enabled "Disable automatic plugin updates" so it doesn't keep trying to get them. Maybe the extensions make some assumption about the location of DCS or VoiceAttack files and crash?

Vaicom Pro has recently stopped working correctly for the Mission/Server communication menu. I believe this started after the recent Vaicom update. Repro Steps: In mission (F16 Free Flight) press and hold PTT button while saying "Options" Result: Options menu appears While still holding down PTT button try saying "Take 1", "Take 2" etc. to select the F1 or F2 options Result: No selection of a communication menu item occurs Looking at the Voice Attack log, even though I haven't released the PTT button, I get a "Listening Suspended" as soon as the Options menu comes up. When I release the PTT key I see the "Joystick: Transmit TX1 release" message, so it knew I still had the key pressed. Example log below: If I test this with VoiceAttack and Vaicom PRO without DCS running, it VA doesn't stop listening till I actually release the PTT key (correct function). Note that other Vaicom commands seem to work fine. This happens in single player and multiplayer on all maps and on the couple planes I tested. "Allow Options" and "Disable Menus" are both selected. Vaicom is most current version (2.5.27.0) and DCS is current Open Beta. Both DCS and VoiceAttack are Steam versions. Vaicom is set to custom DCS path which is the correct DCSWorld path for my Steam install. Vaicom is also set to use the Steam version of VoiceAttack. I'm running SRS with Allow VAICOM TX Inhibit OFF, and I don't use the VA mic buttons in SRS except to switch radios - SRS PTT is completely separate button. Steps I've tried so far: Re-did Vaicom Editor>Finish, then copying the keywords list over from the copy buffer, then restarting Used Vaicom Reset tab to reset Lua code and the VA Profile. (It didn't appear to actually reset the profile so I re-imported the newest profile.) I haven't yet tried resetting my Keywords and Settings (or reinstalling) since I'd like to avoid having to rebuild things. I've verified there are no other instances of VoiceAttack or Vaicom present in my system I've tried this without my custom profiles referenced from the Vaicom profile with the same issue Tried with Tacview disabled by commenting it out from lua - same problem Here's my Export.lua in case that's useful: Any thoughts on what might be going on? Thanks in advance for any help with this.

Is there a waitlist for these Total Controls Apache MPDs? Quite interested in them.

Got vrperfkit to work with DCS finally. Still not sure what the problem was, but replacing the .yml config file with the original .yml config file got it working. Weird thing is that doing a text diff of the two config files, the only difference shown was sharpness being set to 0.8 instead of 0.7. Maybe some invisible character?

Don't you only need to rename dxgi.dll to d3d11.dll if you're also using another dxgi.dll? I'm using DCS's original version of openvr_api.dll.

No, I'm not renaming anything. With a vanilla DCSWorld\bin directory, per the readme, I copy the dxgi.dll and vrperfkit.yml file into my DCSWorld\bin directory. The vrperfkit.yml file has very few changes.

This was with the games default openvr_api.dll. I had disabled the FSR mod which restored the original version - just double checked it to make sure.

Tried vrperfkit 0.2.2 with DCS (open beta) and my G2 (SteamVR, Windows 10) a couple times now, without success. I had been using FSR 2.1.1 which worked great. Removed FSR using my mod manager, and installed the verperfkit dll and yml file, with settings matching my previous FSR setup (using FSR instead of NIS even though I have a 3090). Running some standard test missions I can see that vrperfkit is running, debug mode hotkeys work and show the overlay, etc., but frame times are about 5ms longer than they were with FSR and the same settings. Tried reboots, etc. without seeing a difference. Tried both FSR and NIS modes. Tried with hotkeys on and off. fixedFoveated is off. Is there something basic I'm missing with how this should work with DCS and the G2? Should I try forcing DirectX 11 for WMR?

Anybody know a way this can be used for increasing pitch (upward tilt) of your head? So not left/right rotation, but looking way up at something above you?

Yardstick, also known as buddy tacan, continues to have this or a similar issue for the F16. It does not seem to require one pilot to change the band either. Pretty much every time I fly with buddy tacan set up (using band Y) it will work for 5-20 minutes, then either I or the other plane or both will get the inverted distance showing on the HUD staying frozen at whatever the last distance reading was. The last time I ran into this (yesterday) TACAN was set to 31Y/94Y. One or both of the pilots changing the band back to X then to Y sometimes works around this, but usually after it has happened once it will only work again for a few seconds to a few minutes before breaking again. This makes tactical formations where you need to know your wingman's distance extremely difficult. What is needed for this to be reproduced by ED? Tracks from both pilots? Or is there already a bug tracking this?

Thanks for the suggestion. I set up NVidia Broadcast, running just the noise removal on input from the default device (NVidia wanted to make it's virtual mic and speakers the default but turned those off). Set up Voice Attack to use the NVidia broadcast virtual mic for speech recognition. Seems to work pretty well! I'll probably use it for SRS too. Does seem silly that the G2 or VoiceAttack can't just cancel out the mic output, since both of those should be aware of all the sound coming out of the speakers, making noise cancellation less of a load on the system. Ah well.

I've been using Vaicom Pro for DCS running a flat screen and headset with headphones + mic. That all works well and is wonderful to use. I've started using a Reverb G2, with it's built in mic and floating ear speakers, and am running into problems. Voice Attack and Vaicom both correctly switch to using the G2's speakers and mic, but the problem I'm running into is that the speech recognition from the mic is almost unusable when the speakers are positioned over my ears. Most commands are only partially recognized, or not recognized at all. Moving the ear speakers up away from my ears (less close to the mic) allows commands to be recognized, but then I can barely hear what's happening. Volume is set pretty low already, so setting it lower isn't an option. Any settings that would help VoiceAttack/Vaicom filter out the noise from the speakers, or do I need to remove the speakers and use my regular headset over the VR headset? I'm not sure that will fit, as I've got an XXL size head... Thanks for any advice.

Still bugged. Simple fix as Jonsky7 posted.