#Shape Loader isnt filling up

10 messages · Page 1 of 1 (latest)

dire shard
#

when the shapes go it it goes up a bit then goes down

sinful agate
#

all shapes have to be in the same rotation

dire shard
#

ooo

#

o well i thought it had to do with the game getting really laggy when you go far away from the hub

bronze rune
# sinful agate all shapes have to be in the same rotation

I am having this issue as well. The problem is, the shape will load, but the other shape that is not rotated correctly cancels it out and begins erasing the shapes already in the loader. This isn't expected behavior. The expected behavior would be to either halt loading and throw a conflict, or fill up with the first shape loaded and not take the shape that doesn't match. I attached a video to show what I mean.

sinful agate
#

the behavior is intended, it's to allow automatically switching shapes without having to clear loaders manually, in MAMs or if you accidentally made a wrong shape for example

bronze rune
#

But it isn't erasing it completely is the thing. In the video it was half way done with a load block, then I changed a shape being loaded along side the other shape. Instead of instantly clearing the loader, it began slowly draining it. If that is intended behavior, it is very confusing for a new player just being introduced to trains like myself.

sinful agate
#

it is indeed confusing if you don't know about it, a better way to tell that this is happening (and maybe an explanation in the knowledge panel) is planned

bronze rune
#

Yeah, that's why I mentioned a conflict. That would have let me know that "hey there's an issue with this loader in particular." It took me a while (almost an hour) to figure out what the problem was after trying to solve it myself. I restarted my game, I removed the merge in the space belt, I rerouted the shapes across a platform instead of using a space belt, I deleted the loader. I tried loading in another loader. Then I finally figured out that one of my shapes wasn't properly rotated. It took me about a half-hour to get there though.

A shape mismatch error (conflict icon shown in the loader or a red X above the lane where the mismatched shape was like when loading a shape not in your tasks), or even just changing the shape being shown on the loader between the 2 shapes like it does when 2 shapes share the same conveyor belt would have let me know right away what the problem was.

Glad to hear that something to make this behavior more obvious is in the works though. And thanks for the quick response.

subtle lotusBOT
#

Thanks for the report, we are improving the loader visuals to communicate it better. Stay tuned.