Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Belt reader feeding directly into storage causes storage to not be able to output on primary output at full speed. #1608

Open
MikeStirner opened this issue Nov 16, 2024 · 3 comments

Comments

@MikeStirner
Copy link

image

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.

@MikeStirner
Copy link
Author

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.

image

@MikeStirner
Copy link
Author

A 240 Hz tickrate solves it, as one would expect. Very interesting.

@MikeStirner
Copy link
Author

Here are pics of that:

image

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant