Yuri Kovelenov

The issue has been fixed in the engine, and Virtual Reality demo updated in the Asset Store. Please download the demo again. Be sure to clear the cache in the web browser of the Quest headset.

Hi jerenz,

Right, Verge3D generates that many individual procedure textures from your scene. Before v.4.8 those were just not visible in the output of the performance profiler.

This is not really good but not critical for performance or memory consumption. We’ll think about possible solutions to cleanup/cache such textures inside the engine.

• This reply was modified 4 days, 19 hours ago by Yuri Kovelenov.

Hi swatchyb,

Is there any particular reason to not use the Verge3D Windows installer? It should do everything automatically. In your case I’d recommend cleaning everything up (delete the local repository) and run the installer.

Hi Tom,

unfortunately it is not currently possible with the Puzzles. It requires custom JS coding.

Hi qiangge,

Verge3D broke with Three.js code base long time ago so there can be many incompatibilities with recent Three.js code. We are still cherry-picking Three.js features from time to time, if we consider them really important for the Verge3D pipeline which is based around the artist. Not sure about any JS API though.

Hi vklein,

The P-P-P keys for printing the performance profile in the browser console still work. The Service Tools is a new feature which combine the performance profile with other useful tools.

Anyway, I agree that the tilde key might not be the best choice. We’ll think what we can do here.

Hi habnet,

Your scene looks quite heavy. For textures a general advice would be using smaller JPGs. Image size must be power-of-two (256, 512 etc). Try to reduce the number of textures – you can use plane-color materials, or procedural textures created in the 3D software, or use vertex colors to paint your meshes.