So much this.
I can never overstate the capacity @fearlessfrog has to both synthetize and simplifying complex concepts into a digestible form.
I believe the external scripting is responsible for the most annoying lag spikes. Even when you have the most advanced CPU & GPU, you will notice when poorly optimized scripting kicks in. This could be related to path finding or other AI logic.
Lua is still a fast language, probably the best for this kind of job, so no blame there. The scripting initiated action just would be better off in its own thread. This means some data synchronization, but would be worth it.
My two cents in case someone is interested what it gives on a PC sporting [email protected], 2080ti and G2 (not being too much different from @fearlessfrog specs, the results are pretty similar )
Test environment:
MiG-21 Instant Action - Take off.
Sorry for no DCS graphics settings - mostly high, but surely constant throughout testing.
Plain vanilla (no OpenVR FSR goodness):
DCS PD: 1.0
SteamVR SS: 60%
FPS: 50-54 fps
OpenVR FSR:
DCS PD: 1.0
SteamVR SS: 60%
OpenVR FSR: 0.75 / 0.75 (default settings)
FPS: 60-64 fps
So here we go with the expected 20% of fps increase. As for visual quality - yeah, there is definitely loss of clarity but I would rate it less than 20% so in the end it feels like we are getting a free lunch here (a small one but stillâŠ).
Now, what does that mean in practical terms? The OpenVR FSR stuff does not tip me over to the native 90 fps - so I am still in the reprojection area. No change on this front. However, in the testing scenario I have noticed that forcing the reprojection gives actually smoother results with the OpenVR FSR than without. Most likely due to lower frequency of the fps dipping below 45. For me that means that I will use it only when I need it for the fluidity - like when flying the MiG-19 and MiG-21 which are more demanding in terms of performance than other modules I flew till now.
One more testing: since the OpenVR FSR upscaler is more efficient than the SteamVR one, I tried to achieve a situation where DCS renders at G2 native resolution of 2160x2160 and the OpenVR FSR upscales the image to the G2 recommended SS of 100% in SteamVR (around 3200x3200). IIRC this has been achieved by SteamVR SS at 100% and OpenVR FSR at 0.8. The performance was on par with my Plain vanilla (see above) scenario so the upscaler is indeed superior to the SteamVR one.
All in all: I will use it sur mesure depending on the modules I fly. I also disabled the OpenVR FSR sharpening and kept the Reshade sharpen mod since it gives me also a slight colour correction which I like.
Thanks @fearlessfrog for posting this! I hope it keeps improving (and once it is perfect, DCS will switch to Vulcan )
Does this work for upscaling a single viewport as well?
Thatâs nice of you to say so @komemiute - thank you.
I thought there might be a general ReShade hook for FSR on 2D by now but on a quick peek not finding anything? I guess this thing being a VR driver hook can get between the device and the game and do the fake resolution and then upscaling thing, so not sure if it can be made 2D without game support.
They could add this to DCS natively without much trouble, the algorithm/code is open source and it wouldnât take a lot of effort - it would work in 2D and for VR - similar to how they added SSAA.
flholger is doing a new build to fix it for IL-2 based on some stuff I sent them. If you are super keen you can grab a fixed build here:
In some quick testing it means IL-2 BoX is pretty much a solid 90 FPS for me in VR, plus looks great.
So, recap.
I buy an overpriced GPU and build a new PC around it.
China cracks down on cryptomining and prices drop as GPU availability increases.
In the meantime the world finds new ways of increasing the perfomance of the simulators that I enjoy, making my investment totally unecessaryâŠ
That about right?
Almost.
At some point you may be able to run DCS/IL2 in native 90 fps whereas the others will be still stuck at (smoother) reprojection
trying this out for DCS, in my log I get error 108 in both eyes when MSAA is on, is this expected behavior?
Do you have a VIVE? Is the USB in the right port of the headset? Make sure is in the middle port.
Negative, index, game is running in VR just fine, not super happy with the graphical artifacts this mod is producing and trying to run down If these errors are to blame
Ah ok. Sorry then
I saw in the reddit thread that others were running ok with MSAA at either x2 or x4 so it might be something specific to your set-up. A 108 is headset not found, so maybe power/USB/device issues? I would also try the SteamVR beta/not beta dance as well. It might be worth adding an issue at the Github in the first post, as the mod author seems quite active.
good call, done.
I just got a letter from the Canadian government saying that due to COVID Relief Package Bravo Sierra I get to pick up my fully assembled VR sim cockpit this afternoon. They are issuing them to everyone here apparently. It comes with a note saying âSorry about the SchuremSlitâ. Weird eh?
On my box, itâs highly unstable. I did a repair, but still it crashes about five minutes into a 1v1 QMB run.
Not really. Totally in line with my expectationsâŠ
I played for about a hour and it worked ok. It might be worth reporting that here, as GPU or set-up dependent, plus might be something in the log file that helps - Projection/inclination correction (so far only observed in IL-2 Sturmovik) · Issue #3 · fholger/openvr_fsr · GitHub
Hey guys, just an FYI on the current release, RC2, I get a huge fps boost, like in one mission flying the AV-8B from the Tarawa in broken skies, in VR getting ~45 fps sitting in parking with engines running, but ~ 70 fps with FSR enabled. The problem is that when I click fly, there is about a 2 second lag before spawning in the cockpit (normally instantaneous) and often it crashes with VR blue screen the headset, SteamVR, and DCS in that order. To keep it easily reproducible, Iâm using the default openvr_mod.cfg setting, SVR:100% resolution RP on, and DCS: 1 PD and VR preset. System is Z5 5600X / RTX3080 / 32GB, latest DCS ob build and Nvidia âGame Readyâ drivers.
I donât remember this being an issue with earlier FSR builds, but havenât had time to try them or alternate openvr_mod.cfg settings.