-
Notifications
You must be signed in to change notification settings - Fork 5
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
Tubes have gone crazy #36
Comments
tubes turn into broken tubes when there are more than 30 stacks in 1 tube... that is intentional, handle your overflow with a trashcan (trashcan has basically the lowest priority) |
OH i didnt notice that im so sorry |
could you tell me more about the crusher bug (how to reproduce it) |
And how do i reproduce this? i've tried to just put up tubes and spam items into them but what you've described never happens The "Clipping around endlessly" may be caused by (network) lag, ive let a lot of stacks run around in tubes and that never happened |
wait this just happened to me now... with an unknown item.... weird |
but only and 100% of the time with unknown items... everything else works normally |
and crusher doesn't have any code to put anything in the input slot, so it's not a crusher bug, it's most likely a tube bug |
I think it's due to a full output for the auto-injector. I think it tries to pass the item on, fails and sends it back. I'm also getting weird stuff where on my: puncher -> auto-injector -> storinator When the storinator is full, it keeps producing, and pushing to the auto-injector. As I remove say 10 stacks from the chest, it keeps putting more in the storinator so it's full within seconds. I think items go into limbo in the auto-injector and build up there. If they cannot go to output, I'm guessing they go back to where they came out of. |
I don't think the auto-injector should try and pull if there is no space to push stuff. |
If you see the first screenshot in this though: They're filter injectors from matter extractors, and there is space in the chest, yet the matter has clipped out of the tube which it never used to do. |
Oh thats weird..... let me check if regular pipeworks has this problem |
i see now |
pipeworks has this same problem too, and i will give you a consistant setup to reproduce it shortly |
the reason this is super problematic for crushers is because the output inventory is different than the input inventory so it transfers stuff from the input to the output |
Or just put up an infinite storinator and hope you will never get 5 000 stacks of random chemicals (btw you can push to those unknown slots but not pull from them, also you can do both) |
so, the solution to the crusher bug: manage your overflow correctly |
But this is a good idea so i will attempt it |
ok so due to how pipeworks works thats slightly tricky |
so instead, i will just make the crusher only accept pebbles |
oh i now saw the matter. yeah that's super weird, i don't understand much of pipeworks's entity code does it end up in that chest? does it happen consistently?
what happens if you break+place the tube? |
My feeling is it was to do with puncher, and the fact it stocked up stuff that got stick in the injector. I'm guessing the extra item entities may have had an effect on performance. Not sure for certain though. I've cleared it out and it seems ok for now, but I'll see have to keep an eye on it. That crusher input change will definitely help. If it ends up crushing more stuff, I guess it can change to a group. :) |
If I have automation set up and I put empty water vials in, they just get spat out quickly. I'm wondering if maybe we need an extra input slot for empty liquid containers. |
see mt-mods/pipeworks#135 maybe? (and also, to keep it absolutely clear, punchers don't need injectors, neither do node breakers) |
also the real way to fix the crusher issue is to handle your overflows |
Is this resolved? |
no, but its very low priority |
What's the issue? |
ive only reproduced this one: mt-mods/pipeworks#135 |
I can't do anything about this, only "upstream" pipeworks can, i don't know pipeworks code nearly as well as them, issue should be closed |
Ok, so this is weird. This setup, the corner turned from this to red, so I replaced it with a tube and it went back to how I wanted it.
Fine so far, right, however, now, when the crusher completes, it sometimes puts the ores in the pebbles slot, and then the pebbles just bounce around the tubes aimlessly until they clip outside the tubes and just head away as can be seen in the picture.
So there is a crusher bug, with other weirdness in there also.
The text was updated successfully, but these errors were encountered: