If I move the tracks up they work but then the next track that drops down and takes place 14 doesn't work anymore.
How do I fix this?

I have also seen this behavior. A track has a perfectly good sequence on it (plays OK in the sequence editor pane) but will not play with the show.CoS2000 wrote: ↑Tue Sep 10, 2024 10:23 pm I had a similar problem myself. On a lower track there was just a small function that only switched on a fog machine. When I played the show, the fog machine didn't react. So I created another track and put the same function on it. When I played the show again, both tracks suddenly responded. When I deleted one of the two tracks, the fog machine stopped responding again. I think it's the same problem you're having.
Yes, that's exactly how it was for me. When I clicked on the sequence, everything worked, but nothing happened in the show. In my case, it was also a very simple sequence. One channel simply set to 255, nothing more. The fog machine was supposed to fog. It did in the editor, but nothing happened in the show.markzvo wrote: ↑Wed Sep 11, 2024 2:06 am I have also seen this behavior. A track has a perfectly good sequence on it (plays OK in the sequence editor pane) but will not play with the show.
Creating a new track directly underneath, and rebuilding the same sequence with the first few steps seems to have brought the track above it back to working order. Very strange.
Yes the sequence we had was fine in 4.12.6 but when we moved to 4.13.1 we began to experience this strange sequence/track issue.CoS2000 wrote: ↑Thu Sep 12, 2024 1:11 amYes, that's exactly how it was for me. When I clicked on the sequence, everything worked, but nothing happened in the show. In my case, it was also a very simple sequence. One channel simply set to 255, nothing more. The fog machine was supposed to fog. It did in the editor, but nothing happened in the show.markzvo wrote: ↑Wed Sep 11, 2024 2:06 am I have also seen this behavior. A track has a perfectly good sequence on it (plays OK in the sequence editor pane) but will not play with the show.
Creating a new track directly underneath, and rebuilding the same sequence with the first few steps seems to have brought the track above it back to working order. Very strange.
Like you, I then created a new track and added the same function to it. Suddenly both tracks fired in the show. I know this because I set the start time of the sequence in one track differently. Both tracks fired. But when I deleted one of the two tracks, nothing happened again.
The error must have occurred in version 4.13.0. The show is older and has been played several times. It always used to run perfectly! The error only occurred when updating to 4.13.0!
We have given you access to our autostart.qxw show file https://github.com/SirMaverick34/Terror ... ostart.qxw in our GitHub repo (I cannot paste it publicly), please accept the GitHub invite to see it.mcallegari wrote: ↑Fri Sep 13, 2024 7:51 am Can someone please share a sample project to reproduce the issue?
Thanks
Ah so I think the limitation (for now) is, no two tracks of any show should have the same name. We will use this as a workaround. Thank you! Hopefully OP is following this.mcallegari wrote: ↑Sat Sep 14, 2024 11:33 am I think I found something.
After 4 hours, I've reduced a 14.4MB project down to 108k and realized two tracks had the same name.
Renamed the second "All/Matrices" to "All/Matrices2" and the issue is gone. (save and re-open)
Now, why this has changed from 4.12.x I still don't know. I'm going to investigate but apparently two tracks cannot have the same name (even if they have different IDs in the engine)