tobspr-games
Belt reader feeding directly into storage causes storage to not be able to output on primary output at full speed.
As you can see, the Storage has a belt reader touching it at the input of the storage and that is causing the output to occasionally go out the secondary output instead of the primary one. Moving the belt reader away a bit fixes it, as you see on the left. I removed the garbage building to clear the left output belt and within 10 seconds there are already several shapes that have come out the wrong way.
60 Hz. All speeds are 19.19/s. Version 1.5.5 via Epic Games. Windows 10.
Easy to avoid, but thought I'd let the community know.
Related is this issue with the tunnel curve tunnel combo (any tunnel type). Also produces a slowdown. Might just be certain belt speeds and refresh rates. It all goes normal if I switch to 30 Hz, but then I get 15 items/s for everything.
Looks related to #781, #1103. Thanks for the detailed info, maybe these setups are a useful diagnostic for these tickrate-related slowdowns. (Whether they will ever be fixed is another question.)
Didn't want to make a new ticket, but I found another similar case, with the belt reader coming directly after a merger:
Simply putting some distance between the two fixed it (17.1/s -> 17.6/s):
My tick rate was 60 at the time. Seeing some comments about tick rate being related, I tested a tick rate of 120 and this also made the problem go away (17.6/s):
I reverted to a tick rate of 60, and the problem came back (17.1/s).
