- This topic has 17 replies, 6 voices, and was last updated 2 years, 6 months ago by
.
-
Blender-specific features
We supported Blender 3.2 and 3.3 for this update. Specifically, Verge3D can now handle the output Alpha of the node Object Info introduced in Blender 3.2. E.g. you can clone an object, and set both color and alpha for each clone, thus making the cloned objects transparent.
Also you can now use two new nodes, Combine Color and Separate Color, to be shipped with upcoming Blender 3.3. Until this version is out, we use nodes called Combine RGB/HSV and Separate RGB/HSV for the same purpose.
We added the demo called 🐇 Transparency to Verge3D Asset Store to show off all types of transparency supported by the engine.
Also we added a new demo called Clone Object to show the workings of the clone object puzzle.
Another demo called Drink Shop serves as example of a 💸 Woocommerce application. You can try it live in the sandbox store.
We added an animation timeline to the Industrial Robot demo.
Finally, the small demo called 🖼️ Canvas Texture creates pictures on the fly using the HTML Canvas API.
3ds Max-specific features
Color space is now correctly assigned to ORM textures generated for gltf-compatible materials. Thus lighting is no longer crippled for such models.
We fixed export crash when empty names are used for morph targets.
We added the demo called 🐇 Transparency to Verge3D Asset Store to show off all types of transparency supported by the engine.
We also added a new demo called 🫖 Gltf Compat featuring an advanced PBR material compatible with glTF 2.0 standard.
We added an animation timeline to the Industrial Robot demo.
Finally, the small demo called 🖼️ Canvas Texture creates pictures on the fly using the HTML Canvas API.
Maya-specific features
We fixed potential problems with installation of Verge3D for Maya on Windows.
We added the demo called 🐇 Transparency to Verge3D Asset Store to show off all types of transparency supported by the engine.
Finally, the small demo called 🖼️ Canvas Texture creates pictures on the fly using the HTML Canvas API.
🧩 Puzzles
The export to usdz puzzle now uses the USDZExporter class from the latest Three.js library. This brought better support for transparent materials, among other features.
We added a new primitive, plane with texture, to the puzzle create object.
We synced with upstream the hardware database used by the puzzle check performance.
We upgraded the Puzzles editor by syncing with the latest version of Google Blockly framework. It now works much faster with big scenarios, and is more stable.
Also, all outdated puzzles will now show in your scenarios as 🟥 red placeholders.
This will happen with old versions of such puzzles as play animation, replace scene, texture from text, external call, load sound, physics body params, physics apply vector, and ssao. Be sure to get rid of such puzzles (that have a ⚠️ warning sign on them) before upgrading to Verge3D 4.0.
The advanced play animation puzzle obtained default fields: from, to, and speed. This way you no longer need to add Number puzzles every time you want to play an animation range.
The puzzle check AR mode now has 3 slots to conveniently use Apple’s USDZ viewer without the need of extra logic in your Puzzles. See the demo Augmented Reality for usage example.
Texture compression
Texture compression can now be used with the puzzle replace texture.
The print performance info puzzle (as well as P-P-P hot keys) now outputs info about texture compression. Namely, it prints what exactly compression format is used internally by Verge3D on the target hardware (intended for advanced users).
The texture compressor launches and works faster on macOS thanks to ARM-based and Intel-based Macs being handled individually now.
We enabled texture compression for all stock demos. Also, we replaced all outdated puzzles by modern variants. Finally, we optimized PNG textures by removing ICC profiles from image files. This is quite relevant because the ICC profile enlarges a file, and more importantly, prevents using compression.
Other improvements
A descriptive message is now shown in the App Manager if the local server is down, instead of ‘This site can’t be reached / localhost refused to connect’.
We removed the workaround we made for buggy Safari browser that had a severe rendering issue, which Apple devs apparently fixed in Safari 15.5. The fix is still in place for v. 15.4.
We implemented progressive loading of Asset Store entries which helps if Internet is slow. We also provided better titles and descriptions for the demos.
You can now navigate to the URL
localhost:8668/resetto clean up the settings of the App Manager. Intended for advanced users, this is a handy way to begin from scratch.glTF-compatible materials now work with IBL Environment Mode, if the option Light Probe + Cubemap (medium) is selected in the dropdown.
Bug fixes
🐞 We fixed the issue with incorrect lighting on originally empty scenes, that is when models are added in run time later.
🐞 We fixed a bug in Verge3D WordPress plugin related to incorrectly determining of product IDs.
Issues introduced in previous preview builds
🐞 We fixed the engine crash occurred when loading third-party gltf files.
🐞 We fixed the bug with rendering Alpha Coverage (Alpha Hashed) materials.
🐞 We fixed the bug with contrast not working in the brightness-contrast puzzle. Thanks for reporting this on the forums.
🐞 We fixed the engine crash when Blender constraint Floor is used.
🐞 Finally, GLB files are now exported again.
Documentation
📝 We made links to the Verge3D Asset Store to serve as examples. We also adjusted styles and improved overall readability of the User Manual.
📝 We created or significantly reworked the following sections: Texture Compression, AR/VR Development, Developer Kit, and Personalizing Verge3D Applications. We also filled various gaps elsewhere.
📝 We synchronized the Developer Reference with the latest Three.js API docs.
📝 We wrote a migration guide to help you with upgrading to Verge3D 4.0.
I tested it with my Gargoyles project using Blender 3.2.
– Unfortunately, objects are invisible if the Bump shader node is used.
– There is also an error for AO rendering.
(see screenshots with error logs.)
– There are no errors when a Normal Map shader node is used. But using a Normal Map with a model that has combined Shape Key and Armature animation gives distorted results. This has been a problem in former versions of Verge3D as well. (I have posted about this issue before.)I’ll try to find time to do more testing.
Good luck with the finishing touches. 4.0 will be awesome!
Simone
- You must be logged in to reply to this topic.