totally agree with that statement…FIX 254!!!
best iracing experience for me.
from 253 hitting 90fps all the time to 260 with as has been discussed terrible visual quality, and an fps drop to mid 70s to early 80s…
i dont get why they just can’t fix 254 with out all the crap associated with the later versions, it had the most fluid feel out of any of the pi tools.
it’s almost like they are “coding” for the dcs flight sim guys who run low frame rates…the stupid thing about the later releases, is now there is no stutter…almost all the way down to stupidly low frame rates…say 78ish…
all the other headsets stutter when you get below the hmd refresh rate…
not the pimax…i dont get what there doing but to have my 2080S sit at 75% utilisation and won’t render any more than 82fps…is really annoying.
ESP since 253/254 can hit 92% gpu utilisation and smash the framerates…
For the love of something… just re-release 254…stable
As previously stated, for a huge chunk of users the headset was unusable in .180 thru .255. Absolute stutter mess, not even remotely enjoyable. It has been assumed that this is a v-sync or timing issue between the CPU and GPU by users here, because its true that yes .254 has the best pitool performance looking at pure FPS. But it was utterly unstable. It didn’t matter if I ran steamVR at 20% resolution at 64 Hz on a 2070 super, it still stuttered.
Once Pimax was able to replicate the stuttering on their end, they realized they HAVE to fix it. They can’t just ignore users who can’t use their headsets, it’s either release a broken version to the public, or you accept a drop of 10 fps… I’m sure things will improve on this, it is unreasonable to make assumptions about their engineers. To be honest, Pimax does a great job of addressing community issues. Every time I whine it’s fixed or at least acknowledged. Speaks volumes, the support may be slow and poor to communicate, but they deliver eventually.
Agreed. Though they maybe could have had the Studder fix a toggle as now it might also be reversed for the opposite reason. Gpu Catalyst could have been maybe made a a fix toggle to enable.
It is essentially a no win situation for users. Fix for one break for another.
ah crap! now my backlight is apparently stuck on the max setting! what the hell did you do?
i cant change my backlight anymore! how did that infernal backlightsetting slip through QA?
for the first time in month everything was working fine and i go ahead and update… im such a collosal moron sometimes…
at least it still working for you.
I had zero issues since last summer and then updated last month and everything went hell since then. can’t even use it because SteamVR suddenly can’t find my HMD anymore…
This! They don’t have much choice, think you all might have to accept the 10fps loss for now. Pitool needs to be stable first and foremost. There are a large number of complexly different configurations of PC’s. I don’t think this is an easy thing to toggle or test for.
Those that got the extra performance never should have probably had it in the first place. You probably only really got it because they pushed things past a tolerance other companies wouldn’t go past. I like that Pimax sail close to the sun and are happy to push things right to the limit. But it means occasionally they have to row things back, and that’s just something we all have to accept.
For everyone complaining, have you tried pushing the catalyst setting to the max? If that doesn’t work for you, maybe they will refine the feature in the future?
Apart from that, new GPU’s on the way this summer… should ease the tight VR rendering budgets a bit.
Unfortunately the GUI frontend for PiTool 260 crashes every time I start it up, so I’ve reverted back to 258 for now which doesn’t have that issue. Looking forward to testing out the tracking improvements though.
My observation is that .253 has aggressive frame pacing compared to 258+. What that means is you will have torn/jumping frames once in a while with 253, but not with 258+ which produces higher quality better paced image, but at a cost of significantly lower framerate. It’s not correct to compare, but it’s like 253 runs without vsync in 2D monitor terms.
I really wish 258+ allowed to have 253 behavior for poorly optimized games that need every FPS that can be squeezed out. Also, 253 does not render correctly during transitions, causing flickering. Supposedly, catalyst value is exactly that, but problem is that it does not work well. At catalyst == 0, rF2 is 10-15 frames slower than with 253. At any catalyst value above 0 image gets corrupted too much.
Luckily, 253 works fine in both racing and index controller games for me, so I can stay on it for now. Biggest issue with 253 is flickering in menus (when game stops submitting frames).
I’ve been playing around tonight with iRacing and found I was getting better image quality and performance on 260 with the ingame MSAA turned off and Steam at 100%, this is on an 8k+.
Hi! I have a strange wobbly double image in my 5K+ whenever I use 120Hz or 144Hz mode and motion smoothing halves the frame rate. It has been present in all versions of Pitool which have offered the higher refresh rates? The dual image is visible in both screens individually so it is not misalignment of the viewports.
Higher refresh rates work normally if motion smoothing is disabled or it gives full FPS.
I think you are missing where im coming from.
I am mirroring other peoples comments.
Ive only ever had stutter on 253 when driving the graphics rendering too hard.
253, 254 have been Stutter free(As is known 254 for me runs for an hour and then crashes) as long as i dont over drive my system.
I can appreciate that may not be possible with a variety of games,
BUT iracing seems to be very suited to VR,
some would say very well optimised.
So for someone that sim races exclusively i am mirroring what other have said.
254 runs the best of the pitools i have used on the 8k+.
And i just wish they could release that version as it works very well with a moderately hi end system, very good frame rates and gpu utilisation. 2080S i9700K
Would you not be annoyed if you had a 2080TI and couldnt max it out as others have reported ? The engineers have done some trickery in the background to improve a problem that a group of people were having, and i think that great, but 254 showed me how well the headset can go…
Dont try 253, youll be forever disappointed after that
8k+ pitool 1.25 steam VR 100 percent, sharpening at 200 in the ini file, and HDR on make it look amazing in iracing
Did anyone else find that it is not possible to pair a second set of controllers to the headset (5k+) with PiTool 260? After updating PiTool and firmware the pairing button stayed inactive. Therefore I had to revert back to PiTool 258 (but keeping the new firmware) and now I can easily switch between Index an Vive controllers again.
Forgot to mention my HMD & hardware
Pimax 5K+ (203)
Hardware > i9-9900KF / RTX2080Ti
So you switch from 253 to 260 with 144Hz on both ?
For me the image was completely distorted on 253 with 144Hz.
It may depend on the HMD model. Are you on a 5k+ ?
I tried 144Hz on 260 but I had an issue on right eye.
The low half of the right screen was shifted/distorted/wavering : As you can see here
Good Point !
I agree with that and I think most people here too.
When I bought my 5K + I didn’t think I would ever have 120Hz with a Normal FOV (Wich is already big compared with others same price range HMDs).
And today we are complaining that the 144Hz mod does not work !?!! - for me
We’re just excited to take advantage of the updates announced and as users we may be a little frustrated when it turn out to be imperfect or even worse than before.
I just hope that our enthusiastic feedback can serve the PIMAX TEAM, and thanks to their hard work they offer to us the best VR experience possible.
