Navigation

Ventuz Introduction

  • Introduction
  • Getting Started
  • Ventuz Editions
  • Ventuz Products
  • Realtime Rendering
  • Frequently Asked Questions
  • Common Mistakes
  • Deploying a Ventuz Presentation
  • Scene Performance and Tweaks

Quick Guides

  • Quick Guide Index
  • Business Logic
  • 3D Art
  • 2D Art
  • Programming
  • System Engineer

General

  • Index
  • What's New
  • Ventuz System Requirements
  • Communication Protocol Overview
  • Configuration Editor
  • Audio / Video Configuration
  • Machine Configuration
  • Web Configuration Editor and License Manager
  • GPI Configuration for Runtime or Director
  • Supported Formats
  • Supported Hardware
  • Multisampling / Anti-Aliasing
  • Input Subsystem
  • Ventuz Proprietary Files
  • Migrating Content to Ventuz 6
  • Migrating Content to Ventuz 5
  • Summary Shortcuts
  • Terminology
  • Manual Index

Ventuz Designer

  • Designer Indices
Introduction
  • Designer Introduction Index
  • Designer Overview
  • Realtime Rendering
  • Project Browser
  • Designer Interface
  • Designer Options
  • Working with Nodes
  • Hierarchy and Content Editors
  • 2D Workflow
  • 3D Workflow
  • Animation Workflow
  • Best Practices
  • Reading Data in Ventuz
  • Display Images and Movies
  • Scene Performance and Tweaks
  • Deploying a Ventuz Presentation
  • Render to Disk
User Interface
  • Designer User Interface Index
  • Designer Interface
  • Renderer Window
  • Layer Editor
  • Property Editor
  • Property Groups
  • Hierarchy Editor
  • Content Editor
  • Find and Replace
  • Toolbox
  • Animation Editor
  • Shader Editor
  • Text Editor
  • Message View
  • Scene Tree
  • Stage Editor
  • Container Outline
  • Watches Editor
  • Performance Statistics
2D Workflow
  • 2D Workflow Index
  • 2D Workflow
  • Layer Editor
  • Common Layer Properties
  • IPP Effects
  • Color Correction FX
  • Distortion FX
  • Filter FX
  • Hierarchy and Content Editors
  • Display Images and Movies
3D Workflow
  • 3D Workflow Index
  • 3D Workflow
  • Hierarchy and Content Editors
  • Renderer Window
  • Camera Navigation
  • Manipulate Objects with Gizmos
  • Layer Editor
  • Property Editor
  • Hierarchy Editor
  • Working with Nodes
  • Isolated Objects
  • Containers
  • Text Rendering
  • Character Sets
  • Geometry Import
  • Display Images and Movies
  • Particle System
  • Creating Realistic Reflections
  • Unreal Integration
  • Notch Integration
  • E2E Node Overview
Logic Workflow
  • Logic Workflow Index
  • Hierarchy and Content Editors
  • Content Editor
  • Hierarchy Editor
  • Working with Nodes
  • Property Editor
  • Containers
  • Project and Scene Data
  • Reading Data in Ventuz
  • Display Images and Movies
  • Input Subsystem
  • Multitouch
  • TUIO Protocol
  • Open Sound Control
  • Unreal Integration
  • Notch Integration
  • E2E Node Overview
Animation Workflow
  • Animation Workflow Index
  • Animation Workflow
  • Animation Editor
  • Content Editor
  • Hierarchy Editor
  • Property Editor
  • Animation and State Engine
  • Templates
  • Template Engine
  • Unreal Integration
  • Notch Integration
Project Structure
  • Project Structure Index
  • Annotations
  • Projects and Scenes
  • Project Properties
  • Project Maintenance
  • Project and Scene Data
  • Scene Management
  • Scene Statistics
  • Scene Tree
  • Performance Statistics
How Tos
  • Designer How to Index
  • How to Run Ventuz
  • How to Work with Designer
  • Ventuz Designer Drag&Drop Workflow
  • How to work with Shadows
  • How to Build Content for Multiple Screens
  • How to Use Emoijs
  • How to Build a Template
  • How to Use the Color Difference Keyer
  • How To Use the HDR Engine
  • How Create Lens Flares and Bloom
  • How to Create Visuals Loader Node
  • How to Remote Control with a Phone
  • How to use Head Mounted Displays
  • How to work with 3D Reference Layers
  • How to create a Firework Particle System
  • How to use DDS with new Block Compression modes
  • How to use the Substance Integration
  • How To Integrate Unreal
  • How To Integrate Notch
  • How To use the Vertex Integration
  • How To Control and Customize Ventuz
Reference
  • Available Nodes
  • Animation Nodes
  • Material&Color Nodes
  • Data Nodes
  • E2E Nodes
  • Geometry Nodes
  • Interaction Nodes
  • IO Nodes
  • Layers
  • Light Nodes
  • Logic Nodes
  • Render Option Nodes
  • Slides Nodes
  • Sound Nodes
  • Text Nodes
  • Texture Nodes
  • VR Nodes
  • World Nodes
  • Summary Shortcuts
  • Layer Editor Shortcuts
  • Hierarchy Editor Shortcuts
  • Content Editor Shortcuts
  • Animation Editor Shortcuts
  • Director Shortcuts

Ventuz Director

  • Index
  • Introduction
  • Environment
  • Show
  • User Interface
  • Assets
  • Taking Action
  • Property Editor
  • Shot Box
  • Project Data
  • Pages
  • Playlist
  • Timeline
  • Content References
  • Topology
  • Channels
  • Macros
  • Designing Templates
  • Plug-Ins
  • Shortcuts
  • Command Line Options
  • Application Settings
  • Glossary
  • GPI Configuration

Ventuz Runtime & Configuration

  • Runtime Index
  • Configuration Configuration Editor
  • Machine Configuration
  • Video/Audio Configuration
  • Web Configuration Editor and License Manager
  • Render Setup Editor
  • Warping and Soft-Edging Editor
  • Machine Clustering
  • Supported Hardware
  • Director Mode
  • Runtime How Tos Index
  • How to Configure Audio
  • How to Use Live Options
  • How To Play Out On Multiple Screens
  • How To Render on a Machine Cluster
  • How to Use Head Mounted Displays
  • How to Setup Spout with Ventuz
  • How to Use Newtek NDI
  • How to Use a Mixed Frame Rate Cluster
  • How to Use Tracking

How To

Designer
  • Designer How to Index
  • How to Run Ventuz
  • How to Work with Designer
  • Ventuz Designer Drag&Drop Workflow
  • How to work with Shadows
  • How to Build Content for Multiple Screens
  • How to Use Emoijs
  • How to Build a Template
  • How to Use the Color Difference Keyer
  • How To Use the HDR Engine
  • How Create Lens Flares and Bloom
  • How to Create Visuals Loader Node
  • How to Remote Control with a Phone
  • How to use Head Mounted Displays
  • How to work with 3D Reference Layers
  • How to create a Firework Particle System
  • How to use DDS with new Block Compression modes
  • How to use the Substance Integration
  • How To Integrate Unreal
  • How To Integrate Notch
  • How To build and playback Ventuz Content in Vertex
Runtime & Configuration
  • Runtime How Tos Index
  • How to Configure Audio
  • How to Use Live Options
  • How To Play Out On Multiple Screens
  • How To Render on a Machine Cluster
  • How to use Head Mounted Displays
  • How to setup Spout with Ventuz
  • How to use Newtek NDI
  • How to use a Mixed Frame Rate Cluster
  • How to use Tracking
  • How To Integrate Unreal
  • How To Integrate Notch
  • How To build and playback Ventuz Content in Vertex
Director
  • How To Control Multiple Graphics Independently From Each Other
  • How to use the Companion with Director

Ventuz Node Reference

ANIMATION
  • Mover
  • Alternator
  • Simple Control
  • Timeline Control
  • Anmation Rig
  • Keyframe Animation
  • Animation Group
COLOR/MATERIAL
  • Alpha
  • Fog
  • Ground Fog
  • Sky Box
  • Color to RGBA
  • HSLA to Color
  • RGBA to Color
  • Color Transformer
  • HLSL Shader
  • Color
  • Material
  • Color Picker
  • Substance Material
DATA
  • Database
  • Excel
  • JSON
  • RSS Feed
  • Resource Linker
  • Text File
  • XML
E2E
  • E2E Axis
  • E2E Data
  • E2E Control
  • E2E Layer
  • E2E Provider
  • E2E Node Overview
GEOMETRY
  • Rectangle
  • Rounded Rectangle
  • Gradient Rectangle
  • Overlay Rectangle
  • Cube
  • Circle
  • Sphere
  • Cylinder
  • Cone
  • Torus
  • Chart
  • Random Points
  • Mesh Loader
  • Geometry Import (Live)
  • Volume
  • Get Bounding Box
  • Arrow
  • Particle System
  • Path Renderer
  • Geometry Renderer
INTERACTION
  • Interaction Rect
  • Touch Button
  • Touch Excluder
  • Touch Marker
  • Touch Paint
  • Touch Pattern
  • Touch Proxy
  • Touch Ripples
  • Touch Transformations
  • Web Browser
  • Touch Teleport
  • Touch Simulator
INPUT/OUTPUT (I/O)
  • GPI
  • Joystick
  • Keyboard
  • MIDI
  • Mouse
  • Network
  • Open Sound Control
  • Serial
  • Timecode
  • DMX
  • HTTP
  • RamDiskWriter
LAYER
  • 3D Layers
  • 3D Layer Reference
  • 2D Layers
  • PSD Import Layer
  • E2E Layer
  • Others
LIGHT
  • Light Sources
LOGIC
  • Array Processing
  • Convert To Text
  • Cluster Synchronization
  • Counter
  • Date Time
  • Directory
  • Dispatcher
  • Enumeration
  • Expressions
  • Invert
  • Log
  • Loop Breaker
  • Math Effects
  • Matrix Operations
  • Scene Event
  • Script
  • String Operations
  • System ID
  • Text Splitter
  • Timer
  • Toggle
  • URL
  • Value Switch
  • Value Buffer
  • Variables
  • Visual Indexer
RENDER OPTIONS
  • Alpha Blending
  • Color Write
  • Alpha Testing
  • Clip Plane
  • Filter
  • Mask
  • Mirror
  • Effect
  • Render Cube Map
  • Draw Modes
  • Stencil
  • ZTesting
SOUND
  • Audio Clip
  • Sound
  • Volume Control
  • Audio Analysis
SLIDES
  • Slide Manager
  • Slide
  • Slide Port
  • Pivot
TEXT
  • Text Effects
  • Text Layouts
  • Text Rendering
TEXTURE
  • Background
  • Hatch
  • Image
  • Texture
  • SVG Loader
  • Gradient Texture
  • Live Video
  • Movie Stream
  • Movie Frame
  • Movie Clip
  • Texture Loader
  • Snapshot
  • Snapshot Framebuffer
  • Texture Saver
  • Video Source Selector
  • VIO Input
  • Spout Receiver
  • NDI Receiver
  • Substance Loader
  • QR Code
VR/AR
  • Tracked Devices
  • Draw Tracked Devices
WORLD
  • Axis
  • Billboard
  • GetWorld
  • SetWorld
  • Arrange
  • Ticker
  • Layout
  • Group
  • World Z Sort
  • YesNo
  • Switch
  • Spread
  • Filter Pass
  • Set Pass
  • Hierarchy Container
  • Scene Port
  • Content Container
  • Template Port
  • Container Info
  • Camera
  • Paths

Advanced and Development

  • Advanced and Development Index
  • Command Line Options
  • Ventuz IP Ports
  • Ventuz Machine Service
  • TUIO
  • .NET Scripting
  • HLSL Shader Programming
  • Ventuz API and SDK
  • Ventuz Extension API
  • Ventuz VIO API
  • Ventuz File Format (VFF)
  • Ventuz Stream Out API
  • Lens Calibration File for FreeD
  • E2E Node Overview
  • Unreal Integration
  • Notch Integration
Remoting
  • Remoting Index
  • Remoting Overview
  • How To Control and Customize Ventuz
  • Remoting 4
  • Remoting 4 via Websockets
  • Remoting 4 via HTTP
  • Director Remoting
  • Deprecated Remoting
  • Remoting Machine Signature

Misc

  • Presets
« Previous:
» Index «
Next: »

Lightsources

Table of Contents

  1. Standard Engine vs HDR mode
    1. Light Attenuation
      1. HDR
      2. Standard Linear Falloff
      3. Legacy Falloff
  2. Types of Lightsources
  3. Using Multiple Lightsources
  4. Shadows
    1. Directional Shadow Volume

DirectionalDirectional light source
PointPoint light source
SpotSpot light source
Lighting GroupDefine a group of light sources

Lighting in Realtime Rendering is a very efficient approximation of real life lighting. There are no global effects like one object casting a shadow onto another or light bouncing of one surface and lighting another. It is therefore often called direct lighting opposed to global lighting as used by raytracing software.

A triangle can be lit by one or multiple light sources. The final color of a pixel in a triangle is dependent on the shape of the objects surface, the characteristics of the light sources, the Material applied to the object as well as the Engine-Settings in the Layer Root of the 3D Layer. For each light source, a number of terms is calculated:

  • Ambient: This term is independent of the light source and the viewer position. It simulates the ambient light that exists in the background and from bouncing off other surfaces and is usually rather weak.
  • Diffuse: Varies the brightness of the surface based on the light direction and the surface normal. This gives an object its characteristic shape, brighter towards the light source and darker on the back side.
  • Specular: Simulates the bright highlight that occurs where the reflection of the light source is visible in the surface. Note that this will only be visible on objects that have a Material defining a specularity.

When there is no light source node in the scene, Ventuz uses an internal default light source. This so called head light is positioned at the exact position of the camera, therefore shiny objects (with a high specular amount) can appear completely white. To disable the default lighting set the DefaultLight to "none" in the 3D Layer Root Node

Both the light source and the material have a color assigned to all of these terms. In addition, the material of an object can have an Emissive term that simulates light coming from the object itself.

Standard Engine vs HDR mode

Light Attenuation

This is about how light gets darker with distance. We use different formulas for different engine modes. Below is an explanation for the formulas. You can skip the math, but remember the following:

  • When changing the falloff model (by changing the engine mode), all lights need to be adjusted for the new model
  • With legacy falloff, light-sources do not scale with the world. With the other models, light sources will scale correctly with the world as long as the scaling is uniform in x, y and z.

Every light source now has a gain property. Gain 0 will not change the light, every positive step will double the intensity of the light and every negative step will half it. So a gain of 3 will increase the intensity by a factor of 8. This is especially useful to adjust HDR lights.

HDR

In reality, light intensity decreases with the square of the distance: I = I0 * 1 / d2. Doubling the distance will quarter the light intensity.

Ventuz light-sources define a maximum radius. If the simply cut the light at a distance, we might see the cut-off point. To avoid this, we subtract the amount of light at the maximum distance (dmax), the corrected formula is:

  • I = I0 * ( 1 / d2 - 1 / dmax2 )

This is the formula we use in HDR.

Standard Linear Falloff

If we do not render in HDR, we do light calculation with gamma 2.2 colors. Unfortunately, with this the physically correct formula produces bad results, as it only applies to linear colors. Instead, we use a simple linear falloff formula: The light is just faded out by distance :

  • I = I0 * (1-d/dmax)

This produces good results and naturally has no cut-off point at the maximum light range.

Legacy Falloff

In legacy mode and advanced legacy we use the DirectX fixed function falloff mechanism, which gives 3 parameters to tweak lights:

  • I = I0 / (attn0 + attn1*d + attn2*d2)

Most people agree that this is a horrible formula that is hard to tweak. Also it does not provide a clean cut-off point and can not be scaled with the world.

Types of Lightsources

In order to make lighting calculation feasible, the travel of light rays through a scene cannot be simulated. Instead the terms above try to simulate the variation of brightness on a surface. The role of the light source is to specify from what direction the light falls on to the surface.

Lightsources are immaterial and therefore no geometry is rendered for them. To see the orientation and shape of a light source activate the show non-render objects.

The Directional light represents a light source that is so far away that the light rays are completely parallel to each other and the actual position of the light source becomes irrelevant. The most prominent analogy is the sun.

The Point light represent a lamp that is infinitely small in size. It emits rays into all directions, originating from a single point in space. Same as the Directional light, it has no surface area to simplify the calculation. The direction of light for a point light at any given point on a surface is equal to the vector from the point lights position to that point on the surface. A rough analogy might be a light bulb or a candle.

The Spot light differs from the point light in that it only emits light in a cone shaped volume instead of all directions uniformly. The InnerCone specifies the radius of the region that is lit at full intensity which then decreases to the OuterCone radius where the light influence of the spot ends. It also simulates brightness decreasing the farther away something is from the spot (Attenuation) and the more it is offset from the center axis of the spot towards the boundary (FallOff).

All lightsources have the Gain parameter in common. If your lightsources appear to dark while using the HDR mode, you can adjust and boost the gain of the intensity here.

An additional way of lighting your scene is by using the Sky Box and an HDRI/Irradiance Map as a lightsource.

The example below shows the same scene lit by a Direction light coming hard from the left, a Point light above the scene and a Spot light coming from the right.

If ApplyAxis is active, the light source will be transformed by the World Matrix as for example influenced by Axis Nodes.

Using Multiple Lightsources

Multiple lightsources can be added to a scene, for example as main and fill lights as often used in a photo shoot. However, they can also be used to light separate parts of a scene differently. For example, a spot light may be used to light only one object but not affect another object, although it would theoretically be in the cone of the spot. Instead the second object could be rendered using a completely different light setup.

Lightsources are special in that they affect all nodes that are rendered after them, not just their child nodes. They are not deactivated once their subtree has been processed.

Each light source has an Input Property Index which specifies whether the light should be used in addition to existing lights (Next) or should replace the last activated light (Override). To limit the effect of light sources to certain parts of a scene, Lighting Group nodes can be used. If their Inherit property is deactivated, lights defined outside the lighting group will have no effect on the objects rendered within the lighting group. The example below shows a scene with four differently colored light sources. In the top row, each light source illuminates each sphere that comes after it in the rendering order. In the bottom row, Lighting Groups have been used to isolate each sphere together with one light source in a separate group.

Shadows

For each lightsource you can enable shadows. Shadows in Ventuz are based on Shadowmaps.
Click the Shadow drop down menu in the Lightsource Properties and select Shadowmap to enable Shadows.



You can adjust the Properties for each lightsource individually.



The Amount is the overall intensity of the shadows. Resolution is the shadowmap resolution and should be as small as possible. With the DepthBias and SlopeBias you adjust the sampling of the shadowmap (see How To Use Shadows for more details). You can define to have the shadows in a group by the Select drop down menu. You can set the Shadowmap in the A or B group or have it off any group. The grouping works together with the Shadow Filter. The Filter drop down menu affects the shadowmap filtering and you can select between Samples 1, Samples 4 and Samples 8. When Samples 4 or Samples 8 is selected you can also adjust the quality of the sampling by changing the AntiAliasScale and FilterScale. If the values for the Scales is 0 and not bound, the sampling scale is completely turned off in the shader and therefor the performance increases.

The Pointlight needs to render one shadowmap for each of its six sides. This can affect the performance a lot! The shadowmap resolution becomes even more critical here!



With the help of the Tint properties you can tint your shadows. This will apply the specified TintColor to the BaseColor of the affected objects after multiplying it with the AmbientColor of your light. The TintMode defines how the Tint should be applied: Full will apply the Tint Color everywhere in the same amount. Attenuated will linearly fade out the amount of the Tint over the distance to the light source.

Since Shadows are working in conjunction with Lightsource as Source, Object as Shadowcaster and at least one receiver to apply the shadow to (except for selfshadowing) you should read the See Also sections as well.

Directional Shadow Volume

You can define a shadow volume for the directional light source. Enable the LightVolume by selecting the Light Relative Volume from its drop down menu.

The so called shadow volume can be visualized by enabling the Show non-render objects button in the top bar.

This will show the shadow volume by rendering infinte lines, which visualize the volume bounds. By using the Width, Height and Depth properties, you can adjust the volume's boundaries. Everything that is inside the volume will act as a shadow caster. It is therefore possible to have just a part of an object throw a shadow, as long as it is inside the volume. See the screenshot below:

This way you can limit the boundaries of a directional shadow. Instead of using the whole scene boundaries to create the shadow map, you can now limit it and therefore safe shadow map precision, therefore performance. Before, you would need to increase the shadow Map Resolution to have at least more details when using a very huge scene. Now you can safe performance and or the resolution, by defining the volume for the directional light shadow.

Below we compare a scene, one without- and one with LightVolume used. The scene is VERY huge because the groundplane has a size of 400 units. The torus is compared really small:

Both scenes use the same settings for the Shadow Map Resolution of _2048, same Directional Light Source and positions. The upper screen shows the Directional Light Source without the LightVolume while the lower screen shows the exact same Directional Light Source with the LightVolume enabled and adjusted to be at 10x10 units (the boundaries are indicated by the yellow lines).

While the upper screen result is more of a blocky and pixelated shadow map, compared to the crisp and high resolution shadow map for the other, you can see, that without a defined LightVolume the whole scene (in this case the 400unit ground floor) is taken into account for the shadow map calculation. Therefore you have less pixels in the same shadow map available - since it has to cover the whole scene. If you define a LightVolume for the shadow map calculation you can define specific areas that really advance of a shadow map or are point of interest, while not wasting the space on the shadow map or resolution in other areas in the scene, which are out of focus or point of interest.

See also:
  • Introduction to Realtime Rendering
  • Shadow Filter Node
  • Material Node
  • How To use Shadows
  • ​MSDN: Common Techniques to Improve Shadow Depth Maps
  • Shadow Options for MaterialNode
  • Shadow Filter
  • How To use Shadows

« Previous:
» Index «
Next: »
Copyright 2022 Ventuz Technology