Forum Discussion
ianmoran1970SS
9 years agoExplorer
OculusTrcValidator 'Error: Failed to launch the app'
Hi, I've tried to follow the instructions in OculusTrcValidator.txt, but I've been unable to successfully get the OculusTrcValidator to validate an app, using this sort of command line....
OculusTrcValidator.exe --path I:\testapp\testapp\.exe --load_time_ms 8000
the validator loads and runs our unreal windows app, but reports "Error: Failed to launch the app", before booting another instance of the app for each test without closing each.
Can you advise if there are further instructions or requirements to run the tests.
many thanks in advance, Ian.
OculusTrcValidator.exe --path I:\testapp\testapp\.exe --load_time_ms 8000
the validator loads and runs our unreal windows app, but reports "Error: Failed to launch the app", before booting another instance of the app for each test without closing each.
Can you advise if there are further instructions or requirements to run the tests.
many thanks in advance, Ian.
7 Replies
- ianmoran1970SSExplorer
- rboerdijkHonored GuestTrying to run the validator on our game shows the exact same issue: "ERROR: Failed to launch the app". There are no updates for the Oculus App (at least it doesn't report that there are updates) and I'm using the latest released SDK 1.12 with the validator which is included in there.Machine: Windows 10 with NVidia 980Oculus App Version: 1.13.0.362051 ( 1.13.0.361842)Oculus SDK Used for compiling the game: 1.12, using the validator from this SDK"OculusTrcValidator.exe --version" returns "OculusTrcValidator.exe version: 0.1"1. you may be using a version of TRC validator that is mismatched with the version of Oculus runtime you have installed-> How do I check it they match? afaik both are the latest build available.. ?
2) you may not be running the TRC validator from the normal install location
-> Do you mean that tool has to be launched from the directory it is installed in ( since our game requires the working directory to be that where the executable is to locate it's resource-files ). Either way, launching the validator from the install location on a game from the Oculus-store didn't work either and reported the same error (see below)
Running the validation-tool in verbose-mode seems to give a clue to what is wrong: "Method not allowed for third party clients (1971049)"... ?
Regards---Trying with our Game, running from our game-directory with the following .bat file:"%ProgramFiles%\Oculus\Support\oculus-trcvalidator\OculusTrcValidator.exe" --max_time_to_frame 60 --load_time_ms 40000 --path .\game.exe --log_file trc.logThe game is launched and displayed in the HMD, the console displays this:Starting TestSdkVersionINFO: SDK version requested 1.12... and then after a little while the console shows:ERROR: Failed to launch the appINFO: Cleaning up...ERROR: Could not quit application gracefully in 30 seconds, force quittingTest Failed---Running with our game, with the validator in verbose mode:D:\projects\game\data>"C:\Program Files\Oculus\Support\oculus-trcvalidator\OculusTrcValidator.exe" --max_time_to_frame 60 --load_time_ms 40000 --path .\game.exe --log_file trc.log -vStarting TestSdkVersionINFO: Sending message to OAF: {"requestData":{"wearing_hmd":true},"requestName":"/life_cycle/proximity_sensor","sequenceId":"0"}INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038232"}INFO: Sending message to OAF: {"requestData":"","requestName":"/life_cycle/get_actual_location","sequenceId":"0"}INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038240"}INFO: SDK version requested 1.12INFO: Sending message to OAF: {"requestData":"","requestName":"/life_cycle/get_top_app_render_pid","sequenceId":"0"}INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038717"}---Trying the validator on "TheBodyVR" from the Store, running from the directory of the validator:OculusTrcValidator.exe --max_time_to_frame 60 --load_time_ms 40000 --path "C:\Program Files\Oculus\Software\Software\moshe-ben-zacharia-the-body-vr-rift\TheBodyVR_Oculus_Rift_1_8_0\TheBodyVR.exe" --log_file trc.logStarting TestSdkVersionINFO: SDK version requested 1.7INFO: SDK version requested 1.7INFO: Engine Identification -EngineName: UnityEnginePluginName: OVRPluginEnginePluginVersion: 1.7.0EngineVersion: 5.3.6.3683664ERROR: Failed to launch the appINFO: Cleaning up...Test Failed - kalmiyaHonored GuestTrying to run the validator on our game shows the exact same issue: "ERROR: Failed to launch the app". There are no updates for the Oculus App (at least it doesn't report that there are updates) and I'm using the latest released SDK 1.12 with the validator which is included in there.Machine: Windows 10 with NVidia 980
Oculus App Version: 1.13.0.362051 ( 1.13.0.361842)
Oculus SDK Used for compiling the game: 1.12, using the validator from this SDK
"OculusTrcValidator.exe --version" returns "OculusTrcValidator.exe version: 0.1"1. you may be using a version of TRC validator that is mismatched with the version of Oculus runtime you have installed
-> How do I check it they match? afaik both are the latest build available.. ?2) you may not be running the TRC validator from the normal install location
-> Do you mean that tool has to be launched from the directory it is installed in ( since our game requires the working directory to be that where the executable is to locate it's resource-files ). Either way, launching the validator from the install location on a game from the Oculus-store didn't work either and reported the same error (see below)
---
Trying with our Game, running from our game-directory with the following .bat file:"%ProgramFiles%\Oculus\Support\oculus-trcvalidator\OculusTrcValidator.exe" --max_time_to_frame 60 --load_time_ms 40000 --path .\game.exe --log_file trc.logThe game is launched and displayed in the HMD, the console displays this:
Starting TestSdkVersion
INFO: SDK version requested 1.12... and then after a little while the console shows:ERROR: Failed to launch the app
INFO: Cleaning up...
ERROR: Could not quit application gracefully in 30 seconds, force quitting
Test Failed---Running with the validator in verbose mode:D:\projects\game\data>"C:\Program Files\Oculus\Support\oculus-trcvalidator\OculusTrcValidator.exe" --max_time_to_frame 60 --load_time_ms 40000 --path .\game.exe --log_file trc.log -v
Starting TestSdkVersion
INFO: Sending message to OAF: {"requestData":{"wearing_hmd":true},"requestName":"/life_cycle/proximity_sensor","sequenceId":"0"}
INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038232"}INFO: Sending message to OAF: {"requestData":"","requestName":"/life_cycle/get_actual_location","sequenceId":"0"}
INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038240"}INFO: SDK version requested 1.12
INFO: Sending message to OAF: {"requestData":"","requestName":"/life_cycle/get_top_app_render_pid","sequenceId":"0"}
INFO: Response from OAF: {"messageType":"RESPONSE","payload":{"description":"OVR80289191","errorCode":"1971049","notificationType":"ERROR","stackTrace":"","title":"Error occurred","untranslatedErrorMessage":"Method not allowed for third party clients (1971049)"},"payloadType":"NOTIFICATION","sequenceId":"0","timestamp":"1490714038717"}
---
Trying the validator on "TheBodyVR" from the Store, running from the directory of the validator:OculusTrcValidator.exe --max_time_to_frame 60 --load_time_ms 40000 --path "C:\Program Files\Oculus\Software\Software\moshe-ben-zacharia-the-body-vr-rift\TheBodyVR_Oculus_Rift_1_8_0\TheBodyVR.exe" --log_file trc.logStarting TestSdkVersion
INFO: SDK version requested 1.7
INFO: SDK version requested 1.7
INFO: Engine Identification -
EngineName: Unity
EnginePluginName: OVRPlugin
EnginePluginVersion: 1.7.0
EngineVersion: 5.3.6.3683664ERROR: Failed to launch the app
INFO: Cleaning up...
Test Failed - kalmiyaHonored GuestI noticed an updated Tools in the following post: https://forums.oculus.com/developer/discussion/51150/download-link-for-the-oculus-debug-tool-for-1-13#latest. It contains an "OculusTrcValidator.exe" with version 0.1 (same version as in the 1.12 SDK) but the executable size is different. Installed it and ran the tool (it does mention that you only need to restart the service if you never installed the tool before), resulted in the same problem.
Rebooted the machine, just in case. Oculus home reported an Update (which I ignored) and ran the tool again - and now it works, nice!
It would be cool if the version of the tool would be updated on each release (to avoid confusion) and also if the tool would be able to tell you if it's mismatching with the installed oculus-runtime (expected version x, running version y), maybe even show a link to where the latest version of the tool can be downloaded. - rboerdijkHonored Guest
- rboerdijkHonored GuestRunning latest available versions:
OculusTrcValidator.exe version: 1.15.0.0 ( from the 1.15 SDK)
Oculus Home: App Version: 1.16.0.409144 (1.16.0.409268)Again running into "ERROR: Failed to launch the app" trying to run the trc-tests. Last time it was mentioned that the version of the validation-tool and the oculus-home runtime have to match, which is obviously not the case... where can I find the 1.16 validation tool ?
btw, thanks for updating the tool, so you can specify the tests to run
Note: I already posted in https://forums.oculus.com/developer/discussion/51150/download-link-for-the-oculus-debug-tool-for-1-13#latest which probably wasn't the best location, so feel free to remove the other post) - rboerdijkHonored GuestRunning latest available versions:
OculusTrcValidator.exe version: 1.15.0.0 ( from the 1.15 SDK)
Oculus Home: App Version: 1.16.0.409144 (1.16.0.409268)Again running into "ERROR: Failed to launch the app" trying to run the trc-tests. Last time it was mentioned that the version of the validation-tool and the oculus-home runtime have to match, which is obviously not the case... where can I find the 1.16 validation tool ?
btw, thanks for updating the tool, so you can specify the tests to run
Note: I already posted in https://forums.oculus.com/developer/discussion/51150/download-link-for-the-oculus-debug-tool-for-1-13#latest which probably wasn't the best location, so feel free to remove the other post)
Quick Links
- Horizon Developer Support
- Quest User Forums
- Troubleshooting Forum for problems with a game or app
- Quest Support for problems with your device
Other Meta Support
Related Content
- 3 years ago