Open VorTechnix opened 2 years ago
Yeah, this is a bug..
You've got the right idea here - when we use a Voxel Manipulator to move nodes, we only move the node ids here and not the param1
/ param2
values. We need to also copy param1
/param2
explicitly.
When moving nodes there is a fault that sets the param2 values of all moved nodes to the param2 values of the nodes at the positions they are moved to.
Before move:![image](https://user-images.githubusercontent.com/45538536/168643502-c65c50bc-f1cc-42d5-a1a7-0e24a1d292ae.png)
After move:![image](https://user-images.githubusercontent.com/45538536/168643634-62f0cca9-36bc-4555-bb40-e8df2765e4da.png)
Note: nodes take the param2 value of the node that was in their positions previously.
When moved back to original position the param2 values restore.
This bug happens regardless of move direction or distance.
After big move into air where no nodes have been all param2s become 0:![image](https://user-images.githubusercontent.com/45538536/168644512-48641518-df75-4ec3-9726-e8167b0797c1.png)
After moving the nodes back to original positions the param2s restored so my guess is that the param2 values were retained by the air nodes in the moved nodes' original locations.