Verge3D 4.7 for Blender is out!

Significant, powerful updates. Love to see it, thank you!!

QQ on the pzlib API (https://www.soft8soft.com/docs/pzlib_api/):

To access, do the puzzles have to exist for the project (I think some functions propagate in the visual logic file when they do), or can we just use the JS Plug object’s pzlib method without actually creating the puzzles? Sorry if it’s mentioned somewhere and I missed it.

In either case, will be upgrading soon, and excited to use this new functionality! Thanks again.

I keep trying to update but still get the 4.70 update available in my App Manager.

Hi all,

masj wrote:

To access, do the puzzles have to exist for the project (I think some functions propagate in the visual logic file when they do), or can we just use the JS Plug object’s pzlib method without actually creating the puzzles?

These APIs are accessible only from plugins. Yep, the good thing is that the necessary code (with all its dependencies) will be inserted to visual_logic.js automatically, once puzzles are added to the workspace.

c4cc wrote:

Speaking of Blender 4.2, why is it when I play animations in it created from previous Blender versions, the animations/meshes look grainy and a little blur, especially around the edges? Any way to remove this blur/graininess/noise?

Unfortunately, this is how the new Blender 4.2 viewport looks like. You might try to increase shadow steps in Blender settings and/or viewport steps.

Aubrey wrote:

I keep trying to update but still get the 4.70 update available in my App Manager.

Appears that the older version is still running. What was the previous version you’re trying to upgrade from? Also, please provide info on what Blender version and what kind of OS you’re using.

bigmike814 wrote:

4.7 already? It looks like I have some catching up to do.

Yep, time flies!

Alexander Kovelenov wrote:

Unfortunately, this is how the new Blender 4.2 viewport looks like. You might try to increase shadow steps in Blender settings and/or viewport steps.

I went to viewport, under performance in scene, and changed pixel to x1. Seemed to solve the problem