Obduction 1.8.0: Promising Update (PP no longer needed)

Heliosurge · August 14, 2019, 2:28pm

No it launches Steamvr on it’s own.

But looking in Obduction directory it has Openvr.dll & oculus dll files.

Do you have Oculus home running? (I don’t) it might be reading both vr platforms.

DrWilken · August 14, 2019, 2:31pm

Nope. No Oculus software installed.

Removed ReVive too.

Launched from Steam or SteamVR dashboard (Vive mode).

I’ll experiment some more tomorrow…

Heliosurge · August 14, 2019, 3:49pm

So yours is Steam bought?

Have you tried cmdline Argument -openvr ?

Mine was the GoG version & it launches Steamvr on it’s own. Not using vive mode either in pitool.

DrWilken · August 14, 2019, 4:11pm

Yes it is, I’ll give that a go tomorrow…

Thanks.

sikjar · August 15, 2019, 1:34pm

I had exactly the same problem as DrWilken, seems this workaround solves the problem:

Open Steam, but not SteamVR.
Got to ‘…\Steam\steamapps\common\Obduction\Obduction\Binaries\Win64’
Run ‘Obduction-Win64-Shipping.exe’
Obduction starts up, and also opens SteamVR.
Avoid moving your headset, so it stays in standby mode.
The following is shown on the main monitor:

Open a game using the menu on the monitor.
Don’t touch the headset, let it stay in standby mode!
After the game opens on the monitor, put on the headset, the game now runs in the headset as well.
If head tracking stutters, then close the game and SteamVR and try again.

I changed a lot of settings to get to this result, so maybe some of these changes also contributed to make it work, but it looks like the main thing is to follow the above procedure.

This must be the worlds best puzzle game, we are solving riddles even before the game has started

DrWilken · August 15, 2019, 1:57pm

Thanks for the hint…

I’m trying here, but I’m not starting in “Standing by” state/mode (I just enabled “Pause rendering when headset is idle” again) … Guess I’l try to wait a few minutes to see if it goes to standby mode…

DrWilken · August 15, 2019, 2:03pm

Tried this too.

Same result (I’m guess using that argument is the same as choosing “Launch Obduction in SteamVR mode”?).

Just came to think about it. You’re not using any basestations, so maybe the standby/proximity stuff works differently because in “gyro-mode”?

sikjar · August 15, 2019, 2:05pm

Yes, that might be it. I have no basestations or controllers, only the Pimax headset.

DrWilken · August 15, 2019, 2:13pm

Judging by what You discovered it seems it has to have a switch from inactive to active after starting the game. It’s not enough to have it active at startup (if that’s what PiTool does now?).

sikjar · August 15, 2019, 2:16pm

Yes, it seems the headset must be inactive/standby when the rendering engine initializes. So when you move on to the next scene in the game, it stops rendering in the headset again. Guess we can save the game, put the headset in standby and restart the game, but its not the ideal solution. Anyway, it looks like it would be a quick fix for the devs to get it working properly with the Pimax.

DrWilken · August 15, 2019, 2:28pm

Tried editing the PiTool/Pimax specific default.vrsettings file to enable the standby again.

It’s located here:

C:\Program Files\Pimax\SteamVRSupport\drivers\aapvr\resources\settings\default.vrsettings

Changed the “pauseCompositorOnStandby” from false to true and restarted PiServiceLauncher:

{
“steamvr” : {
“enableDistortion” : false,
“supersampleManualOverride” : true,
“supersampleScale” : 1.0,
“background” : “#FF000000”,
“maxRecommendedResolution”: 8192
},
“power”: {
“autoLaunchSteamVROnButtonPress”: false,
“pauseCompositorOnStandby”: true,
“powerOffOnExit”: false
}
}

My son just woke up, so I’ll look into it later tonight, but maybe that option isn’t being read by SteamVR any longer (I believe others have stated that the “maxRecommendedResolution” option wasn’t read/used any more either)?

sikjar · August 15, 2019, 2:32pm

Just checked my settings, they look like this:
{
“steamvr” : {
“enableDistortion” : false,
“supersampleManualOverride” : true,
“supersampleScale” : 1.0,
“background” : “#FF000000”,
“maxRecommendedResolution”: 8192
},
“power”: {
“autoLaunchSteamVROnButtonPress”: false,
“pauseCompositorOnStandby”: false,
“powerOffOnExit”: false
}
}

By the way, I am not using the latest PiTool, I’m on version V1.0.1.129

DrWilken · August 15, 2019, 3:01pm

Yeah, that’s what mine looked like too…

DrWilken · August 15, 2019, 3:44pm

Tonight, I’ll look into faking the input in this .json file.

I’m guessing it’s a “boolean” (i.e. true/false) so if we can find an input variable that always returns true (there must be a built-in in Unreal Engine for that) we can change the input part to that…

EDIT: We probably “just” need to replace “/user/head/proximity” with some other boolean input which coincidentally always returns true…

EDIT2: Or we can try to remove that specific binding.

EDIT3: We’re probably using the “generic_hmd.json” config placed in the same directory:

C:\Program Files (x86)\Steam\steamapps\common\Obduction\Obduction\Config\SteamVRBindings\generic_hmd.json

Contents are the same:

{
“name”: “Default bindings for Generic Headset”,
“controller_type”: “generic_hmd”,
“bindings”:
{
“/actions/main”:
{
“sources”: [
{
“mode”: “button”,
“path”: “/user/head/proximity”,
“inputs”:
{
“click”:
{
“output”: “/actions/main/in/SteamVR_Proximity”
}
}
}
]
}
},
“description”: “Obduction”
}

DrWilken · August 15, 2019, 6:57pm

Checking the SteamVR logs shows the following interesting entries:

Thu Aug 15 2019 20:43:50.048 - steam.app.306760 (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FObduction%2FObduction%2FConfig%2FSteamVRBindings%2Fgeneric_hmd.json

Thu Aug 15 2019 20:43:50.048 - steam.app.306760 (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FObduction%2FObduction%2FConfig%2FSteamVRBindings%2Fvive_controller.json

Thu Aug 15 2019 20:43:50.048 - openvr.component.vrcompositor (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Fvrcompositor_bindings_generic_hmd.json

Thu Aug 15 2019 20:43:50.048 - openvr.component.vrcompositor (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Fvrcompositor_bindings_vive_controller.json

Thu Aug 15 2019 20:43:50.049 - ovras-team.advancedsettings (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%2FOpenVR-AdvancedSettings%2Fdefault_action_manifests%2Fovras-team.advancedsettings_default_hmd.json

Thu Aug 15 2019 20:43:50.049 - ovras-team.advancedsettings (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%2FOpenVR-AdvancedSettings%2Fdefault_action_manifests%2Fovras-team.advancedsettings_default_vive_controller.json

Thu Aug 15 2019 20:43:50.050 - system.generated.steam.exe (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Flegacy_bindings_generic_hmd.json

Thu Aug 15 2019 20:43:50.050 - system.generated.steam.exe (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fdrivers%2Fhtc%2Fresources%2Finput%2Flegacy_bindings_vive_controller.json

Thu Aug 15 2019 20:43:50.050 - htc.vive.overlay (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Flegacy_bindings_generic_hmd.json

Thu Aug 15 2019 20:43:50.050 - htc.vive.overlay (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fdrivers%2Fhtc%2Fresources%2Finput%2Flegacy_bindings_vive_controller.json

Thu Aug 15 2019 20:43:50.051 - system.vrwebhelper.controllerbinding (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Flegacy_bindings_generic_hmd.json

Thu Aug 15 2019 20:43:50.051 - system.vrwebhelper.controllerbinding (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fdrivers%2Fhtc%2Fresources%2Finput%2Flegacy_bindings_vive_controller.json

Thu Aug 15 2019 20:43:50.051 - steam.overlay.908520 (aapvr_hmd) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fresources%2Fconfig%2Flegacy_bindings_generic_hmd.json

Thu Aug 15 2019 20:43:50.052 - steam.overlay.908520 (vive_controller) attempting to load default config from file:///C%3A%2FProgram%20Files%20%28x86%29%2FSteam%2Fsteamapps%2Fcommon%2FSteamVR%2Fdrivers%2Fhtc%2Fresources%2Finput%2Flegacy_bindings_vive_controller.json

Thu Aug 15 2019 20:43:50.132 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/right/input/b)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/left/input/b)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/right/input/b)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/right/input/a)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/left/input/b)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/left/input/a)

Thu Aug 15 2019 20:43:50.133 - Invalid input type click for controller (/user/hand/left/input/thumbstick)

Thu Aug 15 2019 20:43:50.133 - Item /user/hand/left/input/skeleton/left in “skeleton” array missing path invalid device path for skeleton output

Thu Aug 15 2019 20:43:50.133 - Item /user/hand/right/input/skeleton/right in “skeleton” array missing path invalid device path for skeleton output

Thu Aug 15 2019 20:43:50.134 - Couldn’t find action /actions/lasermouse/in/TrackpadScroll. Ignoring it.

Thu Aug 15 2019 20:43:50.134 - Couldn’t find action /actions/lasermouse/in/TrackpadScroll. Ignoring it.

Thu Aug 15 2019 20:43:50.135 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.135 - Unknown action set /actions/main

Thu Aug 15 2019 20:43:50.136 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.137 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.137 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.138 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.146 - Couldn’t find action /actions/lasermouse/in/TrackpadScroll. Ignoring it.

Thu Aug 15 2019 20:43:50.147 - Couldn’t find action /actions/lasermouse/in/TrackpadScroll. Ignoring it.

Thu Aug 15 2019 20:43:50.150 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.152 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: Reading data from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\rendermodels\vr_controller_vive_1_5\vr_controller_vive_1_5.json

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=base inputRouting=0 filename=

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=body inputRouting=0 filename=body.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=button inputRouting=1 filename=button.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=gdc2015 inputRouting=0 filename=

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=handgrip inputRouting=0 filename=

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=led inputRouting=0 filename=led.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=lgrip inputRouting=1 filename=l_grip.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=rgrip inputRouting=1 filename=r_grip.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=scroll_wheel inputRouting=2 filename=scroll_wheel.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=status inputRouting=0 filename=status.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=sys_button inputRouting=1 filename=sys_button.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=tip inputRouting=0 filename=

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=trackpad inputRouting=2 filename=trackpad.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=trackpad_scroll_cut inputRouting=0 filename=trackpad_scroll_cut.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=trackpad_touch inputRouting=2 filename=trackpad_touch.obj

Thu Aug 15 2019 20:43:50.152 - RendermodelManager: name=trigger inputRouting=2 filename=trigger.obj

Thu Aug 15 2019 20:43:50.154 - Invalid input type click for controller (/user/head/proximity)

Thu Aug 15 2019 20:43:50.156 - Invalid input type click for controller (/user/hand/right/input/b)

Thu Aug 15 2019 20:43:50.156 - Invalid input type click for controller (/user/hand/left/input/b)

Thu Aug 15 2019 20:43:50.156 - Invalid input type click for controller (/user/hand/right/input/b)

Thu Aug 15 2019 20:43:50.157 - Invalid input type click for controller (/user/hand/right/input/a)

Thu Aug 15 2019 20:43:50.157 - Invalid input type click for controller (/user/hand/left/input/b)

Thu Aug 15 2019 20:43:50.157 - Invalid input type click for controller (/user/hand/left/input/a)

Thu Aug 15 2019 20:43:50.157 - Invalid input type click for controller (/user/hand/left/input/thumbstick)

DrWilken · August 15, 2019, 7:43pm

Digging deeper and deeper…

github.com/ValveSoftware/openvr

SteamVR beta 1.4.1 breaks proximity sensor support through the SteamVR Input API

opened 05:50AM - 17 Apr 19 UTC

closed 06:13PM - 11 Oct 19 UTC

muchcharles

SteamVR beta 1.4.1 seems to have broken the ability to do a generic headset bind…ing for the proximity sensor through SteamVR input (and when SteamVR input is active the legacy way to check the proximity sensor doesn't work). On the prior version this binding would work regardless of headset brand, so long as it had a sensor: ``` { "name": "Default bindings for Generic HMD", "controller_type": "generic_hmd", "bindings": { "/actions/main" : { "sources" : [ { "inputs" : { "click" : { "output" : "/actions/main/in/generic_hmd_proximitysensor" } }, "mode" : "button", "path" : "/user/head/proximity" } ] } }, "description": "" } ``` The action's bActive and bData now always return false starting in 1.4.1. I can give you a reproducing steam app id if needed. I tested on stable and things work fine. The prior beta before 1.4.1 worked fine too.

Which leads to:

github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings

Prox sensor re-integration

OpenVR-Advanced-Settings:master ← OpenVR-Advanced-Settings:proxsensor

opened 10:31PM - 11 Jun 19 UTC

ykeara

+419 -130

fixes #82 fixes #200 updates openVR api to 1.4.18 moved proximity sensor …to haptic instead of Misc fixed a change to getting openVR path from 1.4.18 we are now limited to 16k character directory paths. **Notes:** ~~Currently not checking if an HMD has a prox sensor.... need to see what state ones w/o it default to.~~ * the property for having a prox sensor does not appear to be set on vive (possible issue w/ using generic hmd?) and probably won't be set.... as such its better to assume that it exists. * ~~NEED testing on both PTT AND chaperone warnings on hmd w/o prox sensor.~~ WHILE I did not test on an hmd w/o a prox sensor, I broke the json file so it would not load.... giving us the same result? (i.e. ideally gets tested on a pimax hmd or another one w/o prox sensor) Behavior: **Chaperone Warnings:** If prox sensor action sets a value (i.e. have a working prox sensor) we will then use prox sensor all the time for turning off haptic and sounds. **Notes** - The alarms will trigger like "no prox sensor" until it turns on for the first time... (i.e. disable after ~15 seconds inactivity) - The alarms WILL NOT TRIGGER while dashboard open if prox sensor is used (but will if its not used) - At some point for Headset should check k_EDeviceActivityLevel_UserInteraction_Timeout (.5 second delay? new?) instead of k_EDeviceActivityLevel_Idle.... This may allow the removal of prox sensor code in chaperone warnings altogether, but will be looked at in the future. **PTT:** if no prox sensor & option is checked mic will be muted (will work regularly if you un-check)

WHILE I did not test on an hmd w/o a prox sensor, I broke the json file so it would not load… giving us the same result? (i.e. ideally gets tested on a pimax hmd or another one w/o prox sensor)

And the latest OpenVR-AdvancedSettings:

Haptics:

Proximity Sensor - Allows us to communicate with prox sensor, IS AUTOMATICALLY BOUND DO NOT ASSIGN

I think I might need to try uninstalling Advanced Settings (though I use it a lot!)…

EDIT: No dice either…

Heliosurge · August 16, 2019, 12:55am

Maybe. But key difference of mine is Gog. Might be game directory structure. I have steamvr in the obduction game directory. (Ie steam settings & openvr.dll)

Maybe try launching with LH tracking off.

DrWilken · August 16, 2019, 5:33am

Tried that too. Didn’t work either.

DrWilken · August 16, 2019, 6:22am

Might also be possible to do something with Controller Bindings in SteamVR as “SteamVR_Proximity” can be found as a shortcut.

DrWilken · August 16, 2019, 8:22am

Making a “chord” in Controller Bindings SteamVR_Proximity on Left Touchpad Touch for example didn’t work either.

I’ve sent the SteamVR logs to Cyan and asked them if they could create a config file for “aapvr_hmd” which disables proximity sensor checking…