VRC Validator

13 Topics

OculusTrcValidator 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.
SamGondelman
7 years ago Place PCVR/Link Development
4.8KViews
1like
24Comments
Where to get more detail docs for VRC Validator?
Hello! I'm trying to use the vrc validator to test the app and got many failures. Attached is the log file. I searched the documentation as well as forum and didn't find much detail info on how to fix each failure. Maybe I didn't get the right place to check that information. Dose anyone meet the same problem? Thanks!
void_main
8 years ago Place PCVR/Link Development
4KViews
0likes
3Comments
How to pass VRC TestLaunchIntoVR
When I used VRC toolto test the TestLaunchIntoVR for the app, I got the error "The application took too long to submit the first frame". The reference link page said that If your app takes longer than 4 seconds to launch, you must provide a head-tracked loading indicator. Head-tracked means the UI elements must remain stationary in space when the user turns their head. Do not lock any logos or progress indicators to the user’s face. For my app, there is no UI element or other game object locking to the user's face at the first 15 secs, but the app can't pass the test. Can someone give an example for this to help me to understand it better? Thanks!
void_main
8 years ago Place PCVR/Link Development
3.6KViews
0likes
12Comments
VRC TestAppShouldQuit fails erroneously
The VRC check fails with this log: ''' Starting TestAppShouldQuit Waiting for the application to run for 5 seconds before testing begins... Starting test... Sending a request to quit... Failed to receive a call for ovr_Destroy on attempt to quit in 30 seconds ''' I am 100% positive that my game is quiting gracefully. When manually testing the quit behavior from both the Oculus Home "return to menu" and Rift Core 2 Oculus Dash quit, my game promptly quits. I can confirm that Application.Quit() is being called in OVRManager. I'm uncertain about ovr_Destroy because I am using Unity and assuming that it is being called under the hood. How serious of a failure is this and would it prevent a successful submission to the Oculus Store?
SplicedDNA
8 years ago Place Unity Development
2.5KViews
0likes
9Comments
VRC.PC.Audio.1 - TestAudioOutput: Failed
Hi there. I have been running the VRC validator on a build of my UE4 game (latest 4.19 Epic launcher release) and it has been failing at the audio test. I have the Oculus Audio plugin enabled and I'm not using any external audio tools. From what I gather it seems that it should just work with UE4 without changing any settings, is that right? If not, does anyone have any idea what I'm doing wrong? Thanks!
Anonymous
8 years ago Place Unreal Development
2.5KViews
0likes
7Comments
VRC Validator 1.20.0.0 fails my Unreal engine app, claiming it's built with an old Unity version
When running the VRC Validator on my app built in Unreal engine, it states the following: Starting TestSdkVersion SDK version detected 1.17 for processId 0x22d8 SDK version detected 1.17 for processId 0x22d8 Engine Identification for processId 0x22d8 EngineName: Unity EnginePluginName: OVRPlugin EnginePluginVersion: 1.19.0 EngineVersion: ++UE4+Release-4.18- ERROR: The application is built against an older Unity version Please refer to VRC Guidelines: https://developer.oculus.com/distribute/latest/concepts/publish-reqs-rift-compatibility/#unity Cleaning up... Test FAILED All the other tests pass without any issues, so I was wondering if anyone has any clues on how to solve this?
Hejden
8 years ago Place Unreal Development
1.4KViews
0likes
5Comments
Validation Questions
Hi everyone, I've been using VRC Validator 1.20.0.0 to test the latest builds of my company's game before we submit it in a few weeks' time, but there are a few tests we're failing that we can't find solutions for. Specifically: 1. TestSDKVersion: We're using Unity 2017.2.0p2 with the 1.20.0 versions of Oculus Utilities and Platform SDK, but the validator does not recognise the Unity version (outputs "EngineVersion: 0.0.0"), so we fail the test. The plugin download page and Compatibility and Version Requirements page both state that 2017.2 is officially supported. Are apps built on this version being accepted for store submissions yet? 2. TestLaunchIntoVR: Our app is taking around 5.6 seconds to launch, so it fails to meet the 4-second threshold. We first load an empty scene (with the player object and a black background) to handle the entitlement check, and if that succeeds, we then load the main menu scene, which happens almost instantly. However, as we're using Unity Personal, the "Made with Unity" splash screen appears on the monitor (not in the HMD) before any of our scenes load. Our only other option is to replace it with our logo using the "VR splash screen" option, but the launch time remains at 5.6 seconds. Does anyone know if it's possible to pass this test with Unity Personal's enforced splash screen? 3. TestAudioOutput: This fails with the following error message: "ERROR: Application should not have played sound thru Rift Audio Device". I tried looking for a solution, but found conflicting information. Some people said Unity is supposed to handle this automatically, while others said the user's audio preferences in the Oculus app should be referenced manually (but did not say how). We are not using any Oculus audio plugins or other third-party audio solutions, and sound successfully plays through the HMD when playing the game. Does anyone have any advice for how to address this problem? Any help would be greatly appreciated.
RobAC94
8 years ago Place Unity Development
1.3KViews
0likes
3Comments
VRC Validation - Unity 2017
I believe I'm running into some of the same problems @RobAC94 was having. Since 1.21 runtime hasn't been released yet, I'll assume that TestSDKVersion isn't going to be a problem. I'm using Unity 2017.2.0f3, and the test shows Engine Version at 0.0.0. TestLaunchIntoVR also fails, I'm thinking because of the Unity intro screen. Again, shouldn't be a problem. TestFrameRate is where I start having other issues that I'm unsure of. Using --print_fps shows me consecutive 90 fps until "ERROR: INTERNAL ERROR: Events Lost" and then test failure. I first load to a scene with nothing more than a cube and a single canvas, so I don't know what could be going wrong. TestSubmitFramesWhenVisible, TestResponseToRecenterRequest, TestAppShouldQuit, and TestAudioOutput all throw the same internal error message and failures. I see in the docs that I should be polling for "ovr_GetSessionStatus". I'm guessing some of the 'Events Lost' are in relation to this. But the code found here in the docs (p 42-44) references variable types that weren't imported with the Unity OVR or Platform packages. Is there something I'm missing? My app handles lost focus via Unity's XR.XRDevice.userPresence, and re-centering through XR.InputTracking.Recenter(), audio works fine, and the app can close gracefully. How do I poll for ovr_GetSessionStatus in Unity/C#?
Anonymous
8 years ago Place Unity Development
1.3KViews
0likes
3Comments
How to pass VRC.PC.Performance.3 (maintain 90fps) for loading
I just read https://developer.oculus.com/distribute/latest/concepts/vrc-pc-performance-3/, it says that it's acceptable if I have a loading screen. Now I use OVROverlay to make loading screen, but will the VRC validator know that there is an overlay when it's loading? The VRC validator still reports the fps test failed even I use the overlay, so I wonder who can decide if the loading overlay is acceptable when the fps is low? Thanks
james_lue
7 years ago Place Unity Development
1.3KViews
0likes
4Comments
Unable to validate
We're currently in the process of submitting our app to the store but we ran into a few problems so here are my questions: Initially when setting up app for Oculus store, I ran the VRC Validator on the app. It worked and everything checks out. Made some changes in-game logic, made another build to same directory, but now validator errors out and fails all checks. It doesn't even open the app. Any insights here? The entitlement check in-game works fine, so I'm not sure where I'm going wrong with this. Another thing, playing the standalone build works fine, but when playing the downloaded app from the store, it closes after a few seconds into the game. It's the same exact build. I also noticed that it is called OculusTrcValidator rather than the VRC. Based on this thread, I have to update the tool? https://forums.oculusvr.com/developer/discussion/49232/oculustrcvalidator-error-failed-to-launch-the-app However the link to update is gone, so I'm a bit lost here.
RLTYCHK
7 years ago Place Unity Development
1.1KViews
0likes
2Comments