Is there a way to get the viewport cache to clear when the Magma modifier updates? Right now I can’t see what I’m doing unless I keep clearing the cache in the PRT Loader.
EDIT: Bunch more things I’m finding in 45677…
The Magma debug doesn’t retain the counts on the particles. So each time I turn it on I get First: 1, Count: 1000. I’d really like it if it defaulted to something smaller, or if the setting was persistent.
I’m still getting errors on the debug. Haven’t been able to use it, really. “–Runtime error: Magma Channel “Normal” Not Available in this PRT Object:ID: 3Property Name: channels”
Is there a way to paste an operator and maintain the connections?
Is there a way to instance an operator?
Are we supposed to get some sort of feedback when there is a mismatch on the types of an input and output? If I connect a float to a vector, I’m getting nothing telling me there’s a problem.
Ctrl+P doesn’t enable/disable the outputs in the editor.
Ah, I would consider that a bug.
I fixed it by adding a loop that collects all PRT Loaders dependent on the current Magma modifier and invalidates their viewport caches if AUTO in on or UPDATE is pressed. I think I also made updates generally faster as the Modifier Name was being updated too often, now it will be updated only if the Output node channels changed or a manual UPDATE was performed or the editor was closed. Spinning spinners should be much smoother now with no flashing Command Panel.
Fixed, both First and Count are now sticky between sessions. Defaults are 1 and 100.
I could store them per Magma modifier if you prefer, right now they are sticky via INI file.
Not at the moment, but I can look into it, assuming you are pasting within the same flow.
EDIT: Would it be enough if this works ONLY if a SINGLE operator is being copied and within the SAME flow? If yes, then consider it done.
Nope. Have to ask Darcy, but I suspect you cannot right now.
Yes, there should be a red node and an error at the bottom text field when evaluated. If >AUTO is off, you won’t see anything until you UPDATE.
The main thing is that depending on your monitors and window arrangement, you probably have a limited amount of space for the rows anyway, and that’s probably user/machine specific.
Same flow is fine, but the use case I had was where 4 tools were connected to 12 other tools, and I wanted to copy the 12 and keep the connections to the 4, so now the 4 would be feeding 24. As it is now I had to make ~22 connections for each paste I did, and yeah, those circles and squares are really tiny when you have to hook them up manually.
I will see if I can preserve connections from nodes that would otherwise become unconnected, but it might become messy.
It works great with a single node. So you could probably collapse a bunch of nodes to a BlackOp temporarily, copy the BLOP multiple times and then explode the BLOPs to get the whole flow again. Not sure if it is applicable to your case, but copying a single BLOP would preserve its incoming connections AND all the connections inside of it.
Ok, I managed to get it to work with multiple nodes.
But I don’t want this to be the default behavior, so I made it a special option.
In the menus, now there is a “Copy and Preserve Connections (Ctrl+Alt+V)” option, and you can press Ctrl+Alt+V to paste within the same editor. Any input write that has been “broken” in the process of copying (that means it connects to a node in the flow that is not in the clipboard) will be reconnected to the node in the flow instead. When using Ctrl+V, only wires within the clipboard will be retained and wires that are severed by the copying won’t be created (as before).
Thanks for the feedback, I think this is an awesome addition.
It works for me on PRT Loaders and non-PRT Loaders, at least in the simplest cases.
If you can give me a case where it does not work, I will look into it.