* Fixed state sets giving an error during recording in release mode (caused by assembly obfuscation error)
* State set to bitmap connections can now be properly disconnected and reconnected (altering the internal state set render outputs)
* Fixed controls being removed from remaining state set nodes when more than one instance is present and deleted
* Major internal changes and refactoring (entities can be instanced/appear twice in the entity tree, as a result each entity can have multiple parents, and multiple nodes in a view)
* Multiple treeview state set fixes: when making a state set current only the currently picked branch is selected, not all instances of specified state set.
* Making a state set current or recording it in schematic view, if state set is instanced, will bring out a popup menu to select which instance branch to use.
* Fixed state sets can be dropped outside master state
* Dragging and ropping a state set now defaults to cloning it (instead of moving it)
* Instanced state sets (having more than one parent) are now marked with a special icon
* If a schematic state set assigned to a bitmap node changes its output path after being assigned the bitmap file name auto-updates
* Schematic state set nodes now have functionaing record and current buttons, and after recording is finished their children are properly displayed inside rollouts/values
+ State set schematic nodes can now be wired into bitmap texture 'file name' slot, this will cause the render output of state sets to be auto-loaded into said bitmap and manipulated using standard Max tools. This is the first step towards schematic render pass compositing.

Marsel Khadiyev (Software Developer, EPHERE Inc.)