First, let’s try to make sure that you don’t lose your work. If you aren’t able to save your show file, try exporting your show data by going to File > Export > Export all show data tables as combined csv… This isn’t the same as saving your show but it will make it possible to recover your positions, script events, and per-show effects which could be much easier than starting over.   As for solving the real problem, is the hard drive in your computer almost full? Each time a show is saved, a backup copy of the show is saved to the backup files directory on your local hard drive. Consequently, low hard drive space can cause a saving errors even if the primary location you’ve selected to save your show is an external hard drive or USB flash drive.

I’ve had this appear a few times. I’ve tried saving both internal hard drives and an external USB, all giving the same error. I have checked that windows defender isn’t doing any scans. Looks like the only solution is to loose any unsaved work and start again. What could be causing this?

Hi guys, could not find the following thing in the rack layout or effect / position parameters, but is it possible to give a 40/60 meters oval safety distance to a cake that we’ve made? I only get a round circle out of the safety distance, tried 40×60 and 40/60 but no succes. Maybe something for the future?

That’s fantastic Will and DrewFinale! Many thanks for resolving this amazingly fast :-).

Blackbat, we just finished fixing the bug for the issue you brought up.  The issue was that modules were not implicitly constrained to sections for locked events on modules with slats.  Thank you again for the MTC.  The fix will come out in a beta next week.  In the meantime, a workaround is to add the constraint, “Modules constrained to a single Custom Script Field” and then copy the position names of the event rows into the Custom Script Field of the same rows.

Blackbat, I am working on the bug fix for the issue you brought up.  As Drew mentioned, the fact that you sent a perfect Minimal Test Case and gave a clear explanation in your email made it easy for me to reproduce the problem and track down what was going wrong.  The problem is that sections don’t work exactly how we describe them with respect to locked events, but I didn’t realize the difference could actually violate the implicit constraint that modules are constrained to a single section.  Nobody has ever pointed this out, over many years, which makes your simple Minimal Test Case all the more impressive.  I’ll circle back when I have a workaround or fix.

Yes, you may absolutely use the 2D and 3D Google Maps imagery for your commercial presentations and productions. This is one of the major use cases for these features.