QuickCloner
Multi-Level Atom + component cloning.
edit: NOT meant for Person Atoms
edit: Person Atoms Supported (collision disabled on Person clone instance)
If that's a requested use case, I can look into it. But this was mainly meant for UI type Atoms.
As promised, another free plugin / one of the building blocks created on the way to SimpleStateMachine.
I am not much of a salesman, so here's a brief description, and a video.
Description:
It attempts to clone the attached atom along with its children.
How deep it goes, I'm not sure. How accurate it is - also not sure.
Q: What happens if you hit "clone" twice on the same instance, without first renaming the already-existing clone and/or its children?
A: Undefined.
Have fun.
P.S. If using just to build your scene / environment / UI, there's no need to leave the plugin attached in attempts to give credit.
Copy/Pasta of Most Recent Update:
- Cloned Person Atom collision is immediately turned off
Known limitations:
The current state of it (v4) is more a remnant, than the path I will be focused on for the next month at least.
Multi-Level Atom + component cloning.
edit: Person Atoms Supported (collision disabled on Person clone instance)
As promised, another free plugin / one of the building blocks created on the way to SimpleStateMachine.
I am not much of a salesman, so here's a brief description, and a video.
Description:
It attempts to clone the attached atom along with its children.
How deep it goes, I'm not sure. How accurate it is - also not sure.
Q: What happens if you hit "clone" twice on the same instance, without first renaming the already-existing clone and/or its children?
A: Undefined.
Have fun.
P.S. If using just to build your scene / environment / UI, there's no need to leave the plugin attached in attempts to give credit.
Copy/Pasta of Most Recent Update:
- Improved positioning of cloned Atoms.
- Fixed an off-by-one bug, where components restoration was misaligned.
- eg. previously only A and/or B in the tree would have restored correctly (2nd video).
- Removed "control" object from restoration, and used constant offset (0.3f away from original Atom position, in all directions)
- Cloned Person Atom collision is immediately turned off
Known limitations:
- Component restoration isn't accurate in all cases.
- Basically, the more components / deeper you go, the more likely a misalignment occurs.
- Custom and Script components on persons are iffy even at the 1st level
- As such can be done with other native means and/or plugins, it's not on the drawing board to make this a key feature of the plugin.
- Atom trees of 3+ height may be cloned as deep as the tree goes, but components will start misaligning, almost guaranteed after the 2nd level.
- Again, wasn't really an outcome required by the larger plugin most of this code was pulled from, so likely not something I'd stop my current development for to work on.
The current state of it (v4) is more a remnant, than the path I will be focused on for the next month at least.
