- 2020-01-10 at 5:00 pm #22739
I keep getting these errors in my browser console and I’m not sure what’s the culprit. Anybody have an idea on how to fix this ?2020-01-11 at 9:19 am #227432020-01-13 at 5:52 pm #22794
After a lot of digging, I found the error to be happening because I had two separate meshes that shared a material which had an animated node value. Once I linked the objects to share object data in blender it went away.
-Jason2020-01-14 at 8:54 am #228102020-01-14 at 10:03 pm #22821
I recreated the issue here:
This is a just an object with a texture that animates from solid to transparent with a keyed Value node.
If you load that app and click the dot, you’ll trigger the error. Seems to be caused when a single object has more than one material assigned and one or more of those materials are animated. Although we did fix it in our production scene, I can’t recreate that fix. I’m also attaching the .blend for this test.2020-01-15 at 12:36 pm #228432020-01-15 at 8:40 pm #22861
I had the same errors in Dreamy Journey. The material animation was only on 3 objects (the body and the 2 doors of the vehicle). But the errors are thrown for all the other objects that are parented to the object, and don’t share or have any animation in their materials.
My application runs fine, so the errors don’t affect the functioning of the application. I think it has something to do with material animation being part of the object animation. Everything is interconnected. It would be nice if material animation could be separated from object animation, but it seems that it is unlikely that that can be done.
I have attached the error log. Hope this helps.2020-01-16 at 6:54 am #22875
You must be logged in to reply to this topic.