Guest User

Untitled

a guest
Jan 21st, 2022
58
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.87 KB | None | 0 0
  1. Admin.exe says:
  2. [2022-01-21 11:17:59.585]: main - Starting PSMoveService v0.9-alpha 9.0.1 (protocol v0.9-alpha 9.0.0)
  3. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\USBManagerConfig.json"
  4. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\USBManagerConfig.json"
  5. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\NetworkManagerConfig.json"
  6. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\NetworkManagerConfig.json"
  7. [2022-01-21 11:17:59.603]: USBAsyncRequestManager::startup - Requested LibUSBApi
  8. [2022-01-21 11:17:59.613]: USBAsyncRequestManager::startup - Creating LibUSBApi
  9. [2022-01-21 11:17:59.636]: USBAsyncRequestManager::startup - Initialized USB API
  10. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\DeviceManagerConfig.json"
  11. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\DeviceManagerConfig.json"
  12. [2022-01-21 11:17:59.661]: DeviceManager::startup - Platform Hotplug API is ENABLED
  13. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\ControllerManagerConfig.json"
  14. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\ControllerManagerConfig.json"
  15. [2022-01-21 11:17:59.728]: bluetooth_get_host_address - Found a bluetooth radio
  16. [2022-01-21 11:17:59.729]: bluetooth_get_host_address - Retrieved radio info
  17. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\TrackerManagerConfig.json"
  18. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\TrackerManagerConfig.json"
  19. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\HMDManagerConfig.json"
  20. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\HMDManagerConfig.json"
  21. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_08#6&32E8A42E&0&0008' is no longer connected!
  22. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_04#6&32E8A42E&0&0004' is no longer connected!
  23. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_05#6&32E8A42E&0&0005' is no longer connected!
  24. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_06#6&32E8A42E&0&0006' is no longer connected!
  25. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  26. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  27. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  28. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  29. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  30. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  31. [2022-01-21 11:17:59.922]: PSNaviController::open - Opening PSNaviController(gamepad_0)
  32. [2022-01-21 11:17:59.923]: PSNaviController::open - Successfully opened gamepad: XInput Controller 1 #0
  33. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\psnavi_gamepad_0.json"
  34. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\psnavi_gamepad_0.json"
  35. [2022-01-21 11:17:59.929]: DeviceTypeManager::update_connected_devices - Device device_id 0 (PSNavi) opened
  36. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_08#6&32E8A42E&0&0008' is no longer connected!
  37. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_04#6&32E8A42E&0&0004' is no longer connected!
  38. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_05#6&32E8A42E&0&0005' is no longer connected!
  39. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_06#6&32E8A42E&0&0006' is no longer connected!
  40. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  41. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  42. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  43. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  44. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  45. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  46. [2022-01-21 11:17:59.946]: MorpheusHMD::open - Opening MorpheusHMD(USB\VID_054c&PID_09af).
  47. [2022-01-21 11:17:59.948]: MorpheusHMD::open - Morpheus command interface is flagged as DISABLED.
  48. [2022-01-21 11:17:59.950]: MorpheusHMD::open - Failed to open MorpheusHMD(USB\VID_054c&PID_09af)
  49. [2022-01-21 11:17:59.952]: MorpheusHMD::close - Closing MorpheusHMD sensor interface(\\?\hid#vid_054c&pid_09af&mi_04#7&cc7816f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
  50. [2022-01-21 11:17:59.955]: DeviceTypeManager::update_connected_devices - Device device_id 0 (USB\VID_054c&PID_09af) failed to open!
  51. [2022-01-21 11:18:00.871]: ClientConnection::start - Starting client connection id 0
  52. [2022-01-21 11:18:00.873]: ClientConnection::send_connection_info - Sending connection id to client 0
  53. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_08#6&32E8A42E&0&0008' is no longer connected!
  54. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_04#6&32E8A42E&0&0004' is no longer connected!
  55. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_05#6&32E8A42E&0&0005' is no longer connected!
  56. libusb: error [init_device] device '\\.\USB#VID_054C&PID_09AF&MI_06#6&32E8A42E&0&0006' is no longer connected!
  57. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  58. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  59. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  60. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  61. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  62. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  63. libusb: error [windows_get_device_list] program assertion failed - existing device should share parent
  64. [2022-01-21 11:18:09.541]: PSMoveController::open - Opening PSMoveController(\\?\hid#vid_054c&pid_03d5&col01#7&32e3586b&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
  65. [2022-01-21 11:18:09.544]: PSMoveController::open - with EMPTY serial_number
  66. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\30_c3_d9_0d_ee_de.json"
  67. [2022-01-21 11:18:09.693]: testMagnetometer - Failed to open read initial controller state after 10 attempts.
  68. [2022-01-21 11:18:09.696]: WorkerThread::start - Starting worker thread: PSMoveSensorProcessor
  69. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\30_c3_d9_0d_ee_de.json"
  70. [2022-01-21 11:18:09.701]: DeviceTypeManager::update_connected_devices - Device device_id 1 (PSMove) opened
  71. [2022-01-21 11:18:09.713]: PSNaviController::open - Opening PSNaviController(gamepad_0)
  72. [2022-01-21 11:18:09.716]: PSNaviController::open - Successfully opened gamepad: XInput Controller 1 #0
  73. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\psnavi_gamepad_0.json"
  74. Config file name: "C:\Users\Toms\AppData\Roaming\PSMoveService\psnavi_gamepad_0.json"
  75. [2022-01-21 11:18:09.722]: DeviceTypeManager::update_connected_devices - Device device_id 2 (PSNavi) opened
  76. [2022-01-21 11:18:09.723]: DeviceTypeManager::update_connected_devices - Closing device 0 (PSNavi) since it's no longer in the device list.
  77. [2022-01-21 11:18:09.726]: PSNaviController::close - Closing PSNaviController(0)
  78. [2022-01-21 11:18:09.734]: MorpheusHMD::open - Opening MorpheusHMD(USB\VID_054c&PID_09af).
  79. [2022-01-21 11:18:09.736]: MorpheusHMD::open - Morpheus command interface is flagged as DISABLED.
  80. [2022-01-21 11:18:09.737]: MorpheusHMD::open - Failed to open MorpheusHMD(USB\VID_054c&PID_09af)
  81. [2022-01-21 11:18:09.739]: MorpheusHMD::close - Closing MorpheusHMD sensor interface(\\?\hid#vid_054c&pid_09af&mi_04#7&cc7816f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030})
  82. [2022-01-21 11:18:09.743]: DeviceTypeManager::update_connected_devices - Device device_id 0 (USB\VID_054c&PID_09af) failed to open!
  83.  
  84. Configtoool.exe says:
  85.  
  86. INFO [Renderer::init()] Initializing Renderer Context
  87. [INFO] ClientNetworkManager::start_tcp_connect - Connecting to: 127.0.0.1:9512...
  88. [INFO] ClientPSMoveAPI - Successfully initialized ClientPSMoveAPI
  89. [INFO] ClientNetworkManager::handle_tcp_connect - Connected to 127.0.0.1:9512
  90. [INFO] ClientNetworkManager::handle_tcp_read_response_header - Received Message Header
  91. [INFO] ClientNetworkManager::handle_tcp_read_response_body - Received Response Body
  92. [INFO] ClientNetworkManager::handle_tcp_response_received - Received notification type 1
  93. [INFO] ClientNetworkManager::handle_tcp_connection_info_notification - Got connection_id: 0
  94. [INFO] ClientNetworkManager::send_udp_connection_id - Sending connection id to server over UDP: 0
  95. [INFO] ClientNetworkManager::handle_udp_write_connection_id - Successfully sent UDP connection id
  96. [INFO] ClientNetworkManager::handle_udp_read_connection_result - UDP Connect Success!
  97. [INFO] handle_server_connection_opened - Connected to service
  98. [INFO] ClientNetworkManager::handle_tcp_read_response_header - Received Message Header
  99. [INFO] ClientNetworkManager::handle_tcp_read_response_body - Received Response Body
  100. [INFO] ClientNetworkManager::handle_tcp_response_received - Received response type 2
  101. [INFO] ClientNetworkManager::handle_tcp_read_response_header - Received Message Header
  102. [INFO] ClientNetworkManager::handle_tcp_read_response_body - Received Response Body
  103. [INFO] ClientNetworkManager::handle_tcp_response_received - Received notification type 4
  104. [INFO] ClientNetworkManager::handle_tcp_read_response_header - Received Message Header
  105. [INFO] ClientNetworkManager::handle_tcp_read_response_body - Received Response Body
  106. [INFO] ClientNetworkManager::handle_tcp_response_received - Received response type 2
Add Comment
Please, Sign In to add comment