New bug: Chase Lighting cue after a hotkey converts itself to Manual Cue after running

[berto2002]

Hi folks,

A new bug has shown-up.

Cue 63 is called Alarm Lights and it is configured to auto start 0 seconds after the named previous cue. It is a chase. That previous cue is a hotkey, Q25.

Attached is a picture of the editor with the config of that cue.

When running the show, the cue correctly states it is ready for Auto Start and, indeed, fires automatically when Q25 starts.

A few seconds later, when the next lighting cue begins, it does duly stop as instructed by the configuration but then it determines itself to be a Manual cue, the row shows black and, indeed it sits there as the NEXT manual cue.

Now, that's a big problem because when I want to fire the next real manual cue about 20 cues later, I find this one is 'in the way' and reacts first.

My workaround is to press the spacebar TWICE at that point: the first press manually starts that old Alarm lights cue (undesirable) but the next press, on the real manual cue is another lighting cue, so it stops the Alarm Lights and proceeds to do what I need; but for having a half second flash of the rogue cue. Fortunately the manual setting of the Alarm Lights does not take the whole show back!

There is nothing in that configuration that tells me this should be happening. It's thoroughly repeatable.

What workaround can I have for my show that is only two weeks away now?

Thanks in advance.

SCS Pro Plus 11.10.7c1 (x64)
Windows 11

[berto2002]

Right, I worked around this (and perhaps this helps highlight where the defect is) by adding a disable hotkey cue after the hotkey and then hanging the Alarm Lights off of that cue instead. Now, when the next lighting cue comes on, the Alarm Lights does not turn to the next manual cue.

So there is something wonky about the chase lighting cue following the hotkey directly which I recommend be explored. Can send logs if required.

PS the enable/disable cue works a treat. I have a big red button that triggers things and it's right in front of the audience. I so need it being disabled right up until it is needed and then taken down again after a single press.

[Mike Daniell]

Try this: in your original cue list, change the Activation Method of Q63 to 'Callable Cue', and in your hotkey cue (Q25) add a 'Call Cue' sub-cue to call Q63.

Note also that you can easily renumber your cues. In the Editor, under the 'Cues' toolbar button there is a menu item 'Renumber Cues'.

[berto2002]

Are we saying the way I had it configured was wrong or that there might be an issue there but you have offered an alternate workaround? Is that a better workaround than my one which seems to be working for me?

[Mike Daniell]

I hadn't actually considered the possibility of having a auto-start cue associated with a hotkey cue. I had always considered hotkey cues to be self-contained. I'm not totally familiar with what you are wanting to achieve but another possibility is to make the lighting cue (Q63) a sub-cue of the hotkey cue (Q25). That's easily achieved in the editor by selecting Q63 (Alarm lights) and clicking on the 3rd arrow button in the vertical toolbar on the left, to 'Make Q63 a sub-cue of Q25'.