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

New implementation of path/railing separation breaks old parks #19503

Closed
ArcticX9 opened this issue Feb 26, 2023 · 4 comments
Closed

New implementation of path/railing separation breaks old parks #19503

ArcticX9 opened this issue Feb 26, 2023 · 4 comments
Labels
bug Something went wrong. regression An issue that was made since the last release.
Milestone

Comments

@ArcticX9
Copy link

ArcticX9 commented Feb 26, 2023

Operating System

Windows 10

OpenRCT2 build

OpenRCT2, v0.4.3-313-gOda9693

Base game

RollerCoaster Tycoon 2

Area(s) with this issue?

This bug is a graphical glitch or error, This issue has to do with park objects and/or asset packs

Describe the issue

Recently I have noticed that, since the implementation of selectable/mix-and-matchable path types and railings, a Tile Inspector trick used in the past featuring queue path being made invisible yet maintaining path objects has become broken.

The trick involved used tile inspector to select three out of four directions, making the queue line invisible but maintaining the path features.
Old Behavior

When I opened a project recently, I noticed this behavior had changed.
New Behavior

Upon investigating older parks, I found that those parks (many which were pre-.park format) had developed this issue retroactively. It's even visible in the official OpenRCT2 title sequence (Ancient Worlds).
Opening
AW New 4

Steps to reproduce

  1. Open any of the attached parks or any park that had used this method in the past.
  2. Find an instance of the technique used; in the case of Ancient Worlds this is clearly visible at the entrance and the boat docks near the entrance.
  3. Note that there is now queue railings where there once was nothing.

Old:
AW Old
New:
AW New 1
AW New 2

Attachments

AW New 3
HH New
Marblehead New
EG New 3
SG New
AW New 4

References.zip

@ArcticX9 ArcticX9 added the bug Something went wrong. label Feb 26, 2023
@spacek531
Copy link
Contributor

spacek531 commented Feb 26, 2023

The queue railings are likely caused by an update that allowed queues to have forks in them. The solution would be to import queue paths like this as invisible from sv6 and park files before this update.

@Gymnasiast
Copy link
Member

Yes, this wouldn't be difficult to fix. I actually employed a solution like that for the steep log flume bits, so it shouldn't be difficult to port. Do note that SV4 would also need to be modified, as it's possible the same trick was used there.

@duncanspumpkin duncanspumpkin added the regression An issue that was made since the last release. label Feb 27, 2023
@duncanspumpkin duncanspumpkin added this to the v0.4.4 milestone Feb 27, 2023
@spacek531
Copy link
Contributor

I'll take this bug.

@spacek531
Copy link
Contributor

will be fixed by #19538

duncanspumpkin added a commit to duncanspumpkin/OpenRCT2 that referenced this issue Mar 14, 2023
This is to prevent existing parks from changing their behaviour
duncanspumpkin added a commit to duncanspumpkin/OpenRCT2 that referenced this issue Mar 22, 2023
This is to prevent existing parks from changing their behaviour
duncanspumpkin added a commit to duncanspumpkin/OpenRCT2 that referenced this issue Mar 22, 2023
This is to prevent existing parks from changing their behaviour
qwzhaox pushed a commit to qwzhaox/OpenRCT2 that referenced this issue Apr 10, 2023
…enRCT2#19644)

* Fix OpenRCT2#19503. Hide 3+ queue junction railings behind a flag

This is to prevent existing parks from changing their behaviour

* Clang format

* Bump version numbers. Update changelog

* Update text
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something went wrong. regression An issue that was made since the last release.
Projects
None yet
Development

No branches or pull requests

4 participants