Openrct2: Queue alignment is worse than RCT2

Created on 6 Apr 2016  路  14Comments  路  Source: OpenRCT2/OpenRCT2

OS: Win 10
Version: 0.0.4
Commit: latest build

  • [ ] Reproducible in RCT2 (vanilla)?
  • [ ] Multiplayer?

Today I have seen this problem, this only happens if the queue line is not linear, straight to the point... these images show the problem:

Screenshots / Video:
Queue on RCT2 (all people are aligned):
rct2

The same queue, on OpenRCT2 (people are aligned in a worst way):
openrct2

Additionally, this problem at sometimes causes a bug (Vanilla bug): https://vid.me/ySCE ( Save game )

PS: I'm not sure if I have written the title correctly ;P

bug

Most helpful comment

This issue is just about the alignment of guests in the queue. We should really fix this. I don't like changing the logic of something accidentally - it should be intentional with the changed part of the code clearly marked. Even if we wanted to leave it like this, we should still mark the part of the code that is different from vanilla.

All 14 comments

I'm not sure if I write the title correctly ;P

Not completely. 'Worse' already means 'more bad', so 'more worse' is not correct English. But we understood you anyway. ^^

oh okay haha, thanks for your help ^-^

Can someone clue me in to what the bug is? I'm not seeing it.

The problem is that people directly turn left or right when entering a tile where they have to turn, instead of walking first to the middle of the tile.

Meh it's more natural. The code that does this is in peep update. There is possibly a rand which is slightly different but I hardly see a difference or care to change it.

If it's _just_ the placement, yes.

Anyway, the video @Wirlie posted is a problem that also affected vanilla RCT2: people joining queue lines, but walking past the queue, to the entrance and then turning around and going back. That was not introduced by OpenRCT2, as I have had that bug lots of times in vanilla.

This issue is just about the alignment of guests in the queue. We should really fix this. I don't like changing the logic of something accidentally - it should be intentional with the changed part of the code clearly marked. Even if we wanted to leave it like this, we should still mark the part of the code that is different from vanilla.

okay i will look into it.

Not sure if that will fix it. Please retest with my change.

I tested the change and the problem still happening (Build 90dbefe)
scr22

AFAIK, this is a bug since the peep code was implemented into OpenRCT2

@Wirlie could you now retest with cfecbed0038f9338f256b0168f7a520d5ad30cb0

Okay now I'm waiting the artifact of AppVeyor for test your change.

Test passed!
scr23

@duncanspumpkin @IntelOrca Thank you very much, you can close this issue :)

Was this page helpful?
0 / 5 - 0 ratings