uses an untested experimental 'dummy' clipsprite ( discussed with @WyldAnimal before ) to hasten finding the swing clips and this could be the cause.
logo: Info/small_logoFractalGardenA467.png
text: Info/infoFractalGardenSeptet.txt
// remix of FG020
//clip {
// id: Clip3A
// allow: top //dummy clip
// }
I think there is a slight misunderstanding about the dummy clip usage.
The Dummy clip should NOT be a Swing clip, it should be a common easy to find clip type.
When and Why use a dummy clip?In a Scene, if the Main clip isn't found fast enough, a Message is displayed, NO CLIPS, and the scene will end.
This can happen for a scene where the swing clip is used as the primary clip.
a random swing clip isn't found fast enough and that No CLIPS message is displayed and the scene ends.
So then a Dummy 1st clip of an easy to find clip type is used.
this fills the 1st clip position fast, and then allows for the 2nd clip to have as much time as is needed to be found.
This dummy clip is never displayed, it's just used to allow the scene to not display that NO CLIPS message.
By using a Swing Clip as a Dummy clip, it actually defeats the purpose of having a Dummy clip.
the Dummy clip should be a common, easy to find clip type, not a rare type of clip that might time out and cause the NO CLIPS message.