David Duperron

Also check if your are moving in LOCAL or GLOBAL coordinates (by default the puzzle moves the object in local coordinates (or parent coordinates if your parented the moving object to another). If you want to move in global coordinates you need to tick the “world” option of the puzzles.
This, together with what @xeon describes above, is the key to getting what you expect when trying to move your objects with Verge3D.
Hope it will help!

Cheers

David

Something like this:

There is still an issue when hovering a cube while orbiting the camera with this solution that causes a crash.

• This reply was modified 4 months, 1 week ago by David Duperron.

Hi Felix!
I guess you could use the “setup preloader” in the init tab of the puzzles, and its “on finish” slot to change the visibility of your elements (buttons) either based on their IDs if they have some or their class name.
Do you have a screenshot of your puzzles in the init tab?
Cheers

David

Hi Kdv, thanks for the advice.
In fact I spent some more time yesyterday on this, and finally discovered that this had to do with a material assignment in earlier steps of my scene loading (steps where I imported some objects and assigning them an already existing material – and these objetcs were importing and displayed correctly!).
However as soon as I invoked the append scene puzzle after that, the imports failed… I had to rework the material assignment part, and make sure the objects had some properties defined with the following script (like the computeTangents(), or a correct UVMap name):

var mat = v3d.SceneUtils.getMaterialByName(appInstance, "NI_paint_vertex_color");
var object = PzLib.getObjectByName(addedPennantName);
object.geometry.attributes.uv.name="UVMap";
object.castShadow = false;
object.receiveShadow = false;
object.geometry.computeTangents();
object.material = mat;