[=.OConnor;229630]
The cyclic dependency improvements were mostly around the fact that some blueprints would become unloadable if they called functions or stored references that in turn stored references to the original blueprints. Blueprints with wide, cyclical dependency graphs could either load with incorrect data or crash while loading. The situations that were corrected could not be described succinctly.
[/]
Thanks for the explanation!
[=.OConnor;229630]
When you click on ‘Class Settings’ in your macro library what is the Parent Class of the macro library?
[/]
I tried “Object”, “Macros”, and “StandardMacros” as parent class.