Getting the Beam Look

The 3D Beam Viewer page lists every control. This one is the working guide: what to reach for when you want a particular look, and what to change when the preview does not read the way you expect.

It is worth knowing up front that the beam modes are a ladder, not a menu of styles. Each step is a closer approximation of a real laser than the one before it, and they trade cost for realism in that order. Picking the "best" one is not always right — the plainest modes are often the most useful, for reasons below.

The Ladder at a Glance

The useful rule: for inspecting stored geometry and planned coverage, work in the plainer modes. For presentation, move up the ladder. Every mode is a visualization; none measures the physical projector, atmosphere, venue, or exposure.

The Three Controls That Decide the Look

Almost every "how do I get that look" question comes down to three controls in the Scene panel.

Beyond those, Width (HD and Translucent) sets beam thickness, and Haze density drives the light cone in Haze mode.

Using the Bloom Slider

Bloom adds glow around bright parts of the beam. It is the control most often turned up too far, and the failure is easy to recognise once you have seen it.

Read that left to right. At the bottom of the range the beam path is exact and unembellished. A little glow makes the emission point read as a light source. Too much and the glow swallows the very thing you were looking at — by the last tile the scan point has become a blob and the path through it is gone.

Guidance:

• Glow should never be what draws the beam. If turning Bloom down makes you lose track of where the beam goes, the beam itself is too dim — fix that with Width or the mode, not with more glow.
• Bloom is per mode. Each mode remembers its own setting, because what is emitting differs enormously between them. Galvo shows a bright travelling point, so start with less bloom than you would use for Haze or Cinema.
• For planning views, turn it down or off. Glow inflates how wide a beam appears, which makes the simulated path harder to inspect. See Laser Clearance Reference for the limits of software planning.
• Galvo is the mode where this slider matters most. In several of the plainer modes you will find that moving it makes very little visible difference — that is expected, not a fault.

Beam Color Comes From Your File

Beams are drawn in the color stored by the content. There is no separate beam color control; the viewer uses the file color in its simulation.

All three tiles are the same file in the same mode, at three different frames. If your beams are not the color you expect, the color is in the file, not the viewer. Load it in the 2D view and step through frames to confirm what is actually stored.

Why Complex Artwork Looks Solid

This is the most common "the 3D view looks wrong" report, and it is usually the content rather than the viewer.

Every visible point in an ILDA frame contributes to the simulated path. A simple ring produces paths you can count. Densely filled artwork puts many paths close together, so the preview can merge them into a solid shape. Physical output can also appear dense, but its appearance depends on the projector, atmosphere, distance, and camera or observer.

If you need to see through it:

1. Switch to Translucent, which is built for exactly this.
2. Turn Bloom down — glow makes overlapping beams merge sooner.
3. Reduce Width so each beam occupies less space.
4. Move to Iso View or Side View; a head-on camera stacks every beam on top of every other one.
5. Consider whether the content itself is too dense — see the Optimization Guide.

Look Recipes

Troubleshooting

The beams are a solid mass and I cannot see individual paths

Cause: Dense content. The preview merges nearby paths; physical output can also appear dense depending on the projector, atmosphere, and viewing conditions.

Fix: Translucent mode, lower Bloom, narrower Width, an angled camera. See Why Complex Artwork Looks Solid.

Everything is washed out and too bright

Cause: Bloom too high for the mode.

Fix: Turn Bloom down until the beam path is crisp again. If the beams then look too faint, raise Width instead of putting the glow back.

The beams are white when my content is colored

Cause: Almost always the frame you are parked on. Many files contain white sections.

Fix: Step through frames in the 2D view to confirm what the file stores at that point.

The pattern sits low in the frame or is half behind the floor

Cause: Screen Height at its default, seen from an angled camera.

Fix: Raise Scr.Ht from its 1.5m default to around 2–2.5m.

I turned on the waveform or an analysis overlay and cannot see it

Cause: The overlays draw onto the screen surface. When the screen sits low, the trace can end up level with or below the venue floor.

Fix: Raise Scr.Ht, or orbit below floor level. The overlays also need Screen ON in Cinema mode — there is nothing to draw them onto otherwise.

Cinema mode is slow or stutters

Cause: Volumetric rendering is the most demanding mode in the product.

Fix: In Cinema's advanced section, lower Res and Steps first — they cost the most. Leave Denoise on; it buys back quality at lower step counts. For scrubbing and editing, drop to Basic and switch back to Cinema for the final look.

The 3D view will not start at all

Cause: Hardware acceleration unavailable or a driver problem.

Fix: See Troubleshooting. The 2D viewer stays available regardless.

Understanding Test Patterns Before Hardware Calibration

The viewer ships a TEST SUITE in the left panel. These reference files help you inspect stored geometry and understand what qualified technicians evaluate on hardware. BeamTracer does not tune, measure, or certify a projector.

BeamTracer previews and exports these files. Hardware adjustment requires the projector or scanner manufacturer's instructions and the official test-pattern procedure.

What "30K" Actually Means

This is the single most useful thing the test pattern teaches, and it is widely misunderstood.

A projector advertised at a given kpps is stating a coordinate-update rate. The useful scanner test condition includes the pattern, point rate, and optical scan angle together. Results at one condition do not predict every frame or angle.

Treat a plain kpps number as incomplete until you know the associated test pattern and angle.

Reading the Pattern

The relationships below help you read a test result. Scanner tuning can damage hardware if performed incorrectly; ILDA says it should be done by a knowledgeable person. Follow the official sequence and the manufacturer's instructions rather than adjusting a projector from this summary alone.

The pattern also carries a blanking section — horizontal lines crossing a small vertical mark, and a row of dots along the bottom. A qualified technician uses those features to evaluate color timing and blanking behavior under the official procedure. In BeamTracer, they remain stored reference geometry.

Choosing a Hardware Test Condition

Do not search for a scanner limit by increasing rate until the image fails. ILDA warns that scanners can be damaged by careless adjustment and that oscillation should never be allowed. Use the rate and angle specified by the manufacturer, then follow the official test procedure with qualified personnel.

The viewer exposes playback speed as FPS. Required points per second is the total records in the frame, including blanked records, multiplied by FPS, so stepping FPS up (>) raises the calculated demand. This is file arithmetic and preview cadence; it is not a physical scanner test. A Device Profile stores the comparison rate you choose for BeamTracer's analysis.

What the Test Pattern Cannot Tell You

The pattern characterizes scanner response at one operating point — one rate and one angle. It is not a full description of the projector. Testing another condition requires the manufacturer's limits and the official procedure.

It also cannot separate every content issue from every hardware response. Dense frames and long coordinate jumps can contribute to rounded corners or flicker. Review that side with the Optimization Guide and the Stress Heat Map.

Further Reading