masj

Thank you for sharing your insights, xeon!

I messed up on my description in the first post and edited it, specifically:

I have several keyframed value nodes driving animation in a few different materials all assigned to faces on the same mesh object, and controlling the looping of each via code.

I think your point still stands though. In V3D, the multi-material mesh object is split into a separate 3D Objects (with the “isMaterialGeneratedMesh” property on), but the animation tracks are all bound to the source object, I think, so the same animation controls affect them all, unfortunately. Having separate objects is the obv way around this, but rly want to see if there are no other options first. Generating a new clip per track via code would be ideal.

Thanks. If that’s the case, that’s clearly one option, yes (noting that this will still require traversing the scene, as far as I can tell, so same difference ).

Thanks for bringing my attn to ‘Instanced Mesh’ – good to know.

@kdv, you are brilliant! Thank you once again for sharing your insights. Really appreciate your help.

Can I ask a follow up question re: the ‘factor’ arg?
I think I found a way manually to set ‘factor’ on a per-object basis via its bounding box & Math.cbrt to keep it at the same scale as inside the 3D model file itself, but was wondering if you knew of a cleaner/simpler way to do this via maths inside the function call, when an object’s bounding box will have grown/shrunk with the object’s scale (hope that make sense).

@xeon, for sure! I was envisioning something almost like fancy 3D UI annotation-like objects on the surface of model(s) in an app with lots of leeway for zooming, kind of like the feel of zooming in to a 2D map in an app, but w/ some proper 3D fanciness.

Yeah, that could be an option ✅
Thanks for your input, kdv – always appreciate it!

…yup, you are totally right. I completely missed that crucial step when updating this time around >.<
Learned a bit regardless, and thanks for calling that out.

Thanks for the offer. I might take you up on that.

Upon further testing, I found the errors would go away if I changed the shader type to something else (i.e. Diffuse BSDF, Sheen BSDF, etc.).
The error only seems to get thrown when it’s a Principled BSDF (even if created from scratch), and it happens when v3d.js is trying to do something with it (the gltf file itself loads fine in the browser on its own).

I guess I can use a different shader type until this gets addressed, assuming its not just me and others are able to recreate the issue as well (Blender 4.0.1, Any Mesh Objects with Principled BSDF Material applied, exported as a gltf file to v3d).

• This reply was modified 1 year ago by masj. Reason: including screenshot

Thanks Crunch!
Clever fix, but if I’m attempting it correctly, it still doesn’t make the annotation clickable to bring up the dialog content box as I need, unfortunately.

Thank you!