Error: "Saving Prefab to immutable folder is not allowed" in Unity with Meta All-In-One SDK
I am setting up a fresh Unity project for a VR project that uses Meta All-In-One SDK. To do this, I created a new 3D built-in render pipeline project, and I imported the Meta-All-In-One SDK (ver.68, but this happens with the 66 as well) from the Package Manager. After the package is imported, I fix and apply all the reccomended fixes, set up the build for Android, and select Oculus as XR plugin manager. Right after doing these operations, and as soon as I save the project, immediately an error pops up: Saving Prefab to immutable folder is not allowed: Packages/com.meta.xr.sdk.interaction.ovr/Editor/Blocks/Interactors/Prefabs/[BB] Hand Ray.prefab UnityEditor.EditorApplication:Internal_CallGlobalEventHandler () This happens mainly on these two objects: BB hand ray, and OVR camera rig interaction. Important to note is that no game objects or prefabs were added to the scene (that contains only Main Camera and Directional Light). This is a problem because is affecting the Build and Run operation, returning in errors when building Player. I also had a try on another, more developed project, and this same error happens, but the Play mode with Quest Link is not affected at all and the app works perfectly, when not built. Does anybody have this same experience and problem? If so, does anyone came up with a solution? I would greatly appreciate any help. Thanks a lot
Blocky, terrible realtime shadows in Quest app built in Unity.
Hello, I am building an architectural visualization app for meta quest devices using Unity 2022 and Meta Interaction SDK v68. I am using realtime lighting where the user is able to manipulate the time of the day using a slider in real time to see how their apartment would look under different light conditions. No matter what light / shadow setting I set, in the headset build the shadows look blocky and pretty hideous. I made sure to: - Remove the window glasses with transparent material which could have affected the quality of the light coming through, - Adjusted URP settings to have highest resolution shadows, adjusted the cascades to make sure highest quality shadows within 25 meters, - Adjusted the light / skylight settings to make sure I have highest shadow quality and soft shadows. When I manipulate the direction of the directional light in the editor, I get flawless shadows: But as you can see above, the build one suffers from blocky, glitchy looking light. I would be grateful for any insight into why this is happening and if there is a fix. Best,
RayInteractor -> Data (Optional field)
Hello, I'm working on pointer events and the RayInteractor -> Data field seems to be exactly what I need. Reading the helper text gives me the impression that I can assign the current eventData to the RayInteractor to identify and match an event with the RayInteractor. Which is what I want. But i'm not understanding how to utilize this Data field. It only takes an Object, meaning it can be pretty much anything from a sprite to a gameobject and I don't see how that works. The documentation doesn't tell me much, perhaps someone understands it better than me. https://developer.oculus.com/reference/unity/v67/class_oculus_interaction_ray_interactor/ Does anyone have an idea?
