RCT Discussion / OpenRCT: advantages and disadvantages

I was building on black thunder mamba railroad today and the clearance option was amazing. The ability to do it without fear of ghost tiles or other miscellaneous fuckups is amazing.

I'm not sure the tile inspector in OpenRCT2 is the best tool to remove black holes with, at least not yet. Especially not the ones with track in it. From my experience, the game freezes and stop working when trying.
However, whenever you open a park in OpenRCT2, with a black hole in it, the black hole disappears, but you still don't own the land. What you could do from here is either to use the sandbox mode to build on the tile, or open regular RCT2 and Invert Land Ownership -> Ignore Rights & For Sale in 8 Cars. In that way you can raise land and/or build on the tile.

There is a different way to deal with black holes too, without using OpenRCT2 or Winhack. I've meant to make a tutorial, but I haven't had the time yet. What I do, is simply to Zero All Clearances -> Relative, then drag an object (for example a deco block) on the corrupt tile, back and forth (a lot of times), and trigger the tile to raise itself. When it finally does I Restore Clearances -> Debug -> Eliminate Duplicate Surface Data -> Landscape -> Cap land at max height. The process to trigger the black hole may take some time, and you need to be patient.

You can also do the same thing, but instead of dragging an object on the tile, you can simply build path on it, If you click fast enough. Then you delete it, and repeat until the magic happens. Kind of simple to be honest. It even works when there is track on the tile. When this is done correctly the tile is fully restored.

I successfully removed a black hole with the tile inspector of OpenRCT. I wouldn't know how to do it in regular rct with trainers, but easy as fuck with openRct.

Is there any way to move guest entry points cause if there isn't that would be very usefull.

The biggest problem with OpenRCT2 that I see right now is that the peep pathing is clearly completely different from base RCT2. In the most recent competition over on Reddit so many of the entries have peeps piled up in random spots trying to get to obviously accessible locations. They choose incorrect travel directions for no apparent reason. If the same park is opened in RCT2, the crowds disperse automatically and find their way to their destination without issue. No idea what causes this, but it's a far more serious problem than entrance/exit huts not being visible in one game or the other. 

We are aware of the peep AI being broken. It's not intentional.

 

 

@Scoop: Yes, there is, by turning on Sandbox mode and using the map window, like in the scenario editor. They won't light up in blue, however. (Which is a bug.)

ok thanks

For some reason (I think it may be my 8cars hacks), one of my current park projects can be built on in OpenRCT, but it opens with an error trapper in Vanilla afterward. I guess I'll have to finish the park with 8cars, which kind of sucks!

We just received our first submission that is not compatible with the default game, because 'corrupt elements' were used... Anything that can be done about this?

We just received our first submission that is not compatible with the default game, because 'corrupt elements' were used... Anything that can be done about this?

 

 

FUCK will be the same I expect. Would be interesting to know if there can be done something about it. If not, so be it, OpenRCT has more advantages than disadvantages to not finish it in OpenRCT.

I‘m building my first openrct2 park XD

We just received our first submission that is not compatible with the default game, because 'corrupt elements' were used... Anything that can be done about this?

I mean the obvious thing would be adding a "OpenRCT" category for submissions.

For some reason (I think it may be my 8cars hacks), one of my current park projects can be built on in OpenRCT, but it opens with an error trapper in Vanilla afterward. I guess I'll have to finish the park with 8cars, which kind of sucks!

I deleted two rides that I had hacked with 8cars, and it seems like I can open the park in both versions of rct2 now. I'll keep testing it over the next few days.

We just received our first submission that is not compatible with the default game, because 'corrupt elements' were used... Anything that can be done about this?

 

Try moving all the objects that should be hidden above the objects that shouldn't using the tile inspector. My understanding is that in the vanilla game a corrupt object will hide every element above it, whereas in OpenRCT2 it just hides the next one. I have no idea if this works or not - I'd test it, but I haven't been able to get the vanilla game to run under Wine for some time now.

Is there a reason, why parks are still should open correctly in the vanilla game? I mean nearly everyone here is using OpenRCT2 to build and also watch parks, so why not just switch completly to OpenRCT2?

Especially since the difference between OpenRCT and RCT2 will only become bigger. Maybe we can get a quick fix now, but a couple of months down the road it could be a whole other thing.

I still like the ghost objects so I'll stick to normal RCT

Peep and staff pathing needs to be fixed before I'll switch.

Guys, this is exactly why I said Open is in the same boat as Modified. The devs said they WILL NOT adjust Open so that it will show correctly in vanilla.

Also, Open will constantly be updated, so it will not be possible to have this as a game choice on this site as rct2/ll is, as the site may not have the latest version installed or a previous version isn't compatible with the newest, or a new version introduces bugs on a previous version..

 

Like many people said, it's best to do the heavy hacking in vanilla and some zero clearancing in Open.

There's really no point adjusting OpenRCT2 to be compatible with vanilla when they will have to break backward compatibility eventually; some stuff just can't be able to be implemented without it. Maintaining compatibility with the original game means you're still subject to the same limitations.

Having a "safe" version of OpenRCT2 might be a good idea for a separate branch though. One that would remain relatively consistent version-wise, and maintain only features that are reverse compatible.