Hi, I was testing immersive-vr on pico neo 3 pro and it looks like the buffer isn’t cleared on new render call, so the screen on VR looks like this when moving your head around:
I wanted to ask if you have any idea what could be causing this. The same scene works fine on oculus 3. When I tested it on needle samples, they also worked fine even using the pico. I am using needle 4.3.2-beta.
Hello Vydymil,
The issue you are experiencing with the Pico Neo 3 Pro, where the buffer isn’t clearing during the VR render calls, could relate to how the rendering context and clear flags are set up in your project.
Here’s a breakdown of some important considerations and potential solutions:
Clear Flags Configuration: In the applyClearFlags method of the camera component, it’s important to ensure the clear flags are correctly applied. The current implementation controls how the background is rendered based on the set clear flags. If it’s set to ClearFlags.None, it won’t clear the buffer, leading to the visual artifacts you observed (see the documentation).
Rendering Order: Make sure that you are rendering the scene correctly with respect to your VR environment. Pay attention to the onAfterRender method in the NeedleXRSession class which manages the render order correctly when in VR (see the documentation).
Update to Latest Version: Since you’re using version 4.3.2-beta, consider testing against a more recent stable version of Needle Engine if available, as updates might have addressed bugs related to rendering and VR session management.
Context Management: Check how the rendering context is being handled during VR sessions. If you call clear() without resetting the render state, it can lead to issues. The context’s clear() function should be properly invoked to reset or manage scene states (see the documentation).
Testing Methodology: Since the scene works on Oculus 3, replicate the settings between both devices as closely as possible. Try to compare the WebXR session settings for both environments.
If your issue persists despite the above checks, it may help to enable debug logging to trace the rendering flow or review any specific configurations related to the Pico and how they apply to the Needle Engine.
Let me know if you need more help with specific parts of your code or further clarifications!
1 replies left - Get a PRO license for more AI replies.
thread_ksLsG9iQBnbAat25xHQGgdUH
Reply to this message to continue the conversation
Hello,
thanks for posting about this.
Could you try if these scenes work on your device?
okay, I tested both, the immersive vr session was working nicely (90fps), but the three.js examples one was quite broken, similar to my photo, but for example the ui was “covered” by something, so it was showing after moving to some side, and it would be qone the next moment. Also, there were black rays similar to my photo.
Maybe worth testing some other three examples then - and we should report it
Sorry, I have some classes I need to attend, so I will get back to the testing in the evening and report back to you.
I just finished testing all the working VR examples on the three,js using the pico neo 3 pro, and everything except this three.js examples was working nicely. I thought maybe it had to do with some effects or something to that effect, but the postprocessing shoud not even be working. Anyway, in the morning I will send you my own scene I tested it on, so you can also check if you have the pico neo 3 pro device. And on monday next week, I can try pico neo 4, if the problem goes across the pico devices, or the problem is only with the pico neo 3. If you find out something about it, please let me know.
Could you post the exact version number of the headset, and the version number of the browser you’re using? We can forward that to our contacts at Pico.
We’ve seen a similar issue on Apple Vision Pro and have a custom workaround for that in place.
The issue will only happen if a device does not correctly implement the WebXR spec (if it implements the spec correctly depth buffers are automatically cleared at the beginning of each frame, and don’t need to manually be cleared from the application).
Pico browser version - 3.3.46
Pico Neo 3 Pro
Software version: c000_rf01_bv1.0.1_sv5.9.8.0_202406140129_neo3_b2787_user
Model: A710
Thanks – just to confirm:
These links do NOT work on Pico Neo 3 Pro:
Would you also be able to make a video recording on that broken three.js link?
Yes, this three.js example is not working + the scene I sent through bug report. And I can make a video, but it would be on monday, because I don’t have the device on me now. Hope that is okay.
Hi, as promised, here are the screen recordings.
three.js example:
my scene:
Thanks – I’ll try to reproduce. So far no luck on an earlier browser version (3.0.3), updating OS + browser now. Also, I reached out to our Pico contacts to check if they know about this problem.
EDIT:
@vydymil I can not reproduce the issue with your submitted bug report, any extra steps I need to take?
hmmm, thats weird. I don’t think I did anything extra. If you give me a while, I can recharge different headset and let you know.
Sorry for the delay, I just tested on a different pico neo 3 pro device, and it still happens. I tested it with and without compression. I just run the local server, load into the browser, and enter VR. I don’t do anything special.
