Official objects for OpenRCT2
License: Creative Commons Attribution 4.0 International
Contains objects from RollerCoaster Tycoon 1, RollerCoaster Tycoon 2 and their expansion packs. For the main development and codebase of OpenRCT2, visit OpenRCT2/OpenRCT2.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
This is not a requirement, but it would be nice if the language_load.py and language_dump.py scripts could spit out the target language completeness when compared to the fallback language.
There's no info I can find about OriginalId, what the 3 sections mean, what the values in those sections mean, etc.
I've been eyeing having to make a json object, most of the parts are easy to figure out but the metadata is very opaque.
A while ago @Gymnasiast (I believe) mentioned importing RCT1 vehicles. There currently is the ability to add this to OpenRCT2, although it is not in an ideal state because there will be many sprites wasted.
This branch solves the waste of sprites for the most part, and is the branch against which the current vehicles are created:
https://github.com/spacek531/OpenRCT2/tree/frames-rotation-count-part-1
This vehicles repository:
https://github.com/spacek531/RCT1Vehicles
The vehicles in the repository could be merged with this repository after some tasks are complete.
Although it is relatively simple to load appropriate RCT1 vehicles only when necessary, users loading a park that has been touched originally by a linked version of OpenRCT2 will not see any sprites. This may or may not be an issue.
Most need the regular door sound, but brown and grey sandstone need the portcullis sound.
To make it even easier to find the last remaining objects that require translation, we should add an option to language_load.py that allows for only dumping untranslated objects.
Flipping the order will make it available for mini coaster again, I think.
RCT1 includes reversed looping and reversed 4-seater wooden coaster cars, which are not available in RCT2. This project would be creating new .json objects which use the RCT2 sprites to create official reversed versions of select trains.
@frutimax points out that some parks run their B&M inverted coasters in reverse for special occasions, this could be included in this project.
A reversed version of the corkscrew coaster would not go too remiss, as Arrow's shuttle coaster runs half the train backwards.
Thoughts?
There are 4 fences from RCT1 that are not in RCT2, Being three versions of the brown wooden fence and an odd height abstract fence. I believe these all should be implemented for better RCT1 accuracy.
The closest RCT2 counterparts to the brown wooden fences are not the right color as they are much darker and the abstract fence is a different height to it's closest rct2 counterpart, left are the RCT1 fences and right are the RCT2 fences.
I have additionally already ported all of them to json objects as seen above and made the abstract fence fully recolorable to make it more in line with the rest of the rct2 abstract fences so the objects are ready should we decide they should be implemented.
A couple of vehicle names/descriptions are of low quality or don't make sense. Most vehicles have “train” or “car” in their name, but some vehicle names and descriptions are weird or just outright wrong.
Here I present the problematic strings (in en-GB) and suggest changes. Please post what you think of my suggestions and if they are OK.
1:
Small flower shaped dinghies powered by a centrally-mounted motor controlled by the passengers
→ Source: rct2.tt.flwrpowr.json
→ I thought dinghies are boats and need water, but this ride doesn't look like it has any water.
→ Suggestion: Small flower shaped dodgems powered by a centrally-mounted motor controlled by the passengers
2:
Roller coaster cars in the shape of lizard carnival floats
Roller coaster cars in the shape of butterfly carnival floats
Roller coaster cars in the shape of frog carnival floats
→ Source: rct2.ww.crnv*.json
→ These are cars for car rides, not for roller coasters!
→ Suggestion: Cars in the shape of lizard/butterfly/frog carnival floats
3:
Carnival Float Ride - Butterfly Cars
Carnival Float Ride - Frog Cars
Carnival Float Ride - Lizard Cars
→ Source: rct2.ww.crnv*.json
→ These vehicle names are a mouthful, let's shorten them!
→ Suggestion: Carnival Butterfly/Frog/Lizard Cars
4: These rollercoaster trains/cars should be renamed to become a proper vehicle name:
Bullet Coaster
Source: rct2.ww.bullet.json
Suggestion: Bullet Trains
Dragon Coaster
Source: rct2.ww.dragon.json
Suggestion: Dragon Trains
Limousine Rollercoaster
Source: rct2.ww.cadillac.json
Suggestion: Limousine Trains
Seals Coaster
Source: rct2.ww.seals.json
Suggestion: Seal Trains
5: Also consider renaming these:
Jaguar Ride
Source: rct2.ww.jaguarrd.json
Suggestion: Jaguar Cars
Sloth Ride
Source: rct2.ww.sloth.json
Suggestion: Sloth Trains
Chinese Dragonhead Ride
Source: rct2.ww.sloth.json
Suggestion: Chinese Dragonhead Dodgem Cars
Flower Power Ride
Source: rct2.tt.flwrpowr.json
Suggestion: Flower Power Dodgem Cars
6:
Raptor Racers Coaster
Source: rct2.tt.raptorxx.json
Suggestion: “Raptor Racers” or “Racing Raptors”
As requested by Gymnasiast, I have made a list of all RCT2 expansion ride objects that currently have errors here on GitHub to make it easier to keep track of these errors. The errors have check boxes listed to denote whether or not the issues have been currently fixed.
UPDATE (2024-02-09): Some of the issues originally listed here are now gone as they have since been fixed.
minCarsPerTrain is also inconsistent with bmrb: should be 5 instead of 4minCarsPerTrain with Twister Trains (rct2.ride.bmsd.json) and Stand-up Twister Trains (rct2.ride.bmsu.json): should be 5 instead of 4
OS: Windows 8
Version: 0.2.5
Commit/Build: d64b73c
On the Water Coaster, both the Flying Boats vehicles and the Trilobite vehicles falsely claim to seat 16 passengers per boat, when like all the other vehicles for the Water Coaster, they actually seat 6.
Default Coaster Boat vehicles and Manta Ray vehicles both display the correct number.
These two vehicle types also have a much more verbose description, which is probably related.
(First reported on this thread on reddit)
Not sure if this is a vanilla bug or not. My vanilla install is broken.
Steps to reproduce:
Screenshots / Video:
Sand (brown) is tagged as rct1 and rct2 while sand is tagged as only rct2. This is an error.
This bit of code is not handling the peep loading positions correctly for rides with 16bit loading positions.
https://github.com/OpenRCT2/objects/blob/master/tools/objexport/PropertyExtractor.fs#L430-L440
Loading positions counts come in two different forms. 8 bit and 16 bit.
First you read the 8bit count.
If the 8 bit count is 255 then you load the 16 bit count.
Loading positions are then split into 3 different types: offsets, waypoints_1, waypoints_2.
Offsets are an array of sint8 of size count.
Waypoints_1/2 have an initial byte that indicates if it is type 1 (if its 0) or type 2 (anything else).
After this there is an array of 3 waypoints comprising of x, y coordinates as sint8's.
There is then a blank waypoint (16 bits).
The above is then repeated for (count - 1) / (2 * 4).
Windows 10, 64 bit
v0.3.4.1 4155bf9
Bengal tiger trains (Heartline twister car from one of the expansions) have a weird graphical glitch when going through turns. Normally you wouldn't see this as heartline twister trains don't go through any turns, so it's only visible if you put them on a different track type, like in the following example:
Majora found the sprite image that's the culprit:
Not sure if this should be fixed, just documenting it here in case anyone wants to fix it ;)
No response
No response
There are currently 3 python scripts for translation handling in this repository:
language_clean_patch.pylanguage_dump.pylanguage_load.pyAll of them relate to dumping or loading translations from and to objects, and thus have some common code, such as the supported languages.
Ideally they should be packaged together, so we can extract bits of code to reuse in all of them and also so that their coupling can be evident
The Chinese Dragon object appears to render the different viewpoint sprites in the wrong order when rotating the game world.
Originally reported here: https://forums.openrct2.org/topic/5017-chinese-dragon-object-rotation-issue/?tab=comments#comment-24113
We could create an open cars version of the american style steam trains by using sprites from AML1.DAT and NRL.DAT, i think this would make for a nice addition to the game to make the american steam trains more consistent with the standard steam trains.
OS: Windows 10
Version: 0.2.5
Commit/Build: b5bcd0c
This has been an issue even as far back as the first release of OpenRCT2 or even RCT2 vanilla. The Manta Ray Boats from the Wacky Worlds expansion for the Water Coaster refuse to slow down greatly on water sections, just speeding through them as though they're normal steel track pieces, even though the other vehicle types (Coaster Boats from the base game, and Trilobite Boats and Flying Boats from Time Twister) do slow down. I looked in the json file for the Manta Ray Boats and it also doesn't have a "playSplashSoundSlide" flag. I suggest having this vehicle changed so that it not only actually slows down on water sections and plays a splashing sound effect, but also has the "hasShelter" flag activated (which should also be activated for the Flying Boats vehicle type, which should even get a description fix so that it mentions having a capacity of 6 passengers per boat, not 16).
Despite this bug, the Manta Ray Boats still do not get an excitement rating penalty that the Water Coaster gets for not having a water section.
Steps to reproduce:
Build a water coaster (any design, preferably Splashtastic).
If the Manta Ray Boats are available, select them. Otherwise, go to Object selection → Ride Vehicles/Attractions → select the Manta Ray Boats (it is at the bottom if you are sorting alphabetically by ride type from A to Z).
Build the exact same design but without the Manta Ray Boats.
The Manta Ray Boats version of the design will end up with higher stats due to lack of speed reduction on water sections, resulting in higher G forces, especially lateral Gs, which can potentially jeopardize the coaster's intensity rating.
Alternatively, you can start the default Wacky Worlds scenarios "Australasia - Ayers Rock" or "Australasia - Fun at the Beach". For the former scenario, you already get a water coaster. For the latter scenario, you need to open the water coaster that's on the far side of the park.
Screenshots:
In this screenshot, you can see the exact same design built four times, with each copy using the four available Water Coaster vehicle types,
In this screenshot, you can see that the Manta Ray Boats refuse to slow down on water sections, which results in higher G forces, which can be especially dangerous as it can trigger a very high (or even extreme) intensity rating due to heightened lateral G force ratings. The Manta Ray Boats are still traveling at 33 mph at the last curve even as the other boat types slow down to 23.
RCT2 simply refunds 3/4 of the original price when demolishing a banner.
The two possible solutions are:
removalPrice field and fill it in the object toolremovalPrice field and keep current behaviourThe pieces of code that handle the updating of translation strings in language_load.py should be extracted so that it can work given a fallback language and a target language.
This will later allow it to be generalized to handle all languages
https://github.com/OpenRCT2/objects/blob/master/tools/objexport/PropertyExtractor.fs#L655
Above line should have been a right shift.
All door sounds need to be looked at and reset back to their correct value. Could possibly just do a re-export as I'm not sure if there are many doors.
In order to have Ride Groups show better descriptions, the object format should support two names: one to show in the New Ride window and one to show in the vehicle tab. An example would be the Floorless Roller Coaster: it will still appear as 'Floorless Roller Coaster' in the New Ride window, but (after the name is corrected) will show as 'Floorless roller coaster train' in the vehicle tab.
On the initial json creation, the original name can be used for both.
I've noticed there are 3 Python scripts but and according to #79 they could be used to report missing translations. My goal would be to get a list with missing translations for pl-PL and a list with current ones with reference English strings.
If it's already possible then please tell me how. I thing it would be a good idea to document it also in README.md
Calling @tupaschoal as it seems you are the author of the mentioned scripts.
Would be great if objexport <path_to_dir_or_dat_file> could be implemented.
Example usage:
objexport /path/to/dir /output/dir
would export all dat files in the specified directory (as it currently does)
objexport /path/to/datfile.dat /output/dir
would export only the specified dat file.
Extracting the images is currently possible with openrct2 itself. I think it would fit the scope of objexport to support this as well.
Something like
objexport <directory_or_dat_file> <output_dir> -images
Bonus points if it is able to generate a .gif for animations.
Refer to OpenRCT2/OpenRCT2#16271 for context.
Not sure what the procedure is for adding new official objects so I'll upload the file here and start it as an issue.
Korean is a known one and could be left out.
But AFAIK, zh-CN and zh-TW are used.
The naming of new paths are inconsistent which looks sloppy.
Naming recommendations:
(What you could also do is put Footpath & Queue in front of the names so Paths & Queues are seperated.)
Ash Footpath (Rounded)
Ash Footpath (Square)
Brown Tarmac Footpath (Stairs)
Brown Tarmac Footpath (Sloped)
Brown Tiled Footpath
Circuit Footpath
Circuit Queue
Crazy Paving Footpath (Sloped)
Crazy Paving Footpath (Stairs)
Dirt Footpath (Square)
Dirt Footpath (Rounded)
Green Tarmac Footpath (Stairs)
Green Tarmac Footpath (Sloped)
Green and Brown Tiled Footpath
Grey Tiled Footpath
Invisible Footpath
Mosaic Footpath
Pavement
Pavement Queue
Blue Queue (Stairs)
Blue Queue (Sloped)
Green Queue (Sloped)
Green Queue (Stairs)
Red Queue (Stairs)
Red Queue (Sloped)
Yellow Queue (Stairs)
Yellow Queue (Sloped)
Rainbow Footpath
Rainbow Queue
Red Tarmac Footpath (Stairs)
Red Tarmac Footpath (Sloped)
Red and Brown Tiled Footpath
Road
Rocky Footpath
Tarmac Footpath (Stairs)
Tarmac Footpath (Sloped)
Wooden Footpath
Balustrade
Bamboo Railings (Black)
Bamboo Railings (Brown)
Bamboo Railings (Yellow)
Circuit Board Railings
Concrete Railings
Concrete Railings (Green Supports)
Invisible Railings
Invisible Railings with Circuit Board Queue Banner
Iron Railings
Jungle Railings
Medieval Railings
Rainbow Railings
Space Style Railings (Grey Supports)
Space Style Railings (Red Supports)
Wooden Railings
I'll gladly do this work for you guys if you want me to, just have to tell me and I'll make a zip file for y'all with the edited texts. Just let me know what format you want to use.
Currently the language_load.py and language_dump.py scripts require a target language to be supplied. We need to make it work on all languages, with a --all switch.
This needs to be mutually exclusive with the -l option, so remember to use:
group = parser.add_mutually_exclusive_group(required=True)Most, if not all, vanilla wall objects are only able to be placed on flat land.
This has some limitations to what they can all be used for (ie. as fences on sloped tiles, lining the roofs without sides). Implementing this wouldn't necessarily be difficult as editing the flat walls to create sloped sprites isn't too difficult:
Alternatively, perhaps this task could be automated. The .parkobj objects from the original objects seem like they use the sprites from the original DATs so I'm not sure how exactly this would look adding additional images to those.
When loading back the translations with language_load.py it will often change the formatting of the JSON, as well as the newly translated strings. I've pasted the outputs below, using different encoders:
Original JSON file
Updated JSON file with default JSON encoder
Updated ´JSON file with less verbose encoder
My idea is to either stop using encoders or investigate and improve the "less verbose encoder" to make sure we don't change the formatting too much or at all.
The "less verbose version" is what language_load.py currently uses. It does a good job on the strings, but makes it too verbose for other things. We either have to fix/modify it, or make sure we use one that is better suited.
OS: [Arch Linux
Version: 0.2.4-95
Commit/Build: 40e22eb
Handymen cut the grass one way, and the cut grass is rendered in a way that indicates they mowed in a different direction
Steps to reproduce:
Dump file
Screenshots / Video:
Save game:
I'm working on packaging openrct2 for Debian. This "objects" repo is a dependency for the game, but is missing any licensing information. Looking through what's here, it appears that there's essentially two different types of resources:
Especially for the included artwork, license information is needed. Ideally there would be links to the original source(s) with that information.
Please add some sort of license file to cover the content in this repo, both the JSON files as well as any artwork.
Currently the language_load.py and language_dump.py scripts require a filename to either be read or written to. In order for them to be generic and work for all languages, we would need --input_dir or --output_dir, so we can write multiple files.
This needs to be mutually exclusive with the file option, so remember to use:
group = parser.add_mutually_exclusive_group(required=True)Requires modification in OpenRCT2 to allow 16 frames per rotation first.
Ported:
Designs to port:
Up for discussion:
I am trying to load the Catalan localisation with:
python3 language_load.py -l ca-ES -i ../Localisation/objects/ca-ES.json -v
in my local copies of "objects" and "Localisation" repositories.
This is the result
As you can check, only the objects with ids *.station.* find the correct translation. Other objects have different ids in the *.json files in "Localisation" and "objects" repositories.
As an example, "'Goliath' Sign" has these ids:
In Localisation: "rct2.glthent"
In objects: "rct2.scenery_large.glthent"
As they have different ids, language_load.py fails to load the translation. I expected all strings would have been loaded. I don't know whether I am missing something here and should run some other script first.
The music objects, and possibly some other types (small/large/wall scenery, banners and path items) lack rct1/rct1aa/rct1ll as a sourceGame. It be nice to add this to make the information and filters of the Object Selection correct.
Or at least they are on the original, plus WW and TT. I don't think we need to have both flags, one will do.
If you enable all RCT2+WW+TT dodgems and open the “build ride” window, the ride names will appear as:
So yeah, the ride itself has the word “cars” in it. If you build one of these, the ride will be named like “Fighting Knights Dodgem Cars 1”.
What is a proper way to fix this? I have 2 possible answers:
Version 0.2.3
OpenRCT2 split up five ride types some time ago. This change has not yet been applied to this repository, so currently OpenRCT2 still converts it on the fly. The objects in question should be modified.
Also, it would be a good thing if the DAT conversion script could be modified to take the new ride types into account.
The pieces of code that handle the extraction of translation strings in language_dump.py should be extracted so that it can work given a fallback language and a target language.
This will later allow it to be generalized to handle all languages
OS: Windows 10
Version: 0.1.3
Commit/Build: 617372f
The hoverboard cars from Time Twister use the wrong sprites while traveling diagonally up the chainlift, and at the start of a diagonal drop. You will suddenly see them move sideways, and at an angle.
Also happens in vanilla RCT2 (with Time Twister).
Please add them.
I have, after a lot of painstaking work, imported the beta RCT1 grass texture from development screenshots and ride thumbnails into an OpenRCT2 terrain_surface object. As an object that was part of the RCT1 series officially, although never released, I think it should be added to the OpenRCT2 official objects like the other DLC objects.
I've merged my vehicle update branch on develop that has labelled the remaining var's in the vehicle object. I've also labelled some of the flags. This information is still required to be added to this.
Currently the language_dump.py only uses the fallback_language to check the progress of the translation and to dump when there is none available. It should always print the reference translation next to the actual key to ease the translators experience
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.