OpenRCT2 / OpenRCT2/OpenRCT2

Spinning Wild Mouse brakes inconsistency

Open
#7,709 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion
Dominant language
C++
Stars
16.2k
Forks
1.9k
Avg merge
1d 20h
Merged PRs (30d)
80

Description

OS: Windows 10
Version: v0.2.0-101
Commit/Build:0oec3ccd

The brakes on Spinning Wild Mouse are inconsistent. The break values seem to be randomly changing between 2 values.
It's been like this in the past year and a half i've been playing on OpenRCT2.

Steps to reproduce:

  1. Build a Spinning Wild Mouse ride with 3x pieces upward into a downhill 3x pieces into a break.
  2. Complete the track.

If F is lesser than or equal to V then V = X
where:

  • F is the value of the brake set to,
  • V is the current speed the car goes into the brake track,
  • X is the new speed the car slows down to when running through a brake of F value.
example:

A Spinning Wild Mouse car (1 car/train) is running on a Hyper Twister track.

  • F := 28 km/h
  • V := 37 km/h
  • then X is either 19 km/h or 27 km/h

A Giga Coaster car (1 car/train) is running on a Spinning Wild Mouse track.

  • F := 28 km/h
  • V := 37 km/h
  • then X is either 19 km/h or 22 km/h

I don't know if this is a bug or it was intended.

Screenshots / Video:
spinningwildmousebreak0
spinningwildmousebreak1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the listed Spinning Wild Mouse setup on Windows 10 and compare the brake outcomes for the two example cars and tracks. Trace the brake-speed calculation used during the run; the issue is done when the inconsistent values are explained and corrected or confirmed as intended, with a regression check for the reported cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.