Feature Requests & Fixture Response Issue – v0.1.31 (Windows)
Posted: Mon Feb 02, 2026 1:08 pm
Hi, good day,
I have a few workflow questions and feature requests regarding The Lighting Controller II, as well as one issue I’ve encountered:
1)Adding multiple generator buttons to a card
Is there a way to add multiple generator buttons to a card at once? Currently, adding buttons one by one requires repeatedly navigating back and forth, which can be time-consuming. The previous version of SweetLight allowed adding multiple buttons at once, which was much more efficient.
2)Direct RGB value entry / RGB faders
Is there a way to enter direct numeric values into the RGB color picker for RGB fixtures?
Alternatively, could an option be implemented to switch between the color picker and individual R, G, B faders, allowing for precise value entry and adjustment?
3)Multiple Child Windows
Is it possible to create and use multiple Child Windows simultaneously? If not, is this functionality planned?
4)Follow spot pan/tilt joystick mapping
Can the follow spot pan/tilt pad be mapped to a joystick or external controller axis?
5)Generic user-assignable faders
Would it be possible to implement a generic “Fader” option for fixture customization?
For example, if a fixture has a “Focus” channel, I would like to:
Add a generic fader labeled “Focus” in the fixture profile
Map that fader to a generic fader in the fader board
Use it to control the fixture’s focus channel directly
At the moment, only Dimmer and Speed faders appear to be supported.
6)Fixture response issue in version 0.1.31 (18 December 2025)
In version 0.1.31 (18 December 2025), fixtures appear correctly in the 3D window, but they do not respond to controls from the software. There is no visible movement or beam output when operating the fixtures.
I have tested this on two separate Windows computers, both exhibiting the same behavior. I have also verified that this is not related to my show file, as the issue persists when creating a new, independent light show in version 0.1.31 using fixtures directly from the fixture bank.
Thank you for your time, and I appreciate the continued development and improvement of SweetLight.
p.s: I’ve also noticed similar reports from at least one other user on the forum describing the same behavior in version 0.1.31, including lack of beam rendering and pan/tilt movement in the 3D View, even when testing with default lightshows.
I have a few workflow questions and feature requests regarding The Lighting Controller II, as well as one issue I’ve encountered:
1)Adding multiple generator buttons to a card
Is there a way to add multiple generator buttons to a card at once? Currently, adding buttons one by one requires repeatedly navigating back and forth, which can be time-consuming. The previous version of SweetLight allowed adding multiple buttons at once, which was much more efficient.
2)Direct RGB value entry / RGB faders
Is there a way to enter direct numeric values into the RGB color picker for RGB fixtures?
Alternatively, could an option be implemented to switch between the color picker and individual R, G, B faders, allowing for precise value entry and adjustment?
3)Multiple Child Windows
Is it possible to create and use multiple Child Windows simultaneously? If not, is this functionality planned?
4)Follow spot pan/tilt joystick mapping
Can the follow spot pan/tilt pad be mapped to a joystick or external controller axis?
5)Generic user-assignable faders
Would it be possible to implement a generic “Fader” option for fixture customization?
For example, if a fixture has a “Focus” channel, I would like to:
Add a generic fader labeled “Focus” in the fixture profile
Map that fader to a generic fader in the fader board
Use it to control the fixture’s focus channel directly
At the moment, only Dimmer and Speed faders appear to be supported.
6)Fixture response issue in version 0.1.31 (18 December 2025)
In version 0.1.31 (18 December 2025), fixtures appear correctly in the 3D window, but they do not respond to controls from the software. There is no visible movement or beam output when operating the fixtures.
I have tested this on two separate Windows computers, both exhibiting the same behavior. I have also verified that this is not related to my show file, as the issue persists when creating a new, independent light show in version 0.1.31 using fixtures directly from the fixture bank.
Thank you for your time, and I appreciate the continued development and improvement of SweetLight.
p.s: I’ve also noticed similar reports from at least one other user on the forum describing the same behavior in version 0.1.31, including lack of beam rendering and pan/tilt movement in the 3D View, even when testing with default lightshows.