Cannot run OculusDebugTool.exe & Black screen when trying to enter Link Rift via Device
Hi there, i am currently experiencing 2 issues. The first is that whenever i connect via my link cable to the Quest 2, after attempting to enter PCVR through the link button from the quest 2 device, all i see is a black screen or sometimes 3 dots. I have been told a solution to this is to reduce the resolution on the oculusdebugtool, however, when attempting to run this tool in the oculus-diagnostics folder, i get an error message which reads: "Unable to connect to service. Unable to locate LibOVRRT symbol: ovr_GetControllerPositionUncertainty Error code:-3023 Version: 23.0.0.43.517. Does anyone have any idea how i can solve these problems? It would be much appreciated :D!!1.6KViews0likes1CommentOculusTrcValidator fails and OculusDebugTool crashes
I am trying to test an app using the OculusTrcValidator before uploading it to the Oculus Store. When I run the Validator: $ ./OculusTrcValidator.exe --path "/c/Program\ Files/High\ Fidelity\interface.exe" -v Almost all of the tests fail like this: Starting TestSdkVersion Sending message to OAF: {"requestData":{"wearing_hmd":true},"requestName":"/life_cycle/proximity_sensor","sequenceId":"128"} Response from OAF: {"messageType":"RESPONSE","payload":{"value":"OK"},"payloadType":"PLAIN_STRING","sequenceId":"128","timestamp":"1540425588143"} ERROR: Application launch was cancelled ERROR: Setup test failed because application couldn't be started. HRESULT: 1223 Cleaning up... Sending message to OAF: {"requestData":{"wearing_hmd":false},"requestName":"/life_cycle/proximity_sensor","sequenceId":"129"} Response from OAF: {"messageType":"RESPONSE","payload":{"value":"OK"},"payloadType":"PLAIN_STRING","sequenceId":"129","timestamp":"1540425588219"} Test FAILED The same thing happens when I try to validate an app that I've downloaded from the Oculus Store, so it's not an issue with the application I'm testing. I've tried to use the OculusDebugTool GUI to do it, but it crashes very quickly if I open "Validate App" and try to do anything (choose a file, select a test, run, etc.). Does anyone have any advice? Thank you.4.7KViews1like24CommentsFrame loss capture tool causing frame loss?
As the title says when I activate the frame loss capture tool (Ver 1.35.00) it uses around 26% of my CPU, this is causing frame loss. Is anyone else having this problem? I am trying to validate my build before I submit to the store but because this tool is so processor heavy I am getting false readings, if I have someone watch the task manager and resource monitor in windows while I play, I average 50% cpu usage with short spikes on loading of 75%, gpu sits under 50% at all times. It feels butter smooth, but with the frame loss capture tool running it jumps and stutters.822Views0likes1CommentOculusDebugTool "can`t find HMD or not connected"
Hello everyone! :) Need help again :( i download OculusSDK and want to start OculusDebugTool, but it don`t start and give me message like " can`t find HMD or not connected" or something like this :( search and find some topics about this, but don`t have anyone about CV1 version1.5KViews0likes2CommentsOculusDebugTool debug HMD can't work in 1.8 runtime
1. Open oculus store 2. Use 1.8 OculusDebugTool, Debug HMD Type select CV1, than debug window can't display It can work on 1.7 runtime, but after this week update, it can't work. Does anyone have any idea on what else I can try?438Views0likes0Comments