Ahhhh. Guess I missed the X vs V thing. Thanks.
1 Like
Good point! The first time I tried both, it kinda looked bad, since both were sharpening. I turned off the sharpening component of ReShade and like what Iâm seeing. Tried it the other way and was getting frame times around 16ms, with FSR and sharpening on OpenVrPerf Kit, Iâm getting more like 12, so I think Iâll keep it off on ReShade.
1 Like
Okay so, I know itâs working (can see the âringâ about the center; little loss in sharpness; none of it significant). Perhaps I just had my âthingâ tuned pretty well (mentioned elsewhere, mostly clean OS and driver).
There is maybe a little bit there, perhaps 2% if I had to nail it down. Iâll leave it on for while.
NIS at 80%
The OpenVR settings at .7 (or was it .8? - took the settings from one mentioned above).
PD 1.0, SteamVR | All = 80%, SteamVR | DCS = 100%. Clarity was very much the same, perceived.
My âbenchmarkâ flight is:
3080Ti, AMD 5900X, 64mb RAM, M.2 drive
Syria, sunrise, over Aleppo at 16,500. Plenty of buildings and such below.
Hornet
My usual settings
Then I do a âStuka Maneuverâ, leveling out to put on on an airshow amid the satellite antennas on the roof tops, etc.
Only time I could get it into the low 40âs was when I touched some [setting] buttons Iâve never dared to (with my old box: 1080). I even tried: Shadows High, And default (terrain shadows); Ultra clouds with Overcast 5 preset.
Of course this isnât with many other objects in mission (planes, trains, automobiles - and tanks, APCâs, etc).
Even so it was basically smooth - I love being able to look to my 3/9 Oâclock and NOT see any âghostingâ (I think itâs called - were at those angles it kind of âstuttersâ). And do hard rolls that are smooth over a populated areas. Easier to spot stuff out the side too when itâs not âskippingâ like that.
Canât wait til they optimize DCS. Maybe the addition of a lot of objects (things to do âcombatâ against) wonât be such a drag. Though Iâve not really tired a âheavyâ object count mission yet.
2 Likes
I launch with these changes from default config, albeit changeable with hotkeys, to get a sharper HUD. Performance hit is minor and mostly imperceptible to me. I use the VR preset with MSAA 2x.
method: nis
renderScale: 0.8
sharpness: 0.9
Use shift as the hotkey modifier, except for the second F1, which I keep alt.
1 Like
Iâd forgotten about that one with the new box. It worked on the old one as a starting point, but was, on that GPU/CPU, not so pleasing visually. Iâll check it out.
One extra note if useful: If you run with SteamVR (and WMR with those headsets) Motion Reprojection on you wonât see a lot of framerate change, just because it will either stay at 45 FPS or 90 FPS, but not varying in-between. What you will get is that it stays in reprojection a lot easier with more things happening, because at 0.8 youâre effectively telling DCS to draw a 20% smaller output and then this thing is upscaling it.
When I did the benchmark graphs above to see the improvement this gives (roughly 20%) then I have to turn off any reprojection.
Yeah, I think that your new rig is a little faster than mine Jeff, so you might be able to push the settings a bit more.
Good one. I thought that I had it disabled, but I am seeing a lot of 90 on the top end and 45 on the bottom (Syria).
1 Like
Check. I turned off repro for the tests. I never ran with it on on the old 1080 - it just âfeltâ better overall without it. On this new box, for now, it just seems âbetterâ likely as you say cuz it stays in repro more easily.
1 Like
Yeah, getting a solid 90 on Syria reliably is beyond where we are with the DCS engine today, regardless of any hardware I think. My goal on that map (a beautiful one for sure) is just to try stay above 45 as much as possible.
1 Like
Same. Man, itâs so tempting to start sliiiiiidddingg things to the right. Iâm resisting this, mostly. I love the smoothy-ness. And I guess clarity-wise Iâm keeping it at whatâs acceptable to me. Iâm half blind up close (far-sighted) thoughâŠso that helps!?
Naturally what I REALLY want is about 60-degrees more FOV. Iâm never happy 
3 Likes
You could bump up the SteamVR resolution a tad? If youâre overall at 80% and then DCS at 100% of that then I would be tempted to try 100% overall. The DCS value doesnât override it, it multiplies it (e.g. 100% in DCS of the 80%).
I have the G2 and the 3080 Ti on 100% SteamVR / DCS PD 1.0 / 100% and it is super sharp (although as I often point out, sharp because I like to see small MFDs / instruments and thereâs shimmer and outside âover-clarityâ - some would call it ugly!). I donât run MSAA, as in VR I think pushing the resolution up higher is a better deal than DCSâs MSAA implementation cost in high resolutions. DCS desperately needs a CAS shader (which we are kind of doing ourselves here), plus a fast version of TAA - the MSAA we have in VR doesnât scale at all.
2 Likes
Going to test it with that mission generator app (name escapes me at the moment) tomorrow, set on high. That thing killed my old box, even on low, and Iâm pretty sure it had little to do with the GPU. Iâm curious.
One nice way of reducing MSAA performance impact is using the mask size in DCS VR settings. Just set it to lowest and MSAA will be applied to about the G2 sharpest area. The corner aliasing does not matter that much anyway.
1 Like
Liberation was the name. Yeah, it destroys my expensive little play thing. Only tested in 2D and where Iâd get ~190FPS Iâm now at 20-30. This is Syria with a Liberation miz perf. est. at 2/3. Culling of course gains back ~15-20 FPS, so that helps, something DCS seems incapable of by nature at this time.
This is why my little Lua Thing keeps it to âlow intensityâ (think: COIN - type ops) missions. I use culling too but I just see no way DCS can do any serious combat as is. So, we waitâŠ
Hello all
Just had a long test with vrperfkit Together with the universal VR shader mod. Works great, seeing a performance increase and the visuals are great.
Only one strange phenomena - sometimes when pressing Ctrl (when trying to increase time compression or ejecting) a red overlay appear around a clear circle in the middle of the view. Not sure where itâs coming from, I presume it could be connected to an hmd mask size option but never seen that before.
Anyone got a clue?
1 Like
Thatâs the debug mode mask popping up. It seems to sometimes get a little excited to see me and prematurely pops up whenever I hit shift, and not just shift-F1. In your case Ctrl-F1 should make it go away.
1 Like
Coincidentally, I was also experimenting with the VR Performance Toolkit yesterday, and I noticed the same phenomenon. WarPig is correct, itâs the debug mode, and the solution for me was to disable hotkeys via vrperfkit.yml. Look for hotkeys:, enabled:, and change the value from true to false. Problem solved.
1 Like
Or change the modifier to âshiftâ and comment out any conflicts or commands that you donât need. I like having the hotkeys enabled, but I guess if you have arrived at your happy place, you might not need them.
I like them too, at least once a flight I play with something, but then put it right back, so I guess I just need them to remind myself how perfect I have it set, lol!
Questions:
Has anyone else tried the Fixed Foveated thing to see if itâs actually working? No detectable change here, I suspect itâs like the MSA Mask setting in DCS that doesnât do anything (yet?).
I tried it and it didnât help. I think the Fixed Foveated doesnât really help with DCS performance because it uses something called a Deferred Rendering Pipeline (rather than the more normal Forward Rendering) and does something weird with how it outputs a texture per eye. A previous experimental version of this listed the games it was tried on with some notes on each one: