X7123M3-256

The boat ride allows you to build a track for the boats, it always has done even in vanilla. You don't need any hacks for this, you just build it like any other tracked ride. It only allows single tile turns and straights though, so if you want wider turns then you do have to merge it or put it onto a different track.

The only one on the list that opened before RCT2 was released is Volcano: The Blast Coaster. RCT2's ride selection is getting rather out of date; there's lots of old ride types from defunct manufacturers that aren't commonly seen these days (in fact, I think the majority of default rides fall in this category), while many of the most commonly seen ride types today are missing (Most Intamin rides are missing, there's nothing at all from Gerstlauer). Indeed, I had a look through the "new for 2016" rides on RCDB to see how many are actually in the vanilla game. Of 198 coasters, I found 4 Reverchon Spinning Coasters 2 Zierer Junior Coasters 2 Intamin Mega Coasters (albeit with new track and trains that are not in the game) 1 B&M Flying Coaster 2 Schwarzkopf Looping Coasters (one relocated, and one is a travelling coaster, it moves every year) 1 B&M Mega Coaster (There's also an unknown B&M that may be a mega coaster) 5 Vekoma Boomerangs (whether this is in the game is debatable; the corkscrew train is an Arrow, but even in the default scenarios it's used as a Vekoma, and many older Boomerangs did run Arrow trains) 1 GCI Wooden Coaster 1 B&M Dive Coaster (nothing like the version that's depicted in the game though) 1 B&M Sitdown Looping Coaster (relocated) That's about 10% of the total. The low percentage isn't necessarily meaningful - a lot of the rides are kiddy coasters or Chinese knock-offs, and wouldn't really add much to the game if they were included. For the sake of comparison, I decided to look at 2002, the year the game was released: 2 B&M Inverted Coasters 2 B&M Floorless Coasters 1 Arrow Mine Train (Relocated) 3 Zierer Junior Coasters 1 RCCA Wooden Coaster (runs Intamin trains, so you could argue this shouldn't be included) 4 Reverchon Spinning Coasters 2 B&M Flying Coasters 1 Intamin Mega Coaster 1 Schwarzkopf Looping Coaster (relocated) 2 CCI Wooden Coasters (One does not run PTC trains so probably shouldn't be included) 2 Vekoma SLCs 5 Mack Wild Mouse (that the game's wild mouse is Mack is an assumption based on the fact that Flying Dutchman Gold Mine is a prebuilt - if it was intended to be a generic wild mouse, there would be a few more to include) 1 Vekoma LSM Coaster (as with the Vekoma boomerang, you could argue this shouldn't count) 1 B&M Mega Coaster 2 Schwarzkopf Jets (relocated) 1 Vekoma Giant Inverted Boomerang 1 Intamin Impulse Coaster 1 Arrow 4th dimension coaster (the only Arrow on the list not relocated) That's about 28% of the total for that year. It also represents a much larger percentage of the "major" ride installations (i.e not kiddie coasters or rides by obscure manufacturers). There weren't many "major" rides built in 2002 that aren't represented in the game; notable is Xcelerator and Winjas, as these ride types would go on to become fairly common. This isn't necessarily the best comparison; aside from including a bunch of uninteresting rides, it would be more informative to look at which rides a typical park has rather than which were being built new at the time. By the time the game was released, Arrow, TOGO, and Schwarzkopf were out of business, but at that time there were still quite a few of their rides around, so it still made sense to include them. Conspicuously missing is anything from Gerstlauer or Maurer. Also interesting is that almost all the B&M models are still being built (except the stand-up). The same can be said of the Vekoma Boomerang, but for a very different reason.

That is all it did. But it's the only other RCT2 mod I can think of. I'd be very interested if there was one that got as far as changing the file format.

You can't build rides in the scenario editor. To create a scenario with prebuilt rides, you save the scenario without rides, then add the rides and use "convert save game to scenario to make it into a scenario again. Then you can delete the original scenario.

Could it have been RCTModified? I don't know if that changed the file extension though.

Night time lighting is in a PR, you can find it here. You cannot add stuff like that with an object. The sea turtles are an expansion pack object and the rest are all custom objects created by players of the game.

Where are you getting this information from? Because it sounds to me like you're just looking at the sprites these rides have. If that's the case, then it does not provide evidence these rides were ever going to have these things. RCT2 uses a 16 bit bitfield to specify which sprites are present in a file. A ride file may have thousands of sprites. Therefore, they are divided into groups, each corresponding to one bit in the bitfield. If the ride needs one sprite from a group, it has to have all the sprites in that group. Flat slopes. This includes a 32 frame rotation of the car on level ground. All tracked rides have this even if they don't have turns, because they need this available to display the car on level track. Gentle slopes. This also includes a rotation of the car; any ride with sprites for gentle slopes also has sprites for curved slopes (except the Spinning Wild Mouse, for some strange reason) Steep slopes. Again, this includes a rotation of the car so every ride with steep slopes can do curved steep slopes as well (but not diagonal steep slopes). Vertical slopes. Again, there's a full rotation of the car, and this group also includes sprites for loops, so any ride with verticals has loops. Diagonal slopes. Diagonal slopes have different angles to the non-diagonal pieces, so all diagonal slope pieces are in this group. Banked turns. Includes sprites for banked turns, on level track. Inline twist. Includes sprites for inline twists, but not those already included with the banked turns (as far as I can tell, every ride with inline twist sprite has to also have banked turns in order to not glitch). Sloped banked transitions. Includes sprites for a transition between an unbanked slope and banked level track, and vice-versa. Diagonal banked transitions. Same as previous, but for diagonal track. Sloped banked transitions. Includes sprites for a transition between an unbanked slope piece and a banked one. Sloped banked turns. Includes sprites for banked curved slopes. Banked slope transitions. Includes sprites for a transition between banked level track and banked sloped track. Corkscrews. Sprites for corkscrews. IIRC to properly show a corkscrew, a ride should also have banked sloped turns as these sprites are also used. Restraint animations. Includes an animation of the restraints opening and closing, from four angles. This leaves one sprite group, which is only used on the elevator, and I still haven't figured out what it's for. You can see from this that a lot of coasters have to have more sprites than they use - the Air Powered Vertical Coaster and Reverse Freefall Coaster both have way more sprites than they use, but they do use at least one sprite from each group. It doesn't mean they were originally going to have those track pieces - the extra sprites could have been left blank, I suppose, but so far the only coaster I've seen that does this is the multidimensional coaster. The others all just include the extra sprites. But, on the subject of stuff that didn't make it into the final game, this page might be of interest, though it is RCT1, not RCT2.

821+1523=2344, so this is how many objects you should have. If it's showing 2100, it's possible that you have duplicates (though I'm not sure how you'd end up with that many duplicates), or perhaps more objects have been installed since you saw that message.

Those rides do not have sprites for those elements. This would require replacing all the default tracked rides with new ones.

Defies the laws of physics Maybe you could build it? Loading might be a problem Is just going to fall over. You probably wouldn't get as far as actually finishing building it. Needs a lot more support work. This is basically a flying elephant ride on steroids. Looks kind of fun. I guess you could build it ... but why? It just looks hideously complicated and it's not clear what it's supposed to accomplish. Also, you're going to have guests suspended upside down while you load each car, and if those arms fail to retract in time the result would be catastrophic. The car surrounds the entire track... so no place for support work. There don't appear to be any supports either, it would just fall down. But I love the idea of an intense vertical launch into a coaster layout - that needs to be a thing. That looks awesome, I want to ride it. Even though I'm not sure how you'd make it work. Would probably be more practical as a double pendulum rather than triple, with only the main joint powered. Incidentally, I had a similar idea for a double pendulum based swing ride a while ago. The double pendulum exhibits chaotic dynamics, so there's the potential for some quite interesting ride cycles. Drive the motors to swing the arm over the top at high speed, then let the chaos commence: You could periodically re engage the motors to stop the main arm at the bottom of it's travel and have the secondary arm swing over the top at high speed. With active feedback you could balance the two arms at the top of the ride, apparently defying gravity, then let them fall again. It would pull like 5Gs, but it should be within the safe range... just. Of all the rides in the video, I think this has the most potential.

I always thought it was dynamite as well. But no, it hasn't been changed. It's always been like this.

It's on the same page I linked above, but here's the direct link

It is uploaded now.

Go to https://github.com/OpenRCT2/OpenRCT2/issues and click "New issue"

I've now finished my Intamin LSM launch coaster (sometimes referred to as blitzcoaster) trains, and uploaded them here. These are the type seen on rides like Maverick, iSpeed, Nefeskesen. They also appear to be used on Intamin's vertical lift coaster (of which the only example is Fahrenheit). These aren't accelerator or looping coaster trains, though they do look quite similar at this scale. There are lots of variants of this train - a lot of the newer ones have lap bars in place of the OTSRs, and many of those that had these OTSRs have been retrofitted with alternative softer versions, so no coaster actually runs this exact train anymore. In addition, many of the trains have additional theming, and Taron's is completely custom. This is the first train I've done for which you have to use a hack to have a realistic layout - it either needs a hacked launch, or a hacked vertical lift. Anything else probably wouldn't be running this train, at least as far as I can tell. I am hoping that OpenRCT2 will at some point in the future add proper launch and inversion pieces, but the former would require a new file format. Here are some screenshots (a subset of the ones I put on the download page):

Object selection and invention list, and scenario parameters are in the debug menu. Editing land ownership/building on unowned land is "Enable sandbox mode" in the cheat menu. These are dropdowns, so you have to click and hold to see all options - people have failed to notice that in the past.

This is already implemented. Why do people keep submitting feature requests for stuff that already exists? Like, at least half of feature requests on this forum are for stuff that's already been done. This is also already implemented, along with the ability to build on land you don't own. Everything you can do in the scenario editor you can do in the game - including changing the park objective, invention list, object selection, land ownership, peep intensity preference, and toggling money on/off. I hardly ever use the scenario editor now - I have a single blank map with nothing selected, and start everything from that. Yes, they got rid of the "Six Flags" restrictions. I never did understand why they disabled editing of these maps in the original game.

A rhythm dancer ride is technically possible - but most flat rides aren't, so I never really looked into them, and I did not implement support for them in my renderer (it would probably be very hard to do so, as every one is a special case). Also, the choice of rides to model is largely dictated by what I can find suitable reference images for - if I can't find at least one diagram, it's very hard to get anywhere with it.

Yeah, I'm just finishing my next one off now. All that remains is to build a layout so I can take some screenshots of it, and then mess around with the lighting some more to decide if this is really the best I can get it, and then it will be uploaded either later today or potentially tomorrow now as I'm running out of time.

Downloads and screenshots for my rides are on this page. I will be aiming to get the Intamin LSM uploaded there later today, after I've finished tweaking the lighting to stop it looking oversaturated. Unrealistic rides are placed on this page instead - I did not bother uploading screenshots of these.

If you've recently got a virus, it is highly unlikely it came from OpenRCT2, as others have said. If you're basing this entirely on the warning from your antivirus, be aware that false positives are a thing and can be quite common, you may not have a virus at all. However, if you are concerned, build the game from source - it is much harder to get malicious source code into the reposititory and have it go unnoticed than if the binaries had been compromised, and you can inspect the source yourself to verify its integrity.

The image I had was sent to me by @Gymnasiast, already loaded into RCT2's internal format, so I don't know exactly what was done to create it. It was used as a preview image for a ride, and displayed fine in the object selection, but upon opening the ride selection window, the game crashed with an assertion failure, saying G1_FLAG_BMP was not set. All images in object files normally have this flag set, so I'd consider the image invalid, yes. All it took to fix the issue was to set the flag. If this is indeed the same issue I had (might not be though - it sounds similar but it wasn't exactly the same error message), it is likely caused by a broken object file. I'd try running with only vanilla objects and see if that works.

I had an assertion failure today because I had an image that did not have the LSB set in the flags (I think the only "images" that don't have this bit set normally are the palette entries). Could that be related to this issue perhaps?

Seriously, it will not work, you will corrupt game data. Just because the game doesn't immediately crash doesn't mean it has worked. The behaviour is completely unpredictable because it doesn't show up until the corrupted memory is actually used. I have had all sorts of things happen as a result of exceeding these limits, from window icons drawing outside of the window to coaster cars turning into trees. There is only a fixed amount of space allocated for rides, if you try to write more than that you will be writing into memory used for something else, which will corrupt that, and then you have more problems when the code that originally used that memory writes over it again, and now whenever that ride is referenced it reads from corrupted memory. Further, only 1 byte is used to index into that array, so the extra ride would get index 0xFF, which is treated as unused (and any further rides would wrap around and start pointing at the beginning of the array instead). And even if it appears to work, it might cease to do so with a later update. I had a ride that (unknowingly) exceeded the cars per train limit, and it appeared to work for months before the problem was discovered when it stopped working. (I then increased the cars per train limit, as it was possible to refactor the code to eliminate it entirely. That is not the case for the rides limit, a new file format is needed). The compiler will assume this type of thing just doesn't happen and doesn't have to account for the possibility - if it can determine that a buffer overflow will occur, it can literally optimize out the entire code block and that's perfectly valid behaviour, because absolutely nothing is guaranteed if you invoke undefined behaviour.

A hex editor can be used to edit any type of binary data, SV6 files included. It's just a matter of how difficult it is. SV6 files are stored in compressed format, and this makes them hard to edit manually. That was true in vanilla as well. I have a script that will decompress the SV6 for editing and then recompress it when done which I've used in the past for hacks not supported by OpenRCT2. However, I prefer to do this sort of thing on the in-memory version of the data (which is not compressed). You can do this with a debugger, or simply by inserting some extra code after the SV6 is loaded. This approach has the advantage that you can take advantage of the existing symbols - you don't have to manually calculate the correct offset for the value you want to change, and you can easily loop over the map data if you need to do something to every tile. A hex editor will absolutely NOT allow you to override these limits. The SV6 file allocates a fixed amount of space for the table of selected rides, and a fixed amount of space for the ride structures themselves. If you want more of them, there's nowhere to put them. These limits cannot be removed without a new file format - if you just patch out the limit, all you'll be doing is clobbering memory reserved for other things. This will corrupt your game.