Occasional stutter/judder issue finally solved by Pimax!

In this version, we have also added the ability to enable/disable Screen Saver mode and Standby mode (GPU saver mode, which puts the headset into 15fps or so).
Unfortunately it got called “Open the screen saver” and “Open the standby mode”, but we will rename it later on in next version…

Another fix is the random disconnection/shut down of the headset after longer use, which is now fixed.

So far so good, seems stable and I cant see any stutters on my both PCs.


Do we know if they resolved the 45min - 1hour resets people have been having - memory leak?

Update - thanks for pointing it out…: YES!


You just got it in the message above.


As I told you I don’t use UAC and that file only contains the Games settings and not the HMD settings so I don’t know where the refresh rate is held maybe you can find out.

You might be able to use something like Process Monitor from SysInternals (Microsoft now) to see what files are read and written to disk. You can filter on specific file names to see if they write/fail to write and find out why.


In the Basic Release Notes of the Pitool
Appears : “Image stutter optimized”? That sounds that still has problems?

1 Like

It’s been awhile since I looked but check the pitool install directory if mem serves there is a json file there.

1 Like

The stutters seems gone now. We have done a lot of testing. But I also know the engineers are still looking for further improvements, and you cant know for sure its fixed in every single scenario, so they prefer to call it “optimized”…


Check your PM regarding new features. There is 2 additional layout options for posting pics vs the default. :beers::sunglasses::+1::sparkles:


In the release notes, I would rather say:

Basic Release Notes

  1. Enable/disable screensaver/screen protection mode added
  2. Enable/disable standby/sleep mode added

Or something like that. Because these features were already existing, but always on before.


Yeah just got a basic set. As you have been testing it out give me additional info and will update.

Still need to get them to post info like “Compatible with Oculus.sdk vX.X”


Congratulations to Pimax engineers; the people who are testing this new version find it much more stable and, at least for the time being, they do not detect any problems.
Although they comment that they feel that it loses some performance, although they are not sure.
In any case, they seem to prefer this version 255.


Yes, it somehow does make a hit on the performance, at least compared to 254, but I much rather prefer 255 solving the occasional stutters and stability.


The hmd_settings.json is in the Runtime folder in Program Files and PiTool doesn’t seem to be writing to it. How do I get it to do that?

Did you try to uninstall PiTool, remove all Pimax-related folders, and reinstall PiTool with Administrator rights?

The folders are:
C:\Program Files\Pimax


To be honest will need to take a better look when I get a chance. There maybe json files in one of the sub directories. Won’t have time to take a look til later tonight.

Please lets discuss the new PiTool here instead:


Yeah, a small loss in performance is definitely worth it. First and foremost you need to be stable, then you can start thinking about performance.


With most things, I would agree with that logic. However, with VR, at least on the sim side, we are pushing well within 10% of failure to render at any usable framerate.

Consequently, both performance and stability are absolutely non-optional.

Hopefully, I will find the performance loss is a multi-threaded CPU issue, so it does not actually add to frame latency in the more critical use cases.

1 Like

But performance you can always influence (e.g. lower resolution or graphics details or even play something else less demanding). Image might not be so pretty but it is at least usable.

Stability you can’t influence much if it is caused by SW (and not overheating or something). So I would say stability is still more important.