We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
I see no critical errors in the console you provided. I believe there is a logical issue in the puzzles scenario itself. There are some hints that might help in debugging it:
1. Use more print to console to find our the possible reason of this misbehavior.
2. Temporary disable blocks that are not relevant to this particular functionality. This will help you in narrowing it down.
You might try using the Chrome Developer Tools to find that element and get it by its class… etc manually, by executing the document.querySelector(" ... ") right in the browser console.
Regarding the upload fail, apparently there is one file that has invalid MIME type (extension). You might need to review your app folder to find it and add its MIME to the plugin settings.
Hi,
There are no specific puzzles required for making it work. The most probable cause of this misbehavior might be specifying a wrong value for the “query selector” puzzle, hence it does not return anything. You might use the print to console puzzle to verify that the proper element is returned by the query selector.
Strange thing, that I don’t see that message Please share the snippet of Puzzles logic that handles the “paisley” switching, perhaps there is something with that code.
Hi,
Unfortunately, it’s not possible to disable the propagation of scaling through the bone hierarchy in Verge3D. You might try to create additional “scalable” bones to address this problem.
Hi,
These textures are quite heavy, perhaps some timeout happens during the load. Try to disable Texture Compression for them temporary or reduce their size to see if it works.
Hi,
Sure, you can modify the source puzzles of this app a to make multiple objects work. Just use some variable as an “active object” and move that instead of directly referencing the object by the name.
Hi, this appears to be a correct behavior. The “inverted” checker inverts the 2D cursor coordinates, not the final vector returned by the puzzle, hence it has no meaning when “from mouse/touch” is disabled (basically in that mode the coords are [0, 0] – the center of the screen).
Hi sergeverge,
Indeed this depends on the target hardware. However, on quite recent devices (both desktop and mobile) the answer to most of your questions would be “hundreds”.
Please share the snippet of Puzzles logic that handles the “paisley” switching, perhaps there is something with that code.
