Pimax Users. How Is SU6 Treating You?

[Tinkicker01]

For me, rather unkindly.

I had the misfortune to be hit by a microsoft windows update, a Pimax update and SU6 all at once. The unholy trinity.

The result was a sim that crashed and froze within seconds of entering the cockpit and then entering VR mode.

After almost a full days worth of messing around, it is finally working, albeit with some bouts of horrible stuttering every minute or so.

Firstly, rolled back the windows update, no difference. Next reseated my GPU and RAM sticks, no difference. Next rolled back Pimax Play to 1.44.2, sim no longer crashed, but stuttered really badly, it really was on the brink.

Next deleted Pimax Play completely and did a clean install of PP2.02. Sim runs albeit with the bouts of horrible stuttering.

Half suspected Sim Racing Studio may be the culprit, specifically Motion Compensation. Disabled motion compensation. No change. Closed SRS completely; no change.

Read somewhere that having integrated graphics enabled can cause stuttering, so switched it off in BIOS. No change.
Still the stutters.

During a bout of stutters, I held my head completely still and looked around the cockpit with just my eyes, using the eye tracking. No stutters. Moved my head very slightly, probably less than one inch and the stutters immediately returned.

So it is something to do with head tracking between Pimax play and SU6, something is not happy.

Did a clean install of pimax 1.442 this time. Still have the bouts of stuttering. Updated and did another clean install of pimax 2.02 again. Stutters the same, once every one or two minutes for a few seconds, but only when looking around the cockpit.

Same result with the Blacksquare Turbine Duke, the stock C172 and the A2A Comanche. Its not the aircraft.

From what I can tell from the above, it has to be SU6 causing it.

EDIT. Should state that I cleared the rolling cache at the first moment I had problems.

[Jazzyboy4]

Hi there, Pimax user here, sorry the updates have given you issues.

If you use the on screen fps counter in development mode can you see if it’s a CPU or GPU issue?

This is first move for me to ID the bottleneck.

If you had stable flight before the updates and Windows was one of the updates I’d bet that it is the windows update causing the issues. In this case is it windows version 25H2 and the latest update? Some people have had stuttering with this one I’ve read.

It may be that you have some other issue of course as the whole systems we use are so complex and often pushed to the limit in VR but if you haven’t tried uninstalling the last update that would be worth a try first.

Hope this helps, good luck and please report back.

[Tinkicker01]

Yes it is 25H2 and it did two updates, one was the usual weekly security update and the other was the latest feature update. I rolled back the feature update and kept the security one.

What it did do however, only found after a lot of poking around is that it re enabled USB select suspend yet again and I had to go through every USB hub in device manager once again to switch it back off.

[Zeanuck]

Agreed, this is likely Windows which is causing the problems. As a note, if you do a deep dive into the background slop that Windows runs, you will find a number of useless programs which can be turned off (or shutdown).

Check out VR Optimization (on github), sorry don’t have the link. And when ever you start the sim, open the task manager and quit anything that is not important to running the sim. I have found instances of things like “start experience” “windows update” running without me starting them, another one which is new is the windows “input experience?” Close close all the slop, and that hopefully will help with resources…

[Tinkicker01]

I am absolutely sure it is windows now. Tried DCS using a mission track I had saved and the stuttering is also present there. Using a saved track means I do not have to look around the cockpit to control the aircraft.

If you keep your head absolutely still, no problem. Move your head very very slightly and the stutters return. What ever it is seems to kill the sim when headtracking is doing its thing.

As far as the offending update, you may find another of my posts helpful. This is the very update that came at the same time as SU6 updated.

How Do You Delete The Shader Cache In FS2024?

Having some problems with VR stuttering at low level since SU6. I already dumped my rolling cache folder and rebuilt it, but read that the shader cache can cause stutters if that is not also dumped. Of course, in DCS it is the FXO and Metashader2 folders in saved games that need to get binned after every update, but I have no idea where the shader cache folder can be found in FS2024. Can someone please point me in the right direction.

[Tinkicker01]

Took another look today and removed the offending KB5121003 update via the restore point created when it installed itself.

Tested FS2024 with Beech Turbine Duke and stock airport. No stutters.

Reinstalled my community folder contents and tested FS2024 with inibuilds Leeds Bradford addon airport and overflew photogrammetry Leeds City Centre contained in ORBX GB Central. No stutters.

Reset my textures and original settings and restarted the sim, again from Leeds. Again, no stutters.

Updated Pimax Play to version 2.03 and tested again. No stutters.

This is not an Asobo problem, it is a bad windows update, so if you have stutters in VR, look for
KB5121003 and get rid.

One thing I did have to do was repair FS2024 before it would open, probably because the version numbers were out of synch after the restore. Deffo SU6 I am using now and absolutely stutter free in VR.

Just made a restore point for right now.

[Jazzyboy4]

Yes a bad update indeed but there is a lesson here.

Anytime you have multiple updates eg Windows, Pimax and/or MSFS 2024 say followed by instability, before you tear your hair out and start major fiddling with the Sim suspect Windows Update and 9 times out of 10 you’ll be right.

I actually postpone my windows updates by 5 weeks to alleviate this issue. If there’s a bad update I usually know about it within 7 days and it’s no issue because I haven’t installed it yet! Also within 7 days of a bad update there’s usually a second update to fix the first one. This works really well for me so you might like to try it. Cancel automatic updates in Win Update and you can postpone updates for up to 5 weeks in the dropdown bar. Saves a lot of fiddling I can tell you.

Oh and finally if you do try postponing updates you will have to remember two things. 5 weeks is the Max before your PC will install them automatically so install them before this point. Your PC will warn you an update is available in the taskbar. Secondly after you install the update you will have to redo the postpone thing again. No it’s not hassle free but it is a heck of a lot better than your own PC stuffing you with a bad update.