Difference between revisions of "Common gotchas with Verge3D"
From Verge3D Wiki
Jump to navigationJump to searchm (Alexander moved page Common Gotchas with Verge3D to Common gotchas with Verge3D without leaving a redirect) |
|||
| Line 1: | Line 1: | ||
This page includes common gotchas you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both). | This page includes common gotchas you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both). | ||
== | == Enabling HDR Rendering when it's not required == | ||
[[File:Hdr_rendering_setting.jpg|490px]] | [[File:Hdr_rendering_setting.jpg|490px]] | ||
| Line 11: | Line 11: | ||
Beware, setting this option is not required to get cool lighting with HDR maps! | Beware, setting this option is not required to get cool lighting with HDR maps! | ||
== Using non-power-of-two (NPOT) textures == | |||
See [[NPOT Textures|here]] to find out why you should avoid them in your apps. | |||
Revision as of 14:10, 13 November 2021
This page includes common gotchas you might experience when creating 3D web content. These issues might cause problems with rendering or performance (or both).
Enabling HDR Rendering when it's 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
See here to find out why you should avoid them in your apps.
