NavMesh not recognised in IL2CPP builds
We have recently run into some problems with navigation in a Quest 2/3 project. Navmesh agents which functioned perfectly in the editor were not working in our test builds for android. After some testing we've learned that when building for Windows or Android, if the Mono backend is available and used, everything behaves as expected, but switching to IL2CPP causes the below error messages, regardless of whether the navmesh agent is pre-existing or instantiated at runtime. I have already tried many potential solutions including Warp() or setting position before enabling the agent, rebuilding NavMeshSurfaces at runtime before instantiating the agents, and have switched back to the legacy NavMesh system to rely on baked navmesh data, none of which have changed anything. We have tested with extremely basic Navmesh agent wander behaviour and it seems clear that the backend is somehow affecting the references to Navmesh or the mesh data itself. Has anybody experienced this problem, or do you have any ideas for workarounds/solutions? I hope someone can help, thanks!621Views0likes0CommentsUnity App Crashing on Quest
After building our metaverse application and not having tested in a while, it seems to not be running and instead crashing on each launch. Oculus firmware 50 seems to be the cause of this. We are using 2021.3 LTS and IL2CPP with Arm64. The error is a Sigabrt Signal 6 Code -1 Fatal Exception Java Lang Error. The app seems to be working with Mono Arm7 but only when it doesn't have more than like 4 scenes. I hear that firmware 50 may have Android 12 and was released for early access users. We've tried everything in the book to fix this, and apparently the performance isn't going to be the same either even if we do get it to run. We are going to update to Unity 2022 to see if this fixes anything but we've been spinning our wheels like crazy. Please let me know if you have any ideas as to why it is suddenly crashing without explanation.Solved11KViews2likes10Comments