Hello,
I just discovered the new magma flow 2 interface.
But I have 2 problems with it:
First: now moving the nodes for arrangement is very jerky and slow, which is strange because I saw in a magma flow presentation where bobo was moving nodes quickly and smoothly as usual (it was smooth for me in 1.6 btw)
Second: magma flow 2 is loading everytime, and, on a new scene for instance, when I make a prt volume, then add a krakatoa channel modifier and load magma flow, the 1.6 version of magma flow is opened. Then, if I save the scene, close max, and reopen it, magma flow 2 will be loaded.
How to deal with that to have magma flow 2 as smooth and responsive as before, and to have it being loaded everytime
First regarding the modifier itself - the Krakatoa Channels modifier IS THE OLD modifier. Same as in 1.6. It is there so you can load old scenes. It is there so you can use it, if you want to send a scene to somebody who does not have 2.0 yet. But it IS NOT Magma 2.
The real new Magma 2 modifier is called “MagmaModifier” and is slightly lower on the modifiers list. If you use the KCM icon/MacroScript as instructed in the documentation (via a toolbar or the Krakatoa menu), the NEW Magma modifier will be added. When you load an old scene, the old Krakatoa Channels modifiers are automatically replaced with new Magma modifiers, but you can disable this for the current Max session via the System Preferences rollout in the Preferences floater. This way you can open a scene from someone using 1.6, make changes to it and save it without losing the 1.6 KCMs.
Now for the slowdown.
First thing first - what version of 3ds Max are you running, and with what Service Packs? There are known issues with 2012 without Service Packs. Not sure if they would be related to the slowdown, but who knows… Second, what kind of flows are you manipulating? In a flow with about 20 nodes, the moving of a node is relatively smooth here, the panning is slightly jerky from time to time (every few seconds) due to the updates to the new navigation field (mostly caused by MXS garbage collection kicking in while updating that bitmap). Is your flow slow when you have an Output and an Input and nothing else? Can you record a screencap video of what you are seeing?