Those of you 5K+ owners that have been experiencing this jitter again with Pitool versions newer than 144, please post the three first numbers of your headset serial number.
I’m just curious if this is just one more bonus for us 5K+ owners with the S/N starting 202 which seem to come with the “black dots” panels and which also seem incapable of 120Hz.
I’ve had it with two separate headsets to varying degrees. One bought in Feb and one a month ago which I’ll presume is newer. I’m not at home to check the number of my current headset. But both were bought much later than the black dot models and I’m running 120hz just fine.
But I’ll point out for the nth time. Pimax have previously fixed this issue. Ie. Made it disappear completely via a software update. So that remains within their power to do again.
You are right. The jitter is gone in Pitool versions .132 and .144 but then reintroduced in versions .180 and .192
If you are capable of 120Hz then you probably have a 5K+ headset with the S/N starting 203, this gives even a bit comfort that these jitters are not just one more fault with the headsets with the S/N starting 202 exclusively…
@Alex.liu are you aware of this issue?
But than i have to adjust the smart smoothing for every single game, thats not ideal.
My Serial Number is
SN: 2036…
hi trevorVR
i think big possible the high gpu usage rate cause this issue .so i consider that add a menu to djust the gpu usage rate to solve the issue.
@Alex.liu Hopefully this does not mean that when the fix to utilize the full potential of the GPU is enabled the trade off is the stutters, and when the fix is not applied and the GPU is not utilized to its full potential the stutters are gone.
If that is the case then perhaps some slider to adjust the GPU utilization rate would be good so that if the maximum utilization setting starts to cause stutters in some cases, you could slide it a bit down until the stutters are gone.
I had the same issue on 180. What helped me was to go into PiTool’s settings, turnt “startup on Windows start” off, then set everything to what I wanted, and restarted the Computer. On next startup, PiTool was not loaded.
Now start SteamVR -> Game. Picked that up on the Facebook group.
The hick-ups are gone!
Great tip! It might be worth trying this: Just stop (quit) PiTool before running your game. I haven’t noticed this, but my i7 8700K has 6 cores / 12 threads and it’s possible the stuttering might be more of a problem on a CPU with fewer cores.
So the solution is to just stop using the Pimax Software lol
Your still using the software just exiting the overlay interface.
Not really. pi_server, PiService, PiServiceLauncher still run. PiTool does not run.
It still helps. So it must be something with PiTool. Is it pulling something it shouldn’t? I don’t care what it is, what I care about is that I have tested it on and off during multiple runs, and that the testruns confirm 100% that it stops the excessive frametime spikes every 20 seconds.
Yep just exit pitool for now.
Really, I’m feeling so “happy” right now about Pimax software engineers I can’t explain it with words.
I recently bought this rig:
AMD Ryzen 5 3600 @3.60ghz
Kingston HyperX Predator DDR4 3200 PC4-25600 16GB 2x8GB CL16
MSI B450 Gaming Plus MAX
Corsair RM650 650W 80 Plus Gold
SSD M.2 2280 500GB
NVIDIA 1080 Ti MSI AERO
Pimax 8K
Well, everything works great except VR is a vomit inducing stutter fest with Pimax 8k. Got absolutely crazy trying everything, reinstall Windows, every USB port, removing every USB device to make sure it wasn’t a power issue, covering half my room with blankets to avoid any possible reflection, reinstalling steamvr, trying beta, every config in Pitool, downgrading graphics to DK2 levels, every lighthouse placerment I could think of, to finally discover that the latest, official, stable v1.0.0.197 Pitool ready to download in their website is a stupid mess and downgrading to 144 fixed that issue completely, I can’t believe my mind about this, I really have no words.
How on Earth this is v1.0.0.197 the official Pitool version? What the hell have they done to make VR a stutter mess just for the driver alone, and keep it there? How can we be years from the Kickstarter and still have this alpha level of support? Yeah sorry for the rant, but after a week of testing everything I could think of, I’m pretty angry right now that it was a stupid software design on their official driver…
And at least thank God for the Pimax community and being able to find this topic, otherwise Pimax 8K would be in Ebay right now, though I’d probably get it back when someone tried v1.0.0.197 and said the device was broken.
You seem to be running quite similar setup to mine. I have:
and Pimax 5k+ (BTW: I have P5k+ with “black dots” i.e. the S/N starting with 202). After installing v1.0.1.197 I had to revert back both PiTool and Firmware because I got regular stuttering in Elite. PiTool version, which works for me is the ancient v1.0.1.132.
I wonder if the newly released beta has changed anything.
I also wonder if someone with P5k+ and AMD CPU + 1080 Ti GPU observes the similar behavior?
Have you tried @Douglaster reccommendation moving Pimax & steamvr processes to last core with high affinity?
As I recall he said it improved performance & reduced stutter/judder
Since the PiTool works quite well in the old version, I assume the problem is in PiTool and not in CPU affinity. Besides, playing with the affinity is basically the last thing you (me) want to do, because it screws up the automatic scheduler and usually makes things works (in a general sense).
the only thing that helps remedy this is setting vr pre rendered frames to 2 in nvidia control panel and closing pitool. Even then it’s still there, just less. I’m willing to try the affinity deal but agree with risa. Frustrating that this isn’t addressed with the new pitool. .132 is OLD
Might have to dust off the 5k+ as I mainly stick with the 8k. I haven’t had the judder issue. But haven’t played ED yet either.