Ivan Lyubovnikov

ducksaber wrote:

Yeah embedding videos doesn’t work for me either following all instructions, really frustrating

Hi, can you share your app to check what’s going on there? One common mistake is trying to play an unmuted video without prior user interaction, e.g. clicking on the page.

Hi, can you check if there’s any errors in the browser console?

Hi aminemod,

Currently the docs for using React/Vue with the puzzles editor don’t reflect changes made in verge3d 4.0 regarding how the editor works with its applications. We’ll fix the instruction in the docs in the next verge3d update. But for now, if you need React/Vue it’s better to stay on Verge3D 3.9.1. Sorry for the inconvenience.

It’s not allowed to attach xml and js files directly to the post. Try to zip the files and attach the archive.

kdv wrote:

Verge3D team, why do you create var VARS with every exec script? Can’t you do it only twice like var PROC?

Hi, that’s a good question! VARS is a bit more complex than PROC – if execScript is used inside a procedure puzzle then it needs access to parameter arguments as well as to global variables.

For example in the following puzzle setup the first execScript puzzle should reference global “test” while the second one the local parameter “test”:

– this is achieved by declaring VARS two times so each of those declarations has correct variables in its closure.

On the other hand VARS doesn’t have to be declared each time execScript is used, it only needs to appear once for the global scope and for every procedure that uses execScript inside.

Initially, there was a measure to detect if we need to declare VARS at each particular place in code but it was commented out due to some issues. We might need to look further into that, because clearly the current approach can be optimized.

kdv wrote:

This code will do exactly the same and there’s no need in var VARS and var PROC…

In general, variables and procedures in the puzzles editor can have names that are not valid JS identifiers, like the default “do something” procedure name. They are renamed in the generated code to make sure that it works. Also, some of them can be renamed just to avoid collisions, e.g. “do_something”, “do_something2”, etc…

So, unless you check the visual_logic.js file you can’t always be sure that the name of your variable/procedure stays the same when it comes to executing the contents of execScript. VARS and PROC are used to avoid something like that by providing mapping between the original names and the resulting identifiers.

Can you check the version of the addon for Blender? It should say 4.0.1

GLiFTeK wrote:

and i still get the same issue.
also i’ve tried without the none material and still same

There’s also an issue with field names: you named them “FIELDNAME1”, “FIELDNAME2”, “NUM1”, “NUM2”, “TEXT1”, etc… but they all should be named as “FIELDNAME”, “NUM” and “TEXT” (no trailing numbers needed) – those are the names the “objectList”, “math_number” and “text” puzzles use.

@gliftek

You have a typo in the first objectList field. There’s a " symbol missing after "FIELDNAME1 – this breaks the rest of the xml markup.