Skip to content
Nexus Workshop Nexus Prop Controller Guides

Lighting Page

Lighting controls addressable pixels and DMX. Configure physical lighting targets first, then create reusable effects and trigger them from Behavior.

UI path

  1. Open Configuration.
  2. Select Lighting.
  3. Configure physical pixel strips or DMX fixtures first.
  4. Create groups, palettes, effects, scenes, or sequences.
  5. Use preview/live controls to test.
  6. Save lighting changes.
  7. Trigger lighting from Behavior or Operator Controls.

Lighting sections

SectionWhat it configures
Pixel stripsPhysical addressable LED outputs from the controller I/O configuration
Pixel groupsNamed ranges or collections of pixels used as targets
Group layoutSpatial arrangement for effects that need position information
PalettesReusable named colors and color sets
Pixel effectsReusable animation/effect presets
Lighting sequencesTimed lighting steps for show moments
DMX profilesFixture channel definitions
DMX fixturesPatched fixtures with start addresses
DMX groupsNamed fixture/channel groups
DMX scenesSaved DMX values for playback
DMX live outputCurrent channel output preview and diagnostics

Build order

  1. Add pixel outputs or DMX hardware in Configuration > Connections > Inputs, Outputs, and Modules.
  2. Apply I/O Changes.
  3. Open Lighting.
  4. Create groups or patch fixtures.
  5. Create palettes and effects.
  6. Preview the effect or scene.
  7. Add a Behavior action or Operator Control that triggers it.

Trigger lighting from Behavior

  1. Go to Configuration > Behavior.
  2. Add an Operator Control for testing.
  3. Select the lighting action.
  4. Choose the target group, effect, scene, or sequence.
  5. Save and test on the Operator page.
  6. Reuse the same action in rules, triggers, or output sequences.

DMX workflow

  1. Create or select a fixture profile.
  2. Add a fixture and set its DMX start address.
  3. Group fixtures if they should be controlled together.
  4. Build scenes or live values.
  5. Watch DMX live output to confirm channel values.
  6. Trigger scenes from Behavior.

Keep channel addresses documented. Most DMX problems are patch or start-address mismatches.