the monolith game cheats developer tools

#The monolith game cheats developer tools update#

Using larger scales results in less sample memory usage and reduces Indirect Lighting Cache update times, but less accurate transitions between lighting areas. Volume lighting samples are computed by Lightmass and are used for GI on movable components. Scales the distances at which volume lighting samples are placed. 0 = no smoothing, 1 = strong smooth (little directionality in lighting). Smoothing is only applied when the ringing artifact is present. Whenever highly directional lighting is stored in a Spherical Harmonic, a ringing artifact occurs which manifests as unexpected black areas on the opposite side.

Volumetric Lightmap Spherical Harmonic SmoothingĬontrols how much smoothing should be done to Volumetric Lightmap samples during Spherical Harmonic de-ringing. Trimming memory too heavily will result in inconsistent resolution and it would be better to increase Volumetric Lightmap Detail Cell Size instead. High-density bricks will be discarded until this limit is met with bricks furthest from geometry discarded first. The maximum amount of memory to spend on Volumetric Lightmap Brick data. Volumetric Lightmap Maximum Brick Memory Mb This setting has a large impact on build times and memory and should be used with caution. Size of a Volumetric Lightmap voxel at the highest density (used around geometry), in world space units. Volumetric Fog cannot be affected by precomputed lighting with this method. This method requires CPU interpolation, so the Indirect Lighting Cache is used to interpolate results for each dynamic object, adding Rendering Thread overhead. Positions outside of the Importance Volume will have no indirect lighting. Volume lighting samples are placed on top of static surfaces at medium-density and everywhere else in the Lightmass Importance Volume at low-density. On mobile, interpolation is done on the CPU at the center of each object's bounds. Positions outside of the Importance Volume reuse the border texels of the Volumetric Lightmap (clamp addressing).

The Volumetric Lightmap is interpolated efficiently on the GPU per-pixel allowing accurate indirect lighting for dynamic objects and volumetric fog. Higher-density grids are used near geometry. Lighting samples are computed in an advanced grid which covers the entire Lightmass Importance Volume. Technique used for providing precomputed lighting at all positions inside the Lightmass Importance Volume. This data structure enables interpolation of indirect lighting to any point in space on the GPU. Near objects, any static geometry that is within one of the bricks will use more cells where indirect lighting changes the most. When lightmass is run, the cells are placed over the whole Lightmass Importance Volume and then it uses more cells around static geometry in the scene to capture better indirect lighting results.Įach of these points (or spheres) is a Volumetric Lightmap lighting sample, which uses a Third Order Spherical Harmonic to store the incoming lighting in all directions. When a Lightmass Importance Volume is placed, the Volumetric Lightmap builds bricks that are made up of 4x4x4 cells (lighting samples). If no built lighting is available (meaning the object is new or has moved too much), lighting is interpolated to each pixel from the Volumetric Lightmap for Static objects until lighting is rebuilt. When it comes time to render a dynamic object, the Volumetric Lightmap is interpolated to each pixel being shaded, providing precomputed indirect lighting. Lightmass places lighting samples throughout the level and computes indirect lighting for them during the lighting build. How It Worksįrom a high-level, the Volumetric Lightmaps system works in the following manner: Sparse Volume Lighting Samples determined leaking amounts and lighting accuracy.

The monolith game cheats developer tools