Mariusz

Thanks kdv for your reply. Unfortunately, I cannot share the project since it’s covered by NDA with a client and is still in progress. I tried to recreate the scene in a separate application that I could share with you but unfortunately, I had no luck in receiving the same error.

But after hours of testing different enable/disable puzzles in the whole application (it’s really quite big and complex) I eventually came up with a walkaround that seems to work. I figured out that the problem was caused by using a “tween camera” in such a complex puzzle structure – it works fine when I try to recreate it in a blank application but messes up when used in my original complex app.

Anyway, I replaced the “tween camera” puzzles (which come up in a sequence to get the animations to flow one after another, so there are a few of them), with “set position” and “camera look at” puzzles to move the camera to the proper position manually. And this way, it all works.

I suppose this might be some internal puzzle bug maybe? I assume this from the console report. I attach the v3d.js file as well, maybe this will give you some clue on what’s going on here.

Thanks Xeon, that might work! As soon as I understand, I must then create two versions for each annotation – one for desktop and one for mobile. So I must double the number of empties and double all the puzzle logic that I created for these annotations (it’s pretty advanced to meet the client’s requirements and different application features). Is there an alternative to this to make it easier: like changing the empty’s position inside Blender depending on the visibility breakpoints?

Thank you Alexander for a quick reply. Do you mean exactly our project case? Or the plugin in general?

What if, in the future, we would like to create a new configurator for the same client? The new configurator should work independently from the old one – but the old one should still function anyway. And let’s say that we create the new configurator in the newest Verge software that probably requires the newest plugin as well. What should we do in such a situation?