Navi controller crashes SteamVR due to colons vs underscores in serial number

[mjducharme]

Hello,

It took me forever to figure out this problem and I hope this helps somebody.

I connected a PS Navi and SteamVR would crash whenever it was connected. Digging through the log, I saw that it couldn't find the parent controller:

Thu Jan 09 2020 21:44:18.022 - psmove: INFO - added new psmove controller id: 1, serial: 00_06_F7_15_DC_A7
Thu Jan 09 2020 21:44:18.022 - Driver 'psmove' started activation of tracked device with serial number 'psmove_controller1'
Thu Jan 09 2020 21:44:18.022 - psmove: INFO - CServerDriver_PSMoveService::HandleControllerListReponse - Allocate PSNavi(2)
Thu Jan 09 2020 21:44:18.022 - psmove: INFO - Failed to find parent controller serial 00:06:F7:15:DC:A7 for navi controller serial 00:00:00:00:00:00
Thu Jan 09 2020 21:44:18.022 - psmove: INFO - added new psnavi controller id: 2, serial: 00:00:00:00:00:00

When you link the navi to the move with the psmoveconfig tool, it puts colons in the serial number of the attached controller in the json file (psnavi_gamepad_2.json). The SteamVR Bridge compares this serial number (with colons) with the parent serial number (which has underscores) and it doesn't find the parent. The result is SteamVR crashes completely.

The workaround for now is to edit the psnavi_gamepad_2.json in %appdata%\Roaming\PSMoveService and change the attached_to_controller to have underscores instead of colons. Then you can start SteamVR with two moves and a navi attached and it will not crash.

[PantACRO4life]

I tried that It launch with no issue but I can get to navi to send input in anyway in the vr room for some reason. XBOX controller support is disable in my steam big picture. I cant think of anything else