- Status Auf User warten
- Prozent erledigt
- Aufgabentyp Fehlerbericht
- Kategorie GUI & Server
- zuständig niemand
- Betriebssystem Windows 11
- Schweregrad mittel
- betrifft Version 3.3 RC x
- fällig in Version unbestimmt
-
fällig am
unbestimmt
- Stimmen
- versteckt
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.
Notes
Attached is a simple project to reproduce issue: https://1drv.ms/u/s!AoDVydc1qfn_nO4RQxh1Mx53xKGg8w?e=4PJRD5
Process:
* 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.
Please find attached project
I think i did something about this issue already. Can you double check whether this has been fixed in our latest RC3?
Dear @Soon5, I've just checked with the last 3.3.0 RC3 and it's the same behavior. Chaser does not restart from the first device. You will find attached a video, hope it helps.
https://youtu.be/abAoQ3t_mHI