Project Rembrandt: Difference between revisions

m
→‎Memory consumption: http://flightgear.org/forums/viewtopic.php?f=47&t=14883&hilit=rembrandt+memory&start=45#p147195
m (→‎Memory consumption: http://flightgear.org/forums/viewtopic.php?f=47&t=14883&hilit=rembrandt+memory&start=45#p147195)
Line 61: Line 61:
=== Memory consumption ===
=== Memory consumption ===


For each camera defined in the camera group, the video memory usage is :
For each camera defined in the camera group, there is a separate shadow map, so the video memory usage is :
*G-buffer and Lighting buffer: 48 bytes per pixel. For an HD screen (1920x1080) memory requirement is 95 Mb
*G-buffer and Lighting buffer: 48 bytes per pixel. For an HD screen (1920x1080) memory requirement is 95 Mb
*Shadow map: 3 x shadow_map_size x shadow_map_size bytes (if size is 8192, whole map size is 192 Mb
*Shadow map: 3 x shadow_map_size x shadow_map_size bytes (if size is 8192, whole map size is 192 Mb
Not counting textures, display list or vertex buffers for models and terrain
Not counting textures, display list or vertex buffers for models and terrain
If you're asking 3x8192x8192x3 = 576 Mb (megabytes) of memory for the shadows alone.
3 HD screens require 237 Mb of memory for the buffers (shadow excluded).
If you are seeing error messages during startup or FlightGear doesn't start up properly, it's probably because you don't have enough video memory. Reduce the size of the shadow map in preferences.xml by locating
<syntaxhighlight lang="xml">
<map-size type="int">8192</map-size>
</syntaxhighlight>
And put 4096 or 2048 instead.
You can also use a startup parameter: --prop:


== Guidelines for shader writers ==
== Guidelines for shader writers ==