[In 11.4.0] Change in behaviour of "Goto" queues
Posted: Thu Oct 04, 2012 5:52 am
Hi Mike,
I'm currently using SCS 10.8.4 but checked the trial of current SCS11 and it still displays the same behaviour: A goto cue acts just like a click in the cue list (with a 'Go' afterwards). This behaviour gets in my way, when I have a helicopter sound with a looping audio file cue with some level change cues afterwards that are looping via goto:
I start the helicopter queue, SCS advances to Q60, because it's the next manual cue. When I action Q60, it advances to Q61 etc. But when the goto cue runs, SCS steps back to Q60 (aka the next manual queue after Q50), so instead of actioning Q61 etc. the next time I'd push my 'go' Key, Q60 instead of Q61 etc. would run.
Of course I could click on the right queue but that marks the auto queues 'completed' so the level change loop is interrupted. I hope I made myself clear.
bye
einhirn
I'm currently using SCS 10.8.4 but checked the trial of current SCS11 and it still displays the same behaviour: A goto cue acts just like a click in the cue list (with a 'Go' afterwards). This behaviour gets in my way, when I have a helicopter sound with a looping audio file cue with some level change cues afterwards that are looping via goto:
I start the helicopter queue, SCS advances to Q60, because it's the next manual cue. When I action Q60, it advances to Q61 etc. But when the goto cue runs, SCS steps back to Q60 (aka the next manual queue after Q50), so instead of actioning Q61 etc. the next time I'd push my 'go' Key, Q60 instead of Q61 etc. would run.
Of course I could click on the right queue but that marks the auto queues 'completed' so the level change loop is interrupted. I hope I made myself clear.
bye
einhirn