Create instance on a mesh with a video texture works fine, if there is only 1 unique sourceMesh in the scene. As soon as I add a second sourceMesh (with a different video texture), and createInstance on that, it bugs out. For a visual example of what I am actually seeing (and or in case for some reason people still can’t reproduce it):
//dont know why the video won’t play but go to url directly I guess Dropbox - IMG_0199.mp4
The red attack icons are an instanced mesh, they play fine, once the blue blocker icons are created (also instances of a source mesh), they bug out.
It’s def specific to createInstance, multiple video textures not using instance behavior or using clone, has been working fine for me. - And it only happens if I have at least 2 different shaderMaterials attempting to use different video textures on different source meshes. If I have just 1 sourceMesh / video texture using createInstance, works fine.
@sebavan were you ever able to test it out on OSX to see if you could recreate the bug?
I dug around in spector, and the only issue I could see, that didn’t happen if I used a normal custom shader with an image instead of a video, is, in the following screenshot, (in which I am rendering the blocker icons, and the 4 blue meshes bugging out below it are the attack icons, which occurs in the second screenshot) - There is a bindTexture null call, in the first frame. Not sure if that is related to the issue or not.
The trace in spector looks as expected despite having a potential rebind optim. I am more and more confident we are unlucky with abdriver issue… could you stitch your video together like an atlas to only have one runing at a time ?
Yea, was just about to reply that it is working on Safari so don’t think it’s driver issue. Sorry forgot to mention that part last night. – Awesome, I will open an issue on chromium tonight, thanks for looking into it!
