Is anyone else experiencing heavy epilepsy inducing (im not exaggerating) needle rendering crashes in the Meta-VR-Headset-Browser when activating VR Mode via the buttons (Needle Bar and Browser VR buttons) since Needle 4.11.0 was released?
Pressing the VR Button makes the browser window go fullscreen (as is normal), i see my scene for a brief moment and then everything freezes … sometimes it looks like something comparable to a visual echo of what was visible at the beginning, sometimes it goes into full on “the whole screen is flickering like hell” Mode O,o
The popping up error message (when force-exiting VR Mode in the browser) sais something along the lines of “Caught exception … rendering loop … look at console…” when it happens in the Meta Browser. Dont know which console is meant there, but neither Unity, nor the server cmd window show anything unusual.
I’m not 100% if its Needle 4.11 or Metas new OS (updated to V81 on my Quest 3 two days ago) which causes this, but Meta definetly changed the OS a lot with this V81 Update, …also forcing users to use their new Ad-filled 3D-Background-Enviroment, which has a new type of “VR App is loading” mechanic -,-
The one thing i can say is, that my Needle 4.10.4 Projects run fine!
Greetings
Hi Aeleks, thanks for the detailed report. From your description, it sounds like the heavy rendering crash could be triggered by changes in how VR mode is handled either in Needle 4.11 or due to the recent Meta OS V81 update on your Quest 3.
Here are a few steps you might take to isolate and potentially work around the issue:
• Verify in the browser’s developer console (using remote debugging on your Quest 3) if there are additional error messages related to the rendering loop or WebGL. The “Caught exception … rendering loop … look at console…” message might be masking further details that could help pinpoint the problem.
• Since your projects built with Needle 4.10.4 work fine, it’s worth checking if any new VR-related changes in 4.11 conflict with Meta OS V81’s updated VR experience (including the ad-filled 3D background and new loading behavior). Testing a minimal reproducible project on our online example tool (Needle-engine - Vite Template (duplicated) - StackBlitz) could help confirm whether the issue is inherent to the engine update or a project-specific conflict.
• If you’re using any custom components or shaders in your VR scene, double-check that they’re fully compatible with the latest rendering loop changes. Sometimes even a minor timing difference can lead to heavy issues in VR mode.
• Finally, submitting a bug report via the Needle Engine menu (“Needle Engine/Report a bug” in Unity) with specific reproduction steps and any available console logs would help the team diagnose the issue more quickly.
Addressing these points should get you closer to understanding whether the crash is directly due to Needle 4.11 or an incompatibility with Meta OS V81. Let me know if you need further assistance or if you can share additional logs, as this will help us better support you.
Hope this helps!
1 replies left - Become PRO for more replies. thread_mxlperrfU7xWMTfAH6XTyq9J Reply to this post directly if you need further help (bottom right button)
Hi, I could reproduce the issue and found the fix. The error was caused by physics raycast hitting an object without geometry where calling getAttribute was not properly safe guarded.
A fix will be available soon today!
Btw the check console message refers to the browser console. When you use Needle Engine you can either append ?console to your URL to get a on-screen console OR you can read console logs on your PC in your web project at node_modules/.needle/logs (for local in-development projects)