Troubleshooting (General Information) DMXC3 - Revision history

Skistner at 14:36, 11 November 2025

2025-11-11T14:36:30Z

← Older revision		Revision as of 16:36, 11 November 2025
Line 1:		Line 1:
	{{Manual Header		{{Manual Header
	\| Type = DMXC3 Main-Software		\| Type = DMXC3 Main-Software
	\| Version = 3.3.0}}		\| Version = 3.3.1}}

	Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them.		Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them.
Line 9:		Line 9:
	{{Manual Box \| en \| Hint \| Some of the issues mentioned below are known and will be addressed in a future version.		{{Manual Box \| en \| Hint \| Some of the issues mentioned below are known and will be addressed in a future version.
	''An overview of these points can be found under {{Manual Windowcaption\|[[Known Bugs (General Information) DMXC3\|Known Bugs]]}}''.}}		''An overview of these points can be found under {{Manual Windowcaption\|[[Known Bugs (General Information) DMXC3\|Known Bugs]]}}''.}}

			= Installation and (first) start =
			== Umbra and / or kernel do not start ==
			''' Problem '''
			If you start the kernel and / or Umbra via the launcher or via the direct shortcuts in the start menu, the console window disappears again after a short moment. The corresponding application is then no longer listed in the Task Manager, and the launcher does not report “Active” or “Active (hidden)” under the respective program section.

			''' Solution '''
			All four packages must be installed on the PC. Usually, the installer takes care of this. In some situations, however, the automatic installation may not be possible, or the installer may not recognize the installed packages correctly. A typical case is when there was no active Internet connection available during installation. If Kernel and / or Umbra do not start, you must manually install the four packages listed below.

			* .NET 6 Desktop Runtime (32bit): '''https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x86.exe'''
			* .NET 6 Desktop Runtime (64bit): '''https://aka.ms/dotnet/6.0/windowsdesktop-runtime-win-x64.exe'''
			* ASP.NET Core 6 (32bit): '''https://aka.ms/dotnet/6.0/aspnetcore-runtime-win-x86.exe'''
			* ASP.NET Core 6 (64bit): '''https://aka.ms/dotnet/6.0/aspnetcore-runtime-win-x64.exe'''

			After installation, it is recommended to restart the PC. The installer for DMXControl 3 does not need to be run again after installing the packages. The program data required for DMXControl 3 is then already available.

	= Working "within" DMXControl 3 =		= Working "within" DMXControl 3 =
	== Devices ~~Stay Dark~~ ==		== Devices stay dark ==
	'''Problem'''		'''Problem'''
	In the {{Manual Windowcaption\|[[Stage View DMXC3\|Stage View]]}}, multiple {{Manual Windowcaption\|[[Device DMXC3\|Devices]]}} or even {{Manual Windowcaption\|[[Device Group DMXC3\|Device Groups]]}} are selected, and their functions are shown in the {{Manual Windowcaption\|[[Device Control DMXC3\|Device Control]]}} or the {{Manual Windowcaption\|[[Control Panel DMXC3\|Control Panel]]}}. Regardless of how the devices are controlled in the project, whether through device control or various control windows, they remain dark in three places. This means there is no response:		In the {{Manual Windowcaption\|[[Stage View DMXC3\|Stage View]]}}, multiple {{Manual Windowcaption\|[[Device DMXC3\|Devices]]}} or even {{Manual Windowcaption\|[[Device Group DMXC3\|Device Groups]]}} are selected, and their functions are shown in the {{Manual Windowcaption\|[[Device Control DMXC3\|Device Control]]}} or the {{Manual Windowcaption\|[[Control Panel DMXC3\|Control Panel]]}}. Regardless of how the devices are controlled in the project, whether through device control or various control windows, they remain dark in three places. This means there is no response:
Line 41:		Line 56:
	If these four steps do not resolve the issue, a restart (if possible) might help as it also resets everything to 0. After loading the project, check if the {{Manual Windowcaption\|Group Master}} slider is set to a very low brightness value.		If these four steps do not resolve the issue, a restart (if possible) might help as it also resets everything to 0. After loading the project, check if the {{Manual Windowcaption\|Group Master}} slider is set to a very low brightness value.

	== Cuelist ~~Won~~'t ~~Start~~ ==		== Cuelist won't start ==
	'''Problem'''		'''Problem'''
	A properly programmed {{Manual Windowcaption\|[[Cuelist DMXC3\|Cuelist]]}} doesn't start, despite multiple presses of the {{Manual Buttons\|Go}} button or pressing a linked button in the {{Manual Windowcaption\|[[Softdesk DMXC3\|Softdesk]]}}.		A properly programmed {{Manual Windowcaption\|[[Cuelist DMXC3\|Cuelist]]}} doesn't start, despite multiple presses of the {{Manual Buttons\|Go}} button or pressing a linked button in the {{Manual Windowcaption\|[[Softdesk DMXC3\|Softdesk]]}}.
Line 51:		Line 66:
	Open the affected {{Manual Windowcaption\|Cuelist(s)}} from the {{Manual Windowcaption\|[[Project Explorer DMXC3\|Project Explorer]]}} and set the fade factor (Fade factor / Timing) slider back to a value greater than 0. If the {{Manual Windowcaption\|Cuelists}} are triggered via a {{Manual Windowcaption\|Softdesk}}, a MIDI controller, or similar devices, you can also add a slider in the {{Manual Windowcaption\|[[Input Assignment DMXC3\|Input Assignment]]}} to centrally control the fade factor.		Open the affected {{Manual Windowcaption\|Cuelist(s)}} from the {{Manual Windowcaption\|[[Project Explorer DMXC3\|Project Explorer]]}} and set the fade factor (Fade factor / Timing) slider back to a value greater than 0. If the {{Manual Windowcaption\|Cuelists}} are triggered via a {{Manual Windowcaption\|Softdesk}}, a MIDI controller, or similar devices, you can also add a slider in the {{Manual Windowcaption\|[[Input Assignment DMXC3\|Input Assignment]]}} to centrally control the fade factor.

	== Last Softdesk ~~Changes Disappear~~ ==		== Last Softdesk changes disappear ==
	'''Problem'''		'''Problem'''
	The custom design of a {{Manual Windowcaption\|[[Softdesk DMXC3\|Softdesk]]}} is not saved, or the last changes disappear when the project is reloaded.		The custom design of a {{Manual Windowcaption\|[[Softdesk DMXC3\|Softdesk]]}} is not saved, or the last changes disappear when the project is reloaded.
Line 61:		Line 76:
	To ensure all changes to the {{Manual Windowcaption\|Softdesk}} are properly saved, always close the {{Manual Windowcaption\|Softdesk Designer}} before saving the project. For "pure" live operation with the {{Manual Windowcaption\|Softdesk}}, it is recommended to open the Softdesk only in display mode. This also ensures that menu elements for selecting and adjusting the controls are completely hidden, preventing accidental changes.		To ensure all changes to the {{Manual Windowcaption\|Softdesk}} are properly saved, always close the {{Manual Windowcaption\|Softdesk Designer}} before saving the project. For "pure" live operation with the {{Manual Windowcaption\|Softdesk}}, it is recommended to open the Softdesk only in display mode. This also ensures that menu elements for selecting and adjusting the controls are completely hidden, preventing accidental changes.

	== Various ~~Windows Not Displayed~~ ==		== Various windows not displayed ==
	'''Problem'''		'''Problem'''
	You receive a project from another user or switch PCs while working on the project. On the new PC, not all windows can be opened because the monitor size and resolution appear to differ.		You receive a project from another user or switch PCs while working on the project. On the new PC, not all windows can be opened because the monitor size and resolution appear to differ.
Line 76:		Line 91:

	= DMX Output =		= DMX Output =
	== Art-Net ~~Output Not Working~~ ==		== Art-Net output not working ==
	'''Problem'''		'''Problem'''
	The Art-Net output cannot be activated. The corresponding rows in the {{Manual Windowcaption\|[[DMX-Interfaces DMXC3\|DMX Interfaces]]}} table remain grayed out even though the checkboxes for "Interface enabled" and "DMX-Out enabled" are checked.		The Art-Net output cannot be activated. The corresponding rows in the {{Manual Windowcaption\|[[DMX-Interfaces DMXC3\|DMX Interfaces]]}} table remain grayed out even though the checkboxes for "Interface enabled" and "DMX-Out enabled" are checked.
Line 90:		Line 105:
	[[Category: Manual DMXControl 3]]		[[Category: Manual DMXControl 3]]

	[[de: ~~Troubleshooting_~~(~~General_Information~~)~~_DMXC3~~]]		[[de: Troubleshooting (General Information) DMXC3]]

Jkuehn: Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them. {{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be appreciated if these cou..."

2025-03-04T20:01:23Z

Created page with "{{Manual Header | Type = DMXC3 Main-Software | Version = 3.3.0}} Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them. {{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be appreciated if these cou..."

New page

{{Manual Header
| Type = DMXC3 Main-Software
| Version = 3.3.0}}

Some issues that occur when using DMXControl 3 can be systematically resolved by the user at the end—especially when the software doesn't behave as expected, as it did previously. This article outlines the most frequently reported problems and describes how to troubleshoot them.

{{Manual Box | en | Important | If errors occur in the software or a function is missing, it would be appreciated if these could be reported as a new ticket in our '''{{DMXCWebLinks|FS|Project|3|Bugtracker}}'''.}}

{{Manual Box | en | Hint | Some of the issues mentioned below are known and will be addressed in a future version.
''An overview of these points can be found under {{Manual Windowcaption|[[Known Bugs (General Information) DMXC3|Known Bugs]]}}''.}}

= Working "within" DMXControl 3 =
== Devices Stay Dark ==
'''Problem'''
In the {{Manual Windowcaption|[[Stage View DMXC3|Stage View]]}}, multiple {{Manual Windowcaption|[[Device DMXC3|Devices]]}} or even {{Manual Windowcaption|[[Device Group DMXC3|Device Groups]]}} are selected, and their functions are shown in the {{Manual Windowcaption|[[Device Control DMXC3|Device Control]]}} or the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}}. Regardless of how the devices are controlled in the project, whether through device control or various control windows, they remain dark in three places. This means there is no response:
* in the {{Manual Windowcaption|Stage View}}.
* in the {{Manual Windowcaption|[[Channel Overview DMXC3|Channel Overview]]}}, where the DMX channels for dimmers and/or the color of the respective devices remain at 0.
* in reality, even though the {{Manual Windowcaption|[[DMX-Interfaces DMXC3|DMX Interfaces]]}} are activated and otherwise working properly.
The only time the devices respond is when manually controlled via the {{Manual Windowcaption|Channel Overview}}.

'''Cause'''
In DMXControl 3, there are several factors that can cause a device to remain "dark," and multiple of the mentioned issues may occur simultaneously:
* The {{Manual Windowcaption|[[Blackout DMXC3|Blackout]]}} function
* The {{Manual Windowcaption|[[Freeze DMXC3|Freeze]]}} function, once activated, prevents the device from turning on again.
* The devices have both a dimmer and a shutter, and the shutter has not yet been opened.
* The {{Manual Windowcaption|[[Group Master (Master) DMXC3|Group Master]]}}.
* The {{Manual Windowcaption|[[Grand Master (Master) DMXC3|Grand Master]]}}.
* Active {{Manual Windowcaption|[[Cuelist DMXC3|Cuelists]]}} with a higher priority than the {{Manual Windowcaption|[[Programmer DMXC3|Programmer]]}}.
* The {{Manual Windowcaption|[[Programmer DMXC3|Blind]]}} function in the {{Manual Windowcaption|Programmer}}, which ensures that the values set in the programmer are not output to the {{Manual Windowcaption|DMX Interfaces}} or the {{Manual Windowcaption|Stage View}}.
* Various modules, including the {{Manual Windowcaption|DMX Interfaces}}, are disabled via the {{Manual Windowcaption|[[Main Switch DMXC3|Main Switch]]}}.

'''Solution'''
This issue typically occurs when programming a new lighting scene and less often when the show is running. To reset everything to 0, follow these steps:
# Stop all {{Manual Windowcaption|Cuelists}} using the {{Manual Buttons|Stop all cuelists}} button.
# Reactivate the {{Manual Windowcaption|DMX Interfaces}} using the {{Manual Windowcaption|Main Switch}}.
# Clear the {{Manual Windowcaption|Programmer}} using the {{Manual Buttons|Clear}} button.
# Open the {{Manual Windowcaption|Programmer}} and disable the {{Manual Buttons|Blind}} option. The default setting is {{Manual Buttons|All}}.
# Check if the {{Manual Windowcaption|Blackout}} is disabled.
# In the window showing all {{Manual Windowcaption|[[Master DMXC3|Master]]}}, set both the {{Manual Windowcaption|Grand Master}} and the {{Manual Windowcaption|Group Master}} for the affected devices back to 100%. Be sure to observe the dependencies between group masters, as described in the relevant article.
# When trying a new lighting scene, both raise the dimmer and open the shutter if the devices have both functions. This can be done manually or by pressing the {{Manual Buttons|Lumos}} button in the {{Manual Windowcaption|[[Control Panel DMXC3|Control Panel]]}} for intensity.
If these four steps do not resolve the issue, a restart (if possible) might help as it also resets everything to 0. After loading the project, check if the {{Manual Windowcaption|Group Master}} slider is set to a very low brightness value.

== Cuelist Won't Start ==
'''Problem'''
A properly programmed {{Manual Windowcaption|[[Cuelist DMXC3|Cuelist]]}} doesn't start, despite multiple presses of the {{Manual Buttons|Go}} button or pressing a linked button in the {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}}.

'''Cause'''
For each {{Manual Windowcaption|Cuelist}}, the fade factor (Fade factor / Timing) can be individually set. Due to various external influences—whether intentional or unintentional—the value of the associated slider has been set to 0.

'''Solution'''
Open the affected {{Manual Windowcaption|Cuelist(s)}} from the {{Manual Windowcaption|[[Project Explorer DMXC3|Project Explorer]]}} and set the fade factor (Fade factor / Timing) slider back to a value greater than 0. If the {{Manual Windowcaption|Cuelists}} are triggered via a {{Manual Windowcaption|Softdesk}}, a MIDI controller, or similar devices, you can also add a slider in the {{Manual Windowcaption|[[Input Assignment DMXC3|Input Assignment]]}} to centrally control the fade factor.

== Last Softdesk Changes Disappear ==
'''Problem'''
The custom design of a {{Manual Windowcaption|[[Softdesk DMXC3|Softdesk]]}} is not saved, or the last changes disappear when the project is reloaded.

'''Cause'''
The command to save the last changes to the {{Manual Windowcaption|Softdesk}} is only transmitted when the {{Manual Windowcaption|[[Softdesk Designer DMXC3|Softdesk Designer]]}} is closed.

'''Solution'''
To ensure all changes to the {{Manual Windowcaption|Softdesk}} are properly saved, always close the {{Manual Windowcaption|Softdesk Designer}} before saving the project. For "pure" live operation with the {{Manual Windowcaption|Softdesk}}, it is recommended to open the Softdesk only in display mode. This also ensures that menu elements for selecting and adjusting the controls are completely hidden, preventing accidental changes.

== Various Windows Not Displayed ==
'''Problem'''
You receive a project from another user or switch PCs while working on the project. On the new PC, not all windows can be opened because the monitor size and resolution appear to differ.

'''Cause'''
In each project, it is precisely recorded where each window was last displayed on the screen. This is based on the available screen resolution. When loading a project and confirming that the stored window layout should be used, the last local settings are overwritten.
{{Picture_with_subtitle|DMXC3 Manual Panel Concept Loadig window layout.png|1|Layout prompt when opening a project|center}}

'''Solution'''
To bring lost windows back into the main screen display area, go to the following menu entry: {{Manual MenuText|Settings|Layout|Move floating windows to primary screen}} (see also Figure 2). This function moves all windows back into the main screen display area. Alternatively, you can load a custom window layout you've created. This can be done through the main menu {{Manual_MenuText|Settings|Layout|Load...}}. In the following example, two saved window layouts named Club-Setup and Programming-Setup are stored in the loaded project.
{{Picture_with_subtitle|DMXC3 Manual Panel-Konzept Window layouts.png|2|Reset window layout and load custom window layouts|center}}

If this function doesn't yield the desired result, you can reset the current window layout through the entry {{Manual MenuText|Settings|Layout|Reset window layout}}. The default arrangement will be loaded as seen after the first start of DMXControl 3. This is also covered in the article {{Manual Windowcaption|[[GUI DMXC3|User Interface]]}}.

= DMX Output =
== Art-Net Output Not Working ==
'''Problem'''
The Art-Net output cannot be activated. The corresponding rows in the {{Manual Windowcaption|[[DMX-Interfaces DMXC3|DMX Interfaces]]}} table remain grayed out even though the checkboxes for "Interface enabled" and "DMX-Out enabled" are checked.

'''Cause'''
The PC might be missing an updated version of the '''Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019'''.

'''Solution'''
Manually install the 32-bit version (x86 version) of the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019. After installation, DMXControl 3 needs to be restarted.

Download link: '''https://support.microsoft.com/de-de/help/2977003/the-latest-supported-visual-c-downloads'''

[[Category: Manual DMXControl 3]]

[[de: Troubleshooting_(General_Information)_DMXC3]]