Dear jgbarah, thank you for your work on the canvas-updater extension.
I have an a-frame project where I have a live stream from ffmpeg going to a canvas texture with ffmpeg.
It works fine in regular view on both desktops and the quest 3 (and 1) headsets, but if I go into full immersive mode the canvas sticks on the frame it was on before switching modes
I'm writing to ask please if there's a possible update for canvas updater that might remedy this?
Thank you for your time in reading this and for your consideration of the matter.
(Edit 21/10/2023, since writing this post I've found a solution in that while the ffmpeg to jsmpeg streamed canvas textures don't animate in Immersive mode in the Meta browser, they do work fine in the open source Wolvic browser on the Quest. I'm not sure what the difference is between both headset browsers, but thought this information might be useful to note. Thanks again for your great a-frame work).
Dear jgbarah, thank you for your work on the canvas-updater extension.
I have an a-frame project where I have a live stream from ffmpeg going to a canvas texture with ffmpeg.
It works fine in regular view on both desktops and the quest 3 (and 1) headsets, but if I go into full immersive mode the canvas sticks on the frame it was on before switching modes
I'm writing to ask please if there's a possible update for canvas updater that might remedy this?
Thank you for your time in reading this and for your consideration of the matter.
(Edit 21/10/2023, since writing this post I've found a solution in that while the ffmpeg to jsmpeg streamed canvas textures don't animate in Immersive mode in the Meta browser, they do work fine in the open source Wolvic browser on the Quest. I'm not sure what the difference is between both headset browsers, but thought this information might be useful to note. Thanks again for your great a-frame work).