Issue with pimax 4k and new steamvr patch 1.2.7 (latest stable version - released 19/1/19)

Hi Pimax,

@Pimax-Support @Sean.Huang @anon74848233

Please note i have found an issue on the latest steamvr version that was released this today with the Pimax 4k. I have tested this on both my test machines that have Pimax 4k, this evening, steamvr has patched the production platform version 1.2.7 of steamvr. when using pimax in steamvr, after a while the game locks up with a black screen and steamvr needs to be closed completely and reloaded. - other applications in the background are still running.

Playing the game without steamvr works fine (using 3 screens and single screen), and has been running for over 2 hours without fault. but when i switch to VR, the game crashes to a black screen and needs to be forced closed.

i then tried a few other things like recording VR gamplay to both youtube and twitch to see if i get any other errors… i got a BOSD with the WHEA uncorrectable error - which usually means drivers, but this has only happened since the steamvr patch this evening.

I have checked the steam forums and at this time there are no posts referring to this issue, but i am getting this problem on both my test machines.

i have produced a steamvr log file and note that there are a lot of

  • aapvr: fail to ReleaseSync with err:-2005270527 errors in that file.
    the log file is very big and i am unable to upload txt files, so let me know if you want me to email it to you? here is a section of the log file with the errors mentioned:

Fri Jan 18 2019 21:06:58.046 - Using existing HMD aapvr.Rift P1
Fri Jan 18 2019 21:06:58.046 - Processing message VRMsg_Connect from Steam (8540) took 0.00661 seconds
Fri Jan 18 2019 21:06:58.075 - Adding application manifest path: D:\Program Files (x86)\Steam\config\steamapps.vrmanifest
Fri Jan 18 2019 21:06:58.118 - Invalid input type click for controller (/user/head/proximity)
Fri Jan 18 2019 21:06:58.129 - [Settings] Save Json Settings to C:\Users\Mike\AppData\Local\openvr\steamvr.vrsettings
Fri Jan 18 2019 21:07:22.671 - 0 - entering standby
Fri Jan 18 2019 21:07:22.772 - aapvr: no layer to present.
Fri Jan 18 2019 21:07:22.772 - aapvr: fail to ReleaseSync with err:-2005270527
Fri Jan 18 2019 21:07:22.873 - aapvr: no layer to present.
Fri Jan 18 2019 21:07:22.873 - aapvr: fail to ReleaseSync with err:-2005270527
Fri Jan 18 2019 21:07:22.974 - aapvr: no layer to present.
Fri Jan 18 2019 21:07:22.974 - aapvr: fail to ReleaseSync with err:-2005270527
Fri Jan 18 2019 21:07:23.075 - aapvr: no layer to present.
Fri Jan 18 2019 21:07:23.075 - aapvr: fail to ReleaseSync with err:-2005270527
Fri Jan 18 2019 21:07:23.176 - aapvr: no layer to present.
Fri Jan 18 2019 21:07:23.176 - aapvr: fail to ReleaseSync with err:-2005270527

Eno

3 Likes

@Sean.Huang
@Alan.sun
Please see this 4K issue

I contacted with my Tech support colleague for fix this headset issue for you.

Please follow these steps:

click the “Support” button on the banner for submit your issue
2.Give me your question number for teach support to contact with you via service desk
3.The issue will be solved soon

@anon74848233

raised ticket ‘1. SUPEN-1287’

thanks

Eno

1 Like

Thanks… Will wait for reply

1 Like