David Duperron

@kdv77kdv
I found something quite odd but interesting, that is apparently not in line with what you mentionned here:

They don’t work at all. You can read them, you can change them, but that’s all.

The “Userdata/CustomProps” dictionnary which is part of the Object3D javascript object IS changed when I manipulate my Object with puzzles, even if I do not explicitely tell my application to write the data in the object’s dictionnary.
In other words, in my Application, I create from scratch a custom dictionnary (addedObjectsDictionnary) where I import a blender created CustomProps dictionnary, name it with a new unique ID. This dictionnary is updated when I make modifications on my object (color, position, rotation, etc…), but for some reason, the “Userdata/CustomProps” dictionnary inside the 3D object is also changed!
And the reason why my objects where linked previously (I guess!) was that I did not make the “import customprops” step and simply duplicated my puzzle created dictionnary and asigned a new UID. But inside the 3D object they were still linked.
Here are two screenshots of the console log for one of my objects before and after a modification (obtained with getObjectByName, no other manipulation). And as I said, I never explicitely tell my application to write something in the Object3D object…
Before:

After modification:

Hoping this is clear…?

I found something: it seems that this has to do with custom properties recovered from the original appended gltf file.
For “properly” appended objects, where the custom properties (that I store in a dictionnary) are pulled from the gltf file, everything works fine.
But for “cloned” objects, where I do not write the new objects properties from the original custom properties, but rather copy them from the cloned object, these properties seem to be linked!
Do you know how exactly these custom properties work and how are they linked/updated (if so?) from within the puzzles??

Ok… I will need to investigate deeper. Appending the same object several times works perfectly fine, but cloning causes all sorts of troubles… strange…

Hi kdv,
I’m already using your “clone object” puzzle, and yes the objects in question originally come from an appended scene, but I the objects renaming and parenting to the new scene was already done, or at least i thought so…
How can I check what exactly I cloned and if the meshes and/or materials are linked in any way?
Thanks for your help again!

David

Good hints, as usual… ;)
I quickly identified that this “function within a function” – local function – was not directly accessible, and as suggested copied it in a custom procedure in my puzzles.
Just had to identify that I needed to properly set the “mesh” using the getObjectByName function and that’s it!
Thanks again!

• This reply was modified 1 year ago by David Duperron.
• This reply was modified 1 year ago by David Duperron.

@kdv77kdv I think I might already have the exact function for that, right?
function setObjectScale(mesh, factor) {
right?
Can I call this function from any other location in my puzzles using the javascript puzzle?

• This reply was modified 1 year ago by David Duperron.

Thanks for the info!
These parameters have an effect indeed, but that’s not really what I was looking for.
My issue is that it looks like there is a constant number of zoom steps, whatever the distance between MinZoom and MaxZoom is, meaning that for small distance, controlling the zoom level is easier than for big distances where one mouse wheel step equals to a much greater distance. My question was: is there a way to increase the number of zoom steps depending on the MinZoom/MaxZoom distance??
Thanks for the help!

David

Changing the camera Object controls using javascript does not seem to have any effect:

const camera = app.scene.getObjectByName('Camera')

camera.controls.orbitMaxDistance = 1500;
camera.far = 3000;
console.log(camera)

using the above code I change the max distance from 500 (original Blender setting) to 1500, and the far distance from 1500 to 3000 but it does not change anything in the 3D viewport…