Creating Custom Luminaire 3D Models (ULD) for DIALux evo
Build custom 3D luminaire models for DIALux evo. Integrate step files with IES photometry to create fully textured, highly accurate ULD files for premium renders
DIALux evo represents the pinnacle of photometric simulation for European and global lighting designers. While standard IES and LDT files define the photometric distribution of a luminaire, they lack the geometric and visual fidelity required for high-end client renderings. To bridge this gap, designers and manufacturers utilize the ULD (Unified Luminaire Data) format. ULD files encapsulate not only the luminous intensity distribution but also complex 3D geometry, material properties, and precise mounting mechanisms, transforming a simple photometric point source into a physically accurate representation within the simulation environment.
The process of creating a custom ULD file demands a rigorous integration of mechanical engineering data and photometric testing results. The starting point is typically a high-resolution STEP or IGES file exported from mechanical CAD software. This geometry must be carefully simplified and mapped to ensure optimal rendering performance without overwhelming the DIALux evo ray-tracing engine. Once the 3D model is prepared, it is fused with absolute photometry data, aligning the physical light emitting surface (LES) with the mathematical origin of the IES or LDT file.
This technical deep-dive outlines the end-to-end workflow for constructing custom luminaire 3D models (ULD) for DIALux evo. The procedure covers the ingestion of standard CAD formats, the specification of material reflectances, the precise alignment of photometric webs, and the final compilation into a proprietary ULD package. Following these strict protocols ensures that custom luminaires calculate accurately against established standards while delivering unparalleled visual realism in professional lighting documentation.
Core Concept Definitions
Understanding the foundational elements of a ULD file is essential before attempting to construct one. A Unified Luminaire Data file is essentially a container. Unlike a basic IES file which only contains arrays of candela values mapped to specific vertical and horizontal angles, a ULD file packages multiple distinct data streams into a single, proprietary format recognized exclusively by DIALux software.
The first critical component is the Photometric Web. This is the mathematical description of how light leaves the fixture, identical in function to an IES or LDT file. The photometric web dictates the calculation engine’s fundamental photon distribution. The second component is the Geometric Mesh. This is the 3D representation of the luminaire’s physical housing, usually derived from a STEP file. The mesh determines how the fixture interacts with ambient light, how it casts physical shadows, and how it appears in high-resolution ray-traced renderings.
The third component is the Light Emitting Surface (LES). This is a distinct, logical boundary defined within the software that explicitly links the mathematical photometric web to specific polygons on the geometric mesh. The LES tells the calculation engine exactly from where the photons defined in the photometric web should originate. The final component involves Material Definitions. These are the reflectance, transmittance, and specular properties assigned to the geometric mesh, ensuring that the physical housing reacts accurately to both its own emitted light and the light from surrounding fixtures within the simulated environment.
Technical Deep-Dive Subsections
Geometric Simplification and Material Mapping
The initial mechanical CAD model, typically a STEP file, often contains excessive detail intended for manufacturing, such as internal wiring, screws, and micro-extrusions. Before integration into a ULD, this geometry must be significantly reduced. High polygon counts exponentially increase calculation times and can crash the DIALux evo rendering engine during complex scenes. The goal is to retain the macroscopic external dimensions and distinct optical features while eliminating internal components that do not contribute to the luminaire’s physical interaction with the environment. Advanced decimation algorithms within 3D modeling software are often employed to achieve the target polygon count while preserving critical edges and optical apertures.
It is imperative to understand that the DIALux evo calculation engine treats every polygon as a potential surface for inter-reflection calculations. An overly complex mesh forces the radiosity engine to compute millions of unnecessary ray intersections. Therefore, external heat sinks should be simplified to continuous geometric blocks where possible, and internal optical chambers that are invisible from the exterior should be completely removed from the mesh.
Once the geometry is simplified, material properties must be assigned to the various surfaces of the luminaire housing. DIALux evo utilizes these material definitions to calculate secondary reflections off the fixture itself. Accurate diffuse and specular reflectances must be applied to the housing, reflectors, and diffusers. Metallic surfaces require precise specification of specular highlights to ensure accurate representation in ray-traced renders, while diffusers must be modeled with correct transmittance values to simulate the luminous surface accurately.
When defining housing materials, designers must explicitly set the diffuse reflectance (rho) to match the physical powder coat or anodized finish. For example, a standard matte white housing typically requires a reflectance definition of approximately 80-85%. Specifying incorrect reflectances on the luminaire body will artificially skew the calculated inter-reflections within tight architectural coves or when luminaires are mounted closely together in continuous runs. Furthermore, clear optical covers or lenses must be assigned a transmission factor and a refractive index to ensure that light rays originating from the internal LES pass through the geometry correctly without being mathematically absorbed by the mesh.
Photometric Alignment and Light Emitting Surfaces
The critical phase of ULD creation is the alignment of the mathematical photometric web (the IES or LDT data) with the physical 3D model. The optical origin defined during goniophotometer testing must map perfectly to the Light Emitting Surface (LES) defined in the 3D geometry.
In standard photometry, the geometric center of the luminous opening is defined as coordinate (0,0,0). When mapping the IES data to the ULD model, the 3D geometry must be translated so that its physical LES perfectly aligns with this theoretical origin. Misalignment by even a few millimeters can result in inaccurate calculation of near-field illuminance and incorrect shadow casting in tight architectural details. This process requires a thorough understanding of the specific coordinate system utilized by the goniophotometer during testing. The C0-C180 and C90-C270 planes defined in the photometric file must be mapped directly to the longitudinal and transverse axes of the physical 3D model.
If the photometric web is rotated incorrectly relative to the geometry, the luminaire will distribute light in the wrong direction during simulation, leading to catastrophic design errors in asymmetric applications such as wall-washing or street lighting. The alignment must be verified by visually overlapping the 3D polar luminous intensity distribution curve with the geometric mesh within the ULD creation software, ensuring that the maximum candela vectors point in the physically logical direction relative to the housing.
DIALux evo requires the explicit definition of the luminous surface geometry. This tells the calculation engine exactly which polygons on the 3D model are emitting the photons defined by the IES file. The luminous surface can be defined as a point, line, rectangle, circle, or complex polygon, depending on the physical nature of the luminaire (e.g., a linear LED extrusion versus a circular downlight). This definition is distinct from the physical geometry and is strictly used for calculating the origin point of the emitted rays during simulation.
The selection of the LES shape is mathematically significant. If a 1200mm linear fixture is incorrectly defined with a ‘point’ LES at its center, the calculation engine will originate all rays from that single point. This creates artificially harsh shadows and incorrect illuminance gradients near the fixture. By defining a 1200mm ‘line’ or ‘rectangle’ LES, the engine distributes the initial ray generation across the entire specified area, accurately simulating the soft-edge shadows and uniform near-field distribution characteristic of linear fluorescent or continuous LED profiles.
Advanced Photometric Interpolation and Spectral Data
When compiling ULD files from raw photometric data, specifically data originating from legacy integrating spheres or older goniophotometers, lighting designers often encounter issues with data resolution. The ANSI/IES LM-63-19 standard permits varying degrees of angular resolution in the candela distribution arrays. For example, a wide-distribution high-bay luminaire might only be measured in 5-degree vertical increments, while a highly collimated spot optic requires 0.5-degree increments to accurately capture the peak intensity and beam spread. When integrating low-resolution IES files into high-fidelity ULD models, the DIALux evo calculation engine must interpolate the missing data points between the measured angles.
During the ULD creation process, it is critical to evaluate the resolution of the raw photometric web. If a sharp cut-off optic is defined by low-resolution data, the resulting interpolation within DIALux evo can create artificial banding or ‘stepping’ artifacts in the simulated light distribution on adjacent surfaces. To mitigate this, advanced ULD authoring tools utilize cubic spline interpolation algorithms to smooth the candela distribution curve before finalizing the proprietary file format. This mathematical smoothing ensures that the simulated illuminance gradients on walls and floors appear continuous and natural, accurately reflecting the physical performance of high-quality optics.
Historically, photometric files have been inherently monochromatic. An IES file defines the spatial distribution of luminous flux but provides absolutely no data regarding the spectral composition of that light. The integration of colorimetry is a defining feature of advanced ULD models. Modern ULD authoring workflows now incorporate full Spectral Power Distribution (SPD) data alongside the standard spatial photometry. This integration enables DIALux evo to perform highly accurate color rendering calculations and visualize complex color mixing scenarios.
The integration of SPD data requires meticulous mapping. The spectral data, typically recorded in 1-nanometer increments from 380nm to 780nm during the goniophotometer or integrating sphere testing, is mathematically associated with the Light Emitting Surface of the ULD model. When the software calculates the inter-reflection of light within a simulated room, it no longer merely tracks the attenuation of luminous flux; it tracks the interaction of specific wavelengths with the spectral reflectance properties of the architectural surfaces. This allows for the precise calculation of metrics such as IES TM-30-20 Fidelity (Rf) and Gamut (Rg) indices directly within the 3D environment.
ULD Creation Specifications Table
| Parameter | Specification Target | Tolerance | Description |
|---|---|---|---|
| Mesh Polygon Count | < 5,000 polygons | +10% | Maximum complexity for optimal calculation speed. |
| Optical Alignment | (0,0,0) exactly | +/- 1mm | Alignment of physical LES to photometric origin. |
| Diffuse Reflectance | 80-85% (White) | +/- 2% | Material definition for standard white housings. |
| File Size | < 2.0 MB | Max 5.0 MB | Final compiled size of the proprietary .uld file. |
| Luminous Flux | Absolute | 0% | Photometric output must match lab data perfectly. |
Real-World Application Examples
Consider a specialized lighting manufacturer developing a custom, highly asymmetric linear LED extrusion designed specifically for architectural cove lighting. The fixture features a complex, sweeping aluminum heatsink profile and a micro-prism lens. The manufacturer provides a high-resolution STEP file representing the physical extrusion, which contains 45,000 polygons per meter, including detailed screw threads and internal driver mounting tracks. They also provide an IES file generated from absolute photometry testing, indicating an output of 2,400 lumens per meter with a peak candela value occurring at 15 degrees off-nadir.
To create a functional ULD file, the lighting design team first processes the STEP file. They utilize decimation algorithms to strip the internal driver tracks and screw threads, reducing the polygon count to 2,500 polygons per meter, maintaining only the external sweeping profile and the flat plane representing the lens. They assign an anodized aluminum material definition to the housing (specular reflectance 15%, diffuse reflectance 65%) and a transmissive definition to the lens plane. Next, they define the Light Emitting Surface (LES) as a continuous rectangle matching the dimensions of the lens. Crucially, they import the IES file and carefully align the C0 plane with the longitudinal axis of the extrusion, ensuring that the 15-degree asymmetric throw is physically directed outward from the cove edge, rather than back into the wall. The final compiled ULD file allows the architectural team to render the cove with precise inter-reflections and accurate shadow casting along the ceiling plane, an effect impossible to achieve with a raw IES file.
Another complex application involves luminaires with motorized or manually adjustable physical optics—such as track heads with variable beam spreads (e.g., adjustable from 15 degrees to 45 degrees via a zoom lens). These present extreme complexities for ULD compilation. A single static photometric web is insufficient. The ULD must encompass an array of IES data files, each representing the absolute photometry at specific detent positions of the zoom mechanism. The authoring process defines a parametric relationship between the physical adjustment parameter and the active photometric file.
When a lighting designer configures the luminaire in the simulation software, adjusting the beam angle parameter dynamically swaps the underlying calculation matrix and simultaneously alters the 3D representation of the lens position within the geometric mesh. This synchronization between mechanical geometry and photometric calculation ensures absolute fidelity in the simulated environment. The mathematical linking of these states requires complex logic definitions embedded within the proprietary ULD structure, demanding a high level of expertise in both mechanical engineering data structures and advanced photometric calculation theory.
Common Mistakes and Troubleshooting
A frequent error in ULD creation is the misinterpretation of absolute versus relative photometry. If an LDT file utilizing relative photometry (lumens per kilolumen) is integrated into a ULD without specifying the exact lamp lumen output and input wattage, DIALux evo will calculate incorrect absolute illuminance levels. The ULD metadata must clearly explicitly define the luminaire’s absolute flux and connected load. Designers must carefully verify the header data of the raw photometric file before integration to confirm the multiplier required for absolute calculations.
Another common issue arises from inverted surface normals on the 3D geometry. If the polygons representing the luminaire housing have their normals facing inward, the calculation engine will treat the luminaire as invisible to light rays, resulting in absent shadows and incorrect inter-reflections within the simulated room cavity. This issue is typically resolved during the geometric simplification phase by running a “recalculate normals” function within the 3D modeling software before exporting the final mesh for ULD integration.
Furthermore, failing to accurately define the physical dimensions of the Light Emitting Surface leads to glaring calculation errors. If the luminous opening of a 2x4 troffer is incorrectly defined as a 1x1 point source in the ULD parameters, the DIALux evo calculation engine will generate severe hot spots directly beneath the fixture and artificially low illuminance values between fixtures. The geometric definition of the LES must correspond exactly to the physical dimensions of the luminaire’s diffuser or louver assembly.
During compilation, the authoring software generates a cryptographic hash of the internal geometric meshes, material definitions, and photometric arrays. This hash is embedded within the ULD file structure alongside the manufacturer’s digital certificate. When the file is imported into DIALux evo, the software recalculates the hash and verifies it against the embedded signature. If a user attempts to manually edit the internal photometric web or alter the input wattage metrics to artificially bypass energy code restrictions, the cryptographic signature will break. When a broken signature is detected, the simulation software will typically flag the luminaire with a severe warning, and often refuse to utilize the file in calculations required for code compliance documentation.