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.

Hi Blackbat, the simple show your described that reproduces the issue is fantastic. We call this a Minimal Test Case (MTC) and it’s exactly what we need to help us efficiently fix the problem. Please send your MTC show file to support@finale3d.com along with any step by step instructions needed to reproduce the issue and we’ll take a look at it ASAP.

I recently finished a design with several hundred cues, addressed it for firetek and locked all the addresses. I now find myself wanting to add a couple of additional shell cues and have come up against what I believe to be a bug, which can be replicate in a much simpler example.   If I have a design with just two positions, cakes and shells, with 2 cues on each and each of the two positions is defined in its own section, then address it for firetek using the criteria “each module is restricted to a single section and —” and “each slat is restricted to a single position”, the result is two modules required, one for the cake section and one for the shell position, with one slat on each. So far so good. If I now lock the address of all four cues, and then add an additional shell cue and re-address, I would expect the new cue to be the third cue on the shell module slat. What in fact happens though is that a 2nd slat is assigned to the cake module (module 1) and thus the new shell cue ends up on 1-02-01, rather than 02-01 03 which is where it should be assigned.   I’m thinking this is a bug with sections. If I repeat the exercise using fireone addressing with no slats then the 3rd shell cue again gets added to the cake section.

I am writing to inquire about the commercial use of the 3D Google Maps feature available in the Professional Edition. Specifically, I would like to confirm whether it is permissible to utilize the 3D Google Maps imagery and features in commercial projects or productions. Your guidance on this matter would be greatly appreciated.  

Thanks Drew, That will make it look nice. Should have tried that.

Seems like it is still deleted  

Hi Pyro_7100000, There is a reason for this behavior, granted, I fully appreciate that the explanation probably won’t make it any less annoying. Here you go:   The angle convention in Finale 3D is designed to handle not only fireworks, but all types of SFX including moving head lights. Doing this requires three angles, Pan, Tilt, and Spin.   Tilt is the angle from vertical, but tilt is not just left and right. In order for tilt to angle an effect left or right, a 90 pan angle has to be introduced. This is the reason cakes swing around when tilted left or right. The same thing is happening when you angle a comet, mine, shell, and every other type of effect, you’re just only noticing with cakes because they’re not rotationally symmetric. That is, a comet looks essentially the same no matter how it’s rotated but a fanned cake or slice does not.   To counter act the undersired side effect of the 90 degree pan, you need to employ the third angle, Spin. The Spin angle is the rotation around the trajectory of the effect. For example, imagine you had a single shot comet in a holder and you rotated the comet so the label was facing a certain direction without changing the trajectory angle – that’s spin. When you angle a cake left or right, a 90 degree pan is added. To fix the orientation of the cake, add a -90 degree spin.   To learn more, check out: https://finale3d.com/video/mastering-angles-pan-tilt-spin/