WipeUout

Entirely possible that lighthouse position tracking compared to SLAM may have a different performance cost. Someone with the crystal lighthouse faceplate could test that. Limiting FPS in DCS has to be slightly above the refresh rate in my case or I get stutters. DCS output varies between 89 and 91 FPS very briefly but enough to cause stutters. My FPS cap in DCS is set at 95 because of that.

That's weird. I flew my FA-18C on Nevada map in a similar fashion and my GPU frametime is between 8.3 and 9.2 ms, no stutters whatsoever. The 8kX has only about half the pixels rendered compared to the Crystal Super but if you are using DFR, you should get decent frametime, certainly lower than 11 ms. This has to be related to settings or something running in the background. Did you tried installing process lasso? It will show what's running in parallel with DCS and you may find the culprit there.

The 22 October did increase frametime for me in my test (FA-18, Caucasus). At first, I though it was related to the visor introduced but I am seeing this increased frametime with all my airplanes by 0,7 to 1 ms. Flying over high density of map objects, such as trees, always caused frametime spikes but it is now more apparent unless I reduce my settings. Using process lasso will certainly help with the random CPU cycle stealing from other programs running in the background and causing stutters but don't expect it will create headroom unless you have something constantly running in the background. The only three ways to regain headroom is lower setting, upgrade hardware or wait for an optimized/improved changed to software. Hopefully the next patch will give us back some headroom.

Anyone tried 1.42 with a Pimax 8kX so far? @Calvin.Pimax : Is it advisable to run 1.42 on an 8kX?

Yes but that is the MSAA mask slider, which is only working if you use MSAA as your AA method and useless for other method such as DLAA. @Mr_sukebe, I suggest you add MSAA between ''VR'' and ''Mask'' in you first post (VR DCS Settings) to avoid confusion with VR mask that is also an option, but in other settings such as in Pimax play (called ''Hidden Area mask''). Very nice post on settings BTW!

null@Mr_sukebe Are you using a special version of DCS? No slider under Enable HMD Mask...

Where do you find this % setting? VR mask is just a tick box in DCS VR settings: null

Only comment is quadviews from Pimax Play is not the most efficient or customizable. I would use mbuccia's quadviews 1.1.3 and switch it off in PiPlay. You just have to install it after pimax play (and anytime after you intall a new version of Pimax Play). Then create a config file following the instructions on the github page where mbuccia's quadviews is. Some people use tally mouse's quadviews companion but it is not meant for HMD without eye tracking, the settings for ''horizontal_fixed_section'' and ''vertical_fixed_section'' is not accessible in the companion. Heres is a simple example of ''settings.cfg'' file: # These settings are for all headsets and applications smoothen_focus_view_edges=0.3 sharpen_focus_view=0.2 [app:DCS] # The settings are specific to the app "DCS World". turbo_mode=0 peripheral_multiplier=0.3 focus_multiplier=1.5 horizontal_fixed_section=0.45 vertical_fixed_section=0.35

Limiting FPS within DCS Settings is good but I have to set it above my HMD refresh rate which It is set now at 90hz. I limit FPS to 95 in DCS because I found out that sometimes, FPS count goes to 91 very briefly and this is causing stutters when the FPS limiter is at 90. Not sure what is happening but setting the limiter above 90 cured the stutters.

NPI 2.4.0.16 Since I am swaping DLL in BIN folder, then my override is off

...not to mention that your settings compared to your hardware capabilities might be the issue...

If like me you are staying away from the NVIDIA App, then it might be that your Nvidia profile is doing an override and using the dll from the display driver instead of the one you copied in the bin folder. Unless the Nvidia driver you have installed contains the latest DLL, this will not work if override is on. I use nvidia profile inspector to direct which dll to use, i.e. the one from the driver (override=on) or the one from the bin folder (override=off).

I did see a small decrease in CPU frametime (about 3%) which could be within the margin of error but as far as quality, very diffcult to assess. There is still some smearing and it seems less than previously but very hard to measure.

If you get this message you can determined which file is causing your integrity check to fail. Juste hover the mouse over the integrity check icon (which will be red if issues) in the multiplayer list and you will see the list of files causing the violation.

I don't have this helo and mission but the cause could be that there are lots of assets on that airfield. Any mission that has many airframes or vehicles added on an area or airfield will cause FPS drop. Although you may have headroom with your GPU, if the CPU rendering thread goes 100%, you will have less FPS eve though your overall CPU usage may be only at 50%.