Plugins Atom Mover (Obsolete)

I'm not updating this plugin anymore. Check its successor, Atom Controller:

Plugins - Atom Controller

Description Atom Controller is the successor of my Atom Mover plugin. I changed it's name so that I have more freedom about features that can be implemented in future releases. Indeed, there are already features (like Physics Constraints) that...

hub.virtamate.com

For those interested in my Atom Mover plugin, here is a sneaky preview of the upcoming BIG update.
It changed so much that I'm thinking about stop updating Atom Mover and release Atom Controller.

P.s. Don't warry, there will be help text to explain the new concepts.

Hotfix for bad sliders showing up in scene triggers setup.
This should also fix any broken triggers problem.

IMPORTAN NOTICE
I want to take this occasion to say that I'm working on version 2.0 of the plugin.
There will be A LOT of changes in how the plugin works and them will very likely broke existing scenes triggers.

I'm sorry for that but I think that the new logic will simplify a lot the triggers setup and will also make everything more intuitive. Meanwhile, I don't like the idea to keep "junk" obsolete code in my plugin just to avoid the re-setup of a bunch of scene triggers.

That said, mind that you can always keep all the versions of the plugin that you like and work with them. This is ok also for released scenes vars if you setup your vars to use "Exact" version of plugins (the HUB keeps older versions and will download these old versions when needed).

I planned to release this update later, there are a few things I wish I could have included in this update but, the Linked Atoms problem, popped out while I'm working so I choose to release this now to fix it.


Fixed errors rised by linking containingAtom to Atoms that are already link targets of other Atoms:
This was harder than expecterd but, with the invaluable help of @everlaster, we managed to solve the problem. Hopefully once and for all.

The plugin will now store separately the Global and Local values of cyan Position \ Rotation Sliders:
Hopefully this will limit the need to check position and rotation in VAM UI.
To keep backward compatibility, in your triggers, you still have to use general Position and Rotation and use the toggles to change from Global to Local. This may change in future updates (always keeping backward compatibility).

Global Position Sliders are now updated in realtime:
Now they will always display the current global position. The same as VAM UI.
There are a number of reasons for which this cannot work with Rotation Sliders but I'm thinking to add an option for this.

Other little things
- Torques and Forces tabs are now disabled if forces are disabled.
- Code optimization.

I solved the problem with linked Atoms (hopefully).
New update coming soon... there will be a number of little things (mainly under the hood) that will bring to a more stable\reliable plugin logic.

Hi!

The new Movable Linked Atom feature rises errors if you try to link the Atom on which you loaded Atom Mover to an Atom that is already a link target of other Atoms. Contrary to what I thought at first, this issue is very ugly and hard to solve but you can try to avoid it like this:

Instead of linking Atoms that way:

Link them that way:

I know it's not very nice and I'm not happy with this. I'll keep trying to find a solution but... it may be not possible to solve without modding VAM's internals.

Fixed local translation bug introduced with HUB release 12 (sorry ?).

All movements now works regardless of linked state:

This turned out to be more complex than what I thought at first but, now, you can use Atom Mover to move and rotate the Atom even if it's linked to another Atom. It seems stable but there is space for improvements and additional features.
I haven't tested this properly so... feel free to report any issue.

A VERY BIG THANK YOU to @everlaster for digging into this with me.


Rotation Control Sliders default range now goes from -360 to +360:

Asked by "Mr Rogers" on VAM official Discord. At first I thought there was no real need for it, but now I have to admit that I like it more that way.


Other little things:
- New Voithe Utils version.
- Code optimization.

- Rotation Control Sliders default range now goes from -180 to +180.
- Rotation Control Sliders will no more get values outside the range -360 +360.

- Fixed a bug in translation control computing.
- Code optimization (implemented Voithe's Utils).

NOTE: If you have scene triggers that trigger "RESET TRANSLATION CONSTRAINTS" plugin action, it maybe necessary to rebuild them.