Virus scanners employ a technique called "heuristics" that looks at how a program behaves, in order to try and detect malware it doesn't (yet) specifically know about. However, this can cause false positives. It is not clear what exactly causes them to flag OpenRCT2, but it might be the frequent updates or the fact it checks for administrative permissions. We certainly haven't put malware into OpenRCT2.

We could reduce these prompts by paying a lot of money to Microsoft/Apple/etc. and get a certificate, which is mostly a box-ticking exercise. Since we provide the software for free, we do not think it is a good use of our limited funds. It is also not a guarantee that it will get rid of all warnings, as virus scanners have even classified parts of Windows as malware by mistake in the past.

As of June 2019, we have made a few changes in order to reduce the amount of virus scanners falsely reporting malware. This will hopefully reduce the problem. If your virus scanners still detects malware, please add OpenRCT2 to your virus scanner's whitelist, or switch to one of a different vendor.

As of version v0.4.0, OpenRCT2 has increased dozens of limits. If you are not yet up-to-date, please upgrade to the newest version and you should be able to make use of them. To see which limits we changed, see Increasing of game limits.

This is because the original RCT2 had no multiplayer, and was thus not set up to accommodate it. This doesn't mean we won't fix it, however. Most desync issues are already reported, but if it isn't, please report it. See here for a list of most causes.

The tutorials in RCT2 used a simple system that consisted of recorded keystrokes, mouse movements and mouse clicks. This required a fixed placement of interface buttons and also needed to be recorded separately for every resolution. Since OpenRCT2 has many interface additions, more flexible button placement and supports and infinite amount of resolutions, this system was not suitable.

This does not mean OpenRCT2 won't have a tutorial, though. It does need a whole new implementation to work and it has lower priority than implementing the game itself, but we will want one in the end.

To close the console, one may do any of the following:

• Type hide, quit or exit
• Press the key between the tab and escape keys¹

¹(On US keyboards, this key is labelled with the ` (grave) and ~ (tilde) symbols. Other layouts will most likely have different symbols printed on them, or might require pressing twice or together with the Alt Gr function key.)

With UDP, packets can easily arrive in the wrong order or not at all. The advantage is lower overhead. TCP solves the mentioned problems at protocol level. Because OpenRCT2 does not send a large amount of updates (it doesn't send peep positions for example, those are calculated by the clients) the higher overhead of TCP is not a problem, while the extra accuracy helps to prevent desyncs.

Mega Park is usually unlocked and shown upon successful completion of all RCT1 (not CF/AA & LL) scenarios, but can be unlocked by setting scenario_hide_mega_park in the config file to false and reloading OpenRCT2.

Because you shouldn't be running OpenRCT2 as an administrator (on Windows) or as root/with sudo (on *nix). OpenRCT2 does not require elevated permissions. If your data files are stored somewhere your user account does not have read rights to, give your account rights or move the files somewhere else.

The reason we explicitly warn against doing this is twofold:

1. OpenRCT2 connects to remote servers for multiplayer, and there is a small but non-zero chance that a remote code execution exploit may be discovered.
2. The scripting system, which increases the risk of (1) happening. Running the process as admin dramatically increases the damage an RCE exploit could do.

OpenRCT2 works fully with the following releases of RCT2:

• Original CD version (expansion packs are recommended, otherwise the expansion rides and scenery will appear invisible)
• Triple Thrill Pack CD version
• GOG version (not the Russian release, which is discussed below)
• Steam version
• Discord Nitro version
• CD Projekt Polish CD version
• RCT Classic

OpenRCT2 partially works with the following releases of RCT2:

• RCT2 Mini Game (lacks some objects, which will appear invisible, and most scenarios)
• Akella/GOG Russian version (font issues. OpenRCT2 ships with a full Russian sprite font set, so if you want to play in Russian, you should still install the English GOG version)

Until the beginning of December 2021, OpenRCT2 still used the SV6 format that RCT2 uses, and was thus bound to its limits. This also meant that imported saves and scenarios from RCT1 are bound to them. Since then, the new save format was merged, which has removed the most visible differences. As of 28 March 2022, this has not made its way to a release, but it will be included in the v0.4.0 release.

In addition to this, there are also a handful of mechanics that work a little differently in RCT2, compared to RCT1. This includes park value calculation. For this reason, park values are adjusted when loading RCT1 saves and scenarios in OpenRCT2, usually with a factor 10.

There are two options:

1. Linking OpenRCT2 to RCT1. This not only makes the scenarios available, but also additional land types and some other small features. This is the best solution. You do need to own RCT1 with Loopy Landscapes or RCT Deluxe for this, though. It can be bought from sites like GOG, Fanatical or Steam, going as low as $1-$3 during sales.
2. Using recreated scenarios. These are pretty close matches, but not as close as using the originals. However, they can be downloaded for free here.

This happens when the g2.dat file is out of date. This is usually the result of only replacing openrct2.exe instead of the all the data files. This can easily be solved by reinstalling OpenRCT2 (your saves and scenario progress will not be erased if you do so).