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

Researching new ride type results in "New vehicle now available" message instead #13236

Closed
SpartanFrederic104 opened this issue Oct 18, 2020 · 3 comments
Labels
bug Something went wrong.

Comments

@SpartanFrederic104
Copy link
Contributor

SpartanFrederic104 commented Oct 18, 2020

OS: Windows 10
Version: 0.3.1
Commit/Build: 59d785e

I have noticed that in some scenarios, when a new ride type is researched, it does not even send me a message saying "New ride/attraction now available: [ride name]", but instead "New vehicle now available for [ride name]: [vehicle name]".

EDIT (2020-10-19 18:12 PST): tupaschoal has confirmed that the research window also shows the wrong info.

Steps to reproduce:

  1. Load up the scenario file shown in the screenshot below and wait until March 30, Year 1.
  2. The Air Powered Vertical Coaster will be researched, but the game will think you've researched a new vehicle type instead of a new ride type. Researching the Looping Roller Coaster (which comes afterwards) still correctly results in the "New ride/attraction now available: Looping Roller Coaster" message though.
  3. I have also been able to reproduce this by researching a new ride type, modifying the inventions list to move said ride type back to the "Items to invent during game" list, and then having said ride type be researched again. This can be done with any scenario, not just custom ones.

Screenshots / Video:
Extreme Heights 2 2020-10-18 15-00-52
Note that researching the Air Powered Vertical Coaster in the original Extreme Heights scenario still brings up the correct "New ride/attraction now available: Air Powered Vertical Coaster" message.

@tupaschoal
Copy link
Member

You don't even have to wait for March 30th, when the researched stuff is defined in the research window it already shows the wrong info:
image

I've bisected it with the releases and it's a regression from v0.1.1 to v0.1.2

@tupaschoal tupaschoal added the regression An issue that was made since the last release. label Oct 20, 2020
tupaschoal added a commit to tupaschoal/OpenRCT2 that referenced this issue Oct 20, 2020
@Gymnasiast Gymnasiast added bug Something went wrong. and removed regression An issue that was made since the last release. labels Oct 21, 2020
@Gymnasiast
Copy link
Member

Changed the label. The regression label is meant for issues that have regressed since the last release, which this hasn't.

Also, note that this is not technically the same bug as the one in 0.1.2, even though the results are nearly identical.

tupaschoal added a commit to tupaschoal/OpenRCT2 that referenced this issue Oct 28, 2020
@SpartanFrederic104
Copy link
Contributor Author

SpartanFrederic104 commented Nov 2, 2020

Funtopia 2020-11-02 10-08-22
Can confirm this bug also occurs on the RCT1 scenarios. Still occurs in 0.3.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something went wrong.
Projects
None yet
Development

No branches or pull requests

3 participants