X7123M3-256

Well, if the length of the cars is indeed the issue, then reducing it should fix it, so that's the first thing I'd try. And if that works, you can submit a PR to the object repository to fix the issue. If that doesn't work, I'd compare the vanilla go kart JSON with the expansion version and look for all the differences, then test them one by one. Code to support wider radius bends was added some time ago, it just needs someone to make a sprite for it. You can hack a wide turn onto the go karts and use scenery to build the track.

I would make the RCT1 version of the car have the RCT1 limits and leave the RCT2 version as it is. All of these rides are single car IRL.

Not really, I still have all the source files, but I just can't get the sprites to look good enough (and I doubt I ever will) so I haven't done much more with it since I made that layout (except to add large half loops, but that was a side effect of implementing them for the single rail track). I might come back to it, it would be a nice track type to have but unfortunately also one of the hardest to get right. I can upload the source code and sprites if you want them.

That's by design. It's intended to operate as a shuttle coaster, the circuit is only completed because the ride type requires it. The "Insectivore" and "Tailslide" designs also function this way.

This scenery group contains custom objects - do you have those objects installed or just the scenery group? If you don't have any objects that are in the group, this would explain why none show up when you select it.

Yeah, there was a bug that caused ratings to take 255x longer to calculate, it's fixed now.

This isn't a bug - setting a higher chain lift speed makes the reliability decrease more rapidly, so setting the chain lift speed much higher than normal has the side effect of making the reliability decay much faster than normal. You can use booster pieces instead, or disable breakdowns.

Huh? If you want to play OpenRCT2, then you obviously need to get OpenRCT2. In order for OpenRCT2 to work, you also need to have the game assets - which can be obtained from either the full game or the demo version. There's no such thing as "OpenRCT2 demo".

You can run OpenRCT2 using the demo version. There is no difference between the demo and the full version if you are using OpenRCT2, because OpenRCT2 only requires the assets and ignores the executable (which is the only thing that differs). There is another demo out there that is missing assets, but the one on this site is not, as far as I'm aware.

There is none. OpenRCT2 requires the RCT2 assets to run, it doesn't matter whether you get them from the demo version or the full version.

Those last screenshots you posted make extensive use of custom scenery - almost all of the objects you see there aren't included with the vanilla game nor OpenRCT2 (currently, OpenRCT2 only adds a small handful of objects to the base game). Unless you have downloaded a park that uses these objects, or visited a server that does, or downloaded the DAT files manually, you won't have these objects available. If you want to start using custom objects, the best place to start is by downloading a custom scenery workbench that has a selection of custom objects included (and pre-selected), as picking out the objects you want and downloading them all can get very tedious otherwise. New Element has a selection of custom scenery workbenches and a very large collection of miscellaneous custom scenery objects that have been created by different people over the years.

I will probably merge more new ride types in future, not sure in what order or exactly when as I've mostly lost interest in this for now. Currently, I have yet to produce any vehicle sprites of sufficient quality to merge, which is a problem. A diesel powered coaster would be an interesting opportunity to use the engine sound effect, but other than that it's far to obscure to be a priority for me (Not that this is necessarily a problem if the ride type is sufficiently interesting - the vanilla game includes such oddities as the Hooper reverser and Skytrak, and I have considered making an Arrow pipeline).

Yes, it would be a hard job. In order to make OpenRCT2 independent of the original game, all the original graphics and sound need to be replaced. This is what was done for OpenTTD, but with OpenRCT2 there are a lot more sprites - while vehicles in OpenTTD can have as few as 8 sprites, coasters in OpenRCT2 range from several hundred to many thousands of sprites. This has been talked about for a while, but there just aren't enough people currently working on it to expect it to be done any time soon - very little progress has been made so far. If you want to help make it happen, then check out the #open-graphics channel on the OpenRCT2 discord. No, no original code remains.

As I said, it's most likely in C://Program Files (x86) if you installed RCT2 with default options. If you can't find it, try searching your hard drive for "rct2.exe" or "g1.dat" as that should take you there. There's not much point me posting pictures of my RCT2 installation as I have it installed somewhere else. No, the disk version will work fine and there is no difference.

OK, now you are running OpenRCT2. The folder you need to select is the one where vanilla RCT2 is installed - since you're on Windows, it's probably somewhere in C://Program Files and will most likely be called "Roller Coaster Tycoon 2". You should see the rct2.exe executable (which is not used), and the subfolders "Data" and "ObjData". Searching for these files may help you find the folder.

OpenRCT2 does not ask for the CD, it asks for the path where RCT2 is installed. It looks like you are running vanilla RCT2 and not OpenRCT2.

The limits will be greatly increased as soon as the new save format is merged. In the current version of the new save format, you can have up to 256 ride/shop types selected, which is double the SV6 limit (this will likely increase further before the new save format is finished), and up to 5 times as many objects on the map. I think sprite counts can go up to 65536 (up from the old limit of 10000). The new save format will not completely remove the limits, and I don't think that's planned - they will just be increased to the point that that they're not a problem.

Your vehicle needs to be selected in the object selection in order to use it. It should not be necessary to build any additional rides. When it comes to creating the vehicle, you make the same sprites no matter how wide the turns are. Each vehicle has 32 angles of the car, and these same 32 sprites are used for both wide turns and small turns. This also means the default vehicles can handle wide turns already, they just lack the track sprites for it (the track will be invisible). The go karts don't just lack the sprites for these elements, they also lack the code to draw them properly. Because the go karts have multiple lanes, they use different drawing logic from the other tracked rides. If you want to make these elements work properly, a custom vehicle that has the sprites would be necessary but not enough - if you want to do this I suggest you talk to the guy who implemented the wide turns (I think he's on the OpenRCT2 discord). The main reason I don't recommend it is because his method is unnecessarily hard, and will actually lead to a worse result than doing things the easier way. For example, he tells you to find the camera angle by trial and error, instead of just telling you exactly what it is, and he suggests dithering the image to the wrong 256 color palette and then dithering it again (which will lead to worse colors than rendering in full color and dithering once). Also, some of his information is just wrong - for example, he says you can't change the spacing of the trains when there are examples of vanilla trains with different spacing. (I know AE didn't know how to change spacing, but really he should have known it was possible). Creating a custom ride - especially a simple one like a go karts vehicle - is not especially difficult for someone who is already familar with 3D modelling or is willing to learn. I recommend starting with the JSON format and Oli414's Blender plugin, because this is the easiest way to get a good quality result IMO (although Oli's tool still has issues and he doesn't seem to be working on it at the moment). If you want your object to be a DAT file, you can work on that later.

Download the objects and put them in your custom object folder There's instructions included with the download. Note that there are three versions of the train included in the ZIP file - two are standard DAT objects and one is a JSON object. I'm pretty sure you can place them all in your normal custom object folder, but the instructions will tell you to place the "official" object somewhere else. Note that you will need to be on the latest develop build to use these, as the single rail track is not available in release yet.

There's a limit of 10000 entities in total (including guests, staff, and coaster cars). There is also a limit of 256 rides on the map. These limits can only be removed with the new save format (which is still in an experimental stage), as SV6 files don't have any room for more data - although the new format isn't truly unlimited either, it just greatly increases the limits.

Do you have any ride in your park that has yet to return to the station? Ride stats are calculated sequentially, so if one ride never gets stats, nothing built after that will either. See if there are any other rides that don't have stats yet and try closing them - the mine train coaster may not actually be the cause of the problem.

It actually already is. But due to the interface being difficult to use on touchscreen, most people prefer Classic on mobile. Although OpenRCT2 currently still uses the same file format as vanilla RCT2, it adds a few new features that are not available in the original game (or Classic). In addition, the code has more sanity checks, so some hacks that are commonly used in OpenRCT2 will crash vanilla (or Classic). If you want your OpenRCT2 park to work in RCT Classic, here are the major things you need to avoid (may not be an exhaustive list): Corrupt Elements Invisible entrances Use of track elements not available in vanilla - this includes steep slopes on the junior coaster, inversions on the giga coaster, and boosters on any ride type that doesn't have them in Classic (note that if you want your park to work with vanilla RCT2 as well, then you can't use boosters at all). Use of unavailable track elements. In OpenRCT2, if you build a looping coaster (for example) and then change it to giga coaster using the arbitrary ride type cheat, the loops will be invisible, but still function. In vanilla RCT2/Classic, this will (generally) crash the game. Arbitrary ride types, in general, is fine to use but be careful of this when using it. The hybrid and single rail coaster types. Any of the RCT1 content (which I think is just the land/wall textures at the moment, but might include the vehicle types in the future).

Yes, there's a plugin for that. That's also something that could be done with a plugin, although I don't know if there's an existing plugin which does this.

They were made by @Spacek, you can get them from his download page on NE.

If I recall correctly, there's a binary out there somewhere but the source code was never released, so no way to merge it with the latest OpenRCT2 code. You might be able to find it and get it to run, but you'd be playing a three year old version of OpenRCT2.