[boskid][2.0.6] Custom fluidbox.max_pipeline_extent does not update properly
Posted: Sat Oct 19, 2024 4:20 am
It seems that the max_pipeline_extent take the min of the lowest max_pipeline_extent in the network.
However when disconnecting the network from such minimum sources, the wrong max_pipeline_extent lingers in the network.
See the video for an example:
As you can see, the top section has extent 320 and the bottom section has extent 1280 despite being the same entities.
However when disconnecting the network from such minimum sources, the wrong max_pipeline_extent lingers in the network.
See the video for an example:
As you can see, the top section has extent 320 and the bottom section has extent 1280 despite being the same entities.