-
Notifications
You must be signed in to change notification settings - Fork 1.7k
SV6 Ride Structure
The SV6 ride structure is the same number of bytes as the SV4 format, but varies slightly from the ride structure in RCT1. Here is everything we know about it. Note, the canonical source of truth for this information is the code in src/openrct2/ride/Ride.h
.
The original RCT Technical Information Depot has been updated and relaunched. There is additional data about this structure (updated in August 2014) at tid.rctspace.com.
It is 608 bytes long. Addresses listed here are hex addresses. Leave a gap in between non-contiguous data.
-
000: ride type
-
001: subtype - a pointer to static information about the ride. For example, the data represented here would be for "Log Flume 7" in your park, and the subtype would point to static information about log flumes, for example the maximum height.
-
004: Ride mode index, where the possible ride modes are described in the enum here for example, the number "5" would correspond to "Boat hire mode"
-
005: Colour scheme type. There are three possible color schemes, outlined in the following enum.
-
006-046: A 2-byte array of length 32, containing data about car colours for the ride.
-
049: status. 0 = closed, 1 = open, 2 = test
-
052-05A: 2-byte array of length 4, having something to do with ride excitement, nausea, etc. 0xFFFF if it is empty/unused
-
06A: a 4 byte array of entrance map coordinates (probably)
-
0E4-0F0: Not sure what is actually here, but in at least one case these values are treated as 4-byte values, summed, shifted right 4 bits, and then allowed to max out at 700.
-
130-131: age (16 bits)
-
132-133: running cost
-
140-141: excitement
-
142-143: intensity
-
144-145: nausea
-
146-147: reliability
-
1B4-1B7: profit
-
1B8: an array of 4 bytes, each an integer representing different data about the queue time.
-
1CE: guests favorite
-
1D0-1D2: flags pertaining to the ride
- bit 0 = train(s) on track
- bit 1 = tested;
- bit 2 = test in progress;
- bit 3 = don't show raw stats;
- bit 4 = pass through station without stopping;
- bit 5 = On-Ride photo;
- bit 6 = ?;
- bit 7 = broken down;
- bit 10 = crashed;
- bit 12 = ever been opened;
- bit 13 = play music;
- bit 14 = construction/demolition prohibited (indestructible ride);
- bit 15 = demolition prohibited (used when there are indestructible track pieces)
- bit 17 = cable lift
-
1F8, 1FA, 1FC: coordinates of cable lift hill's start position, 1FC is the elevation. see the copy at
0x6C5716
-
200-203: 4 8-bit integers representing queue length
Additional data about rides is stored in an 8 byte wide struct starting at 0x97D218
. Byte 1 is the ride's minimum clearance.
See https://x123m3-256.github.io/RCT2/rct2data.html for more information.
- Home
- FAQ & Common Issues
- Roadmap
- Installation
- Building
- Features
- Development
- Benchmarking & stress testing OpenRCT2
- Coding Style
- Commit Messages
- Overall program structure
- Data Structures
- CSS1.DAT
- Custom Music and Ride Music Objects
- Game Actions
- G1 Elements Layout
- game.cfg structure
- Maps
- Music Cleanup
- Objects
- Official extended scenery set
- Peep AI
- Peep Sprite Type
- RCT1 ride and vehicle types and their RCT2 equivalents
- RCT12_MAX_SOMETHING versus MAX_SOMETHING
- Ride rating calculation
- SV6 Ride Structure
- Settings in config.ini
- Sizes and angles in the game world
- Sprite List csg1.dat
- Sprite List g1.dat
- Strings used in RCT1
- Strings used in the game
- TD6 format
- Terminology
- Track Data
- Track Designs
- Track drawers, RTDs and vehicle types
- Track types
- Vehicle Sprite Layout
- Widget colours
- Debugging OpenRCT2 on macOS
- OpenGL renderer
- Rebase and Sync fork with OpenRCT2
- Release Checklist
- Replay System
- Using minidumps from crash reports
- Using Track Block Get Previous
- History
- Testing