errors

5 Topics

Meta Quest Developer Hub App Distribution error with APK: "can not be launched on Windows platform"
Problem Trying to upload and distribute (alpha) of our pretty stable App built. APK totally runs on Meta Quest, just tested it. But when trying to Distribute getting the error: can not be launched on Windows platform Checked the APK, it looks like many others: ./aapt2 dump badging debug.apk package: name='com.voccent.voccent' versionCode='1' versionName='0.0.117' platformBuildVersionName='' platformBuildVersionCode='' compileSdkVersion='34' compileSdkVersionCodename='14' sdkVersion:'24' targetSdkVersion:'34' Any ideas? Really can't find a solution.
victorbrunko
2 years ago Place General VR & MR Development
841Views
0likes
0Comments
Error Ruined My Unity Project
I keep getting these two errors: 1. Multiple plugins with the same name 'ovrplugin' (found at 'Assets/Oculus/VR/Plugins/1.38.0/Win/OVRPlugin.dll' and 'Assets/Oculus/VR/Plugins/1.38.0/Win64/OVRPlugin.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor. OculusSampleFrameworkUtil:HandlePlayModeState(PlayModeStateChange) (at Assets/Oculus/SampleFramework/Editor/OculusSampleFrameworkUtil.cs:43) UnityEditor.EditorApplication:Internal_PlayModeStateChanged(PlayModeStateChange) 2. Multiple plugins with the same name 'ovrplugin' (found at 'Assets/Oculus/VR/Plugins/1.38.0/Win/OVRPlugin.dll' and 'Assets/Oculus/VR/Plugins/1.38.0/Win64/OVRPlugin.dll'). That means one or more plugins are set to be compatible with Editor. Only one plugin at the time can be used by Editor. Please somebody help me with this
vrguestnet
5 years ago Place Unity Development
1.7KViews
0likes
2Comments
I've updated both unity (2018.3) and Oculus SDK (1.36) and I'm having too many issues, what's wrong?
Hello everyone, I just updated unity to 2018.3.11f1 and Oculus SDK (from store) and after that I get a lot of C# errors, like types and namespaces are not defined or found. Partially solved the issue moving the SDK scripts into plugins (since Unity compiles them first) but I still have these 2 errors that prevent me from compiling the whole project. (""ZEditor" folder is the folder containing all of the scripts that were in the Oculus/VR/Editor folder) Assets/Plugins/ZEditor/OVRSystemProfilerPanel.cs(38,2): error CS0246: The type or namespace name 'OVRNetwork' could not be found (are you missing a using directive or an assembly reference?) Assets/Plugins/ZEditor/OVRSystemProfilerPanel.cs(46,7): error CS0246: The type or namespace name 'OVRSystemPerfMetrics' could not be found (are you missing a using directive or an assembly reference?) Is there any clean way to solve this? I'd like to NOT move those classes into the scripts requiring them
ZioMikeCaste
7 years ago Place Unity Development
472Views
0likes
0Comments
Strange display errors inside the camera rig (both eye anchor)
Hi everyone, I'm developing a simple vr application in Unity 3D for Oculus Rift. I'm Using Unity Oculus Utilities 1.26 and Oculus Avatar SDK 1.26. I've noticed these strange errors inside the both eye anchor (Camera RIG, oculus default prefab): there are some many grey elements flickering and disappering on the screen. On the cameras is aplied Post Processing Stack (I've tried disabling this, but I've the same problem). Do you know what is the cause of this error? I've choose the wrong rendering mode? The UI can give these strange problems? I've attached some errors screenshot and rendering settings. Thanks a lot!
paolo_orabona_
8 years ago Place Unity Development
483Views
0likes
0Comments
[Oculus Staff] Steam Builds not working
Hey guys, I have a quick question for you regarding Oculus under Steam. I have a Oculus game made with unity that is compiling and running just fine (both with DK2 and CV1), it is set for Runtime 1.6 and all is fine and dandy. However when I build it for Steam, the only way to launch the game is directly though the .exe on the folder, any of the Steam launchers won't work (returns "Headset not compatible" error). Now, I know you guys have nothing to do with Steam's shannanigans, but: Are there any issues between Oculus builds and Steam I should be aware of? Is this a documented situation by you guys? Is there a procedure for this on your end? Does anyone found any similar situations? Thank you in advance for the help on this! And please let me know if there are further questions.
GroundControlGa
10 years ago Place PCVR/Link Development
2KViews
0likes
8Comments