Supmua

For me OpenXR increases CPU frametime slightly and at the same time lowers GPU frametime by a bit also. If you have top-tier CPU you may not see this but my 9900K is no longer modern. In any case, the rtx 4090 can flatten GPU frametime so much that you might not need to monitor this and only just CPU frametime, unless the rendering is at crazy high resolution such as 7-8K. When my GPU arrives I’m planning to do full analysis, and if the current CPU performance is not satisfactory might upgrade to 5800X3D to get by until super fast DDR5 RAM and next gen motherboards become widely available and cheaper. This route seems the most economical with the ability to reuse my RAM.

Guess you got lucky then.... Do me a favor. In NV control panel, change VR latency (might be called pre-rendering frames) to 3 or higher and VSync to fast. See if that affects the stuttering behavior?

CPU frametime dropped as much as 3-4ms with the 4090. I bet you’ll see better results with the default VR preset vs High, even better with custom settings. Can probably eliminate CPU FT spikes by reducing rendering res a bit too. Finally a good GPU for SC operation for high-res VR headsets. Using a standard preset for testing like this is good because everyone can reproduce and compare.

The next RTX will prob be in 2 years, and unless NVIDIA can make a big performance jump like this time again expect the usual 30-35% improvement from the 4090. The high-end GPU is getting up to a point that it's not really much of a factor in performance now, it's the CPU that really needs to catch up in single core performance as long as we don't have multi-core DCS engine.

For the current DCS you mostly need rasterization power from GPU (brute force if you will) as DLSS or RT isn't supported, you can use upscaling tech such as FSR or NIS though. In general, fast single core CPU, fast GPU, fast memory (can also make a big diff). Knowing how to fine-tune the settings can help a lot too. MSFS supports DLSS so it's a bit different, don't know much about IL-2 but it uses older engine so likely similar to DCS in terms of requirement.

It was Syria + Apache though which is a bad combo for VR. The frametimes are highly dependent on DCS settings also (as well as rendering pixels). You can see my fpsVR grab above in much less stressful scenario and I rendered at slightly higher res than his, but used my own custom settings instead of High preset (which is very taxing for VR). It's all about tuning and reducing things to get the frametime numbers that you want. With fine-tuning of DCS settings I bet I can make that scene much better in GPU performance (but the overall fps already at >45 fps so not much of a point doing it) at slightly reduced image quality. The CPU is still going to drag the final fps down so it won't get to 90 in this map, but DCS on the Aero with locked 45 fps is very very good (except for this ongoing tearing issue which is probably related to the new NVIDIA driver). You can run OXRTK with the G2 and check those frametimes in real-time also, it's in the advanced tab (the unit is in ns instead of ms with OXRTK). I do it all the time when I run it in OpenXR mode, everybody should do this since it tells you exactly what's going on with the CPU and GPU and you can fine tune your setup and settings this way to get the performance you want.

Seems like it might help a bit with bottlenecking.

It's interesting that CPU frametime also dropped a few ms? Wonder why...but in any case this is a good thing.

Setting up some stuff to get ready for benchmarking with my 4090, won't have the card until midweek. The fpsVR grab below is what I get with the default Harrier Caucasus Free Flight right now (9900K HT off/3090), ALT around 1500-1600 ft. CPU frametime is pretty good on this mission and I'm pretty sure the GPU frametime will drop below 11ms with the 4090 which means I get 90 fps. This is sort of best case scenario with light flying mission in a VR friendly aircraft. Varjo Aero OpenVR mode at 3144 Horizontal pixels per screen (Very High setting on the headset but reduced SS to 76%, frame locked at 45 fps, Reshade 5 for sharpening and color correction). null

Seeing GPU frametime down to 7 ms (from 13s) at high setting in ACC is kind of crazy. Looking forward to trying this too.

So are we discussing 3090 vs 4090 here or is it going to be yet another Intel vs AMD thread?

Looking forward to experiencing it myself lol. EDIT: Actually, I'm experiencing this now with the 3090 after the new driver update 522.25. Just ran some tests and tearing now occurs in the yaw axis (rotating head side to side), there was no such behavior with the previous driver (In the past only movement in straight forward motion (up-down, left-right) would induce tearing but never rotational such as with yaw or pitch axis. I see this in both OpenVR and OpenXR mode in DCS. This also happens with VR desktop apps especially when foveation is used (more pronounced in Varjo's Workspace vs Virtual Desktop app). This might be the same issue that people with 4090 are experiencing, maybe to a lesser degree on the 3090. It almost feels like a latency issue, but the reported display latency is 19.5ms in the analytics window which seems alright. This is also independent from framerate, occurs event at 90 fps.

For now don’t move your head around too much or too quickly when you fly, lol.

So Pimax also stutters at max FOV? What's the common denominator here, NVIDIA software?

That's a pretty strong statement considering the 13900K isn't even out yet. Not quite the right thread, but the 13900K is no slouch especially at 1% percentile fps besides avg fps.

With my current setup I get good CPU frametimes in some maps (9ms Harrier Caucasus free flight, 11ms Hornet Syria Freeflight), so I’m hoping to see some 90 fps especially when up in the air. My card was shipped last night so hoping to post some numbers next week although there’s some issues between the 4090 and Varjo Aero currently.

The latest NVIDIA driver 522.25 seems to cause slight tearing in yaw axis on my system (turning head side to side), prior to the update this only occurs with rolling or rapid movement in lateral axis. This is with OpenVR, will test OpenXR tomorrow as well as other games to see if this is reproducible. On a positive note, Newegg shipped my Asus TUF 4090 so I’ll get to mess around soon and see what’s going on with the current complaints on the Varjo discord.

As seen on several tech sites, increase the power and voltage limiters a bit, and the clockspeed can be pushed up to a whopping 3GHz while core temp remains at 70C. Mem speed can go up to 22 Gbps also. The 4090 is an overclocking monster for those who need it as the stock cooler is already very good, power draw goes up to 500W though.

Have to say discord isn’t my cup of tea, more of a quick chat platform. Maybe I’m too old school. Seems like a few people experienced similar stuttering issues when turning side to side, I wonder if this is universal or is it something in lieu of the blur issue that doesn’t happen with everybody.

This isn’t anything new (current 4090 issues), remember the Vive Pro 2 fiasco with the stuttering problem when it first came out, or the Aero with bad distortion with early software? It happens with any brand new product and it will eventually get sorted out. It’s early adopter’s problem, sometimes it’s better to wait out, but I just gotta jump in.

I can’t see how selling high end cards would make them a lot of money just bragging rights and reputation, the enthusiast/hard core market segment is very small. The biggest revenue would be from mid-tier/lower end products that millions of people would buy.

I don’t have high hope for the MeganX, also look what happened with the Arpara that received all the hypes back then being innovative with pancake OLED and so on. The demand isn’t there now. The next VR HMD will need to have some major breakthrough features or really good pricing to get people excited again.

The 4080 16GB has better fps than 3090Ti in recently leaked game benchmarks, and this is not simply synthetic benchmarks. So it’s a faster card plus DLSS3 and better raytracing, just lower amount of VRAM. But I still think the 4090 is the better bang for bucks especially for VR with significant shift in performance.

Hard for me to comment since I still don't have the card, but as an early adopter this isn't anything new especially with a brand new product like this. There's bound to be glitches, but the real question is can you do something right now as a workaround to make it work until the problem is fixed.

I mostly play SP as well, and sometimes I hosted with 2-3 other guys. My CPU hasn't really been a problem and I either have fpsVR or OXRTK window on all the time to track performance.