Worked terrific and I went up to 258b to actually use a backlit 144 hz.
So I got it up to 258b but think if I try the latest 259 I will mess it up again and lose the bright back light.Jesus loves you !
Can anyone provide a link to PiTool version 144? I canât find it anywhere, all the links I find are dead.
Found it and saved: https://community.openmr.ai/t/pitool-firmware-links/26733
Anybody knows why my device pair button is not functionnal with pitool 259 ? The button is black color instead to be blue and clickable like the others. Everytime I switch headset ( Artisan - 5K+ ) I need to reinstall pitool 255 to be able to pair the index controllers with the proper headset.
Itâs the same for me, it must be a pitool problem
Are You sure itâs not just because it switches to 9-axis instead of lighthouse tracking when switching headset?
Defaulting to 9-axis is a new thing, I think.
Iâve always used lighthouse tracking and 9-axis was selected after the update for me.
I noticed that PiTool had selected 9-axis for me too. I think they should change the default, at least if youâve ever run a previous version of PiTool.
I was watching a movie â1917â in VR, but finally decided it was better on my 4K monitor. I hope the 8KX is much better than my 8K, for watching movies. (1917 is a great film, btw, one of the best Iâve seen in years.)
If Youâve run a previous version of PiTool they should just keep the previous valueâŚ
I really donât want to start over every time I update, unless I have to (changing the way settings are saved etc.).
I agree. My point was that if they have added a new value, the default should be the same as what PiTool was defaulting to previously. (I never saw this particular option before.)
I totally agree on thatâŚ
They should make it easy (easier) to just enjoy the devices from the get go. Not everybody wants to scour the web for setup guides every time they want to play some VRâŚ
EDIT: Donât get me wrong. PiTool is definitely moving in the right direction compared to earlier releases so kudos for that!
I been trying this version and no problems at all. Now with normal FOV the values changed it in steam VR, surprised to set it 300% but performance still the same (good of course), on other hand clarity seens a lot better, best version so far.
Thnks Pimax
How about GPU Catalyst in 259 ? Its working better now than in previous realeses ? I have not tested this verison yet ( playing with 253 and afraid dimming issue) but remebered that some racing sims stutter with added Catalyst values.
Hey @Yata_PL i´ve tested it for you real quick. Best setting is still on my sweetspot. If i go other then my sweetspot, game will Stutter/Judder.
Which is unfavorable, because in some GPU demanding Games,my 2080ti is stuck at ~75% of its potential.
From my understanding, GPU Catalyst is not meant to gain more GPU utilization rather then help some GPU´s to fix Stutter/Judder problem.
But if GPU Catalyst is meant to gain GPU utilization/performance, then please Pimax fix this. I would love to see my GPU uses 99% of its potential.
@Alex.liu
It is not that simple. The GPU is not the only bottleneck, it is complex. The GPU catalyst slider is a hack that lets you push past the tolerance of your system but that tolerance is there for a reason; to ensure stability of frame delivery and vertical sync. If pushing it up results in instability for you, then you are already at or close to the maximum level for your system.
If you want to increase your GPU utilization crank up your Supersampling. But I wouldnât overfocus on that number, it is a bit of a red herring.
I agree! This is why Pimax should clearly describe via tool tip what the individual settings are exactly doing. Since most people dont know what the settings are doing or misunderstand the settings in Pitools. It´s obvious that people think, if they crank up âGPU Catalystâ they will gain more performance. Which is not the purpose of that setting.
For example the tool tip for âGPU Catalystâ is: âAdjust carefully, too high value may cause abnormal pictureâ
This leads totaly to misunderstanding or to not understand what it´s for.
It would be very nice, if Pimax could overlook the Tool Tips and give them some in depth explanations for better understandings.
Iâm having the same issue. Pitool logo, then it closes. disappears from the tool tray if I try to click it, Iâm on the 8k, not sure what SN since the sticker text has faded to nothing. I guess Iâll try to reinstall 258.
5K+ latest model (203 I think)
Tested this against 253 pitool - As was the best until this pitool.
No longer is there a performance drop. In fact 253 would have a drop every 2sec in 120hz mode. 259 is rock solid and still with the great performance. Well done Pimax.
I have noticed the most about the improvement in pitool is if you peer through the nose gap the controllers line up exactly with the controllers in both real life and VR. this was not the case with previous pitools. not sure what version this was corrected with but another plus.
144hz mode is just slightly blurry for me than 120hz mode. This is only slightly and most notable in steamvr desktop with text on the screen. I think Ill be staying with 120hz mode for the momdent. Still need to test in skyrimvr to see which I like best as like I said its mainly with desktop text.
And yes I have the dimmed screens
Overall this is the best pitool to date for me. Shame about the dim screens and the slight blur in 144hz. Man if pimax just sorted out there support and order update process they would be killing it with the best HMD.
Tested latest pitool 259 and yesâŚgot dimmed displays too.
Tried reverting back to 255 firmware and still getting dimmed displays.
204 and was on 72 hz before upgrading.
any solution ?
You need to reinstall pitool 144 to have the backlight option available again and set it to high.
Then close everything and reinstall pitool 259.
I am not going to install 259 until majority of sim racers confirm it is faster than 253, but hint for fellow adventurous programmers regarding brightness setting - maybe it is just a registry setting? Registry activity can be monitored using Sysinternals Procmon