Date:
Issue Title:
Description:
HMD Model:
First 3 Numbers Serial:
Pitool Version:
HMD Firmware:
Tracking:
System Info
- Windows Version:
- CPU:
- RAM:
- Motherboard:
- GPU Model:
- GPU Driver:
- SteamVR Version:
- Oculus Version:
Date:
Issue Title:
Description:
HMD Model:
First 3 Numbers Serial:
Pitool Version:
HMD Firmware:
Tracking:
Date: 20. Dezember 2019
Issue Title: Headset not recognized
Description: Pitool .245 does not recognize headset running dfu .255
HMD Model: 5K+
First 3 Numbers Serial: 204
Pitool Version: .245
HMD Firmware: .255
Tracking: 2x HTC Lighthouse 1.0
Logfiles from ~\AppData.… folders enclosed:
We can’t currently create threads from within the Pitool subcatagories and the only Catagory available to select if we create a thread from the main page is Pitool-Discussions.
I’m not sure if you want to fix that or have us submit bug reports uner Pitool-Discussion instead or just respond in this threa as Jocool has
FIXED
It seems that first firmware update didn’t work. It worked after a re-install of .249
Date: 2019-12-28 (Date of test)
Issue Title: Connection issue with .249 on serial 203…
Description:
I can’t use version .249 FW255. I have to force it to connect by restarting the service and after about 20 minutes of play, it disconnects and the screens turn black. When it does that, I need to exit everything and restart the service for another 20 minutes of play.
The serial number of my 5K+ starts with 203.
I re-installed .197 and everything is back to normal and working.
HMD Model: 5K+
First 3 Numbers Serial: 203
Pitool Version: .249
HMD Firmware: 2.1.255.255
Tracking: One V1 Base Station
Date: 01/07/2020
Issue Title: Pimax 5k+ Sparkle Grid
Description: A horizontal sparking grid appears in the lower half of the right panel. The issue appeared following upgrade to latest PiTool and firmware versions. Note, the issue began as intermittent which seemed to relate to power and/or performance draw on the system; however, now the issue is constant. Issue occurs on all 120 to 72hz ranges.
HMD Model: 5k+
First 3 Numbers Serial: 203
Pitool Version: V1.0.1.245
HMD Firmware: V2.1.255.255
Tracking: Lighthouse tracking
YouTube Video of issue:
FIXED
It seems that first firmware update didn’t work. It worked after a re-install of .249
hi
my 5k+(serial 204) firmware 244 pitool 197
run at 120htz large fov and pitool 1 steamvr 130
3525x2987
but 100 its a little better 3092x2620
and i run at oround 100 /120 fps with many cars
my config /
i7 6850k
rtx2080ti
32go 3200
super smooth
no problem +++
Date: 10-01-2020
Issue Title: Vibrating image when Motion Smoothing is active
Description: When motion smoothing is active the image vibrates, it seems like the reprojected image is slightly out of position creating a vibrating image.
HMD Model: Pimax 5k+
First 3 Numbers Serial: 204
Pitool Version: .249
HMD Firmware: FW255
Tracking: No tracking
Date: 13 January 2020
Issue Title: Light Bar Color not saved
Description: When changing the light bar color for the headset, after a computer reboot, it reverts back to the default color.
HMD Model: 5K XR
First 3 Numbers Serial: 201
Pitool Version: 1.0.1.197
HMD Firmware: 2.1.255.244
Tracking: Lighthouse x 2
This is the log from my windows event viewer:
Faulting application name: pi_overlay.exe, version: 0.0.0.0, time stamp: 0x5e1316f9
Faulting module name: pi_overlay.exe, version: 0.0.0.0, time stamp: 0x5e1316f9
Exception code: 0xc0000005
Fault offset: 0x000000000001dce4
Faulting process id: 0x3394
Faulting application start time: 0x01d5d2cd606e219d
Faulting application path: C:\Program Files\Pimax\Runtime\pi_overlay.exe
Faulting module path: C:\Program Files\Pimax\Runtime\pi_overlay.exe
Report Id: c663a74b-5ecb-4135-a2b3-ab703afd743e
Faulting package full name:
Faulting package-relative application ID:
Going back to Pitool 1.0.1.253 again.
Date: 26/01/2020
Issue Title: Pitool 254 alpha crashing
Description: After installing 254a my VR would keep crashing after a short time of use. I think it was pi_server crashing. Rolling back to 253 has stopped the crashing.
HMD Model: 5k+
First 3 Numbers Serial: 204
Pitool Version: 254a
HMD Firmware: 255
Tracking: NA
Date: 28/01/2020
Issue Title: Pitool 254 alpha crashing
Description: After installing 254a my VR crashs after approximately one hour. Older versions of PiTool do not exhibit this, I have rolled back to .249
HMD Model: 5k+
First 3 Numbers Serial: 203
Pitool Version: 254a
HMD Firmware: 255
Tracking: NA
Date: 12/02/2020
Issue Title: Movement latency at 65Hz
Description: When rotating or bobbing the head while at 65Hz the world slightly drags behind. Instant nausea guaranteed. Similar to what was a problem with the original 8K in the past. It does not appear on 90Hz or on 120Hz.
HMD Model: 5K+
First 3 Numbers Serial: 204
Pitool Version: 254
HMD Firmware: 255
Tracking: 2 x Lighthouse v 1.0
Date: 18/03/2020
Issue Title: Refresh rates don’t work, still capped at 90fps
Description: I just installed the latest FW release that was meant to add a new refresh rate tp SN204 but I am still capped at 90fps and no other refresh rate works.
HMD Model: 5k+
First 3 Numbers Serial: 204
Pitool Version: 258
HMD Firmware: 263
Tracking: No Tracking
Isn’t the latest firmware 255? Have I missed a 263?
Date: 2020-04-04
Issue Title: PiTool “My Games” doesn’t handle launch options
Description: Elite Dangerous (as an example) in order to work with canted displays needs to be launched via the EliteDangerous64.exe with a “ServerToken” option (with the user’s server token) (also requires adding some OpenVR files - see links at bottom). Currently the executable can be added (or a link to the executable with the ServerToken option), however PiTool ignores it and launches EliteDangerous64.exe without options. It enters the game (and works without SteamVR and with canted display compatibility) but can’t progress further in the game due to lack of the Server Token.
Adding game links via “Import” in “My Games”. Tried various ways:
Created link with ServerToken option (link works by itself). Launching link with PiTool it skips link and adds executable.
Tried adding batch file with options. Batch file launches correctly with “ServerToken Option” by itself. Launching in PiTool results in 10-12 cmd windows and no launch.
Tried adding executable directly (game launches and “works” however without ServerToken option, unable to actually play).
Converted batch file to exe. Again, works fine by itself, does not work with PiTool (Game launches but preview window is now upside down and again, no ServerToken option was passed).
Possible Fixes
Adding the ability to read in options or just launch links (with options).
Adding a field to add launch options in the “My Game” category.
HMD Model: 5k+
First 3 Numbers Serial: 203
Pitool Version: V1.0.1.249 (254-255 had performance issues)
HMD Firmware: V2.1.255.255
Tracking: Lighthouse
More info on what I’m trying to do:
(Posted in wrong section before)