Tema: Error que provoca la desconexión de Link
Mensajes
-
8 Ago 2014 11:45
Mensajes: 225
Visores
Oculus Rift Development Kit 2
Cardboard
Oculus Rift
Oculus Quest 2
No se si a alguno os habrá ocurrido algo similar, tras una hora u hora y media con Flight Simulator o DCS se cuelga Link (se queda en negro la pantalla o se queda la imagen estatica, no vuelve al entorno de Quest si no desconecto el cable) aunque el juego sigue funcionando con normalidad. Me ocurre desde hace un par de semanas, antes iba sin problemas.
Del log de Service:
14/01 17:11:25.660 {INFO} [RPCServer [RUNTIMEIPC]] HandleClientDisconnect: Client: WindowsPackage:WindowsProcess:11968:, Server: WindowsPackage:WindowsProcess (HapticsServer)
14/01 17:11:25.660 {INFO} [ThreadHelpers [RUNTIMEIPC]] RuntimeIPC::ThreadHelpers::SetState: threadName: IpcDCReqHandler, currentState: STATE_RUNNING, newState: STATE_STOPPED
14/01 17:11:25.660 {INFO} [RPCServer [RUNTIMEIPC]] HandleClientDisconnect: Client: WindowsPackage:WindowsProcess:11968:, Server: WindowsPackage:WindowsProcess (RuntimeIPCLinkServer)
14/01 17:11:25.660 {INFO} [ThreadHelpers [RUNTIMEIPC]] RuntimeIPC::ThreadHelpers::SetState: threadName: IpcDCReqHandler, currentState: STATE_RUNNING, newState: STATE_STOPPED
14/01 17:11:25.661 {WARNING} [RPCClientHandler [RUNTIMEIPC]] RPCClientHandler::SetClientStateData: Client not valid: Client: WindowsPackage:WindowsProcess:11968:, Server: WindowsPackage:WindowsProcess (HapticsServer)
14/01 17:11:25.661 {INFO} [ThreadHelpers [RUNTIMEIPC]] RuntimeIPC::ThreadHelpers::SetState: threadName: IpcDCReqHandler, currentState: STATE_STOPPING, newState: STATE_STOPPED
14/01 17:11:25.687 {DEBUG} [IPCDataChannelServer [RUNTIMEIPC]] Disconnected: 2741339747, WindowsPackage:WindowsProcess:11968
14/01 17:11:25.687 {INFO} [ThreadHelpers [RUNTIMEIPC]] RuntimeIPC::ThreadHelpers::SetState: threadName: IpcDCReqHandler, currentState: STATE_RUNNING, newState: STATE_STOPPED
14/01 17:11:25.705 {DEBUG} [IPCDataChannelServer [RUNTIMEIPC]] Disconnected: 2741339747, WindowsPackage:WindowsProcess:11968
14/01 17:11:25.705 {INFO} [ThreadHelpers [RUNTIMEIPC]] RuntimeIPC::ThreadHelpers::SetState: threadName: IpcDCReqHandler, currentState: STATE_RUNNING, newState: STATE_STOPPED
14/01 17:11:25.705 {DEBUG} [xrstreaming_v2] receive ping: org 0 recv 0 xmt 5373163868157 (received at 4821489597800), offset divergence 29
14/01 17:11:25.714 {INFO} [Client] pid: 11968, file: (OpenProcess failure)
ovr_Destroy_Impl called.Y del de client:
[(OpenProcess failure) (11968)] 14/01 17:11:25.598 {DEBUG} [D3D11_CliCompositorClient] Detected display loss, unblocking monitored fence
[(OpenProcess failure) (11968)] 14/01 17:11:25.602 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::release 3
[(OpenProcess failure) (11968)] 14/01 17:11:25.602 {DEBUG} [D3D11_CliCompositorClient] Detected display loss, unblocking monitored fence
[(OpenProcess failure) (11968)] 14/01 17:11:25.604 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::release 2
[(OpenProcess failure) (11968)] 14/01 17:11:25.604 {INFO} [OXR] xrDestroySession 0x1002ec000000001
[(OpenProcess failure) (11968)] 14/01 17:11:25.604 {DEBUG} [D3D11_CliCompositorClient] Detected display loss, unblocking monitored fence
[(OpenProcess failure) (11968)] 14/01 17:11:25.605 {DEBUG} [D3D11_CliCompositorClient] CliD3D11CompositorClient::release 1
[(OpenProcess failure) (11968)] 14/01 17:11:25.605 {DEBUG} [D3D11_CliCompositorClient] Unblocking monitored fence
[(OpenProcess failure) (11968)] 14/01 17:11:25.615 {INFO} [D3D11_CliCompositorClient] CliD3D11CompositorClient released
[(OpenProcess failure) (11968)] 14/01 17:11:25.640 {INFO} [TREX] Shutting down system...En el resto no veo nada raro.
¿a alguien se le ocurre algo para solucionarlo?