Another 10001.9 Vive Pro Wireless thread.

[rowan_u]

Same old story, 10001.9 pops up, only a reboot will clear it.  Sometimes it runs perfectly fine for hours (8+ hours straight is my record)  Other times it 10001.9's every few minutes.  Have been troubleshooting this for MONTHS at this point.  If anybody has any new insights on this issue I would really appreciate it.  Thanks!

 

Some other threads.

Some more.

@jagibson @Synthesis

 

[CMDRZOD]

Just found this in a log file from the system info program:

[2020-05-10 13:11:32.053 -7 0x4A84 INFO LOG] MCU Update Closed. Wait for 3 seconds.
[2020-05-10 13:11:35.082 -7 0x4A84 INFO LOG] [SetCosmosAudio] Launch OK.
[2020-05-10 13:11:35.099 -7 0x4A84 INFO LOG] Connection Status set to 5(CONNECTION_STATUS_CONNECTED)
[2020-05-10 13:11:39.261 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.264 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_UNINITIALIZED(1), reason = SDK_CURRENT_STATE_REASON_REQUESTED_BY_APPLICATION(9)
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] [SetCosmosAudio] Terminate OK.
[2020-05-10 13:11:41.265 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.280 -7 0x1060 INFO LOG] Show error code : 10001.9
[2020-05-10 13:11:41.296 -7 0x1060 INFO LOG] Connection Status set to 6(CONNECTION_STATUS_NOT_READY)
[2020-05-10 13:11:41.465 -7 0x4064 INFO LOG] (ControlCenter)CallbackDeviceStatus : SDK_WIGIGFSM_STATE_ERROR(0), reason = SDK_CURRENT_STATE_REASON_PLATFORM_ERROR(15)
 

Seems to be something to do with the Intel SDK software. Would be nice for HTC to address this issue. It plagues many users. 

 

[rowan_u]

11 hours ago, CMDRZOD said:

Seems to be something to do with the Intel SDK software. Would be nice for HTC to address this issue. It plagues many users. 

 

Perhaps it's just something that's impossible to fix . . . it would be nice if they would even just admit its a known issue.  Even with having to reboot the PC every few hours to clear this error, wireless is still the best way to play :)

[JanS19]

Same issue here. Really frustrating, I'm about to contact every Vive-wireless user I know on Reddit and send this hole thing to some gaming-news websites (including those specialized in VR), title "HTC's wireless VR-hardware plagued with issues, no statement from HTC".

Maybe then we'll get a reaction out of them...