- 2020-07-23 at 12:47 pm #30517
Here is the 3rd preview build of the upcoming Verge3D 3.3. In this update we included important optimizations that led to significant reduction of loading time, several new puzzles, Noise map and OSL shaders support for the 3ds Max version and some other minor improvements.2020-07-23 at 12:47 pm #30518
We drastically improved loading performance thanks to various optimizations. Namely, we implemented parallel shader compilation among other things. Also the loading stages were restructured to speed up the overall loading process.
The results can be seen on the chart below (measured on Intel Core i7-4790K / NVIDIA GTX 970 / Win 10).
The category Misc in the Puzzles editor was renamed as Advanced.
New puzzles wait promise and promise value were added to the Advanced category.
New Material puzzles were implemented: get color and get value that now exist alongside the previously available set color and set value puzzles.
The variant of Verge3D run-time v3d.module.js is now provided with software installations (previously it was only contained in the Enterprise builds). This fixes issues with code examples most of which use this run-time.
The Noise map is now supported by Verge3D. Also we initiated supporting Open Shading Language (OSL) maps.
We fixed another export crash with incorrectly assigned UV coordinates.
2020-07-23 at 12:48 pm #305192020-07-23 at 2:26 pm #30525matthijsbinmatLicensee
- This reply was modified 3 months, 1 week ago by Yuri Kovelenov.
These load times are way better!2020-07-23 at 2:29 pm #305282020-07-23 at 2:30 pm #30529core3dLicensee
This is great! Thank you2020-07-23 at 3:24 pm #30541webLicensee
Great improvements. Thank you very much for all your hard work in making verge better and better.
I tested the update on a bigger app. Sadly the scene loading time went from 3180ms to 6180ms. I just updated the v3d.js. Do I need to update gltf and other stuff also to make it work?2020-07-23 at 3:57 pm #30542kubuzLicensee
nice !!2020-07-23 at 4:35 pm #30549zjbcoolLicensee
——https://zjbcool.com/2020-07-24 at 8:20 am #305872020-07-24 at 8:21 am #30589GlifTekLicensee
Holy goodness, Batman!
This is like early Christmas!
The promises!! (The precciousss!!)
The CSS HEX RGB! color values!
The loooad times!
THE MODULE FOR CODE EXAMPLES!
…it’s all coming together now….
Very psyched for this update guys!
…but still gotta test it now…
Kudos for always listening to your user-base!
Thanks!2020-07-24 at 8:27 am #30590Ivan LyubovnikovDeveloper
I tested the update on a bigger app. Sadly the scene loading time went from 3180ms to 6180ms. I just updated the v3d.js. Do I need to update gltf and other stuff also to make it work?
No, you only need to update v3d.js. Also, loading time depends on whether a browser can utilize shader cache or not. If you change materials in your scene or the engine was changed somehow in a way that affects shader code then a browser needs to compile shaders again during the first load and it’s generally slower. But on subsequent loads it should be faster due to shader caching. Nevertheless the optimization that we made in this update should cover both cases.
If you can share a link to your app we can check if something goes wrong during loading.
Co-founder and lead developer at Soft8Soft.2020-07-24 at 12:53 pm #30605illussimoLicensee
Works great, super-fast loading in Chrome and the latest version of Edge. (Edge is now based on Chromium.)
Unfortunately, the KHR parallel shader compile extension is not yet supported in Firefox.
But I suppose Firefox will follow soon.2020-07-25 at 5:08 am #30620GlifTekLicensee
Works great, super-fast loading in Chrome and the latest version of Edge. (Edge is now based on Chromium.) Unfortunately, the KHR parallel shader compile extension is not yet supported in Firefox. But I suppose Firefox will follow soon.
AH! is this issue caused by the canvas puzzle?
Edit: hmm but the canvas works though…hmmm
2020-07-27 at 8:44 am #30664NaxosCGLicensee
- This reply was modified 3 months ago by GlifTek.
Hello, is that safe to install the 3.3 pre-release while i’m in production ? I mean, is it stable enough, not too “beta” ?
"1+1=3... for large values of 1"
- You must be logged in to reply to this topic.