Page 1 of 1

[boskid][2.0.6] Custom fluidbox.max_pipeline_extent does not update properly

Posted: Sat Oct 19, 2024 4:20 am
by micromario
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:
Recording 2024-10-18 231839.mp4
(4.24 MiB) Downloaded 53 times
As you can see, the top section has extent 320 and the bottom section has extent 1280 despite being the same entities.

Re: [2.0.6] Custom fluidbox.max_pipeline_extent does not update properly

Posted: Sat Oct 19, 2024 4:21 am
by micromario
Loggers

Re: [boskid][2.0.6] Custom fluidbox.max_pipeline_extent does not update properly

Posted: Sat Oct 19, 2024 9:44 am
by boskid
Thanks for the report. This issue is now fixed for 2.0.7. When fixing this i also fixed 2 other issues (one desync and one case where overextent would not trigger when low-extent entity was attached to a segment that is already over the limit of the new entity).