Apex console ignores marks after updating to 3.3.3.10

We have identified the issue, and will have a fix available for this issue in the first open beta build of 3.3.4. (Build 3.3.4.8 or higher) We expect this will be available in the next day or so.

Update: posted to open beta here - (+) Eos v3.3.4 Build 8 is now available! - Eos 3.3.x Open Beta Announcements - Eos 3.3.x Open Beta - ETC - Community

Hi Hans, 

This is causing me a heap of problems on a show (we ran a show last night with no problems, this afternoon half the show is spinning into place as if it's not marked).  I will roll back to 3.3.1.11 where we had no issues, but it feels like the 3.3.3 release with this mark issue could be quite damaging.

Hans, I think you all need to pull 3.3.3 from the website ASAP. It’s been 8 days and people are updating shows with no idea that it could break mark. 

Thanks for raising this again Paul and Vic. I think at the very least it would be good to issue some guidance about under what circumstances this problem will manifest so that folks can make more informed choices about whether to upgrade.

Currently it feels very unpredictable in terms of when or why a light will decide to ignore a mark command.  Once we've got through this put-in we will roll back for the dress this evening.  But it would be good to know what is causing this and why it is in a release build.

All, feedback is heard and appreciated. I know many of you have been involved in off-forums conversations as well. More official guidance will be coming soon from Nick Gonsman, but the urgency for resolving is understood. 

The current 3.3.4 beta build contains the fix for the original mark issue. One additional newly reported case of mark not working in some specific circumstances (involving intensity delay and firing cues before they are complete - EOS-57610), is being investigated by the team right now.

All, feedback is heard and appreciated. I know many of you have been involved in off-forums conversations as well. More official guidance will be coming soon from Nick Gonsman, but the urgency for resolving is understood. 

The current 3.3.4 beta build contains the fix for the original mark issue. One additional newly reported case of mark not working in some specific circumstances (involving intensity delay and firing cues before they are complete - EOS-57610), is being investigated by the team right now.