Can I link my Quest 2 to the Oculus App on PC with a non-supported GPU for development in Unity?
I understand that the Oculus app for PC requires newer, more powerful GPUs in order to link the Quest 2 for PCVR games, however I need to link the Quest 2 to my PC for the purpose of development of a school project in Unity. I'm borrowing the Quest 2 from my school, so I didn't know that it would require such GPUs. From a couple tutorials I've watched, the easiest way to test a playable version of the project that I'm building in Unity is to link the Quest 2 to my PC via a link cable. I've already spent a bit of time setting up and developing my project in Unity, and now I'd like to test if the XR interaction and other elements in my project actually work with the headset. The problem is that my Quest 2 can't link to my PC app, because I have an older laptop with an outdated GPU(NVIDIA GeForce MX150), but my processor should be compatible(Intel Core i5-8250U[8th gen]). I don't actually want to link the Quest 2 to the PC app for any other reason than for my Unity to recognize/use the Quest 2 as the run device. From my understanding, the reason it only lets the Quest 2 pair with newer, more powerful GPUs is so that it can run PCVR games without any problems, but I only want to link it to test my Unity project. I think there is a way to build the project and then move it onto the Quest 2 without the need of a link cable, but that would waste time during production and I'm not totally sure how to do it. Is there any way to link the Quest 2 to the Oculus app on PC just for the sake of development? If not, can anyone point me to any resources to bypass the Oculus app for PC and still be able to test my Unity project?2.1KViews0likes3Comments
Unity Oculus Build failed with IL2CPP
Building an oculus app with Unity 2020.x IL2CPP with target architecture arm64 failed for: Exception: Failed running "response.rsp" stdout: Fatal error in Unity CIL Linker System.InvalidOperationException: No action for the assembly TinCan, Version=1.3.0.0, Culture=neutral, PublicKeyToken=7e2d97554f738180 defined at Mono.Linker.AnnotationStore.GetAction(AssemblyDefinition assembly) at Mono.Linker.Steps.MarkStep.IsFullyPreserved(TypeDefinition type) at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference) at Mono.Linker.Steps.MarkStep.MarkField(FieldDefinition field) at Unity.Linker.Steps.Marking.MonoBehaviourMarking.MarkNeededFields(TypeDefinition type) at Unity.Linker.Steps.Marking.MonoBehaviourMarking.DoAdditionalTypeProcessing(TypeDefinition type) at Unity.Linker.Steps.UnityMarkStep.DoAdditionalTypeProcessing(TypeDefinition type) at Mono.Linker.Steps.MarkStep.MarkType(TypeReference reference) at Mono.Linker.Steps.MarkStep.MarkField(FieldDefinition field) at Mono.Linker.Steps.MarkStep.MarkEntireType(TypeDefinition type) at Mono.Linker.Steps.MarkStep.MarkEntireType(TypeDefinition type) at Mono.Linker.Steps.MarkStep.MarkEntireAssembly(AssemblyDefinition assembly) at Mono.Linker.Steps.MarkStep.InitializeAssembly(AssemblyDefinition assembly) at Unity.Linker.Steps.UnityMarkStep.InitializeAssembly(AssemblyDefinition assembly) at Mono.Linker.Steps.MarkStep.Initialize() at Mono.Linker.Steps.MarkStep.Process(LinkContext context) at Unity.Linker.Steps.UnityMarkStep.Process(LinkContext context) at Mono.Linker.Pipeline.ProcessStep(LinkContext context, IStep step) at Unity.Linker.UnityPipeline.ProcessStep(LinkContext context, IStep step) at Mono.Linker.Pipeline.Process(LinkContext context) at Unity.Linker.UnityDriver.UnityRun(ILogger customLogger) at Unity.Linker.UnityDriver.RunDriverWithoutErrorHandling(ILogger customLogger) at Unity.Linker.UnityDriver.RunDriver() Any Help? Thanks998Views0likes0Comments