WipeUout

QVCompanion is good for dynamic foveated rendering, not fixed foveated renderrng. In other words, unless you have eye-tracking it does not give acces to the right variables. The size of the foveated area will not change as it is a different set of values for the fixed foveated. Companion only shows dynamic foveated area H and V sizes. In order to change the values of the fixed area, you need to create a config file as described on the github page of mbuccia's QVFR.

Gave it a try, all running fine but still using Mbuccia's QVFR 1.1.3 which gives better performance and customization.

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%.

Have you checked the log file in the same location as the config file? This will tell you what is being applied and resulting performance. You may also check if the quadviews openXR layer is active in DCS settings by hovering your mouse pointer over the triangle beside the quadviews selection box. The install order may also cause problems, quadviews must be installed after OXRTK.

Definitely less ghosting, no noticeable performance drop or gain, no VRAM saving in DCS VR.

Not sure about that, I believe that barrel distortion correcting is done through shaders, not rendering. In other words, the computer generates the image at the native resolution, then shaders are applied to increase image size (or resolution) in the shape of a barrel to compensate for the pinching effect of lenses. the barrel shaped image has to be bigger in order to fill completely the panel in your HMD, thus exceeding native resolution but the panel in your HMD will never display more pixels than native because it is physicaly impossible. Transforming image by using shaders is much faster than generating an actual rendering and GPUs are very good at this with thousands of computing units to apply the shaders. At least that is my understanding.

Have you tried setting your GPU MSI mode ''on'' and prioritized it? Try the little utility attached. 1. Open ''MSI_util_v3.exe'' as administator 2. Find your GPU and turn on MSI mode if supported 3. Set prioity to high 4. Apply and restart It might help also to set everything else's priority to ''undefined'' and only keep the GPU on high. MSI_util_v3.zip

Some possible problems: 1. Windows 11 23Hxx. Swtiching to 24H2 could improve quite a bit as it is more stable for both AMD and Intel. 2. HAGS on. Since a couple of updates, I started to get stutters and had to disable HAGS, not sure if it is nvidia driver related or windows related but no stutters anymore. 3. Process Lasso. Good tool to ensure DCS gets priority on performance cores for Intel mainly, I find little to no benefit on my 9800x3D compared to my previous 13900k. 4. Overclocking your GPU. In some cases, this can cause stutters even with very light overclocking. Try disabling it if applicable to see if it makes a difference. 5. Caping FPS in DCS. If you cap your FPS at the HMD refresh rate, it could cause stuttering. Try caping 5 fps above your HMD refresh rate, i.e. 95 FPS for a 90hz refresh rate.

null

From my experience, moving to DLSS 4 preset J or K from DLSS 3 increased GPU frametime but provides much better visual that could not be achived. One significant improvement is in MFD screen (in the FA-18 at least). It is always a trade-off and there is no magical gain of performance. With the improved visual quality provided by DLSS 4, I was able to reduce my supersampling and thus bring back down GPU frametime with a net zero increase. As far as CPU load difference, I have not seen much difference.

Again, when DCS crashes completely, what is the status of the HMD in pimaxplay? Is it still connected and tracked? Cable problem can show only in certain games and not all of them. One of my cable was showing issues only in 90hz refresh rate and blacking out, another had interference and the display was showing white dots. I had to replace my cable three times and finally got my hands on a fiber optic cable that is far more reliable. Pimax don't have them in stock but you can find some in Aliexpress for about 200$. But before shelling hard earned money, as suggested by @71st_Mastiff, the latest nvidia driver could also be the issue.