Ivan Lyubovnikov

Hi, which Verge3D version are you using? I recall there was a similar bug a while ago, but we fixed it in 3.9.0. Also, can you provide an example or a link to reproduce this issue?

Hi,

It doesn’t work with the existing puzzle setup because this is what’s actually happening:
– objects get hidden
– screenshot is scheduled to be taken after 2 sec delay (this puzzle doesn’t pause the logic, so we just continue to the next puzzle)
– objects get shown
– 2 seconds pass…
– screenshot is taken

To make it work you should move the second “for each” puzzle block into the “after 2 second(s)” puzzle right after “download file”.

karonte wrote:

But is there a “on capture end” method? because the delay is relative to a specific hardware…

There’s nothing like that available yet, but the ability to specify exactly the next frame instead of an arbitrary amount of time could be useful in this case. We added such feature into our TODO list.

Hi,

Sorry for the late answer, pointerlock for first-person cameras is now supported in the latest verge3d 3.9 release: https://www.soft8soft.com/verge3d-3-9-for-blender-released/

Now it can be enabled in the camera settings in Blender, Max or Maya. Also, it can be controlled via API:

app.controls.enablePointerLock = true;

Hi,

The “look at” parameter specifies a 3d point where the camera should look at after the movement is done. If you want to keep the camera’s orientation the same then you can calculate the “look at” parameter by adding together the camera’s current direction/orientation vector and the new position to move to.

I attached a test demo, where you can look around via the left mouse button and move by clicking the plane with the right mouse button.
Hope this helps!

Eugene Zos wrote:

Not pushing by any means, basically, the project is sitting waiting for the fix before we deliver. Do you think it will be out soon?

The fix should be available right now with the new pre-release version: https://www.soft8soft.com/topic/verge3d-3-9-pre1-available/

Hi Simone,

We tried to reproduce this bug but to no avail. Can you share an example?

Hi, thanks for the report! This bug will be fixed in the next Verge3D update!