Idea is to make a docking rail for things that don't move thus saving a rail speed controller and an actuator block to set speed zero for something that isn't going to move anyways.
It does however continue to do checks for movement and collision, which is why people put a speed controller and actuator block (off) on a rail to stop those checks and cut the server loadjust use a single rail and it aint gunna move
Does it still do that? I thought this was fixed (or at least massively reduced), and that fix was responsible for the huge lag reduction with lots of rails.It does however continue to do checks for movement and collision, which is why people put a speed controller and actuator block (off) on a rail to stop those checks and cut the server load
It still does it, just not as bad as it used to, as evidenced by the "Entity is too large ... speed is x%" warningsDoes it still do that? I thought this was fixed (or at least massively reduced), and that fix was responsible for the huge lag reduction with lots of rails.