MrShipwreck

The Aero runs at 90 Hz, and so I capped my output at 90 FPS via OXR Toolkit in 2.7. With high settings basically across the board (with the exception of clouds, which I couldn't care less about and that chew up performance, but even still had set to normal.) Those settings were essentially solid at 90, with excursions above and below that were well within acceptable range and still quite enough for play matching refresh rate without issues. Tested in the F-16C on Caucasus ready-on-ramp and in free flight (and through numerous training flights and the like.) With the update, I didn't change a thing. Loaded up the F-16C free flight module mission over Caucasus and it's 62 FPS right off the bat, dropping considerably when I look at clouds (into the low 40's!) Even with shadows off and clouds at low. When the clouds are out of the picture it will climb up to 72 FPS, but generally gets no higher. The settings I have to use just to achieve those numbers are worse, overall, than the settings I had in 2.7. Not sure what ED is talking about when they try to suggest they made VR optimizations, because they most certainly did not; especially when it comes to the 'new' clouds, which chew up about 30 frames on their own when set to high, yet still look like a pixelated mess. Or perhaps they thought they did, but then never bothered to actually test it, because just 10 seconds in game with a VR headset on would've shown the tester that whatever changes were made had a major negative impact on performance. I've since decided to downgrade back to 2.7 and forego any multiplayer, for the simple fact that the performance hit is so egregious. 60 FPS doesn't sound bad on paper, but when taken against the refresh rate of 90 Hz on the HMD it creates problems like stuttering, doubling, and smearing when moving the head from side to side. It's also problematic when the FPS are that low to start because they take such a dramatic hit now under certain circumstances.. Like any time I look at a cloud. Considering the raw horsepower of my system, those numbers are crazy bad. I get that it's a beta, and things are bound to go wrong, but this feels like it wasn't tested at all. One step forward, two steps back.

Replying to confirm significant drops in VR performance after updating to 2.8. In 2.7 I was able to achieve 90 FPS stable at the settings I had implemented; however, when I updated to 2.8 I saw a 30+ FPS average drop. Whereas before I was getting 90 FPS average (85-95 range), in 2.8 with the same settings I was seeing 60 FPS (52-62 range), often dipping below and rarely climbing above (except when looking at something like open, empty sky.) System: 12900KF, 32 GB DDR5, RTX4090, all NVMe storage, running on a Varjo Aero HMD at 39 PPD through OpenComposite. I've since had to redo my settings. They are lower overall than they were previously, and still I only see 72 FPS average in game (whereas in 2.7 these settings would have pushed over 100 FPS on my system.)