Bugtracker DMXControl 3

  • Status Neu
  • Percent Complete
  • Task Type Fehlerbericht
  • Category GUI & Server
  • Assigned To No-one
  • Operating System Windows 11
  • Severity Medium
  • Reported Version 3.3 RC x
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: DMXControl 3
Opened by Anonymous Submitter - 12.02.2024

FS#5258 - Chaser filter restart with previous state

Error Description

The issue I’m dealing with is only with the 3.3.RC 1, with the official one, 3.2.3, no problem.

Issue is related to “chaser restart”: when a chaser is stopped in a cue, if I restart it (Play the cuelist) during a very short amount of time, the last fixture used by the previous run is set on.

Expected behavior

Expected behavior is the same as 3.2.3, the chaser should start at the first step.


Attached is a simple project to reproduce issue: https://1drv.ms/u/s!AoDVydc1qfn_nO4RQxh1Mx53xKGg8w?e=4PJRD5

* add some generic fixture with dimmer only,
* create a group for those fixtures,
* assign a chaser to the dimmer property of the group device: fixtures light on from the first to the last,
* create a cue from this state,
* clear programmer,
* set the fade of the created to 0,
* set the release time of the cuelist to 0,
* when pressing the GO button, chaser starts from the first fixture,
* press STOP when another fixture than the first is on, for example, the third,
* press GO: for a short time, the third fixture is on (and it’s visible too with the Channel Overview) and immediatly it goes to the first one. With the 3.2.3, no issue, the chaser starts with the first one.

Mikol commented on 12.02.2024 13:31

Please find attached project


Available keyboard shortcuts


Task Details

Task Editing