Taterbootz

The motion sickness thing is so weird. I dont get it playing DCS or MSFS or most things in VR, but I absolutely cannot ride in a car on a twisty road without getting it. I also cant go to any of the 4D "rides" at amusement parks or disney due to massive motion sickness. But my wife that doesnt have either of those two issues, cant even look at a VR screen for more than a few seconds without getting motion sickness.

I have done the latest 23H2 update and it didnt affect WMR. It should only be the big 24H2 update that does it.

Well, considering nobody but you has asked about efficiency of power supplies, it doesnt seem that many people care about the efficiency of power supplies. They are either effective or ineffective. Now, since I've said my peace: Go away.

Ah, I cant do with darker screens. My low light vision is fading more and more with each passing year, and I tend to not like it really dark. I've heard of people getting used to it, but I honestly cant get used to it enough to spend enough time to try and "get used to it" actually lol. But I think VR is a way more personal experience thats hard to translate like 2d gaming is too honestly.

So what exactly was your point by bringing up efficiency? Efficiency doesnt matter at all except when determining x per y. What are your two variables that its more efficient at and why should that matter to someone who wants to play DCS? It doesnt, except in terms of cost. If you're building a 13900k/4090 system, efficiency of cost isnt something you've factored in your build. Otherwise you'd get a lower powered computer and be okay with lower quality graphics. You're talking to people that are overbuilding their computers to get maximum performance, not efficiency. I dont factor in efficiency when I'm modifying my car, because efficiency isnt why I'm modifying the car. You're arguing a point that nobody cares about but you and acting like everyone else is the idiot. You can be technically correct and still wrong. Context matters. The mission defines the goal.

No idea. I just dont consider seeing individual frames or the change in frames stuttering, I consider a frametime spike to be a stutter. One is an issue with the computation to be displayed, one is just how its displayed IMO. Thats strictly my terminology and was only used to describe what was happening easier for people to understand. Frametime spikes stutters arent the same as sub 90fps stutters on motion from what I've seen. I'm not here to argue semantics, just trying to give an accurate account of what I mean and what I dont in easy to understand terms (which is the point of communication...not the actual definition of the term, but the understanding of the message conveyed using the means of the conversation). What did you do to remove the flicker?

The difference in efficiency between 50% and 100% load is 4% at the most. The amount you'd "save" by spending more on a larger PSU is more than likely less than you'd have saved by buying the cheaper power supply from the start, unless your power is astronomically expensive where you live. And if it is, getting a 13900k and a 4090 then arguing over 4% of efficiency in regards to power cost is kinda ridiculous and semantic at that point.

If you cant deal with the frames jumping, you either need to set it to hold 90FPS, downgrade it to 60 and set your graphics to hold that if you can deal with the flicker (I cant), or get used to MR and get it smooth with that locked at 45. Eventually I got used to the slight frame jumps from less than 90 with no MR to where I dont even like how MR warps the image to get me steady picture a lot of the time and I'd rather have it frame jump (I'm not calling it stuttering because stuttering to me is different, this is just you seeing the sub 90 frames vs it actually framerate spiking and stuttering). I have a 13900k, 4090, 64gb@6400CL30

I run mine at 100% voltage, +100/+200, and 95% power limit and a custom fan curve. Usually between 60 and 90FPS, ocassionally dropping to mid 50's with whats in my sig. I havent checked average power draw, but peak is 454w on the GPU.

Did you have to buy any lighthouses or controllers for it? I have an occulus CV1 with lighthouses I might be able to use, but I'm not sure if the Aero requires them or if it just helps.

I have similar specs (13900k@5.8ghz, 64gb 6400CL30, MSI 4090 Suprim) and I get between 60 and 90 (depending on location, mission, etc) in DCS VR with an HP Reverb G2, 1.0 PD, 100% in OpenXR Companion, Turbo Mode in OpenXR Toolkit, Shaking Reduction @ 10% in OpenXR Toolkit, and some post processing in the toolkit. No FFR, no FSR/NIS/CAS, high settings on all, no SSAO, 2x MSAA, Ultra clouds, ultra visible range. No motion smoothing/repro, Windows 11. No real mods this go around (some missions, but no perf/texture mods)

Yes, you have to uninstall the newer version to go back to the old one.

It has been disabled since I bought the computer. I honestly didnt give it much of an effort to figure it out, as I've spent way too much time fiddling so I just went back to the tried and true 1.1.1 for me. I'll give it another go maybe this weekend. Appreciate all of your efforts regardless! OXR Toolkit has been a gamechanger.

1.1.3 seems to hit my GPU significantly harder than 1.1.1 does. I will say I didn’t uninstall 1.1.1 before installing 1.1.3 but I’m not sure if that would cause it or not. Used the exact same settings (NIS or FSR @ 80, conservative mip, graphic/balanced FFV, 20-40 anti shake, default MR with it set to Auto in OXRDT). I might try to uninstall and retry the new update tomorrow to see if that was it.

It’s a junky engine lol. Think what you want, it was designed a decade ago and not updated or optimized. You can’t “inform” me of anything I don’t already know, so I’m glad you have no time to.

From my understanding, running anything other than a 1.0 PD in DCS with OpenXR causes some issues. I havent tried it yet honestly. When I first tried OpenXR, it was amazing. Then I kept fiddling trying to get that ever last decimal point worth of extra clarity or smoothness (both...really) and screwed it up. It took me a couple days of fiddling and downloading/redownloading files and trying various settings to get back what I had before. Cant really explain it other than theres some weird relationships with the OpenXR files needed that cause things to get wonky if you dont get everything exactly how it needs to be. I have it working great now (well...everything except certain missions in Syria because I'm limited by the junky DCS engine), and its incredible again. But I'm just not fiddling with it anymore lol.

A loooong time to initially compile. I cant remember but probably 15 or so minutes. And yeah, definite gain in terms of smoothness and settings I can run, as well as the albedo supersampling is still incredible and makes it so you can run lower resolutions without any issues.

I just installed Kegety's last night. Works great. I did notice an error in the logs where DCS went to naming the subfolder the .lua is in when using the include function, so I went in and just changed "#include "_HMD.fx" to "#include "deferred/_HMD.fx" or whatever the file name it was referencing is. I also removed the NVG mods as I already have it where I want it with my own tweaks to the DCS files (removed the noise and changed the focal distance so I could see the DDI's).

FYI, I've noticed that some of the random stuttering and frame drops or dropping to super low FPS and getting stuck seems to be if too many registry entries are made for the OXR toolkit. Usually what I do is find what I want it to be by playing with it, then wiping the registry by opening in safe mode and hitting CTRL+F1+F2+F3 to wipe it clean, getting out of DCS and then reopening without the toolkit in safe mode and only touching the settings I want to where I want them. Not sure what it is but its almost like its just causing the CPU to try and compute more than it needs to or something, but that usually helps smooth things back out. worth a try anyway if you're fiddling with it a bunch.

Its not about it being a problem, but its immersion breaking. I'd rather not have to toggle the pilot on and off to see something I could just move my arm or leg slightly to be able to see/reach, so I keep it off. I personally would rather be able to fly unconstrained than just to look at an unbelievable pilot "body" taking up space and obscuring the view. I dont mind having to look around, but the fact that I cant move the limb a bit to help so I dont have to try and crane my neck /body as far is just as bad as not having one there.

What are your settings and what have you tried to alleviate stuttering? If you want to play at a locked 90FPS, it wont happen unless you're running pretty low settings. But even with my PC (see sig for specs) I can run fairly high settings and keep 45fps locked on 90% of maps/missions. The biggest one I have issues with still is a loaded carrier on some missions/campaigns I do. No real issues in multiplayer.

I’ve found one of the most effective things to do when stuttering seems to happen a lot is to rebuild your saved games folder. Rename your current folder to like Dcs.old or something, and then start the game letting it rebuild it. Then move things like your inputs and mods back into it to see if that helps. It has fixed a ton of issues I’ve fought for hours trying to track down.

Loving 14.0. How do you change the noise in the NVG's? Right now it seems like its off (which is something I was struggling trying to modify Kegety's mod to try and get...couldnt stop getting hot pixels that just increased as time went on to where the NVG's were useless), but I'd like to mess around with how much I want to have or if I just like it with no noise at all.

Honestly I had to go back a bit. I'm not saying it will work because its just weird how it interfaces, but I definitely tried a lot of them before I found one that worked. I think I'm on like 2.05 now but I have no way of checking.

Try a earlier version. I dont remembr which one I run, but I run an older version and cant get the newer ones to work. Not sure why tbqh, but I gave up trying after I found one that works.