[Replied]Pimax 5k+ stuck in standby

[Clinch]

@Douglaster

I believe they are created after you run the initial setup.

I’ve never been able to do a room setup with the lighthouses active because the lack of tracking won’t allow me to proceed. I’ve only done the room setup for seated playing. If that’s what you mean by initial setup.

Just in case I’m doing something stupid as I’m a VR-newbie, this is my entire course of action for setting it up:

Installed SteamVR.
Installed PiTool.
Mounted and plugged in one lighthouse which is ~1,5m away and aimed at my seat and set to channel A.
Started the headset.
Attempted to run room setup (but unable to proceed due to no tracking).

Am I missing something here?

@TrevorVR

@Clinch try running the setup as admin.

Good idea. I’ll give that a shot.
EDIT: Didn’t do any difference. No folder created and no tracking working when the lighthouse is enabled (again, the headset tracking works perfectly with the lighthouse disabled).

[TrevorVR]

Wasn’t there some talk before about how you need two basestations in the initial setup…?
And after the setup you can play with only one.

I think they fixed that though.
I’m out of ideas, sorry.

[Clinch]

@TrevorVR

Wasn’t there some talk before about how you need two basestations in the initial setup…?
And after the setup you can play with only one.

I think they fixed that though.

No idea. I’ve just seen (old) information saying that playing with one lighthouse is fine. If two are required for the initial setup then all of this sure would make sense.

I really hope my ordered power cable for my second lighthouse shows up before the weekend so I can actually try it out and know for sure.

If that does not solve it, my next course of action would be to find out why the lighthouse folder is not being created, and after that flash the firmware.

Thanks a lot for the help though, all of you. Very much appreciated.

[V.Anaconda]

I had the same issue.
Accidentally turn the headset upside down.
And that fixed it.
Try it. It might work for you too.
Lol

[TrevorVR]

Ok just to confirm I installed the Pitool in my laptop and it didn’t create the folder.

[Clinch]

@V.Anaconda

I had the same issue.
Accidentally turn the headset upside down.
And that fixed it.
Try it. It might work for you too.
Lol

I’ve turned it in all manners of directions, different distances etc. Didn’t work.

@TrevorVR

Ok just to confirm I installed the Pitool in my laptop and it didn’t create the folder.

That’s good to know. I guess they’re created by the room setup then?

[Douglaster]

Here, just put the folder inside this .rar inside your runtime folder.

https://ufile.io/scxi5

I believe it will work but the Lighthouses will be wrong positioned, as will your playspace.

But if it manage to wakeup your HMD, you could redo the VR area setup.

[risa2000]

@Clinch

The only weird thing in the diagnostic is Steam VR. I have reinstalled it twice and it keeps saying so. But my issue appears already in PiTool, so not sure if it could be related.

Can you check in SteamVR logs, in particular in “vrserver.txt” (choose “create system report” in SteamVR drop down menu) search for “aapvr” driver. It may give some hints what is happening with the driver initialization for Pimax.

[cruser_icu]

Hey Clinch ,
May be a dumb question but did you try to swap the lighthouses out?

[Clinch]

@Douglaster

Here, just put the folder inside this .rar inside your runtime folder.

I believe it will work but the Lighthouses will be wrong positioned, as will your playspace.

But if it manage to wakeup your HMD, you could redo the VR area setup.

Good idea but it still wasn’t able to use it and just prompted me for room setup (which it then can’t complete). Might be because of an id mismatch between the device in the config and the one I use.

@risa2000

Can you check in SteamVR logs, in particular in “vrserver.txt” (choose “create system report” in SteamVR drop down menu) search for “aapvr” driver. It may give some hints what is happening with the driver initialization for Pimax.

Here’s the whole output:

SteamVR System Report created Wed Feb 13 22:19:42 2019

<Report>
SteamVR Version:	1.2.10 (1548804153)
SteamVR Date:	2019-01-30
Steam:	Public
Steam Branch:	
Steam AppID:	250820
Tracking:	aapvr
OS:	Windows 10
OS Version:	10.0.0.16299
Direct Mode Vendor:	NVIDIA
Direct Mode Version:	418.81
Admin:	No
AsyncReprojection:	Disabled
Performance drops:	0/1 0/2 0/3 0/4 452/452
Display Mode:	Direct Mode
</Report>

<Displays>
DeviceName:	\\.\DISPLAY1
DeviceDirectMode:	No
DevicePrimary:	Yes
DeviceRect:	2560x1440 @ (0, 0)
DeviceString:	NVIDIA GeForce GTX 1080 Ti
DeviceID:	PCI\VEN_10DE&DEV_1B06&SUBSYS_85EA1043&REV_A1
DeviceKey:	\Registry\Machine\System\CurrentControlSet\Control\Video\{4E015418-8293-11E8-9D28-F07959DBDD18}\0000
DeviceMonitorCount:	1
Monitor 0 DeviceName:	\\.\DISPLAY1\Monitor0
Monitor 0 DeviceString:	Generic PnP Monitor
Monitor 0 DeviceID:	MONITOR\ACR0408\{4d36e96e-e325-11ce-bfc1-08002be10318}\0005
Monitor 0 DeviceKey:	\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0005

DeviceName:	\\.\DISPLAY2
DeviceDirectMode:	No
DevicePrimary:	No
DeviceRect:	2560x1440 @ (2560, 0)
DeviceString:	NVIDIA GeForce GTX 1080 Ti
DeviceID:	PCI\VEN_10DE&DEV_1B06&SUBSYS_85EA1043&REV_A1
DeviceKey:	\Registry\Machine\System\CurrentControlSet\Control\Video\{4E015418-8293-11E8-9D28-F07959DBDD18}\0001
DeviceMonitorCount:	1
Monitor 0 DeviceName:	\\.\DISPLAY2\Monitor0
Monitor 0 DeviceString:	Generic PnP Monitor
Monitor 0 DeviceID:	MONITOR\AOC3279\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007
Monitor 0 DeviceKey:	\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007

</Displays>

<Devices>
Device 1 - Pimax P2C Headset Vive MV HTC
Device Path:	/devices/aapvr/Pimax P2C
Best Alias:	/user/head
Firmware: 	
Hardware Revision: 	
Camera Firmware: 	Version not available.
VSync to Photons: 	0.0111112
Display Frequency:	89.9995
User IPD (m):	0.063
Current Universe ID:	30
Previous Universe ID:	30

Device 2 - PVR_Tracking_camera_0 Base PVR Tracking device HTC
Device Path:	/devices/aapvr/PVR_Tracking_camera_0
Firmware: 	
Hardware Revision: 	
Radio Version: 	Feature not configured for this device.
Channel: 	
FOV Left: 	60
FOV Right:	60
FOV Top:	60
FOV Bottom:	60
Range Minimum (m):	0.5
Range Maximum (m):	5

</Devices>

<USB>
    [HostController] USB xHCI Compliant Host Controller
    Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 17-Jul-18, 10.0.16299.579
        Root Hub
            [Port1]
            [Port2]
            [Port3]
            [Port4]
            [Port5]
            [Port6]: Generic USB Hub
                [Port1]
                [Port2]
                [Port3]: USB Composite Device (VID:28DE PID:2300), Valve, LHR, LHR-1FB0AA7B
                [Port4]: USB Composite Device (VID:0483 PID:0101), Pimax VR, Inc., Pimax P2C, 260084901223
                [Port5]: USB Composite Device (VID:0D8C PID:0013), C-Media Electronics Inc., USB Audio Device
                [Port6]: USB Input Device (VID:28DE PID:2101), Valve Software, Watchman Dongle, 5437C6B533
                [Port7]: USB Input Device (VID:28DE PID:2101), Valve Software, Watchman Dongle, 08B066E0B8
            [Port7]
            [Port8]
            [Port9]: Generic USB Hub
                [Port1]
                [Port2]: USB Composite Device (VID:1038 PID:1212), SteelSeries
                [Port3]: USB Composite Device (VID:1038 PID:1217), SteelSeries, SteelSeries H Wireless
            [Port10]: Generic USB Hub
                [Port1]
                [Port2]
                [Port3]
                [Port4]: USB Composite Device (VID:1532 PID:0067), Razer, Razer Naga Trinity, 00000000001A
            [Port11]: ASUS USB-BT400 (VID:0B05 PID:17CB), Broadcom Corp, BCM920702 Bluetooth 4.0, 5CF3707A46AD
            [Port12]
            [Port13]
            [Port14]: USB Composite Device (VID:1B1C PID:1B2D), Corsair, Corsair Gaming K95 RGB PLATINUM Keyboard, 1400E013AF1C88A459DCBF81F5001BC7
            [Port15]
            [Port16]
            [Port17]
            [Port18]
            [Port19]
            [Port20]
            [Port21]: Generic SuperSpeed USB Hub
                [Port1]
                [Port2]
                [Port3]
                [Port4]

    [HostController] USB xHCI Compliant Host Controller
    Manufacturer: Generic USB xHCI Host Controller, Provider: Microsoft, 17-Jul-18, 10.0.16299.579
        Root Hub
            [Port1]
            [Port2]
            [Port3]
            [Port4]

    [HostController] Standard Enhanced PCI to USB Host Controller
    Manufacturer: (Standard USB Host Controller), Provider: Microsoft, 21-Jun-06, 10.0.16299.522
        Root Hub
            [Port1]: Generic USB Hub
                [Port1]
                [Port2]
                [Port3]
                [Port4]
                [Port5]
                [Port6]
                [Port7]
                [Port8]
            [Port2]

    [HostController] Standard Enhanced PCI to USB Host Controller
    Manufacturer: (Standard USB Host Controller), Provider: Microsoft, 21-Jun-06, 10.0.16299.522
        Root Hub
            [Port1]: Generic USB Hub
                [Port1]
                [Port2]
                [Port3]
                [Port4]
                [Port5]
                [Port6]
            [Port2]

</USB>

<Logs>
C:/Users/OMITTED/AppData/Local/openvr/vrserver.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrmonitor.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_vrmonitor.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrcompositor.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_vrcompositor.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/firmware_update.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrserver.previous.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrdashboard.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_vrstartup.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_steamtours.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_steamvr_room_setup.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrclient_steamvr_tutorial.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/vrwebhelper.txt is not available.

C:/Users/OMITTED/AppData/Local/openvr/properties.json is not available.

</Logs>

<Configuration>
Runtime Directory:	C:\Program Files (x86)\Steam\steamapps\common\SteamVR\
Log Directory:	C:\Users\OMITTED\AppData\Local\openvr
Config Directory:	C:\Users\OMITTED\AppData\Local\openvr
Driver0:	C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr
</Configuration>

<ConfigFile>
{
   "DismissedWarnings" : {
      "DismissableWarning_RunTutorialAgain" : true
   },
   "GpuSpeed" : {
      "gpuSpeed0" : 1089,
      "gpuSpeed1" : 1076,
      "gpuSpeed2" : 926,
      "gpuSpeedCount" : 3,
      "gpuSpeedDriver" : "25.21.14.1881",
      "gpuSpeedHorsepower" : 1030,
      "gpuSpeedRenderTargetScale" : 0.68000000715255737,
      "gpuSpeedVendor" : "NVIDIA GeForce GTX 1080 Ti",
      "gpuSpeedVersion" : 2
   },
   "LastKnown" : {
      "HMDManufacturer" : "HTC",
      "HMDModel" : "Vive MV"
   },
   "steamvr" : {
      "installID" : "7164690471248931424",
      "lastVersionNotice" : "1.2.10",
      "lastVersionNoticeDate" : "1548809190",
      "mirrorViewGeometry" : "777 469 720 400"
   }
}
</ConfigFile>

<Chaperone>
Play Area Size:	None found
Collision Bounds:	None found
</Chaperone>

<ChaperoneFile>
</ChaperoneFile>

<LighthouseDB>
</LighthouseDB>

@cruser_icu

Hey Clinch ,
May be a dumb question but did you try to swap the lighthouses out?

Not at all. And yes, I have tried with both (but running one at a time).

[cruser_icu]

@Clinch

“DismissedWarnings” : { “DismissableWarning_RunTutorialAgain” : true

Can you edit the config file and change the true to false?

[risa2000]

@Clinch

C:/Users/OMITTED/AppData/Local/openvr/vrserver.txt is not available.

This is strange. It looks like your SteamVR is not creating any log file. Can you check if anything is wrong with C:/Users/OMITTED/AppData/Local/openvr directory?
Normally, you should have all the files which are marked in your log as “not available”.

EDIT: Interestingly, I checked my config and my log directory defaults to D:\Games\Steam\logs i.e. the folder is in root directory of my Steam installation. Might be related to the fact that this folder is RW, while if I installed it into C:\Program Files\blabla it would not.

You can also change the log directory in SteamVR settings → Developers → Path

[Clinch]

@cruser_icu

Can you edit the config file and change the true to false?

I’ll give it a try as soon as I get home from work.

@risa2000

This is strange. It looks like your SteamVR is not creating any log file. Can you check if anything is wrong with C:/Users/OMITTED/AppData/Local/openvr directory?
Normally, you should have all the files which are marked in your log as “not available”.

EDIT: Interestingly, I checked my config and my log directory defaults to D:\Games\Steam\logs i.e. the folder is in root directory of my Steam installation. Might be related to the fact that this folder is RW, while if I installed it into C:\Program Files\blabla it would not.

You can also change the log directory in SteamVR settings → Developers → Path

I’m not at home right now, but I remember seeing something odd. There was more than one user with a similar name to mine. Probably because my last name has region-specific letters that some systems probably can’t handle, so it replaces it with encoding. The correct name is where most of my stuff is, but there were some (iirc mostly empty) folders, which might have been named “openvr” under the incorrect username. Won’t know for sure until I get home though.

The log I generated was shown directly in SteamVR, so it never output it to a file from what I could find. I’ll double check this info and give it a shot in a few hours.

[risa2000]

@Clinch

The log I generated was shown directly in SteamVR, so it never output it to a file from what I could find. I’ll double check this info and give it a shot in a few hours.

When you run “Create system report” then on the tab “Logs” you should see log files for all different components of SteamVR:

[Clinch]

It was as I remembered. I had a second windows user folder for where (I assume) SteamVR has tried to place some files because it couldn’t find my regular user (most likely due to region specific characters in my name). I changed the config and log folders of SteamVR to be within its directory now instead. Still getting the “Abnormality” result for SteamVR when running PiTool diagnostics though.

Here is my vsserver.txt file just from the past few minutes or so. I’m getting flooded with one error in particular. So something is almost certainly off. Does this help?

vrserver.txt Thu Feb 14 2019 18:02:45.965

Thu Feb 14 2019 18:02:45.965 - //==============================================================================================

Thu Feb 14 2019 18:02:45.965 - ================================================================================================

Thu Feb 14 2019 18:02:45.965 - ================================================================================================

Thu Feb 14 2019 18:02:45.965 - vrserver.exe startup with PID=14556, config=C:/Program Files (x86)/Steam/steamapps/common/SteamVR/bin/win64/config, runtime=C:\Program Files (x86)\Steam\steamapps\common\SteamVR

Thu Feb 14 2019 18:02:45.966 - Runtime path was C:\Program Files (x86)\Steam\steamapps\common\SteamVR. Setting it to C:\Program Files (x86)\Steam\steamapps\common\SteamVR\ to match vrserver.exe

Thu Feb 14 2019 18:02:45.968 - Setting shared memory namespace to 14556

Thu Feb 14 2019 18:02:45.968 - VR server (v1548804153) starting up with config=C:/Program Files (x86)/Steam/steamapps/common/SteamVR/bin/win64/config

Thu Feb 14 2019 18:02:45.968 - VRServer will wait for VRMonitor before exiting

Thu Feb 14 2019 18:02:45.974 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings

Thu Feb 14 2019 18:02:45.974 - [Settings] Load Default Json Settings from C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr\resources\settings\default.vrsettings

Thu Feb 14 2019 18:02:45.974 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\htc\resources\settings\default.vrsettings

Thu Feb 14 2019 18:02:45.974 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettings

Thu Feb 14 2019 18:02:45.974 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettings

Thu Feb 14 2019 18:02:45.975 - [Settings] Load Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\config\steamvr.vrsettings

Thu Feb 14 2019 18:02:45.981 - Unable to read app config file from C:/Program Files (x86)/Steam/steamapps/common/SteamVR/bin/win64/config\appconfig.json. No applications will be available

Thu Feb 14 2019 18:02:45.989 - Add Json firmware manifest from {htc}/firmware/manifest.vrfirmware

Thu Feb 14 2019 18:02:45.990 - Add Json firmware manifest from {lighthouse}/firmware/manifest.vrfirmware

Thu Feb 14 2019 18:02:45.990 - [Web] Starting web server on port localhost:8998

Thu Feb 14 2019 18:02:46.052 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrstartup.exe (VRApplication_Bootstrapper) (Args: ) 13928

Thu Feb 14 2019 18:02:46.056 - Setting app openvr.component.vrstartup PID to 13928

Thu Feb 14 2019 18:02:46.148 - aapvr: add hmd device.

Thu Feb 14 2019 18:02:46.187 - Driver 'aapvr' started activation of tracked device with serial number 'Pimax P2C'

Thu Feb 14 2019 18:02:46.187 - driver aapvr implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_005 IVRDisplayComponent_002 IVRDriverDirectModeComponent_005 IVRCameraComponent_002 IServerTrackedDeviceProvider_004 IVRWatchdogProvider_001 IVRVirtualDisplay_002 IVRDriverManager_001 IVRResources_001 IVRCompositorPluginProvider_001

Thu Feb 14 2019 18:02:46.187 - Loaded server driver aapvr (IServerTrackedDeviceProvider_004) from C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr\bin\win64\driver_aapvr.dll

Thu Feb 14 2019 18:02:46.187 - aapvr: hidden area mesh vertex count:0

Thu Feb 14 2019 18:02:46.187 - aapvr: hidden area mesh vertex count:0

Thu Feb 14 2019 18:02:46.188 - Active HMD set to aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.188 - Using display adapter luid: 52784

Thu Feb 14 2019 18:02:46.188 - Adding controller type to aapvr_hmd

Thu Feb 14 2019 18:02:46.188 - DXGI thread failed to get SDL display index

Thu Feb 14 2019 18:02:46.188 - Driver 'aapvr' finished adding tracked device with serial number 'Pimax P2C'

Thu Feb 14 2019 18:02:46.189 - driver gamepad implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_005 IVRDisplayComponent_002 IVRDriverDirectModeComponent_005 IVRCameraComponent_003 IServerTrackedDeviceProvider_004 IVRWatchdogProvider_001 IVRVirtualDisplay_002 IVRDriverManager_001 IVRResources_001 IVRCompositorPluginProvider_001

Thu Feb 14 2019 18:02:46.189 - Loaded server driver gamepad (IServerTrackedDeviceProvider_004) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\gamepad\bin\win64\driver_gamepad.dll

Thu Feb 14 2019 18:02:46.189 - Processing message VRMsg_Connect from vrstartup (13928) took 0.137 seconds

Thu Feb 14 2019 18:02:46.189 - Failed to read chaperone file from C:/Program Files (x86)/Steam/steamapps/common/SteamVR/bin/win64/config\chaperone_info.vrchap

Thu Feb 14 2019 18:02:46.189 - aapvr: add tracker device 0

Thu Feb 14 2019 18:02:46.189 - Driver 'aapvr' started activation of tracked device with serial number 'PVR_Tracking_camera_0'

Thu Feb 14 2019 18:02:46.190 - Device 4294967297 somehow got through OnDeviceActivated with no controller type

Thu Feb 14 2019 18:02:46.190 - RendermodelManager: Reading data from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\rendermodels\lh_basestation_vive\lh_basestation_vive.json

Thu Feb 14 2019 18:02:46.190 - Driver 'aapvr' finished adding tracked device with serial number 'PVR_Tracking_camera_0'

Thu Feb 14 2019 18:02:46.236 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrcompositor.exe (VRApplication_Background) (Args: ) 15948

Thu Feb 14 2019 18:02:46.240 - Setting app openvr.component.vrcompositor PID to 15948

Thu Feb 14 2019 18:02:46.241 - App openvr.component.vrcompositor (aapvr_hmd) loaded fallback binding file file:///C:/Program Files (x86)/Steam/steamapps/common/SteamVR/resources/config/vrcompositor_bindings_generic_hmd.json

Thu Feb 14 2019 18:02:46.241 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.241 - Processing message VRMsg_Connect from vrcompositor (15948) took 0.00542 seconds

Thu Feb 14 2019 18:02:46.429 - [Settings] Save Json Settings to C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\config\steamvr.vrsettings

Thu Feb 14 2019 18:02:46.572 - Processing message VRMsg_CreateSwapTextureSet from vrcompositor (15948) took 0.0129 seconds

Thu Feb 14 2019 18:02:46.612 - Setting app openvr.tool.steamvr_environments PID to 13612

Thu Feb 14 2019 18:02:46.612 - Processing message VRMsg_LaunchApplication from vrstartup (13928) took 0.0089 seconds

Thu Feb 14 2019 18:02:46.646 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\vrwebhelper.exe (VRApplication_WebHelper) (Args: ) 4644

Thu Feb 14 2019 18:02:46.651 - Setting app openvr.component.vrwebhelper PID to 4644

Thu Feb 14 2019 18:02:46.652 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.652 - Processing message VRMsg_Connect from vrwebhelper (4644) took 0.00582 seconds

Thu Feb 14 2019 18:02:46.656 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win32\vrdashboard.exe (VRApplication_Overlay) (Args: ) 13956

Thu Feb 14 2019 18:02:46.662 - Setting app openvr.component.vrdashboard PID to 13956

Thu Feb 14 2019 18:02:46.662 - VRDashboard watchdog enabled for pid:13956

Thu Feb 14 2019 18:02:46.662 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.662 - Processing message VRMsg_Connect from vrdashboard (13956) took 0.006 seconds

Thu Feb 14 2019 18:02:46.730 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\vrwebhelper.exe (VRApplication_WebHelper) (Args: --type=gpu-process --no-sandbox --lang=en-US --log-file=C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\debug.log --log-severity=disable --product-version=SteamVR HTML --gpu-vendor-id=0x10de --gpu-device-id=0x1b06 --gpu-driver-vendor=NVIDIA --gpu-driver-version=25.21.14.1881 --gpu-driver-date=1-30-2019 --lang=en-US --log-file=C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\debug.log --log-severity=disable --product-version=SteamVR HTML --service-request-channel-token=8C351962410F25C85FC854D7762EFB89 --mojo-platform-channel-handle=1556 /prefetch:2) 2900

Thu Feb 14 2019 18:02:46.735 - Setting app openvr.component.vrwebhelper PID to 2900

Thu Feb 14 2019 18:02:46.735 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.736 - Processing message VRMsg_Connect from vrwebhelper (2900) took 0.00575 seconds

Thu Feb 14 2019 18:02:46.785 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrmonitor.exe (VRApplication_VRMonitor) (Args: -nokillprocess) 10064

Thu Feb 14 2019 18:02:46.790 - Setting app openvr.component.vrmonitor PID to 10064

Thu Feb 14 2019 18:02:46.790 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.790 - Processing message VRMsg_Connect from vrmonitor (10064) took 0.00544 seconds

Thu Feb 14 2019 18:02:46.818 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\steamvr_environments\game\bin\win64\steamtours.exe (VRApplication_Scene) (Args: -vr -retail -useappid SteamVRAppID -nowindow -vconport 29009) 13612

Thu Feb 14 2019 18:02:46.822 - Setting app openvr.tool.steamvr_environments PID to 13612

Thu Feb 14 2019 18:02:46.823 - App openvr.tool.steamvr_environments (aapvr_hmd) failed to load binding file. Input will not be available

Thu Feb 14 2019 18:02:46.823 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:46.823 - Processing message VRMsg_Connect from steamtours (13612) took 0.00512 seconds

Thu Feb 14 2019 18:02:47.025 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\vrwebhelper.exe (VRApplication_WebHelper) (Args: --type=renderer --enable-experimental-web-platform-features --enable-pinch --no-sandbox --service-pipe-token=110E979B8BABA84298F13C0F4050B977 --enable-blink-features=ResizeObserver --lang=en-US --lang=en-US --log-file=C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\debug.log --log-severity=disable --product-version=SteamVR HTML --disable-spell-checking --enable-pinch --device-scale-factor=1 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553;5,0,3553;5,1,3553;5,2,3553;5,3,3553;5,4,3553;5,5,3553;5,6,3553;5,7,3553;5,8,3553;5,9,3553;5,10,3553;5,11,3553;5,12,3553;5,13,3553;5,14,3553;5,15,3553;5,16,3553;5,17,3553;6,0,3553;6,1,3553;6,2,3553;6,3,3553;6,4,3553;6,5,3553;6,6,3553;6,7,3553;6,8,3553;6,9,3553;6,10,3553;6,11,3553;6,12,3553;6,13,3553;6,14,3553;6,15,3553;6,16,3553;6,17,3553 --enable-gpu-async-worker-context --service-request-channel-token=110E979B8BABA84298F13C0F4050B977 --renderer-client-id=3 --mojo-platform-channel-handle=2388 /prefetch:1) 706Thu Feb 14 2019 18:02:47.029 - Setting app openvr.component.vrwebhelper PID to 7068

Thu Feb 14 2019 18:02:47.029 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:47.030 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\vrwebhelper.exe (VRApplication_WebHelper) (Args: --type=renderer --enable-experimental-web-platform-features --enable-pinch --no-sandbox --service-pipe-token=7262916563689B12DDAEC9D3663F13A9 --enable-blink-features=ResizeObserver --lang=en-US --lang=en-US --log-file=C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\debug.log --log-severity=disable --product-version=SteamVR HTML --disable-spell-checking --enable-pinch --device-scale-factor=1 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553;5,0,3553;5,1,3553;5,2,3553;5,3,3553;5,4,3553;5,5,3553;5,6,3553;5,7,3553;5,8,3553;5,9,3553;5,10,3553;5,11,3553;5,12,3553;5,13,3553;5,14,3553;5,15,3553;5,16,3553;5,17,3553;6,0,3553;6,1,3553;6,2,3553;6,3,3553;6,4,3553;6,5,3553;6,6,3553;6,7,3553;6,8,3553;6,9,3553;6,10,3553;6,11,3553;6,12,3553;6,13,3553;6,14,3553;6,15,3553;6,16,3553;6,17,3553 --enable-gpu-async-worker-context --service-request-channel-token=7262916563689B12DDAEC9D3663F13A9 --renderer-client-id=4 --mojo-platform-channel-handle=2488 /prefetch:1) 172Thu Feb 14 2019 18:02:47.034 - Setting app openvr.component.vrwebhelper PID to 17244

Thu Feb 14 2019 18:02:47.034 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:47.040 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\vrwebhelper.exe (VRApplication_WebHelper) (Args: --type=renderer --enable-experimental-web-platform-features --enable-pinch --no-sandbox --service-pipe-token=1A9475367631B5DF3B0263753B689AA2 --enable-blink-features=ResizeObserver --lang=en-US --lang=en-US --log-file=C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\vrwebhelper\debug.log --log-severity=disable --product-version=SteamVR HTML --disable-spell-checking --enable-pinch --device-scale-factor=1 --num-raster-threads=4 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;0,16,3553;0,17,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;1,16,3553;1,17,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;2,16,3553;2,17,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553;3,16,3553;3,17,3553;4,0,3553;4,1,3553;4,2,3553;4,3,3553;4,4,3553;4,5,3553;4,6,3553;4,7,3553;4,8,3553;4,9,3553;4,10,3553;4,11,3553;4,12,3553;4,13,3553;4,14,3553;4,15,3553;4,16,3553;4,17,3553;5,0,3553;5,1,3553;5,2,3553;5,3,3553;5,4,3553;5,5,3553;5,6,3553;5,7,3553;5,8,3553;5,9,3553;5,10,3553;5,11,3553;5,12,3553;5,13,3553;5,14,3553;5,15,3553;5,16,3553;5,17,3553;6,0,3553;6,1,3553;6,2,3553;6,3,3553;6,4,3553;6,5,3553;6,6,3553;6,7,3553;6,8,3553;6,9,3553;6,10,3553;6,11,3553;6,12,3553;6,13,3553;6,14,3553;6,15,3553;6,16,3553;6,17,3553 --enable-gpu-async-worker-context --service-request-channel-token=1A9475367631B5DF3B0263753B689AA2 --renderer-client-id=5 --mojo-platform-channel-handle=2592 /prefetch:1) 114Thu Feb 14 2019 18:02:47.045 - Setting app openvr.component.vrwebhelper PID to 11448

Thu Feb 14 2019 18:02:47.045 - Using existing HMD aapvr.Pimax P2C

Thu Feb 14 2019 18:02:47.068 - Enabling legacy input for system.vrwebhelper.controllerbinding

Thu Feb 14 2019 18:02:47.068 - Enabling legacy input for system.vrwebhelper.bindingcallouts

Thu Feb 14 2019 18:02:47.071 - App system.vrwebhelper.controllerbinding (aapvr_hmd) loaded fallback binding file file:///C:/Program Files (x86)/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json

Thu Feb 14 2019 18:02:47.071 - App system.vrwebhelper.bindingcallouts (aapvr_hmd) loaded fallback binding file file:///C:/Program Files (x86)/Steam/steamapps/common/SteamVR/resources/config/legacy_bindings_generic_hmd.json

Thu Feb 14 2019 18:02:47.094 - Invalid input type click for controller (/user/head/proximity)

Thu Feb 14 2019 18:02:47.094 - Invalid input type click for controller (/user/head/proximity)

Thu Feb 14 2019 18:02:47.114 - Closing pipe vrstartup (13928) because it was broken from the other end

Thu Feb 14 2019 18:02:47.114 - Process vrstartup (13928) disconnected (Thread(0x0000017EA1338870/0x000)

Thu Feb 14 2019 18:02:47.114 - Clearing application openvr.component.vrstartup PID because 13928 has exited

Thu Feb 14 2019 18:02:54.835 - Processing message VRMsg_WritePropertyDataToFile from vrmonitor (10064) took 0.015 seconds

Thu Feb 14 2019 18:02:57.114 - 0 - entering standby

Thu Feb 14 2019 18:02:58.323 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:02:59.402 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:00.480 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:01.547 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:02.624 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:03.690 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:04.769 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:05.836 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:06.913 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:08.003 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:09.058 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:10.158 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:11.224 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:12.302 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:13.426 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:14.504 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:15.582 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:16.651 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:17.728 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:18.806 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:19.950 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:21.029 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:22.106 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:23.174 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:24.249 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:25.319 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:26.405 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:27.483 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:28.550 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:29.629 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:30.704 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:31.833 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:32.907 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:33.986 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:35.072 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:36.116 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:36.603 - Processing message VRMsg_WritePropertyDataToFile from vrmonitor (10064) took 0.0129 seconds

Thu Feb 14 2019 18:03:37.220 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:38.306 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:39.376 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:40.452 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:41.531 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:42.606 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:43.683 - aapvr: fail to ReleaseSync with err:-2005270527

Thu Feb 14 2019 18:03:44.757 - Processing message VRMsg_WritePropertyDataToFile from vrmonitor (10064) took 0.0129 seconds

[risa2000]

I do not know. I checked my log, and I see exactly same sequence:

https://pastebin.com/raw/b9CxMaG2

What I do not see in my log is this error of yours:

Thu Feb 14 2019 18:02:46.189 - Failed to read chaperone file from C:/Program Files (x86)/Steam/steamapps/common/SteamVR/bin/win64/config\chaperone_info.vrchap

I guess it is alright if you have not set up your play space, but I wonder, if you tried, I guess without base station you would go for “standing experience”.

[Clinch]

Finally managed to get it to work. The problem was that my Windows account had Swedish letters in it, so PiTool was unable to install properly as it couldn’t find the directory and instead tried to put files in a non-existing folder. After removing my Windows user account and creating a new which only uses English letters and reinstalling PiTool it started working instantly. Thanks a lot for your assistance in troubleshooting this issue. Time to play some VR games!

[Davebobman]

@Clinch

The problem was that my Windows account had Swedish letters in it, so PiTool was unable to install properly as it couldn’t find the directory and instead tried to put files in a non-existing folder.

I have added your solution to my wiki.

[anon74848233]

Thank you so much for your help,your topic is such good thing for our backers.I have pin your topic to the top of 8K section

[Davebobman]

@anon74848233

Thank you so much for your help,your topic is such good thing for our backers.I have pin your topic to the top of 8K section

Thank you for your appreciation

The biggest problem with pinning something is that the default setting for pinning topics is that they become unpinned after you view them the first time. I think it would be a good idea in general for the forum’s default setting be to keep the topics pinned, since the pinned topics (ie Spreadsheet, FAQ, etc) are usually topics that most people would want to view multiple times.