Rangoon

So if I use the system-wide installer, I never need to manually download and manually replace the openvr_api.dll files? That is all handled automatically via the switcher application? And that works in both directions and for all games? Are there specific dll's for each game? Or is there a generic SteamVR openxr dll that is used by all games?

That was definitely the problem. Thank you!!

Thanks for the input, you guys. Foveated rendering is disabled, and no zoom is set. I'll double check the toolkit version, though I just downloaded it yesterday. I have my super sampling set to 1.0 in PiTool (I used to have it set to 0.75 for DCS with SteamVR, but moved it to 1.0 thinking I would do anything like that in the Toolkit - it's also at 1.0 in DCS). I'll try unplugging the headset and restarting. I'm using an RTX 3080Ti (with i9-12900k and 64GB RAM). I'm just trying to get things working on a fundamental level here, so I haven't really even played with any other settings at this point. Just have the performance overlay turned on.

I'm trying to get my Pimax working with OpenXR in DCS. I am seeing a double image. I believe with SteamVR, turning on "Compatible with parallel reprojections" would fix that. But now that just seems to leave me with a double image or blurring when I turn my head. Is there something within the OpenXR Toolkit that might fix this? Or is it something within PiTool? I have read about people using PiTool version .263. Is that generally considered the best version to use? Might that fix my issue? I've tried locking framerate to 45fps and I am not using motion smoothing.

Also in the Huey, S2 Weapons Release Button is toggling VAICOM PRO's Chatter extension. It's set to Joystick 1 Button 2 in the VoiceAttack VAICOM PRO profile. I didn't see anything in the setup guide or other documentation about modifying this. I assume the button assignment should just be disabled in the profile, but it made me wonder if that meant my TARGET DCS PTT Import didn't work correctly. I don't see an entry for Chatter in the .vap file. In the setup guide, it says "...Chatter has been changed to R_CTL+L_ALT+V to prevent direct entry of numbers from also inadvertently toggling the Chatter function." The keyboard shortcut in my profile is 0 (zero). I'll change mine to that manually for now. Maybe that entry slipped through the cracks at some point and simply needs to be re-added to the .vap?

Perhaps I've messed something up on configuration, but I think there may be something wrong with the UH-1H profile and VAICOM PRO. I am using Easy Comms just to try and eliminate as many variables as possible, but it was happening even with Easy Comms off. I also have Realistic Helicopter 2-stage Radio Trigger disabled (set to 0, per default). My Global - Communications settings are: VAICOM PRO 1, SRS 0, SR PTT Common 0, TS as DX 1, CommState Allow 1, Comm Menu by station 0, Chatter 1, AI RIO 1, TX5 Delay KBDelay, SR Overlay 1. Here's what I see: Throttle PTT Common Up: VoiceAttack shows TX1 press (release upon release), VAICOM Pro flashes TX1 SEL/AUTO and displays XMIT while held, Right MFD LED 1 illuminates while held. VoiceAttack and DCS respond to voice input. So this seems to work as expected in every regard. Throttle PTT Common Down: VoiceAttack shows TX5 press (release upon release), VAICOM PRO does not respond, Right MFD LED 2 illuminates while held. It's labeled PTT Common, so I assumed this should do the same thing as pressing it up. DCS does not respond to voice input, but VoiceAttack acknowledges in red text and says "...currently disabled for this session and was not executed." Throttle PTT Common Center Press: VoiceAttack shows TX4 press (release upon release), VAICOM PRO does not respond, Right MFD LED 1 illuminates while held. It's also labeled PTT Common. It's odd that the LED behavior changes again here. DCS does not respond to voice input, but VoiceAttack acknowledges in red text and says "...currently disabled for this session and was not executed." Trigger Stage 1: VoiceAttack shows TX5 press (release upon release), VAICOM PRO does not respond, neither Right MFD LED illuminates. DCS does not respond to voice input, but VoiceAttack acknowledges in red text and says "...currently disabled for this session and was not executed." Trigger Stage 2: VoiceAttack shows TX5 and TX1 press (release upon release), VAICOM Pro flashes TX1 SEL/AUTO and displays XMIT while held, neither Right MFD LED illuminates. VoiceAttack and DCS respond to voice input. So this seems to work, though it's odd about the LED. The other thing about Trigger Stage 2 is that you have to move slowly through 1 to 2. If you quickly full press to Stage 2, you get a different behavior: Trigger Stage 2 fast press: VoiceAttack shows TX5 and TX1 press (release upon release), VAICOM Pro flashes TX1 SEL/AUTO but only briefly flashes XMIT, neither Right MFD LED illuminates. DCS does not respond to voice input, but VoiceAttack acknowledges in red text and says "...currently disabled for this session and was not executed." Any idea what is going on here? All I'm doing is loading up an Instant Action mission on Caucasus: "Free Flight" where radios are tuned by default to Tbilisi and responds when the PTT is working.

I can't get the updater (normal or full) to work, nor can I get a full reinstallation to complete. At some point during the downloads, it just freezes and eventually crashes Windows (freezes, requires hard reboot). I have tried a fresh download of the latest installer, as well as the verstion.txt on page one of this thread. Neither works. After trying the full installation, and hard reboot of the system, I was able to launch CTS, which prompted to open the setup guide, as if it was the first time running CTS. Just to be sure, I ran an update, but it crashed again.

It is. I have single dislplay set in DCS settings, but resolution there is set lower but I don't think that has any effect. I think in the past I wondered if that might affect the mirror's resolution, set it, never touched it again. I do have 4 displays connected and running, but that also has never been an issue in DCS as far as displaying on single screen, mirror, or in the HMD.

I just updated to the current release version today, after having not fired up DCS in several months. I am using a Rift S. Unless I press Alt+Ent for full-screen mode, the mirror cuts off the bottom 1/3 on my 2D display. In VR, the mouse will not reach below that point, so the bottom third is inaccessible (i.e., cannot click on OK, Quit, etc.). Any ideas how to fix this?

Selecting/activating another profile and then back to the Ka-50 profile worked! I'll make this my habit for now, and hopefully this info helps you sort it out down the road.

Hi Hollywood, the only thing I can find in dcs.log that seems related are a great many lines like this: 2019-03-14 23:54:52.400 ERROR SOUND: can't load wave: "sounds\speech\sound\rus\common\disabled_player\callsign\kobuleti" I assume this is normal due to having Disable Player Voice selected? Not sure. Is there anything else I should look for in the log? Also, this happens with UH-1 as well as Ka-50. Not sure about other modules. As for other apps running along with DCS, I generally do have the following: TARGET GUI GPU-Z HWMonitor SimShaker for Aviators (and JetSeat Handler) MFD4CTS Oculus DCS Updater/Launcher GUI Utility Notepad Anything problematic here?

I have an issue with the Ka-50 profile after ejecting (which happens...frequently). It never works correctly afterwards. I see in the log: Ejecting...S2 Set to CommState...Done! Resetting GearState and profile arrays... Done. I see on the LED's the Rotor Brake and Landing Gear lights. I do not see Fuel Switch On lights (per my profile start settings). Everything seems normal there. However, trim does not work. Trim does not work regardless of changing or not changing Gear State. Instead of trim, I get nothing on press and then SHKVAL Uncage on release. There are other little issues as well, but this is always what I notice first. The only solution I have found is to stop the profile and run it again. I don't know if this is related, or whether it's working as intended, but normally if I cycle the Gear state (using S3+LDGH), the Fuel Switch lights follow suit. i.e., from profile load, if I switch to Gear Up state, I see the Fuel Switch lights turn on (mission starting in the air). If I then cycle again to Gear Down state, I see Fuel Switch lights turn off (mission starting on the ground, engines running, Rotor Brake light also stays off). That's as it should be. After an Ejection sequence, and subsequent profile reinitialization, these Fuel Switch lights no longer behave the same. In this case, they start out on, stay on at Gear Up state, but go out on Gear Down state (Rotor Brake light is off). This is a little inconsistent from a fresh profile start, so maybe there is a connection? Just wanted to mention that in case there is. As always, thank you!!

KI am still having this issue after having used VAICOM PRO for over a year and would love to get this solved. I reinstalled DCS just to make sure that wasn't the problem, having come from 1.5 install, 2.5 beta, then release, etc... Just wiped it all out and installed 2.5 release, then updated to open beta. I am using VAICOM PRO 2.5.9.2, VoiceAttack 1.7.3, DCS 2.5.4.28461. This has been happening since I first began using VAICOM PRO, primarily UH-1 and Ka-50 is what I fly. After the latest DCS update, as usual, I reset just my "Lua code" through the Reset page (Master Zero). Easy Comms is off. I am not using a custom DCS path. Everything starts out fine. I can change frequency in the Ka-50, talk to tower, talk to wingmen, use the "options" command and get a menu, etc. Everything works as expected. Until it doesn't. I can't figure out a pattern, but at some point in nearly any mission the comms seem to get out of sync between DCS and VAICOM PRO. What happens is I say a command to my wingman, hear the confirmation (high) beep, but don't see anything printed in the upper left. VoiceAttack registers the command in the log. The command is not acknowledged by my wingman. However, if I repeatedly press the TX button a few times, it will eventually print to the upper left and the wingman will acknowledge. It seems like it can store more than one of these commands in limbo, and then execute only eventually after repeating TX. Any ideas here? EDIT: not sure if this is helpful, but it seems like it's always 4 presses of the TX before the response processes in DCS once it gets stuck. Also, once this happens, it never recovers without starting the mission. I'll confirm whether it's the mission or DCS entirely. It does not require a restart of VoiceAttack to fix it. EDIT: confirmed, it's just a restart of the mission, not DCS.

That's a great suggestion. I am positive I have multiple binds for throttle up/down. I use the excellent CTS utility for my TARGET profiles, and it does map one or two other commands there. I will look into this. I wasn't activating anything redundantly, but worth looking into.

Thanks for the replies to help sort this out. As I mentioned in my original post, "I am using idle stop release, and can visually confirm the release button is being depressed." I also did have the battery on and was using axis, page down, and mouse wheel down. i.e., throttle axis to idle, press idle release, then follow up with either page down or mouse wheel down (battery on). I really feel like it was interference between me looking at the throttle (in VR) with mouse cursor pointing at the throttle (but invisible, as in mouse not moved so not activated) and using the page down key. I will test this again and see if I can reproduce it. I am familiar with an odd behavior in the past with Huey where I have to roll throttle up once fully with mouse wheel before my axis from HOTAS will get full travel between idle stop and full open. That is still the case. It was this other odd behavior I haven't seen before.

Since updating today, I am unable to roll throttle toward the closed side of the idle stop, to cutoff position. This is release version 2.5.4.24730. I have tried the default keyboard controls of Page Up and Page Down, the mouse wheel, and a bound throttle axis. None of these work. I can get full travel between idle stop and full throttle, but no movement from idle stop to cutoff. I am using idle stop release, and can visually confirm the release button is being depressed. I can also confirm this behavior in the control indicator overlay. Edit: it seems to be working now. I'm wondering if possibly my "invisible" mouse cursor was aimed at the throttle and, even though I was not touching the mouse wheel, perhaps that was causing some interference? It seems intermittent now. Sometimes I have to use the mouse wheel to move the throttle, and then the axis will start to work again. I can't quite determine the exact pattern, but it seems like this could happen if the two were acting on the throttle simultaneously. Again, this is happening even when I don't see the mouse cursor, and am not touching the mouse. Almost like there is "noise" coming from the mouse wheel that isn't triggering the cursor to display, but is somehow acting on the throttle. I am not seeing any movement in the throttle when this happens, either. But for now, the throttle is working correctly some of the time.

Okay, thanks for clarifying. I checked mine and it was also 200%. I set that back to 100%. Probably explains why my framerate had been cut in half or worse after the last update. It was likely SteamVR, not DCS to blame.

Do you mean in SteamVR Settings -> Applications -> SteamVR Home (or DCS)? Or do you mean in SteamVR Settings -> Video -> Manual Override and adjust slider there? I haven't touched my SteamVR Settings, so mine are still at their default.

I was going to suggest the same as TOViper. I wear glasses sometimes, contacts other times. I prefer VR with contacts. Inter Pupil Distance comes into play twice with DCS: 1) I find that the manual adjustment for the lens spacing (the slider under your right eye on the Oculus frame - you move after pressing up on it) can cause a lot of strain and focus issues. I tend to move this to the extremes once or twice to find what *doesn't* feel right, and then keep walking it toward the middle, closer and closer to where I feel the least strain. It isn't scientific (there is a more scientific way in Oculus calibration or your optometrist can give you the exact measurement and you can try that). 2) in DCS VR settings, you can override the IPD setting there. I use 37. I just kept trying extremes and walking it to what *looked* right to me. This seems to affect the scale/size/proportion of the aircraft and world. I moved mine until it looked like 1:1 scale. Not sure if this could affect the HUD and gunsights etc. Definitely makes a huge difference in immersion. Good luck!

This really is an excellent utility! Saves so much time in setup, and improves over what I had been doing to get things to "look right" before. Now with integration into CTS, it's going to get better and better.

I am now a couple weeks into using SSA with the Jetseat FSE and two buttkickers. I have one buttkicker set to mono audio out for use with the sound module. The other buttkicker feeds from system audio. In DCS this creates a nice effect. Such an excellent experience, thanks to Andre and Olaf! I have noticed something odd with regard to weapon feedback in the Ka-50, DCS open beta latest version. Cannon and rockets are what I have tested, and there appears to be about a 20-second delay in just the Sound Module. The Jetseat feedback is timed correctly with the weapons, but the Sound Module is delayed. I am using SSA version 1.3.2.1 and Sound Module version 2.8. If I disable the system audio buttkicker, then alternately the Jetseat (USB) and Sound Module buttkicker, I can isolate this. Is this something with my installation or settings? Or possibly a bug? EDIT: False alarm - it seems simply restarting SSA fixed the problem. Everything is back in sync.

Today I saw again an issue from the past where the transmission I am making does not actually execute until PTT is pressed a second time. This usually happens somewhere into the mission, not in the beginning. I can get through many transmissions without trouble, then suddenly this behavior appears seemingly out of nowhere. I press and hold PTT, say what I want to say, hear the higher pitched beep confirming the message got through to VAICOM, but nothing happens in DCS. Once I press PTT again (immediately, without saying anything), DCS registers my transmission. I see the text appear in the upper left corner for what I had said previously, followed by the response.

I am using VAICOM PRO 2.5.5 with the latest DCS beta version. In the VAICOM options, I have the PTT Dial Selector set to Manual (MAN). In the Huey, with Easy Comms off, and everything correctly registering in the VAICOM options, the selector dial in the aircraft still moves on its own. Does that sound like something wrong with my install or settings?

I'm basically giving up on the Device Analyzer. It seems totally broken now, presumably with the driver/TARGET updates, maybe something new in Windows 10, not sure. I'm at least able to get things working consistently. I changed around the ports I'm using, maybe that helped. So the controllers are working, and registering in Windows fine. CTS is working great. DCS sees everything as it should. Whatever my issue was clearly has nothing to do with CTS. I do still get the problem after some sessions where I can't load the script again without some TM devices staying in the Game Controllers list. I get the virtual controller, but also still see MFD, Joystick, and/or Throttle populating the list. System restart is the only reliable solution I've come across.

Today I updated my Warthog joystick firmware from v11 to v12, uninstalled old drivers and TARGET, installed the latest version of both. I also updated to CTS 2.25b. For some reason, now when I activate my profile (Warthog HOTAS+2xMFDs), device analyzer will not enumerate more than one device (and it's not a thrustmaster device). In USB controller list "Game Controllers" I see 5 or 6 devices including the Thrustmaster virtual device. However, when I run the device analyzer from the active script window under "Tools", I am only seeing a single, unrelated device. I run "Enumerate Devices" but nothing new shows up. At first, after the TARGET update, I was seeing in DCS that my X/Y joystick axes were not registering. After this, I ran the uninstall/reinstall update process again, confirmed that I could see the joystick and other devices working individually in Windows. I ran the TM calibration utilities, then ran a test script. Now sometimes I could see a few devices in the device analyzer, but not all...it became seemingly unstable/unpredictable. Whenever I run the script from CTS, it goes down to just one (not Thrustmaster) device and nothing else populates. I used to always be able to test my combined HOTAS script in the analyzer, including after running CTS, before launching DCS. Has anyone else seen odd behavior with the latest TARGET version? Right now I'm stumped.