Ghostrider711

nullYes, I do use them for startup and changes during flight. I had zero issues with them prior to this last update.

All that is off.

After update, joystick quits working in F1/cockpit view. From external it works fine. The only thing I notice is my hand controllers will flash right when it stops working/when switching back to cockpit view. It starts to work normally, when returning to cockpit view, then oculus hand controllers will flash and joystick stops working until you use another view, back to working again. Extremely weird, anyone else?

In Oculus 3200x 1632, with an 80HZ RR. OTT FOV 0.64 0.69, encode res 2912, 400 bitrate, EDB disabled. And that's a really cool deal how that lets you adjust periphery.

If I leave PD at 1 and adjust literally anything else and any combination thereof , the performance takes an absolute nose dive. The only way it works is if DCS PD is 1.7+ and the HMD is a lower res. I’ve literally tried hundreds of combinations. I get that worked for you, but my question would be how long ago did you do that and what was your hardware at the time? Is this what you’re currently doing?

Yes, I am aware of that, if you leave the HMD at X res and raise PD to 1.2 from 1.0, you still have jaggy edges and a poor image quality/poor performance in DCS. By decreasing the HMD’s res and forcing a huge upscale in PD within DCS, you get a much cleaner image and your lower HMD res, in some way, prevents DCS from using VRAM. The higher res you run the HMD at, prior to changing PD numbers, the more VRAM DCS will use, by a LOT. lowering HMD res does something to cap the resources DCS is using. What I meant when I said “if we can figure out why it does this” I was referring to why that prevents DCS from eating resources when adjusted the way I describe .

I keep the fps limit in DCS to whatever my VR refresh rate is. I think it’s possible to keep lowering your headset res and keep raising pixel density until it crashes it, then back that off. You basically want enough pixel density that when you look at the mountains at a distance that the peaks are clean cut and that will allow you to spot enemy and MFD’s as well. Do not use AA or AF , use pixel density to get clarity and sharpen the image. Lower your headset resolution to give you performance headroom. Shadows of any type will have to be carefully added and check performance after every shadow change. you can lower cockpit res to 512 and with 1.7 VR pixel density, in sim, and it looks like 1024 with a higher headset resolution, in oculus software. the biggest thing we need to do is figure out why that’s like that.

For, off and on a month now, I have been messing with settings to get this thing to run good in VR. Lower texture settings *Cockpit to 512* Ect. Tonight, on a whim I raised DCS VR pix dens to 1.7 and cut my headset res in half. Not only did DCS look better, sharper on my Quest 2/link cable, performance went way up and now I can actually see enemies and spot ground targets. I will try to screen shot all settings and update this thread but, this made a MASSIVE difference, I'm talking 40% gains. HALF whatever res you're running on the headset and then raise VR pix Dens in sim to 1.7. Magic bullet.

As a few people know, polling rate seems to affect performance. Do certain things that are modeled in the sim/VR headset tracking and controller tracking somehow have this same interaction? When you move your head, does that use the same ''API'' to communicate with Windows that a change has happened? I am not a programmer, I do not know how to technically state this. I am only going from my previous dev experience in other software I have worked with. It would seem to me, the same stuttering you get with this mouse glitch is the same ''feel'' you get when moving hand controllers or, your head, while in the sim. Is there some way to investigate this? Do headsets use the same ''API'' when interacting with Microsoft to track head movement? Meaning, is it ''polling'' in the same way? Same with certain radar functions, could they also be tapping into this same thing in some way to be causing performance drops? I realize there are smarter people than me, but it got me thinking. Disregard if this is a known issue, just trying to help.

Final, above settings work, I missed cockpit textures. With my above hardware, online, if cockpit textures are anything above 512, it ain't happening. If you keep 512, it works. Come to find out, it's actually VRAM that was limiting the system in MP.

I will take a look at this tonight and try it out, after I backup my stuff. Appreciate it. Anything is worth a shot. Out of being curious, does the 6950XT struggle at all?

Will include log file but the only time I have issues is when I'm online, populated servers. When I take the headset off, while holding my thumb over the sensor, and I look at VR preview, I see stuttering but no distorted images. Runs great til you join a server. I tried turning resolution way down on headset, multiple things. Turned settings way down, it doesn't affect it, still jittery and unplayable online. Anyone else have this or, know what the deal is? dcs.log

Disabling OpenXR fixed the issue. Runs fine in single player, 32Gig page file and 32Gig physical ram. When sitting on runway in multiplayer pieces of runway and the image contort while in VR. Fine in single player. memory use is 84% when it's doing this. Will post that issue in the proper places. Appreciate you sir.

Everything was working fine after the update, I played it for hours, multiple times too. I will do that repair, I will also disable openXR toolkit. Will report back so that whatever is found can help someone else, assuming I can fix it.

Running lasso, also ran with it disabled. Quest 2 with OpenXR and OTT with .67/.67 on FOV. Ran pretty good, had stuttering when using VR in populated servers. Went through all the discord dcs.log suggestions, changed page file and rebooted. Now, game refuses to start in VR. I tried reg and MT DCS, both will start in 2d mode just fine, both refuse to run VR mode. i9-9900K 3070TI 32Gigs Fully updated. Crashes after DCS splash screen. Any help would be great. dcs.log dcs.log-20240719-112943.zip