Lighty Bulb 2

Getting Started With Lighty Bulb 2

Lighty Bulb 2 is a lighting design and simulation tool that most stage technicians and AV engineers use when they need to plan fixture placement, calculate beam spreads, and verify rigging loads before ever touching a truss. It replaced the original version because the older build couldn't handle modern LED pars without crashing every few minutes. The interface looks like a 3D modeling program that got married to a spreadsheet. You drag fixtures onto a floor plan, assign DMX addresses, set intensity curves, and then run a test render to see what the audience actually sees from different seating positions. I've been running Lighty Bulb 2 on tour for about three years now, across venues that range from 800-seat theaters to outdoor festivals where we set up in forty-five minutes between soundcheck and doors. The biggest headache people hit early on is the DMX addressing sequence. By default the software groups fixtures by type and assigns addresses in block order, which works fine until you try to patch two different manufacturers' fixtures into the same universe. I spent an entire load-in once trying to figure out why my wash cans were cross-responding to my strobes. The fix was going into the patch editor and manually assigning each fixture a static address instead of letting the auto-patch do its thing. Took about twelve minutes to readdress sixty channels. Worth it.

What Lighty Bulb 2 Actually Does

At its core the software models your venue as a 3D space and lets you place virtual fixtures at exact positions with accurate beam angles and color temperatures. You import venue measurements from CAD files, AutoCAD drawings, or you can draw the floor plan by hand if you don't have blueprints. Once the space is built you drop in fixtures from the library, which includes thousands of profiles from manufacturers like High End, Martin, Clay Paky, and ADJ. The beam spread calculation uses the actual photometric data from manufacturer IES files when available, so the output is closer to reality than most people expect. Not perfect, but close enough that you catch problems on paper instead of on site. The scheduling feature is where this tool actually earns its weight. You can program cue sequences, automate fades, and time them to a SMPTE clock if your production uses timecode. Export options include DMX .txt files, MA2 show files, and a proprietary format that some larger console manufacturers can import directly. If you're working with a Show Master or an MA onakkels system, the export path matters because going through the wrong one can corrupt your fader assignments. I learned that the hard way during a corporate event when I exported to the generic MIDI path instead of the dedicated MA export. Half the shows lost their intensity curves and I had to rebuild them live while the clients were walking in. Never happened again.

Installation and License Setup

You can download Lighty Bulb 2 from the official Sapiens AI website. The installer runs on Windows 10 and later, and there's a macOS version but it's lagging behind the Windows build by about six months in terms of features. The free trial gives you thirty days with full access, but the demo mode disables the export functions so you can't generate show files. If you just want to learn the interface and practice building shows, the trial is fine. If you need to deliver actual show files to a client, you'll want the paid license before the trial ends. Activation requires a Sapiens AI account and a hardware-locked dongle option if your shop already uses those. Standalone licenses tie to your machine and work offline, which matters when you're loading a show at a venue with terrible Wi-Fi. I've seen technicians try to activate on a phone hotspot in a parking garage and waste twenty minutes watching the spinner. Save yourself the trouble, activate at the office, and carry the offline license file on a USB stick just in case.

Building Your First Show

Open the software and start a new project. Set your venue dimensions first, then add your fixture library. Most people skip the dimension step and just draw a basic box, but if you get the measurements wrong the beam overlap calculations will be off and you'll end up with hot spots or dead zones that you didn't see in the sim. Measure twice, patch once. Then drag your fixtures onto the floor plan and connect them to a universe. Assign DMX addresses manually if you're mixing fixture types. Run a test render from the main audience position and look for areas that are over or under lit. Adjust fixture angles and intensities until it looks reasonable. Export the show file to your preferred format and load it onto the console. The built-in renderer isn't photorealistic, so don't expect it to look like a marketing video. It shows relative intensity and beam coverage using a grayscale heatmap overlay. Brighter areas mean more light output. That's all you need to spot problem areas. If you want more visual fidelity you can export to a ray-tracing plugin, but that's optional and most people don't bother because it takes much longer to render and the difference in decision-making quality is marginal.

Common Pitfalls and What to Watch For

One thing beginners miss is the faders on exported shows. Lighty Bulb 2 maps your virtual faders to physical console faders based on the channel count, but if your fixture has more than sixty-four channels the extra controls get pushed into sub-universe slots that not all consoles support. Check your console's sub-universe limits before you build a show that assumes they exist. Another issue is color temperature drift in the simulation. The software uses standard D65 white point for its renders, so if you're working with warm LED pars set to 2700K the visual output in the sim might look slightly cooler than reality. It's a small shift, maybe fifty Kelvins, but it adds up when you're trying to match existing house lights or fixtures from another vendor. The biggest limitation is that Lighty Bulb 2 doesn't model ambient light conditions very well. If your venue has windows, skylights, or strong stage rigging that casts shadows, the software won't account for them unless you manually add light sources to the scene. I worked a wedding once where the venue had massive stained glass windows and the afternoon sun was cutting through them. The simulation looked fine on paper. On site it was a disaster because the natural light washed out half the designed wash and created uneven color temperature across the dance floor. We ended up closing the drapes and adding a few fill fixtures that weren't in the original plan. Next time I just run the sim with the windows blocked out and add a safety margin of twenty percent on intensity. Works every time. There's no mobile companion app, which would be nice if you're on a venue walkthrough trying to verify fixture positions against the printed plan. You can export PDFs of your layouts, but they're static and don't link back to the project. If you need that kind of interoperability you're better off pairing it with a separate floor plan tool or just printing the show sheet and taping it to a clipboard. It's not elegant but it gets the job done.

Lighty Bulb 2 costs around two hundred ninety-nine dollars for a standalone license and four hundred ninety-nine for a network license that covers multiple workstations in a shop. If you're a freelancer doing occasional shows the standalone is fine. If you run a production company with five or more people who all need their own installation, the network license pays for itself in saved headaches. There's also an annual subscription option at one hundred eighty-nine dollars per year that includes updates and priority support, which some people prefer because it spreads the cost out and keeps you on the latest version without buying a new license every time a major update drops. Support is available through the Sapiens AI portal, and the forum community is decent but slow to respond on weekends. If you hit a critical issue right before a show, the best path is usually the email support ticket with screenshots and your project file attached. Response time averages six to eight hours during business days. Not instant, but usually fast enough to save you if the problem isn't a software crash. I recommend it for mid-size to large productions where planning accuracy matters. For small one-night gigs with simple setups, the free trial or even just a paper plot and a tape measure might be faster. Lighty Bulb 2 shines when you have complex multi-universe shows, moving heads, and tight timelines where catching errors before load-in saves hours of frustration on site.