Modeling Complex Architectures in Dialux Evo

Technical methods for executing Dialux Evo geometry modeling, focusing on importing complex CAD files and rendering accurate surface textures.

Illumination Pros Editorial

May 23, 2026 9 min read

In the contemporary landscape of architectural lighting design, standard rectangular volumes are increasingly rare. Today’s lighting professionals are routinely challenged with illuminating parametric facades, organically curved atriums, and multi-layered spatial volumes. Executing rigorous Dialux Evo geometry modeling is essential for handling these non-standard building geometries. While DIALux evo remains the preeminent lighting software for European and global compliance—alongside counterparts like AGi32—its approach requires specific technical workflows. Poorly optimized models not only extend calculation times exponentially but can fundamentally corrupt the accuracy of your photometric results.

This technical guide outlines methodologies for optimizing architectural environments within the software. We will explore the integration of complex building import files, the mitigation of polygon bloat, the assignment of accurate surface reflectances for radiosity calculations, and the preparation of spaces for advanced ray tracing simulation.

The Challenges of Complex Geometry in Lighting Calculations

DIALux evo utilizes a radiosity algorithm to compute illuminance and luminance values across surfaces, complemented by a ray tracing engine for photorealistic visualizations. The radiosity method divides all spatial boundaries into a calculation mesh (a matrix of patches). Light is exchanged between these patches until energy equilibrium is reached.

When importing highly detailed architectural models containing thousands of complex surfaces—such as those exported directly from Revit, Rhino, or SketchUp—the radiosity engine is forced to subdivide every micro-surface into its own patch matrix. This “polygon bloat” causes severe performance degradation. More importantly, excessive localized geometric details (such as door handles, window mullions, or HVAC grilles) can introduce microscopic shadow artifacts and infinite reflection loops, artificially lowering the calculated average illuminance on working planes.

Polygon Decimation and Complex Building Import Formats

To ensure calculations remain robust and accurate, lighting designers must rigorously simplify 3D models before importing them into DIALux evo. The software supports several 3D file formats, each with distinct behaviors:

IFC (Industry Foundation Classes): The standard for BIM workflows. IFC files bring structural intelligence (walls, windows, doors are recognized as such). However, architectural IFCs are often overly detailed for lighting purposes.
3DS and SAT: Traditional 3D formats. SAT files (ACIS solid models) often provide the cleanest importation for curved surfaces, as they represent true mathematical curves rather than faceted polygons. 3DS files are mesh-based and must be carefully decimated prior to import.
DWG/DXF: Primarily used for 2D underlays, though 3D DWG is supported. Using 2D DWGs to manually extrude the room contours within DIALux evo is often the most computationally efficient method, albeit labor-intensive for complex curves.

Best Practices for Complex Building Import

When executing a complex building import into DIALux evo, the primary directive is maintaining photometric integrity while shedding superfluous geometric data.

1. Abstracting the Architecture

Prior to export from the native modeling software (e.g., Revit or Rhino), create a dedicated “Lighting Analysis” view. Disable all hardware, furniture, casework, complex railings, and mechanical equipment that does not materially impact the distribution of light. A curved architectural bulkhead that shields a cove must remain, but the millimeter-precise reveals within that bulkhead should be simplified into a single planar surface.

2. Managing Curved Surfaces

DIALux evo evaluates curved surfaces by breaking them down into faceted planar polygons. A tightly curved architectural feature exported with a low segmentation angle will generate thousands of vertical calculation faces. Restrict the tessellation of curved surfaces in your modeling software. An angle tolerance of 10 to 15 degrees is typically sufficient for photometric accuracy without overloading the DIALux evo radiosity engine.

3. IFC Workflow Optimization

If utilizing an IFC workflow, coordinate with the architect to receive an exported IFC model configured to the “Level of Development 200” (LOD 200). This provides the overall massing and structural boundaries without the granular detailing of LOD 300 or 400 models that induce calculation errors. Upon import, ensure DIALux evo successfully recognizes the building shell; manual correction of room contours may still be necessary to seal the environment against light leaks.

Texturing and Surface Reflectance Calibration

Accurate surface texturing in DIALux evo is not merely an aesthetic consideration; it is the mathematical foundation of inter-reflection calculations. When applying textures to complex geometries, lighting engineers must manually assign physical properties to imported images.

Defining Reflectance (Rho)

A common error in Dialux Evo geometry modeling is importing a visual texture (e.g., wood grain or concrete) without overriding the software’s default reflectance assumptions. The luminous flux reflected by a surface is dictated by its reflectance factor.

If you apply a dark walnut texture, the visual representation may appear dark, but if the material properties still possess a 50% reflectance factor, your inter-reflection calculations will be heavily inflated. Always calibrate the reflectance manually in the material properties tab.

Specularity and Roughness

For standard radiosity calculations (which are utilized to verify compliance with ANSI/IES RP-1-20 for office lighting, or EN 12464-1), surfaces are generally treated as perfectly diffuse (Lambertian reflectors). However, for spaces containing significant specular materials—like polished marble floors or extensive interior glazing—the standard Lambertian assumption will fail to capture concentrated specular reflections and potential glare sources.

When setting up these materials, input the precise degree of reflection and adjust the specularity slider. Note that highly specular surfaces require the use of the ray tracing engine to accurately visualize the resulting caustics and mirrored reflections, as radiosity alone cannot resolve directional reflection vectors.

Comparison of Dialux Evo Geometry Modeling Methodologies

The table below contrasts the three primary methodologies for generating complex environments in DIALux evo.

Modeling Methodology	Computational Efficiency	Photometric Accuracy	Ideal Application Scenario
Native Extrusion (2D DWG)	Extremely High	High	Standard office floors, industrial facilities, and environments with rectilinear architecture.
BIM Import (IFC LOD 200)	Moderate	High	Multi-story buildings, projects requiring room-by-room compliance, and complex structural shells.
Direct 3D Mesh (3DS/SAT)	Low to Moderate	Variable	Highly organic architecture, parametric ceilings, and custom luminaire integration. Requires rigorous pre-decimation.

Optimizing the Calculation Grid

Once the complex geometry is established, the calculation grid must be deployed. In non-standard architectures, a simple rectangular working plane often intersects with curved walls or multi-level platforms, yielding invalid calculation points (zero illuminance values).

Polygonal Calculation Areas: Discard the default rectangular working plane. Draw polygonal calculation surfaces that accurately track the contours of the complex geometry. Ensure a minimum offset of 0.5 meters from all walls to prevent extreme illuminance gradients near vertical surfaces from skewing the average illuminance and uniformity.
Grid Spacing: The spacing of calculation points must reflect the scale of the space and the mounting height of the luminaires. In AGi32, halving the grid spacing quadruples the calculation points; the same mathematical principle applies to DIALux evo. Over-densifying the grid on complex surfaces exponentially increases processing time. Adhere strictly to the maximum grid spacing formulas stipulated by the relevant regional standards.
Adaptive Meshing: DIALux evo utilizes adaptive meshing for its radiosity calculations. On complex imported 3D models, ensure that the calculation parameters for the room surfaces are set to an appropriate mesh density. Reducing the mesh resolution on non-critical architectural elements can salvage calculation speeds.

Executing the Ray Tracing Simulation

While the radiosity calculation provides the numeric illuminance values necessary for engineering compliance, communicating complex architectural lighting to stakeholders often requires photorealistic visualization. The DIALux evo ray tracing simulation engine calculates the precise path of light rays, capturing specular highlights, refractions, and accurate shadow casting that radiosity approximations miss.

Preparing for Ray Tracing

Ray tracing is highly sensitive to polygon counts and transparent materials. Before initializing a render:

Ensure all glass surfaces have accurate transmission factors defined.
Confirm that the IES or LDT photometric files attached to the luminaires have accurate luminous dimensions. A highly detailed 3D luminaire model paired with a mismatched photometric web will cast disjointed shadows.
Utilize the “Fast Raytracer” for preliminary checks before committing to a high-resolution, high-bounces final render.

Managing Light Leaks

Complex geometries, particularly those imported via 3DS or Rhino, are notorious for non-manifold edges—tiny gaps between intersecting polygons. During ray tracing, direct sunlight or exterior ambient light can penetrate these microscopic gaps, creating erratic bright spots on interior walls. To resolve this, ensure the architectural model is completely “watertight” prior to import, or manually construct blocking volumes (simple opaque cubes) within DIALux evo, hidden within the structural cavities, to intercept rogue light rays.

Validating Results Against Standards

Regardless of the modeling complexity, the final output must remain technically defensible and aligned with industry standards. Whether you are targeting the lighting power density (LPD) limits of ASHRAE 90.1-2022 or the illuminance and glare limits of ANSI/IES standards, the integrity of the 3D model is paramount.

Failing to simplify complex imported meshes can result in the radiosity engine trapping luminous flux within microscopic architectural crevices, artificially deflating the calculated efficiency of the space. Always cross-reference the calculated average illuminance against a simplified average illuminance manual calculation (using the Zonal Cavity Method) to verify that the software output remains within a logical margin of error.

By meticulously controlling the import of complex building geometries, rigorously managing surface texturing, and understanding the computational limitations of the radiosity engine, lighting professionals can leverage DIALux evo to accurately simulate even the most avant-garde architectural environments.

Frequently Asked Questions

What 3D file formats are best for importing complex geometry into DIALux evo?

For building architecture, IFC is the standard, though models should be simplified to LOD 200. For organic shapes, SAT solid models provide cleaner curves than faceted 3DS meshes.

Why do imported 3D models slow down DIALux evo calculations?

DIALux evo radiosity calculates light exchange between patches. Highly detailed imported meshes with thousands of micro-polygons cause polygon bloat, exponentially increasing calculation times.

How do I handle specular reflections on imported 3D surfaces?

Radiosity assumes surfaces are Lambertian. For accurate specular reflections from glossy textures, adjust the specularity slider and execute a ray tracing simulation.

What is the primary cause of light leaks in imported geometries?

Light leaks are typically caused by non-manifold geometry or microscopic gaps between intersecting polygons in imported files. Ensure 3D models are mathematically closed prior to import.