SOLVED: Fake Controller for Oculus games? (Chronos)


#1

I bought an Oculus game called Chronos: today but cannot play it because I get:

“please check that your headset and sensor are connected”

Now Chronos can be played with either a controller (I have an Xbox One) or the Touch, but I think the game is checking for the second USB port sensor (which is not present with PiMax)

Does anyone know of a way to emulate the sensor in the USB port (I’m thinking of somethink like vJoy). (vOcSensor?)


#2

You can fix that with a ps eye, by using psmove service (search for it). You also need to run the game with Revive.

The rift is looking for the rift sensor, as a kind of copy protection i think. Psmove service makes the ps eye act like one.

You also need the controller but yours is fine. I had the same problem with Chronos. This fix works with other games too.


#3

So you are saying that if I buy one PSEye, then use PSMove, that Chronos will get past the sensor check?

In that case, will the PSEye also work for the “lean in” function? I was watching a video of Chonos where the player could lean in for a different view angle. I thought the Oculus sensor works by using IR LEDs on the headset which the pimax does not have.

I’ll get myself a PSEye today.


#4

Yes, one pseye will get you past the sensor check. You won’t need a psmove if you don’t want one. You just need the camera. You should be able to find one pretty cheap.

You won’t be able to get positional / leaning tracking with it. You can get 360 rotational tracking and vive controller emulation with 3 or 4 ps eyes and 2 move controllers, but it is a lot of effort.


#5

Thank you again:

I got one eye on order from Amazon. $6 is not bad.

It sounds like the one eye does not really need to be pointed at anything or calibrated or the like (just watched the PSMove setup video), just connected.

Later on I might want to get the controller and extra cameras but for now just for seated games with the XBOX controller I should be good to go.

You are a great help. Thanks again.


#6

This has drove me ruddy nuts,thought I could get away with emulating in OSVR,like the one for Pimax that Crony did still trying that method,as It’s hard to fathom as it’s silent and in Chinese !

But this does seem a great alternative,will be getting the NoloVR at some point might even get a move set up going for the time being,I have picked up a cheap Leap Motion so could go for all 3 emulation methods at this rate :wink:


#7

O.K. I got my PS Eye in the mail yesterday and went to set it up.

I ran into some PSMove install issues and am corresponding with the coders in this thread:
https://groups.google.com/forum/#!topic/psmoveservice/pYYxjzB-n1o

However I am getting the feeling that PSMove service is not the answer to this problem. It is designed to used with the PS controllers. It could be made into a positional head tracker by strapping a controller to your head, but I am not certain that is will actually let the system (Oculus/Revive/SteamVR) think that the Oculus sensor is present and allow Chronos to get past the hardware check.

JonnyPanic, what is your setup that allows you to play the game. Are you using PS Move Controllers with PSMove service? I did not get those, only the one PS Eye camera.


#8

It does work, believe me. It doesn’t do head tracking, but all you want is a dummy device to trick Oculus Home into letting you get past the check.

I have the psmove controllers too but if I want to play Chronos, I just have one pseye plugged in, no controllers.
I just plug in the pseye, launch psmove service, start steam vr (I can see the camera on the Steam VR panel), launch the game through revive, and it works.

If you can’t see the camera in SteamVR, yeah it must be a psmove service problem.

If you are having a problem after the camera is installed, I suspect it is a problem with revive. I launch revive through a shortcut on my desktop with admin rights, recently there was a problem and it became necessary to do that.

What exactly is the problem you are having with installing the camera?

Ok I just read the post. It seems that they aren’t aware of the fact you can use this solely as a way of getting past the check. It has nothing to do with tracking the HMD. It works because using psmove service plus revive emulates Oculus Touch. You launch the game through revive (once the camera shows up). In Oculus, you don’t need to do anything, it won’t detect the camera whatever you do. All you need to do with Oculus is have Oculus Home running in the background.

Do all of your other Oculus games work ok through revive? If you don’t have any, I would try a free one like Lucky’s Tale. Think you don’t need the sensor for that. Good game, too. I’ll try to get a photo of Chronos so you know I’m not talking shite. Hope you manage to get it working.


#9

Fantastic, it is really helpful to see something that is working and see the icon on your steam VR panel.
Revive starts automatically with SteamVR. I don’t do anything additionally to start it…

Here is mine:


#10

I also play Lucky’s Tale and Goat Mountain with no issues.

Keep watching the thread over on https://groups.google.com/forum/#!topic/psmoveservice/pYYxjzB-n1o


#11

If this is the case, I am sorry I made you go out and buy the pseye, but is it possible you need the psmove controller to complete the steam setup?
That’s the only reason I can think of that your camera isn’t working, since I see you followed the steps with usb drivers etc.
If you could borrow one from somewhere maybe you could test it.
What do you see in psmove config?

Have you tried doing the room setup in steam vr?

Once you do get the camera working, I think you have to run revive from the shortcut because you need admin mode, because of a recent Oculus update.

I’ll go back to defaults and see if I can get it working without any using the controller at all from the start.

Update:
Ok, so this is hopefully good news. On my computer, the tracker appears in Steam VR without any input from the controllers. I don’t need to do the controller setup to get the camera to show up on the Steam VR panel.


#12

No worries about buying the PSEye, It was inexpensive and I eventually want to build up a full roomscale system anyway. I do see a possible error message in the output I posted above so maybe the PSMove programmer can help me past it.


#13

Johnnypanic:

Would you do me a favor? go to your C:\Program Files (x86)\Steam\logs and delete vrserver.txt, Then with pimax and PSMoveService running, start steamVR then shut it down, then send me or copy/paste the contents of the log here to this forum. I’d like to compare it to my logs.

Thanks!


#14

Ok, here it is. This will probably be a huge wall of text, apologies. And that is only for 2 seconds.

Sat Apr 22 2017 17:47:56.380 - ================================================================================================
Sat Apr 22 2017 17:47:56.380 - ================================================================================================
Sat Apr 22 2017 17:47:56.381 - VR server (v0) starting up with config=C:\Program Files (x86)\Steam\config
Sat Apr 22 2017 17:47:56.387 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings
Sat Apr 22 2017 17:47:56.388 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettings
Sat Apr 22 2017 17:47:56.388 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettings
Sat Apr 22 2017 17:47:56.394 - [Settings] Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettings
Sat Apr 22 2017 17:47:56.405 - Load Json firmware manifest from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\firmware\manifest.vrfirmware
Sat Apr 22 2017 17:47:56.405 - Loading of firmware manifest file not successful: (C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\htc\resources\firmware\manifest.vrfirmware)
Sat Apr 22 2017 17:47:56.426 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrmonitor.exe (VRApplication_VRMonitor) (Args: -startedbyvrbutton) 6528
Sat Apr 22 2017 17:47:56.429 - Creating builtin app for C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrmonitor.exe (VRApplication_VRMonitor)
Sat Apr 22 2017 17:47:56.429 - Setting app system.generated.vrmonitor.exe PID to 6528
Sat Apr 22 2017 17:47:56.438 - lighthouse: Attached HID Devices:
Sat Apr 22 2017 17:47:56.438 - lighthouse: No devices
Sat Apr 22 2017 17:47:56.438 - driver lighthouse implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_005 IVRDisplayComponent_002 IVRDriverDirectModeComponent_002 IVRControllerComponent_001 IVRCameraComponent_002 IServerTrackedDeviceProvider_004 IVRWatchdogProvider_001 IVRVirtualDisplay_001
Sat Apr 22 2017 17:47:56.438 - Loaded server driver lighthouse (IServerTrackedDeviceProvider_004) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\bin\win64\driver_lighthouse.dll
Sat Apr 22 2017 17:47:56.438 - Driver lighthouse has no suitable devices.
Sat Apr 22 2017 17:47:56.474 - oculus: [CAPI] LibOVR module is located at C:\Program Files\Oculus\Support\oculus-runtime\LibOVRRT64_1.dll
Sat Apr 22 2017 17:47:56.476 - oculus: Connected to the server running version (prod = 1).1.13.0(build = 361842) feature version = 0. Client runs version (prod = 1).1.13.0(build = 361842) feature version = 0
Sat Apr 22 2017 17:47:56.976 - oculus: ovrHmd_Create failed
Sat Apr 22 2017 17:47:56.976 - error VRInitError_Driver_Failed when initing driver oculus from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus\bin\win64\driver_oculus.dll.
Sat Apr 22 2017 17:47:56.976 - Unable to load driver oculus because of error 200. Skipping.
Sat Apr 22 2017 17:47:56.978 - error VRInitError_Driver_RuntimeOutOfDate when initing driver oculus_legacy from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus_legacy\bin\win64\driver_oculus_legacy.dll.
Sat Apr 22 2017 17:47:56.978 - Unable to load driver oculus_legacy because of error 204. Skipping.
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: PCHCK: Subscription data is empty
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: Using settings values
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Serial Number: 0.8
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Model Number: Vridge
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Window: -1 -1 3200 1800
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Render Target: 1600 1800
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Seconds from Vsync to Photons: 0.000000
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: Display Frequency: 58.000000
Sat Apr 22 2017 17:47:57.063 - oculus_vridge: driver_vridge: IPD: 0.065000
Sat Apr 22 2017 17:47:57.063 - driver oculus_vridge implements interfaces IVRSettings_001 ITrackedDeviceServerDriver_004 IVRDisplayComponent_002 IVRDriverDirectModeComponent_001 IServerTrackedDeviceProvider_003 IClientTrackedDeviceProvider_004
Sat Apr 22 2017 17:47:57.063 - Loaded server driver oculus_vridge (IServerTrackedDeviceProvider_003) from C:\Program Files (x86)\Riftcat\lib\Driver\oculus_vridge\bin\win64\driver_oculus_vridge.dll
Sat Apr 22 2017 17:47:57.063 - Driver oculus_vridge has no suitable devices.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::Init - called.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::Init - Using Default Server Address: localhost.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::Init - Using Default Server Port: 9512.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::Init - Initializing.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::ReconnectToPSMoveService - called.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::ReconnectToPSMoveService - Existing PSMoveService connection NOT active.
Sat Apr 22 2017 17:47:57.066 - psmove: CServerDriver_PSMoveService::ReconnectToPSMoveService - Starting PSMoveService connection…
Sat Apr 22 2017 17:47:57.069 - psmove: CServerDriver_PSMoveService::ReconnectToPSMoveService - Successfully requested connection
Sat Apr 22 2017 17:47:57.069 - driver psmove implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_005 IVRDisplayComponent_002 IVRDriverDirectModeComponent_002 IVRControllerComponent_001 IVRCameraComponent_002 IServerTrackedDeviceProvider_004 IVRWatchdogProvider_001
Sat Apr 22 2017 17:47:57.069 - Loaded server driver psmove (IServerTrackedDeviceProvider_004) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\psmove\bin\win64\driver_psmove.dll
Sat Apr 22 2017 17:47:57.069 - Driver psmove has no suitable devices.
Sat Apr 22 2017 17:47:57.070 - psmove: CServerDriver_PSMoveService::Init - called.
Sat Apr 22 2017 17:47:57.070 - psmove: CServerDriver_PSMoveService::Init - Already Initialized. Ignoring.
Sat Apr 22 2017 17:47:57.070 - driver psmove implements interfaces IVRSettings_002 ITrackedDeviceServerDriver_005 IVRDisplayComponent_002 IVRDriverDirectModeComponent_002 IVRControllerComponent_001 IVRCameraComponent_002 IServerTrackedDeviceProvider_004 IVRWatchdogProvider_001
Sat Apr 22 2017 17:47:57.070 - Loaded server driver psmove (IServerTrackedDeviceProvider_004) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\psmove\bin\win64\driver_psmove.dll
Sat Apr 22 2017 17:47:57.070 - Driver psmove has no suitable devices.
Sat Apr 22 2017 17:47:57.073 - pvr: Verbose logging disabled.
Sat Apr 22 2017 17:47:57.073 - pvr: ServerDriver_PVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Sat Apr 22 2017 17:47:57.073 - pvr: ServerDriver_PVR::GetTrackedDeviceDriver(): Returning tracked device #0.
Sat Apr 22 2017 17:47:57.073 - pvr: ServerDriver_PVR::GetTrackedDeviceCount(): Detected 1 tracked devices.
Sat Apr 22 2017 17:47:57.073 - driver pvr implements interfaces IVRSettings_001 ITrackedDeviceServerDriver_004 IVRDisplayComponent_002 IVRDriverDirectModeComponent_001 IVRControllerComponent_001 IVRCameraComponent_001 IServerTrackedDeviceProvider_003 IClientTrackedDeviceProvider_003
Sat Apr 22 2017 17:47:57.073 - Loaded server driver pvr (IServerTrackedDeviceProvider_003) from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\pvr\bin\win64\driver_pvr.dll
Sat Apr 22 2017 17:47:57.073 - PoseUpdated from driver 6 for object 0 which is actually from -1
Sat Apr 22 2017 17:47:57.073 - pvr: PVRTrackedDevice::GetBoolTrackedDeviceProperty(): Unknown property Prop_Firmware_ForceUpdateRequired_Bool requested.
Sat Apr 22 2017 17:47:57.074 - pvr: PVRTrackedDevice::GetBoolTrackedDeviceProperty(): Unknown property Prop_DisplaySuppressed_Bool requested.
Sat Apr 22 2017 17:47:57.074 - pvr: PVRTrackedDevice::GetFloatTrackedDeviceProperty(): Unknown property Prop_ScreenshotHorizontalFieldOfViewDegrees_Float requested.
Sat Apr 22 2017 17:47:57.074 - pvr: PVRTrackedDevice::GetFloatTrackedDeviceProperty(): Unknown property Prop_ScreenshotVerticalFieldOfViewDegrees_Float requested.
Sat Apr 22 2017 17:47:57.074 - Active HMD set to pvr.Pimax P1
Sat Apr 22 2017 17:47:57.075 - DXGI thread failed to get SDL display index
Sat Apr 22 2017 17:47:57.590 - oculus: ovrHmd_Create failed
Sat Apr 22 2017 17:47:57.590 - error VRInitError_Driver_Failed when initing driver oculus from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus\bin\win64\driver_oculus.dll.
Sat Apr 22 2017 17:47:57.590 - Unable to load driver oculus because of error 200. Skipping.
Sat Apr 22 2017 17:47:57.591 - error VRInitError_Driver_RuntimeOutOfDate when initing driver oculus_legacy from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\oculus_legacy\bin\win64\driver_oculus_legacy.dll.
Sat Apr 22 2017 17:47:57.591 - Unable to load driver oculus_legacy because of error 204. Skipping.
Sat Apr 22 2017 17:47:57.592 - Not loading driver null because it is disabled in settings
Sat Apr 22 2017 17:47:57.592 - Processing message VRMsg_Connect from vrmonitor (6528) took 1.17 seconds
Sat Apr 22 2017 17:47:57.604 - psmove: CServerDriver_PSMoveService::HandleConnectedToPSMoveService - Request controller and tracker lists
Sat Apr 22 2017 17:47:57.637 - psmove: CServerDriver_PSMoveService::HandleServiceVersionResponse - Received expected protocol version 0.9-alpha 8.1.0
Sat Apr 22 2017 17:47:57.659 - psmove: NotifyClientPSMoveResponse - Controller Count = 0 (request id 1).
Sat Apr 22 2017 17:47:57.659 - psmove: CServerDriver_PSMoveService::HandleControllerListReponse - Received 0 controllers
Sat Apr 22 2017 17:47:57.659 - psmove: NotifyClientPSMoveResponse - Tracker Count = 1 (request id 2).
Sat Apr 22 2017 17:47:57.659 - psmove: CServerDriver_PSMoveService::HandleTrackerListReponse - Received 1 trackers
Sat Apr 22 2017 17:47:57.659 - psmove: added new tracker device psmove_tracker0
Sat Apr 22 2017 17:47:57.659 - psmove: Begin CServerDriver_PSMoveService::RefreshWorldFromDriverPose() for device psmove_tracker0
Sat Apr 22 2017 17:47:57.659 - psmove: worldFromDriverPose: [Pos: (0, 0, 0), Rot:(1, 0, 0, 0)]
Sat Apr 22 2017 17:47:57.659 - PoseUpdated for invalid object ID -1
Sat Apr 22 2017 17:47:57.659 - PoseUpdated for invalid object ID -1
Sat Apr 22 2017 17:47:57.669 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win32\vrcompositor.exe (VRApplication_Background) (Args: ) 10540
Sat Apr 22 2017 17:47:57.673 - Creating builtin app for C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win32\vrcompositor.exe (VRApplication_Background)
Sat Apr 22 2017 17:47:57.673 - Setting app system.generated.vrcompositor.exe PID to 10540
Sat Apr 22 2017 17:47:57.673 - Using existing HMD pvr.Pimax P1
Sat Apr 22 2017 17:47:57.673 - psmove: CPSMoveTrackedDeviceLatest::Activate: psmove_tracker0 is object id 1
Sat Apr 22 2017 17:47:57.673 - psmove: Begin CServerDriver_PSMoveService::RefreshWorldFromDriverPose() for device psmove_tracker0
Sat Apr 22 2017 17:47:57.673 - psmove: worldFromDriverPose: [Pos: (0, 0, 0), Rot:(1, 0, 0, 0)]
Sat Apr 22 2017 17:48:00.678 - Processing message VRMsg_ComputeDistortion from vrcompositor (10540) took 0.00995 seconds
Sat Apr 22 2017 17:48:00.684 - Processing message VRMsg_ComputeDistortion from vrcompositor (10540) took 0.0051 seconds
Sat Apr 22 2017 17:48:00.714 - Processing message VRMsg_ComputeDistortion from vrcompositor (10540) took 0.0101 seconds
Sat Apr 22 2017 17:48:00.723 - Processing message VRMsg_ComputeDistortion from vrcompositor (10540) took 0.00555 seconds
Sat Apr 22 2017 17:48:02.794 - [System] Not launching home app, since home app option isn’t enabled.
Sat Apr 22 2017 17:48:03.280 - New Connect message from C:\Program Files (x86)\Steam\Steam.exe (VRApplication_Overlay) (Args: -silent) 9172
Sat Apr 22 2017 17:48:03.282 - Creating builtin app for C:\Program Files (x86)\Steam\Steam.exe (VRApplication_Overlay)
Sat Apr 22 2017 17:48:03.282 - Setting app system.generated.steam.exe PID to 9172
Sat Apr 22 2017 17:48:03.282 - Using existing HMD pvr.Pimax P1
Sat Apr 22 2017 17:48:03.307 - Processing message VRMsg_AddApplicationManifest from Steam (9172) took 0.0064 seconds
Sat Apr 22 2017 17:48:03.564 - New Connect message from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrdashboard.exe (VRApplication_Overlay) (Args: ) 10896
Sat Apr 22 2017 17:48:03.568 - Creating builtin app for C:\Program Files (x86)\Steam\steamapps\common\SteamVR\tools\bin\win32\vrdashboard.exe (VRApplication_Overlay)
Sat Apr 22 2017 17:48:03.568 - Setting app system.generated.vrdashboard.exe PID to 10896
Sat Apr 22 2017 17:48:03.568 - VRDashboard watchdog enabled for pid:10896
Sat Apr 22 2017 17:48:03.568 - Using existing HMD pvr.Pimax P1
Sat Apr 22 2017 17:48:13.571 - 0 - entering standby
Sat Apr 22 2017 17:48:15.002 - Setting app matzman666.advancedsettings PID to 12276
Sat Apr 22 2017 17:48:15.002 - Started autolaunch dashboard matzman666.advancedsettings.
Sat Apr 22 2017 17:48:15.005 - Tried to start binary process C:\Program Files\Revive\ReviveOverlay.exe -compositor (working directory C:\Program Files\Revive) as app revive.dashboard.overlay but it failed
Sat Apr 22 2017 17:48:15.005 - Unable to start autolaunch dashboard revive.dashboard.overlay: VRApplicationError_LaunchFailed
Sat Apr 22 2017 17:48:15.005 - Processing message VRMsg_StartAutolaunchOverlays from vrdashboard (10896) took 0.33 seconds
Sat Apr 22 2017 17:48:19.072 - 0 - leaving standby
Sat Apr 22 2017 17:48:23.504 - New Connect message from C:\Program Files\OpenVR-AdvancedSettings\AdvancedSettings.exe (VRApplication_Overlay) (Args: ) 12276
Sat Apr 22 2017 17:48:23.507 - Setting app matzman666.advancedsettings PID to 12276
Sat Apr 22 2017 17:48:23.507 - Using existing HMD pvr.Pimax P1
Sat Apr 22 2017 17:48:28.143 - PowerOffTrackedDevice for 0
Sat Apr 22 2017 17:48:28.143 - Process vrmonitor (6528) has initiated a quit all
Sat Apr 22 2017 17:48:28.152 - Sending Quit event to process Steam (9172)
Sat Apr 22 2017 17:48:28.152 - Sending Quit event to process vrdashboard (10896)
Sat Apr 22 2017 17:48:28.152 - Sending Quit event to process AdvancedSettings (12276)
Sat Apr 22 2017 17:48:30.353 - IPCPipe(Steam (9172)): Process disconnected.
Sat Apr 22 2017 17:48:30.353 - Process Steam (9172) disconnected
Sat Apr 22 2017 17:48:30.353 - IPCPipe(vrdashboard (10896)): Process disconnected.
Sat Apr 22 2017 17:48:30.353 - Process vrdashboard (10896) disconnected
Sat Apr 22 2017 17:48:33.163 - Kill process AdvancedSettings (12276) because it didn’t quit in time
Sat Apr 22 2017 17:48:33.188 - IPCPipe(AdvancedSettings (12276)): Process disconnected.
Sat Apr 22 2017 17:48:33.188 - Process AdvancedSettings (12276) disconnected
Sat Apr 22 2017 17:48:33.196 - Sending Quit event to process vrcompositor (10540)
Sat Apr 22 2017 17:48:33.196 - Sending Quit event to process vrmonitor (6528)
Sat Apr 22 2017 17:48:34.428 - IPCPipe(vrmonitor (6528)): Process disconnected.
Sat Apr 22 2017 17:48:34.428 - Process vrmonitor (6528) disconnected
Sat Apr 22 2017 17:48:34.467 - IPCPipe(vrcompositor (10540)): Process disconnected.
Sat Apr 22 2017 17:48:34.467 - Process vrcompositor (10540) disconnected
Sat Apr 22 2017 17:48:34.472 - VR server shutting down
Sat Apr 22 2017 17:48:34.537 - Listener thread ending
Sat Apr 22 2017 17:48:34.649 - psmove: CServerDriver_PSMoveService::Cleanup - Shutting down connection…
Sat Apr 22 2017 17:48:34.649 - psmove: CServerDriver_PSMoveService::Cleanup - Shutdown complete


#15

this is very interesting. What version of Pimax app and HMD firmware do you use?

Some differences I see:

  1. you are using VRidge although it reports no suitable devices found. I am not using VRidge yet.
  2. your HMD is reported as a Pimax but mine for some reason is reported as a Rift.

Some other subtle difference I’ll also look int when I get back from the March for Science!

Thanks


#16

I am using 1.1.92 and .251 (I think - the latest) fw. I have tried all the new drivers and went back to 1.1.92.

Mine has previously shown up as a Rift in Device Manager. In order to get Extended Mode on 1.1.92 working you have to delete it and any extra monitors (though now I just use Steam VR’s extended mode, it is much less hassle).

VRidge is from an old installation. Before I got Pimax I tried out the psmove service controllers using my phone and VRidge. I don’t actually use it now. Guess the drivers are still installed. Maybe that helps? I dunno.


#17

I have all the latest from Pimax but have read on this forum that .92 is the best performing.

I havent looked at the monitors in Device Manager. it sounds like a good idea and clean out the old ones…

Think I’ll try rolling back in my next session.


#18

The Pimax (Rift or otherwise) does not show up under monitors or anywhere else in Device Manager. Only my two other monitors show up.

You are using Extended mode in 1.1.92 and not Pimax Mode to run SteamVR? That seems odd.

Are you running SteamVR in Direct mode (the recommended mode).

Thanks, I hope to eventually solve this issue. You are helping.


#19

I use Pimax mode, but never use Piplay at all, just the piserver running in the background. Then I mostly use Direct Mode in Steam VR, and use Disable Direct Mode in Steam VR if I ever need to play a game that uses extended, like for Half Life 2.

To see the other monitors, make sure you have selected Show Hidden Devices in Device Manager (or some such thing - my windows is not in English). There is probably a few of them.


#20

I GOT CHRONOS WORKING!

The SteamVR panel still does not show any sensors or lighthouses (only the HMD shows green). And I did verify that PSMove service is required to run Chronos and that it does appear to be opening the PS Eye camera.

I wish I could point to one thing and say “it was this” but because I did so much without testing Chronos each time (I was looking for the sensor icon) I’m not sure what did the trick. by 2 am this morning I had reinstalled and reconfigured Revive and PSMove and put SteamVR back to default settings, tried SteamVR in both direct and extended mode, tried Pimax version 1.1.92 and 1.2.57, bluescreened Windows 10 a couple of times (SteamVR and Pimax 1.1.92 both in extended mode bluescreens Win 10). Rebooted dozens of times.

In the end, here is my configuration and how I start it all up:

  1. Pimax 1.2.57 in Pimax mode (I have investigated a number of issues with 1.1.97 but not having much luck getting it, steamVR, and Oculus/Revive driver to all play nice together).
  2. Start PSMove Service (AS ADMINISTRATOR) with only one PSEye connected.
  3. Start Steam AS ADMINISTRATOR (to avoid the "failed entitlement check of even free Oculus games such as Goat Mountain, and Lucky’s Tale)
  4. Start SteamVR from the Steam task (note that only the HMD icon shows green, not any of the controllers or lighthouses and there is no PS Eye icon). Steam is running in direct mode (in SteamVR extended mode (disable direct mode, the the steamVR panel loos the same but the game does see the hardware on my system)
  5. Run Chronos from the Revive tab inside the Steam Big Picture panel in the VR HMD.

(notes:

  1. In device manager, the HMD only ever appears as a Genric PNP monitor, but after all the stuff I did last night, the SteamVR log now reports it as a Pimax device, not a Rift any more.
  2. In general I have been noticing some juddering when I turn my head that was never present under 1.1.92 so I’m hoping iMax is thinking about performance for their next release.

Thank you to everyone’s help, especially HipsterSloth908 I(one of the developers and supporters of PSMove) and Jonnypanic on the PiMx support forum! I could not done this without bot of their help and especially being able to see jonnypanic’s logs and understand the details of how he got it working.

I hope these two long threads help others fighting the same fight:

https://groups.google.com/forum/#!topic/psmoveservice/pYYxjzB-n1o