Forum Replies Created
-
@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…?
Yes I know… I started again from scratch, using the same method I use for appending objects in the first place, to create a clone based on the same gltf file, and now it’s working! I guess this had to do with the way I was defining the custom parameters for my “cloned” objects…
for the record, the two puzzles:
the one which is working fine:
and the one which is not:
I don’t know if I can build something “simple” to reproduce this behaviour… there are a lot of procedures and puzzles involved as well as UI.
However I’ve tried to inspect the various objects to get a clue.
Attached are the console logs of three “Object3D”
The cube1 is the first one to be appended to the scene, from an original file called GENERIC_cube.gltf.
The cube2 is a second object appended from the exact same gltf, with the same parameters.
The cube3 is a duplicated object that I create by copying the parameters of the cube1 (in an internal dictionnary: gltf_file path, dimensions, rotations, etc… basically all the parameters that are originally imported with the object as customprops), using the same processus as for a new object appending (like for cube2): I get the gltf file path, append the scene, rename the objects, etc…
And for a completely unknown reason the cube2 and cube3 are linke din some way, and when I try to change some parameters on one it changes on both.
Cube1 remains untouched.
I don’t know if these json files can give us a direction to look??
Cube1
Cube2
Cube3
DavidOk… I will need to investigate deeper. Appending the same object several times works perfectly fine, but cloning causes all sorts of troubles… strange…
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 thegetObjectByNamefunction and that’s it!
Thanks again!@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?
