Home › Forums › WebGL & WebXR Troubleshooting › v3d.js:1 v3d.PropertyBinding: Animated node not found error
Tagged: Error, material animation, parenting, PropertyBinding, webgl
- This topic has 13 replies, 5 voices, and was last updated 4 years, 9 months ago by Ivan Lyubovnikov.
-
AuthorPosts
-
2020-01-10 at 5:00 pm #22739samuraijkmCustomer
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 #22743Yuri KovelenovStaff2020-01-13 at 5:52 pm #22794samuraijkmCustomerHi Yuri,
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.
-Jason
2020-01-14 at 8:54 am #22810Yuri KovelenovStaff2020-01-14 at 10:03 pm #22821Branden CokerCustomerI 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.
Attachments:
You must be logged in to view attached files.2020-01-15 at 12:36 pm #22843Yuri KovelenovStaff2020-01-15 at 8:40 pm #22861illussimoCustomerI 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 #22875Yuri KovelenovStaff2020-01-22 at 8:30 am #23003Ivan LyubovnikovStaffHi,
We managed to fix this error. Thanks everyone for the bug reports!
Co-founder and lead developer at Soft8Soft.
2020-01-22 at 2:24 pm #23009Branden CokerCustomerVery cool. Thank you devs!
2020-02-07 at 2:27 pm #23412Branden CokerCustomerTrying out v3.0 pre1 today. I’ve updated my applications, but I’m still seeing the error.
Verge3D 3.0.0 pre1 (WebGL 2.0) v3d.js:1 v3d.PropertyBinding: Animated node not found _h {path: "Cylinder_1.material.nodeValue["Value"]", parsedPath: {…}, node: _i, rootNode: Bn, getValue: ƒ, …} bind @ v3d.js:1 getValue @ v3d.js:1 saveOriginalState @ v3d.js:1 _activateAction @ v3d.js:1 play @ v3d.js:1 processAnimation @ visual_logic.js:210 operateAnimation @ visual_logic.js:254 (anonymous) @ visual_logic.js:466 (anonymous) @ visual_logic.js:444 (anonymous) @ visual_logic.js:442 pickListener @ visual_logic.js:386
2020-02-07 at 4:06 pm #23417Ivan LyubovnikovStaffHi Branden,
Just to be sure, did you reexport the blend files as well? Sorry, I forgot to mention that. The fix actually relies on some animation data that was previously missing in the exported files.
Co-founder and lead developer at Soft8Soft.
2020-02-07 at 4:11 pm #23418Branden CokerCustomerThank you Ivan! That was the missing piece. Re-exported my gLTF and all is well now.
2020-02-07 at 4:21 pm #23419Ivan LyubovnikovStaffThank you Ivan! That was the missing piece. Re-exported my gLTF and all is well now.
Nice!
Co-founder and lead developer at Soft8Soft.
-
AuthorPosts
- You must be logged in to reply to this topic.