Pitool 260 So far, so good

i’m back to v.253. I have ZERO problems with it, maximum FPS and good resolution (im set SS to 2.0)
no stutter at all. Never. And good tracking.

v.260 - less FPS, less picture quality (a bit). Worse tracking (HMD starting move left-right when one of Base station not visible. v.253 tracking much better. (using Vive 1.0 stations with 5.2m between them)

CPU: 8700k 5.2ghz
GPU: RTX2080ti overclocked 2.1ghz

14 Likes

I’m back to 259, am I the only one that has an issue with the brightness changing on its own? When there’s much bright stuff on the screen the whole backlight brightness gets turned up and when I look at something dim it gets darkend. The change is jarring, it’s like if someone is playing with the lightswitch all the time! So annoying!

That’s really strange. Are you certain the backlight is changing? Is it possible that you have set the Contrast value very high in PiTool? That might cause some brightness shifts. Try setting it to 0 or +1, if it’s higher than that.

No, contrast was set to the standard value of 0.
The issues also went away with installing 259 again.
Are you sure you don’t have the issue yourself? It’s mostly apparent in darker environments. If you look at something bright in the center of the screen the whole screen will get brighter like a light switch being turned on and if you look away it’s turned off again. Only in version 260

v 261 anyone? Is it same as 260 just bug fixed?

Just some bug fixes mainly. See release notes as there posted now.

1 Like

v261:
Selection button added for native resolution and scaled-up resolution.

Is it for 8kX only?

I assume we’ll need a new thread, but with 259/260/261 I get a warning that my 5700XT driver is too old. I’m on the latest build 20.5.1.

Stephen

the latest 260 version won’t let me pair new device for some reason, have to go back to the old version

1 Like

Are on 260 or 261? Also verify Lighthouse tracking is still on as installing 260 was defaulting to lighthouse tracking off.

3 Likes

Any change on 261 for utilisation?

259, 260, 261… all that we want is a 254 version with a fix for crashing issue.

5 Likes

253 not bad too. Its almost same as 254.
I dont understand why Pimax programers cant make adaptive gfx core, so its will work with any configuration fine. Ive think they are more creative :slight_smile:

look: i have really heavy power gfx config (overclocked 2080ti) and 253-254 just fine for me (never had problems with them)
But ive heard some ppls has problems with stutter etc.

OMG just write some internal test for gfx sybsystem so Pitool core will adapt for user gfx card.
So ppl with 2080ti will have nice utilization… and ppl with 1060 will have no stutter!

Just test gfx system delays and speed every time piservice starting so it can adapt for any user configuration! Its only way to make things better.
I dont want to lose 20% fps because ppl with low-end gfx cards have a stutter with 253 pitool core.
I dont want to lose pic quality because ppl with low-end gfx cant use old Pitool SS 2.0 resolution.

7 Likes

Pimax test on an old 9800GT graphics card

1 What do you mean by distortion profiles are cool?

  1. 144hz mode got a performance boost?

  2. What gpu do you have?

people with 2080tis stuttered too, my 2070 super and 1080 did as well. Idk, ive seen all system specs do it, but you’d imagine theres a root cause

Hey could you describe the “crashing issue” on 254? I have a new Artisan, and on 254 (and several others maybe) I get a “headset disconnected” bug. I’ve tried re-seating the cables, and it’s not a USB unplug event. But the headset in PiTool goes to the red “disconnected” icon. Is that the crashing issue on 254, or something different?

2 Likes

Yes that´s the bug. 254 HMD randomly disconnects at around 1h playtime.

1 Like

Funny, I had never had this issue with 254a.

1 Like

ive never had any stutter at all (with any versions) i dont even know what is it :smiley:

1 Like