I am on .129 and the Index controllers work great. I used the old driver hack posted around here somewhere, then refreshed the firmware using the other trick (noHMD) and it works great.
1 Like
Hey guys!
I got an update from Alex about the DEFAULT-tweak. They are still working to find a âfixâ for this so we always get the full GPU utilization. But for now, he have discovered what was blocking this âtweakâ to trigger in PiTool 132 and 144. They changed something in the LibPVRClient64.dll file upon version 132 that was supposed to fix some ghosting issue, but at the same time this blocked the âtweakâ. So Alex have compiled a new dll file as a temporary fix.
So to get the high GPU utilization working again (with better FPS) in PiTool 132 and 144, do this:
-
Download the file âLibPVRClient64.dllâ (from my Google Drive):
PiTool fix - Google Drive -
Stop or close down Piservicelauncher (or preferrably all Pi-services running)
-
Replace the current LibPVRClient64.dll file in C:\Windows\System32
with the new file. -
Reboot your PC.
-
Now, you should be able to do the âDefault button tweakâ again, and get up to 40% more fps.
I just tested and confirmed this in Hellblade an hour ago, see how it changes the GPU utilzation and fps:
(yes I know the temps are really high in this test, but it doesnt matter if its 45 degrees or 70+ degrees in this case. I had the fans on minimum here)
So now, lets just hope they find a permanent solution for this, so we dont need to do this manuuallyâŚ
7 Likes
Thanks.
Is this a rollback of the ghosting fix, or just a rollback on what was blocking the trick while maintaining the ghosting fix ?
1 Like
I assume its a rollback including the new fix for ghosting, but I must double check⌠Gimme a moment!
Edit: Nope, unfortunately its the DLL before ghosting was fixed. Not that I have noticed the ghosting really when using SmartSmoothing on and off, but I understand this might be a deal breaker for some people.
At least they are working to add the âtweakâ ability again including the new ghosting fix, for the next updateâŚ
1 Like
Well, the ghosting is quite heavy on Project CARS 2 (looks almost like temporal anti-aliasing), but itâs not so unbearable that I would pass on the performance gain this tweak bring.
Thank you for the confirmation.
1 Like
Interesting, I will test, thanks. I just tried DCS World with SS a moment ago at stable 45fps, and I was surprised the stutters/ghosting while rolling the aircraft were completely gone in 144, even when using the old DLL.
1 Like
Sweviver Did Nvidia respond to you, or acknowledge the problem,
Ok I am experiencing strange resultsâŚ
If I launched the Pcars 2 with Steam and PP, the trick doesnât work.
If I launch Pcars 2 without Steam and no PP, GPU usage is aound 90%, without any trick (I just downloaded your dll file), while frame rate is around 25 fps, but the picture is betterâŚ
This is interesting and weird. If theyâre able to add the ability to use the trick again, surely they know then whatâs caused it to go away and also whatâs causing it in the first place?
Hopefully we get a resolution to this soon. Itâs so nice being able to use the whole GPU!
1 Like
Check your reported target resolution in steamVR or fpsVR, PP mode has higher target resolutions which would explain the heavier GPU workload.
EDIT: found an old post of mine:
https://community.openmr.ai/t/psa-pitool-render-resolutions-are-not-linear/12079?u=milopapa
The actual numbers have probably changed since, but you can see that with normal FOV, the workload difference used to be 50% between PP OFF and PP ON.
2 Likes
No unfortunately nothing yetâŚ
Thats strange. I see a difference regarding of using PP on or off, but the performance increase in PC2 is rather small compared to other titles and sims.
Btw, 25fps frame rate sounds very low. Are you using very high supersampling or an older GPU?
The interesting thing is that when having PP enabled, decreasing the render quality in PiTool from 1.0 to 0.75 gives basically no difference in image sharpness or clarity. This lowers the total target resolution to a more reasonable level. Give it a go and let me know what you think!
I got a 2080 ti but Pitools was at 1 or 1.25 with MSAA high and everything on ultra, that could be the reason 
Anyway, the game already shines with SmartSmoothing. I wonât say no to further optimisations but itâs already acceptable for me.
BTW, the picture is really different with and without PP. I donât know why it is the case, and itâs hard to say which one is better tooâŚ
Yeah Smart Smoothing does wonders for PC2! For me I actually get better results running at PiTool 1.0 or even 0.75 and bumping up the in-game resolution scale to 1.5/1.6 or higher. Looks very similar to PiTool 1.0 or 1.25 on standard settings, but with better frame rates. Have you tried that?
3 Likes
I didnât try that, I thought that it would be the same thing as increasing the pitool settings !
Ok Iâll try that as soon as possible !
Do you have a description on the software you use?
Thanks Martin, I just tried it, what a difference in performance! I can set in game ss at 2.0 and itâs buttersmooth with smartsmoothing, you just made my day 
4 Likes
Well, Pitool supersamping (coefficient applied to both height and width, so squared coefficient is applied to the number of pixel) doesnât work the same way as SteamVR supersampling (coefficient directly applied to the number of pixel), so maybe the in-game supersampling is based on SteamVR method, which is lighter.
2 Likes
I tried your trick. I am not convinced that low Pitools//high in game SS is more efficientâŚ(because itâs quite hard to note the visual differences between each settings).
Otherwise it is a good way to fine tune the visuals/framerate.
Currently Im using ther latest Nvidia drivers, latest PiTool + that DLL file I mentioned.
The monitoring software I use is NZXT CAM and latest MSI Afterburner.
Basically no settings needs to be set in the above software, to get the âtrickâ to work.