#[0.0.9-rc6][and previous] Bug on shape loader <-> unloader
17 messages · Page 1 of 1 (latest)
Thanks for the reprot. There seems to be something off indeed. We will have a look.
🚑 Your bug report has been verified and is now in the triage phase. We're working to reproduce and fix it.
Could that happen because you upgraded the train capacity inbetween?
I tested, but at base speed and at max. upgrade speed. It seems to load correctly on my version.
It must be a side effect from upgrading train capacity while loading current shape crates.
hi. no. staying on the same train capacity. thet was my first thought. but i didnt
Wow two dev messages next to each other never seen that
the effect occurs only after a longer time
right after builing it works just fine. packes are delivered unloaded and loaded as expected. after undertimened time a diff occurs and packages are not completely transferd. btw i like the feature that I can connect those loader/unloader directly. I have to test with a platform in between
I know I'm not a Dev that works on the game, but does this happen if you leave it on screen?
My guess as to how the game is optimized is that it estimates the flow rate of anything off-screen, and in the process of unloading the active models and such, it drops a shape or two.
Hi. its happening while on the center of my screen. Thanks for asking.
I considered that packages have equal amount of shapes eacht, so direct unloading-loading should work fine. If the the loose shapes during transfer it happens that remains of packages got stuck. more on the unloading side then on the loading.
when you then load different packages of different shapes they cancel each other out causing not being delivered to the vortex.
eg when a red-dot on blue package remain receives a delivery of yellow-dots the yellows will cancel out the remains.
Technically it could happen if you clear (i) one of the platforms mid transfer.
I guess when you fill a loader eg at level 1 with 360 bluedots and when new greendots come in, they get canceled out in the shape loader. For this overwrite/cancel a unknown amount of shapes will be consumed. Lets say 30 for example, this cancellation shapes will then be substracted and gone missing, causing the transfer between loader/unloader to be incomplete.
This behaviour can be seen when you connect a belt to a loader which has already parts of a different shape. the first new incoming cancel the stored ones so the storage is cleared by the cost of a few new incomming.
maybe direct connecting loader/unloader is not the best idea. but it is convinient to avoid cross routes and easy to use with only one colored train available (which can run separate then)
I sense there is no serious bug then. sorry for misleading
Yeah it could be clearing contents or canceling each other out.
With these two mechanics in place there is no real way to prevent that from happening with direct loader-to-loader transfer.
Thanks for the reports and all the details.
We are closing this report as "not a bug" in our system.