GIProbe

Inherits: VisualInstance < CullInstance < Spatial < Node < Object Real-time global illumination (GI) probe.

Description

GIProbes are used to provide high-quality real-time indirect light to scenes. They precompute the effect of objects that emit light and the effect of static geometry to simulate the behavior of complex light in real-time. GIProbes need to be baked before using, however, once baked, dynamic objects will receive light from them. Further, lights can be fully dynamic or baked. GIProbes in a scene can be expensive, the quality of the probe can be turned down in exchange for better performance in the ProjectSettings using ProjectSettings.rendering/quality/voxel_cone_tracing/high_quality. Procedural generation: GIProbe can be baked in an exported project, which makes it suitable for procedurally generated or user-built levels as long as all the geometry is generated in advance. Performance: GIProbe is relatively demanding on the GPU and is not suited to low-end hardware such as integrated graphics (consider BakedLightmap instead). To provide a fallback for low-end hardware, consider adding an option to disable GIProbe in your project’s options menus. A GIProbe node can be disabled by hiding it. Note: Meshes should have sufficiently thick walls to avoid light leaks (avoid one-sided walls). For interior levels, enclose your level geometry in a sufficiently large box and bridge the loops to close the mesh. To further prevent light leaks, you can also strategically place temporary MeshInstance nodes with GeometryInstance.use_in_baked_light enabled. These temporary nodes can then be hidden after baking the GIProbe node. Note: Due to a renderer limitation, emissive ShaderMaterials cannot emit light when used in a GIProbe. Only emissive SpatialMaterials can emit light in a GIProbe.

Tutorials

• GI probes
• Third Person Shooter Demo

  Properties

  Methods

  Enumerations

  Subdiv:
• SUBDIV_64 = 0 —- Use 64 subdivisions. This is the lowest quality setting, but the fastest. Use it if you can, but especially use it on lower-end hardware.
• SUBDIV_128 = 1 —- Use 128 subdivisions. This is the default quality setting.
• SUBDIV_256 = 2 —- Use 256 subdivisions.
• SUBDIV_512 = 3 —- Use 512 subdivisions. This is the highest quality setting, but the slowest. On lower-end hardware, this could cause the GPU to stall.
• SUBDIV_MAX = 4 —- Represents the size of the Subdiv enum.

  Property Descriptions

• float bias GIProbe. This can be used to avoid self-shadowing, but may introduce light leaking at higher values. This and normal_bias should be played around with to minimize self-shadowing and light leaking. Note: bias should usually be above 1.0 as that is the size of the voxels.

• bool compress Deprecated. This property has been deprecated due to known bugs and no longer has any effect when enabled.

• GIProbeData data GIProbeData resource that holds the data for this GIProbe.

• int dynamic_range GIProbe will recognize. Brightness will be scaled within this range.

• float energy GIProbe brighter.

• Vector3 extents GIProbe. If you make the extents larger without increasing the subdivisions with subdiv, the size of each cell will increase and result in lower detailed lighting.

• bool interior true, ignores the sky contribution when calculating lighting.

• float normal_bias GIProbe based on the object’s normal direction. Can be used to reduce some self-shadowing artifacts.

• float propagation How much light propagates through the probe internally. A higher value allows light to spread further.

• Subdiv subdiv GIProbe operates on. A higher number results in finer detail and thus higher visual quality, while lower numbers result in better performance.

  Method Descriptions

• bake ( Node from_node=null, bool create_visual_debug=false ) GeometryInstances marked with GeometryInstance.use_in_baked_light and Lights marked with either Light.BAKE_INDIRECT or Light.BAKE_ALL. If create_visual_debug is true, after baking the light, this will generate a MultiMesh that has a cube representing each solid cell with each cube colored to the cell’s albedo color. This can be used to visualize the GIProbe‘s data and debug any issues that may be occurring. Note: bake works from the editor and in exported projects. This makes it suitable for procedurally generated or user-built levels. Baking a GIProbe generally takes from 5 to 20 seconds in most scenes. Reducing subdiv can speed up baking. Note: GeometryInstances and Lights must be fully ready before bake is called. If you are procedurally creating those and some meshes or lights are missing from your baked GIProbe, use call_deferred("bake") instead of calling bake directly.

• debug_bake ( ) bake with create_visual_debug enabled.