Common gotchas with Verge3D
This page describes some typical problems you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both).
Too much copy-paste in Puzzles
Say you need to perform 10 different actions for 5 objects on your scene. The most straightforward way to handle this would be just using copy-paste:
However, such a scenario is really hard to maintain. It also slows down the Puzzles editor. Instead, you might employ procedures that will make your scenario way more compact:
Also, by using lists you can simplify the logic even further:
It's definitely worth spending a little time to learn these two techniques, since it may save you many hours later.
Enabling HDR Rendering when not required
Activating this feature causes excessive GPU memory consumption and rendering slowdowns. Use it in two cases only:
- You have the Bloom post-processing effect.
- You use procedural gradients in your node-based material.
Beware, setting this option is not required to get cool lighting with HDR maps!
Using non-power-of-two (NPOT) textures
Avoid textures which have resolutions like 1000x1000, 1200x600, 1920x1080. See NPOT Textures article for more info.
Huge shadow maps
Setting shadow size to high values basically kills performance on most devices:
Try to minimize shadow maps as much as possible. Instead of increasing shadow size, reduce pixelation of your shadows by using more advanced shadow filtering algorithms, like PCF (Poisson Disk) or ESM.
Swapping object on click
Say you need to replace some object by another one given they both occupy the same place, e.g swap CubeGold by CubeSilver and vice versa. Most evident way would be using two when clicked puzzles:
This won't work however since both events happen right after another. So the first event handler will switch to CubeSilver, then the second will switch back to CubeGold.
A possible workaround could be delaying the actions by one render frame:
Forgetting to enable asset compression in the scene file
Say you enable asset compression in Puzzles but forgot to enable it in the modelling suite:
There will be one of the two consequences of it.
- Case (bad). You won't be able to load your scene, since your app expects the compressed asset (e.g my_awesome_app.gltf.xz) which is unavailable.
- Case (even worse). You have file called my_awesome_app.gltf.xz in your app which you exported using