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.