Lumen Pro 2 Documentation

Blender lighting addon — your pro tool for handling and analysing illumination data. User manual.

Chapters

1. Introduction
2. Installation & License
3. Quick Start
4. Photometric Lights
5. GLDF / L3D
6. IES Library
7. Analysis Planes (Lumen Graph)
8. Realtime Tools
9. Compositor
10. CIE Sky & Weather Data
11. Geo Tracer (Realtime CIE Sky)
12. Glazing
13. Export
14. Preferences Reference
15. Validation (CIE 171:2006)
16. Tips & Troubleshooting

5. GLDF / L3D

GLDF (Global Lighting Data Format) is an open XML/ZIP container for complete luminaires. It bundles the 3D geometry (L3D) with the photometric measurements, light-emitting objects / surfaces, and product information. Lumen Pro imports the file through File → Import → GLDF / L3D (*.gldf, *.l3d), or via the N-panel Import → GLDF / L3D. Cycles must be the active render engine.

Importing a GLDF product

1. Run File → Import → GLDF / L3D (or the N-panel import button) and pick a .gldf file.
2. A preview dialog opens with the product Name and Description read from product.xml.
3. Choose one of the available Variants (each variant groups a specific emitter + geometry combination of the product).
4. Click Import. Lumen Pro imports the L3D geometry with joints and positions, attaches an empty with lumen_type = 'GLDF' as the luminaire origin, imports the OBJ geometry with its materials and textures (units converted: cm/mm → m), and parents the photometric lights to the luminaire objects so the whole assembly moves as one.

If you pick a file whose data contains no product.xml or no valid variant, the import is cancelled and an error dialog is shown.

Joints

L3D files can define adjustable joints (e.g. for pendants and gimbal rings). Lumen Pro reconstructs the joint hierarchy: each joint is an empty at its declared position and rotation, sized to the part, and the child geometry is parented to it. Joint rotation limits from the L3D file become Limit Rotation constraints. Select the luminaire origin empty (a GLDF object) and open the GLDF tab in the 3D Viewport N-panel (GLDF Joints panel): it lists every joint and provides editable X / Y / Z rotation fields in degrees, each showing its allowed range (e.g. [-15.0° ... +15.0°]) so you can aim the light within its mechanical range.

Light-emitting objects & surfaces

• Luminaire objects (LEO) and luminous surfaces (LES) from the L3D structure are represented in the scene, matching the real emitting parts of the fixture.
• The photometric data of the GLDF variant (“ldt” file) is applied to the emitted light as a Lumen Pro photometric light (IES/Polar grid) parented to the object. The Use Area Light toggle again selects a point or area emitting surface.

Tips

• The luminaire origin empty (visible as plain axes at the product mount point) is the convenient handle for placing and rotating the entire product.
• Photometric data and all Lumen Pro node groups behave exactly like the lights described in chapter 4 — edit lumens, temperature and inspect the data panel afterwards.
• Use the L-pie menu “Update Lumen Graph” after moving geometry if you already baked analysis for the imported scene.

↑ back to top

6. IES Library

The IES library turns a folder of photometric files on your disk into a visual, thumbnail-based browser. You can browse IES / LDT files with a real preview render of their luminous distribution and add, convert or apply a profile in a single click — without touching the file picker for every single light.

Preparing the library

1. Open Edit → Preferences → Add-ons → Lumen Pro 2.
2. Set Library Directory to the global folder that stores your IES profiles (the folder is scanned for .ies, .IES, .ldt and .LDT files).

Browsing the library

1. In the 3D Viewport open the N-panel (Lumen Pro tab) and expand the Library box. If the folder is empty you’ll see “Choose a Folder” and can point the browser at another directory.
2. The first time you open it, Lumen Pro renders a preview thumbnail of every file in the folder (a small Cycles render of the IES profile) and stores it in a previews subfolder. Depending on the folder size this can take a moment.
3. Use the refresh button (FILE_REFRESH) to re-render previews, e.g. after you added new files to the folder.
4. If the folder has subfolders, a subfolder dropdown appears above the grid — pick one to browse it (the previews folder itself is skipped).
5. The grid shows the thumbnails; hovering shows the parsed file description (manufacturer, lumen, watts, catalog …). Click a thumbnail to select it — the filename is shown below the grid.

Add, Convert or Apply

With a profile selected, the Library box offers three actions, depending on your selection:

The Use Area Light toggle (below the grid) maps the profile onto an area / luminous surface instead of a point light.

A note on physics: photometric data is captured in spherical format, so mapping it onto a flat area light is an approximation rather than physically exact. The results are nonetheless very close, because Lumen Pro maps the total luminous flux (energy) over the whole emitting area — which makes rendering noticeably more realistic (soft shadows, luminous size of the fixture). The trade-off: for rendered light this behaviour is limited to 90° vertical profiles (Type 90). For vertical Type 180 files an area light is not suitable — Lumen Pro then shows a warning popup (“Area Lights are not suitable for vertical TYPE180 ! May alter Illumination !”) — use a point light for those. Also note that the luminous panel itself only appears in the final render / camera view when its camera visibility is enabled — if the light does not show up on camera, enable its camera visibility in the light’s ray visibility settings.

The L key “Lumen Pro” pie menu

Press L in the 3D Viewport:

• Add from Library — same as the “Add” button, using the currently selected thumbnail.
• Apply from Library — appears when a Lumen Pro light is active whose profile differs from the previewed file.

↑ back to top

7. Analysis Planes (Lumen Graph)

A Lumen Graph (also called lightplane / texture grid) is a flat mesh that Lumen Pro converts into an illuminance analysis plane: it bakes the incident light onto an image texture, computes DIN EN 17037-style statistics and visualizes the result on the mesh — as textured values, 3D bars, numeric geometry or matplotlib ISO lines.

Creating an analysis plane

1. Select a flat mesh that will be the analysis surface (the floor of a room, a work plane …). The object must not be a Lumen object yet (no lumen_type).
2. Create the plane: press L → Create Lumen Graph, or use the Create Texture Grid button (N-panel → Lumen Pro → Texture Grids).
3. The object is renamed Lumen_Graph and tagged GRAPH. It is excluded from light transport (no rays bounce off it), receives the Lumen_data_vis material with its baked-image node, and the texture resolution is derived from the graph’s footprint and the cell size: resolution = plane width / cell size per axis.

Creating a graph bakes it immediately — you get the illuminance result right away. The bake runs Cycles with the samples from the Bake Samples preference (default 512) and converts the render to lux using the lumen efficacy preference.

Display types

In the N-panel Texture Grids section, Type chooses how the result is drawn:

After switching the type, run Update Texture Grid (or the L-key Update Lumen Graph) to rebuild the display. Update Matplotlib refreshes only the ISO lines without re-baking.

Statistics & DIN EN 17037

Every bake computes, from the valid pixels of the analysis plane:

• min / max / mean illuminance,
• uniformity ratios min/mean and min/max,
• the percentage of the plane above 100 / 300 / 500 / 750 lx — the building blocks of DIN EN 17037 daylighting assessments.

The bake resolution is controlled by Cell Size at the moment the graph is created — the smaller the cell, the higher the texture resolution (texture width / height = plane size ÷ cell size per axis). The default Graph Cell Size is 0.3 m, which matches the cell size used in the DIN EN 17037 example. The values are shown as an on-screen legend / scale bar with the 5-step color ramp once the graph is selected. Global Scale lets you fix a shared min/max range across several graphs so their colors can be compared directly.

Update, reset and clear

• Update Texture Grid — re-bakes after you move light-fixtures or geometry.
• Update Matplotlib — re-renders ISO lines from the existing bake.
• Reset Lightplane — restores the image to a fresh generated texture and reveals the editable width / height fields, letting you type in a custom resolution directly (e.g. multiply by 10 for a high-res textures).
• Clear Lightplane — removes the graph behaviour, statistics and material (back to a plain mesh).

↑ back to top

8. Realtime Tools

The realtime (“RT”) tools compute illuminance live in the viewport while you work. They only act on Cycles Rendered shading — activating a mode switches the viewport to Rendered and snaps cursor placement to faces. Everything is local and does not change your scene data (probes are empties you can delete anytime).

RT Probe mode

1. Activate Rendered shading (or press L and toggle Lumen RT Mode in the pie menu).
2. Hold Ctrl+Alt and release the left mouse button on the surface you want to measure — a probe empty (Lumen_RT_Probe) is placed.
3. Each frame Lumen Pro samples one pixel under the probe and displays the value next to it, plus min / max / mean and uniformity edges on the whole line of probes.
4. Set the displayed unit in the N-panel RT box: W/m² (irradiance), Lux, cd/m² (luminance), Footcandles or Daylight Factor (%).
5. Adjust Font Size, Min Size (empty height floor) and Size Multi (height scaling of probes) while Hide Label / Show Label toggles the numeric readout.
6. Exit with ESC (or toggle Exit RT Mode in the pie menu).

RT Grid

• Select a flat mesh and press L → Create Lumen RT Grid (or the Create RT Grid button in the RT box).
• The mesh is renamed Lumen_RT_Graph (RT_GRAPH) and a probe empty is created on every grid point. The Grid Spacing value (default 0.5 m) controls the probe density.
• Activate Lumen RT Mode afterwards — the whole grid now shows live values and statistics.

RT ISO mode

1. Press L → Lumen RT ISO Mode (or the N-panel toggle). The viewport runs the live contour shader over the rendered scene.
2. Configure in the N-panel RT box: Line Width, Line Alpha, Line Levels, Min / Max lux, Use Bands (filled contour bands instead of lines) and Colors (matplotlib colormap).
3. With Camera View Only the analysis is limited to the camera view frame; without it the whole viewport is covered.
4. Overwrite Scene Materials replaces materials with a neutral Lumen_overwrite material during the mode, so the ISO colors are easier to read — the original materials are restored on exit.
5. A color scale bar and min / max / mean stats are drawn on screen.

ISO from a render

The Iso Lines from Render button (N-panel → Lumen Pro → Export) renders the beauty frames through the same contour shader offline and stores the result as the packed image Lumen_ISO_Overlay. The image can be used in the compositor to overlay the iso lines onto your render for the final output — see chapter 9.

A camera and a rendered render result are required: make sure the scene has a camera that frames your analysis, render the image first (image → any frame of the animation), and then run Iso Lines from Render. It reads the last render result present in Blender, so there is nothing to overlay without a rendered image.

↑ back to top

9. Compositor tools

Lumen Pro ships a set of premade compositing node groups and a legend generator. The node groups let you build flexible overlays — for example the same look as the realtime ISO lines (chapter 8) — but composited through the node editor: you can regenerate, recolor and recombine them live, on top of any render or viewport stream.

Enabling compositing (Blender 5.1 and newer)

Lumen Pro supports Blender 5.1 and up, where the old “Use Nodes” toggle no longer exists. Compositing is driven by a compositing node group attached to the scene:

1. Open a Compositor editor (switch an editor type to Compositor).
2. In the Compositor header, click New to create a compositing node group. It becomes active for the current scene and is used by the render pipeline and by the realtime compositor.
3. Enable the Realtime Compositor in the 3D viewport header (the realtime-compositor dropdown → Realtime or Always) so the composite shows live in the viewport while you work — switch it off for full-performance viewport previews.
4. Make sure a Group Output node is present; if it is missing the compositor does not run.

Premade node-group assets

Lumen Pro registers its assets folder as the Lumen Pro asset library, which includes the pre-built compositor_nodes compositing node groups. Append a group from the asset browser (or from File → Append) inside your compositing group — several can be wired together:

• lumen compose — the base group: Render Layers → Exposure → Group Output. Use it as the backbone of your compositing setup.
• Analysis overlays — colorramp min max, Daylight Factor, DayLightFactor, area greater than and area less than recolor image regions by value, e.g. to highlight the iso-contour look from chapter 8.
• Line styles — line, single_line, three lines and dots draw contour-style line/hatch overlays over the image.
• Unit conversion — Units, W/m² to lux, W/m² to fc and rgb to W/m² convert between irradiance, illuminance and raw image values.
• Place Legend — places a legend image onto the frame (used together with the legend generator below).

The legend tool

The legend generator is one of the compositor tools: it creates a color legend image for your analysis and inserts it into the compositing node group, so an annotated scale is composited into the final frames. Its Lumen Pro Legend panel appears in the N-panel of the Compositor editor.

Legend items list

1. Click Add Legend Item to add steps. Each item has a value (a lux level), a color and a style (area bar or thin line). Use the + / − / up / down buttons to manage the list; values of new items step by 100 lx and cycle through rainbow hues as defaults.

Layout

• Width (default 200) and Height (default 400) of the legend image.
• Margin (default 20) around the contents.
• Label (e.g. “Illuminance”) and Unit (e.g. “lx”) become the header Illuminance [lx] on top of the legend.
• Font Color and Background Color for the legend.
• Image Name — the Blender image that receives the legend (default Lumen_Legend).

Generating

1. Click Generate Legend Image. Lumen Pro renders the legend offscreen (GPU), packs it into the named image and inserts an Image node with it into the compositing node group at a convenient position.
2. Connect the node’s Output into your setup (e.g. combined via Place Legend, a Mix, or an Overlay) so the legend lands where you want it in the frame — in Blender 5.1+ results flow to the Group Output node.
3. With the realtime compositor enabled, the legend appears live in the viewport; render to bake it into the frames.

↑ back to top

10. CIE Sky & Weather Data

Lumen Pro generates physically based CIE standard skies and combines them with real EPW climate data for daylighting analysis. The sky is baked into an equirectangular High-Dynamic-Range environment image and plugged into the World background of your scene.

Setting up the sky

1. Open the N-panel → Lumen Pro tab → CIE Sky box.
2. Click Setup CIE Sky Environment. Lumen Pro builds the world shader (Lumen_CIE_Sky_Env environment texture → Background → World Output) and generates the initial sky image.
3. Pick a Sky Type — from the CIE standard series (overcast 1–5, partly cloudy 6–11, clear skies 12–16) plus the Perez all-weather model (default).
4. Set the daylight via Sun Altitude, Sun Azimuth, DHI (diffuse horizontal irradiance) and DNI (direct normal irradiance). If Include Sun is on, a bright solar disc is baked directly into the texture — there is no separate sun light object, which keeps the analysis clean.
5. Ground Reflection controls the ground luminance (DHI/π · reflection).
6. Choose a Resolution (Low 256×128 up to Ultra 2048×1024, or Custom) and click Update Sky Texture. Enable Auto Update to regenerate automatically whenever a parameter changes.

EPW weather data

EPW files (EnergyPlus / Ladybug) provide per-hour climate data for any location:

1. Click Load EPW Data and choose a .epw file. Lumen Pro reads the location (latitude / longitude / timezone from the header) and the hourly GHI / DNI / DHI (plus their illuminance equivalents and zenith luminance).
2. The Ev,d,med value (the median daylight illuminance of the brightest half of the year) is computed automatically — this is the reference value used for daylight-factor-based assessments.
3. The EPW fields now drive the Month / Day / Hour (and day-of-year) sliders: choosing a date & time sets the sun position and irradiances from the weather file, so the sky matches the real sun ” for that moment.

Accumulated sky

With EPW data loaded you can aggregate many sky states into one average sky:

1. Enable Calculate Accumulated Sky in the Accumulated Sky box.
2. Set the start / end date (month, day, hour) and the Time Step in hours (minimum 1 minute).
3. Click Calculate Accumulated Sky. Lumen Pro walks the EPW data through the range, computes a CIE sky for each step and sums them into one image (Lumen_Accumulated_Sky) that is plugged into the world — your annual average daylight situation as a single environment.

Import CIE Sky (CSV)

The Import CIE Sky button loads a per-patch sky CSV (Tregenza-style subdivision with direct beam / diffuse horizontal data) and rasterizes it into the same equirectangular environment, useful for external sky-model / simulation tools.

Geo Tracer & realtime CIE skies

For realtime sky analysis in the viewport, Lumen Pro provides the Geo Tracer workflow: a Geometry Nodes based tracer that evaluates the CIE sky (and EPW weather) inside Blender’s node graph. See the next chapter.

↑ back to top

11. Geo Tracer (Realtime CIE Sky)

Geo Tracer is Lumen Pro’s Geometry-Nodes based tracer for realtime daylight analysis. Instead of baking a static environment image, it evaluates the CIE sky and weather data directly inside Blender’s node graph — so moving the sun, changing the date or the sky model updates the illumination live in the viewport.

It ships as custom geometry node groups (Lumen Sun Sky, Lumen Accumulative Sky) that you add to your analysis mesh from the asset library. The whole sky / weather model lives in the node tree and can be combined freely with other geometry nodes.

Geo Tracer panel

The N-panel → Lumen Pro tab → Geo Tracer box provides weather data tools for the node groups:

• Download Weather Files — opens the EPW weather map (ladybug.tools / EPWmap) in your browser so you can fetch real climate files for your location.
• Import Weather Data (EPW/WEA) — loads an .epw or Radiance .wea file. The operator writes two CSV files next to your weather file (weather_data.csv with month, day, hour, dni, dhi rows, and weather_meta.csv with lat, lon, tz, elevation) and wires them into the CSV sockets of the node group on your active Lumen mesh — the tracer can then drive the sun position and irradiances from the real hourly data.

Workflow

1. Create or select the analysis mesh you want to shade with the tracer.
2. Add a Lumen Sun Sky node group (from the Lumen asset library) as a Geometry Nodes modifier. The operator requires a Lumen object with a node-group modifier to import weather data.
3. (Optional) Import your EPW / WEA weather file from the Geo Tracer panel — it fills the node’s weather_csv / meta_csv sockets with the generated CSVs.
4. Drive the node inputs for date, time and sky type. The viewport reflects the daylight conditions in realtime.

Node groups

All Geo Tracer node groups are part of the Lumen Pro asset library (geo_nodes) and are evaluated by Blender normally. The two main tracers:

• Lumen Sun Sky — the realtime tracer. Inputs: name, weather_csv / meta_csv, the month / day / hour start+end range, and the display toggles Compass, Analemma, Sun Vectors and Limits.
• Lumen Accumulative Sky — aggregates many sky states into one result. Adds the Subdivision Type and Sky Components menus and the Accumulate in Sensor toggle; it sums hourly contributions over the selected date/hour range (for annual / seasonal averages on a sensor grid).
• Lumen CIE Sky — a single, static sky state from Day Of Year, Sun Altitude / Sun Azimuth, DNI / DHI and Dew Point — useful when you do not need weather data.

Supporting groups round out the tracer: Lumen Compass, Lumen Date, Lumen Location, Lumen Day Of Year, the sensor grid (Lumen Sensor, Lumen Sensor Grid / Grid Loop), Lumen Statistics, Lumen Filter EPW Data / Lumen Sample EPW, Lumen Display Values, Lumen Legend, Lumen Texture to Grid and the solar-astronomy / CIE helpers (Sun Vector, altitude / azimuth, decl, eot, ha, lst, tc, the CIE type0 / linear coefficient formula groups and DLA EN DIN 17037 for glare/daylight-assessment shading) — all reusable inside your own geometry-node trees.

↑ back to top

12. Glazing

Lumen Pro imports angle-dependent window optics from LBNL’s WINDOW program reports (the de-facto tool for window performance data) into a material, so your daylighting analysis uses the real transmittance / reflectance of the glazing at every incidence angle.

Preparation

• Create a material with the required nodes: Tvis (visible transmittance), Rfvis (front reflectance) and Rbvis (back reflectance) as Float Curve nodes — the templates are part of the Lumen Pro node assets. Optional transmittance and reflectance RGB nodes receive the integrated colors.
• Select the glazing material so it is active (the tool writes into context.material).

Applying glazing data

1. Open the Shader Editor and switch the sidebar (N-panel) to the Node category — the Lumen Glazing panel appears (it shows only for shader/material editing).
2. Either pick a glazing from the bundled assets folder (dropdown “Glazing File”) and click Apply, or load your own report with Import from File (*.txt).
3. Lumen Pro parses the WINDOW report (Optical Properties for Glazing System): the incidence-angle table with per-angle Tvis, Rfvis and Rbvis values (the trailing hemispherical average is skipped), and optionally the CIELAB color properties, which are converted to linear RGB and fed into the color nodes.
4. The float curves are repopulated with the measured pairs and the material is refreshed. From now on the glass reacts correctly to oblique light, exactly like the measured pane.

↑ back to top

13. Export

Lumen Pro provides three ways to get your analysis out of Blender: a formatted illuminance report, a contour overlay image from your final render, and raw per-pixel data as CSV. All of them work on a selected Lumen Graph object and live in the N-panel → Lumen Pro → Export box.

Report header

Before exporting, fill in the User, Client, Project and Installation fields at the top of the Export box — they are printed in the header line of the report together with the current date.

Export Lumen Graph (A4 report)

1. Select the analysis plane that holds the illuminance data.
2. Click Export Lumen Graph. Lumen Pro opens an A4 portrait report (matplotlib): header (User / Client / Project / Installation / Date), the results block (min / max / mean in lx, plus the min/mean and min/max uniformity ratios), the logo, and the colour plot of the plane — either the baked ISO-line image or freshly drawn contours following your ISO style, with a “Illuminance [lx]” colorbar and metered axes (aspect equal).

Iso Lines from Render

1. Select the graph whose range your render represents and click Iso Lines from Render.
2. Lumen Pro renders the current frames through the contour shader (see RT ISO), stamps min / max / mean + a mini legend and writes the result into the packed image Lumen_ISO_Overlay in your blend file — ready to combine with the legend of chapter 9.

This requires a camera framing your analysis and a rendered render result present in Blender — render the image first, otherwise there is no beauty frame to draw the contours onto.

Export CSV

Raw data export for further processing (e.g. in Excel / CAE tools):

1. Select the graph and click Export CSV.
2. Choose a destination file. For every pixel of the analysis plane the CSV writes one row with: X / Y / Z world coordinates (m), the pixel area (m²), the visible irradiance (W/m²) and the illuminance (lux).

↑ back to top

14. Preferences Reference

All add-on settings live in Edit → Preferences → Add-ons → Lumen Pro 2. They are split into sections; most appear only while the license is active.

License

IES diagram / gizmo

Bake

Library

Units / conversion

Maintenance and glazing factors

↑ back to top

15. Validation (CIE 171:2006)

The daylight calculation engine of Lumen Pro 2 was validated against the analytical reference values of CIE 171:2006 — “Test cases to assess the accuracy of lighting computer programs” (the CIE standard used worldwide to verify daylighting software). Eight test cases are covered, split into four series:

• 5.9 — daylight factor under a 1×1 m and a 4×4 m roof opening (CIE general sky type 1)
• 5.10 — the same roof openings fitted with glazing (transmission 0.88)
• 5.11 — daylight factor through a 2×1 m and a fully-open 4×3 m vertical facade opening
• 5.12 — the same vertical facade openings fitted with 6 mm glazing (transmission 0.88)

All calculations use CIE general sky type 1 (overcast sky) and a 100% white diffuse BSDF (0 roughness) on the internal surfaces. The daylight factor is calculated at calculation points A to N plus the extended grid G’ to N’ and compared with the analytical reference values. The calculated daylight factors closely match the reference values across all eight test cases.

The report contains the per-point comparison table, the accuracy indicators (MAE, RMSE, relative deviation) and the reference-versus-Lumen graph for every test.

↑ back to top

16. Tips & Troubleshooting

“Select Cycles as Render Engine!”

Every importer, converter and most analysis operators require Cycles. Switch in Render Properties → Render Engine before adding photometric lights, GLDF products or baking graphs.

Library shows “Choose a Folder”

No Library Directory is set (or the folder is empty). Point the field in preferences, or set the folder picker in the Library box. After adding new IES files to the folder, use the refresh button to render the new previews.

License / activation issues

• Lumen Pro validates against the license server at Blender startup (and every 50th file load). Blender must reach lumenpro.eu — firewalls/proxies can block it. Without a valid, active response the add-on stays disabled.
• If a message box complains or the status stays empty, paste the key again (it is validated on Enter) and make sure the key is for the matching machine count.
• Before moving to a new computer, use Deactivate Lumen Pro (see chapter 2).

IES files failing to preview

Lumen Pro warns about unsupported details in the file metainformation, e.g. “TILT keyword not found, check your IES file”, “Units type should be either 1 (feet) or 2 (meters) using 2” or lamp-type messages (vertical / horizontal angle ranges). These are fall-backs — the light is still created with sensible defaults for the file type.

Analysis plane bakes “black” / all zeros

• Make sure the plane is inside the lit room (the gizmo and lights above it).
• Check that the lights emit (energy > 0) and the Include Sun / sky is present for daylighting.
• Increase Bake Samples if the result is noisy; enable denoising.
• After moving geometry, run Update Texture Grid (L-key → Update Lumen Graph) to re-bake.

Vertical TYPE180 profiles and area lights

Lumen Pro warns that area lights are not suitable for vertical TYPE180 photometries and may alter the illumination. Use a point light (disable Use Area Light) for such profiles.

RT modes do not start

RT modes require Rendered viewport shading. If the toggle seems to do nothing, switch shading to Rendered manually, then toggle the mode again. Probes are placed with Ctrl+Alt+left mouse button (release) over the surface.

Glazing panel is disabled

The Lumen Glazing panel needs an active material with Tvis / Rfvis / Rbvis float-curve nodes. Import the material from the Lumen assets first (see chapter 12).

General performance tips

• Lower the graph cell size grid and bake samples during model exploration, raise it for the final results.
• For documentation-grade daylighting use CIE sky + EPW and an accumulated sky for annual values (see chapter 10).
• Use RT mode for probing while iterating — it is interactive and leaves the bakes untouched (see chapter 8).
• Baking hundreds of preview thumbnails can take a while — generate the library previews once on the fastest machine.

Support

For further help, questions or to report a problem, visit lumenpro.eu or join the community on Discord.
GLDF / L3D is experimental — samples from real manufacturers are always welcome to improve the importer. The format itself and its schema are open source on GitHub (globallightingdata/gldf, L3D in globallightingdata/l3d) — example luminaires can be found in the examples repository.

↑ back to top