mirror of
https://github.com/OpenRCT2/OpenRCT2
synced 2025-12-11 10:02:27 +01:00
Updated FAQ & Common Issues (markdown)
@@ -1,16 +1,15 @@
|
||||
The following is a process of how to solve common problems with the game, providing that they have a solution.
|
||||
|
||||
### Why does my virus scanner not trust OpenRCT2?
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
### Can OpenRCT2 increase the number of ...?
|
||||
Not yet. See [here](https://github.com/OpenRCT2/OpenRCT2/wiki/Increasing-of-game-limits) why.
|
||||
See [[Increasing-of-game-limits]].
|
||||
|
||||
### When using multiplayer, I get frequent desyncs.
|
||||
This is because the original RCT2 had no multiplayer, and was thus not set up to accomodate 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.
|
||||
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](Multiplayer-issues#desynchronisation) for a list of most causes.
|
||||
|
||||
### Why was the tutorial removed?
|
||||
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.
|
||||
@@ -19,8 +18,8 @@ This does not mean OpenRCT2 won't have a tutorial, though. It does need a whole
|
||||
|
||||
### How can I close the console?
|
||||
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<sup>1</sup>
|
||||
* Type `hide`, `quit` or `exit`
|
||||
* Press the key between the _tab_ and _escape_ keys<sup>1</sup>
|
||||
|
||||
<sup>1</sup>_(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.)_
|
||||
|
||||
@@ -33,25 +32,25 @@ Mega Park is usually unlocked and shown upon successful completion of all RCT1 (
|
||||
### Why do I get a 'It is not recommended to run OpenRCT2 with elevated permissions.' dialog on startup?
|
||||
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, and (2) an upcoming change will add a scripting system, which increases the risk of (1) happening. Running the process as admin dramatically increases the damage an RCE exploit could do.
|
||||
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.
|
||||
|
||||
### Does OpenRCT2 work with all versions of RCT2?
|
||||
OpenRCT2 works fully with the following releases of RCT2:
|
||||
|
||||
- the original CD version (expansion packs are recommend, otherwise the expansion rides and scenery will appear invisible)
|
||||
- the Triple Thrill Pack CD version
|
||||
- the GOG version (though not the Russian release, which is discussed below)
|
||||
- the Steam version
|
||||
- the Discord version
|
||||
- the CD Project Polish CD version
|
||||
* Original CD version (expansion packs are recommend, 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 version
|
||||
* CD Project Polish CD version
|
||||
|
||||
OpenRCT2 partially works with the following releases of RCT2:
|
||||
|
||||
- RCT Classic (there will be no sound and music, although you can copy those from the free RCT2 Mini Game to get a full set of assets)
|
||||
- RCT2 Mini Game (lacks some objects and most scenarios)
|
||||
- the 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)
|
||||
* RCT Classic (there will be no sound and music, although you can copy those from the free RCT2 Mini Game to get a full set of assets)
|
||||
* RCT2 Mini Game (lacks some objects and most scenarios)
|
||||
* 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)
|
||||
|
||||
### I loaded an RCT1 save/scenario, but there are some differences.
|
||||
Currently (25 March 2019), OpenRCT2 still saves to the SV6 format that RCT2 uses, and is thus bound to its limits. This also means that imported saves and scenarios from RCT1 are bound to this. This will change in the future, when OpenRCT2 switches to its own save format.
|
||||
|
||||
In addition to this, there are also a handful of mechanics that work a little differently in RCT2, compared to RCT1. This includes interest calcution (in RCT1, it's around 1.33%, in RCT2, it's always an integer percentage) and park value calculation. For this reason, park values are adjusted when loading RCT1 saves and scenarios in OpenRCT2, usually with a factor 10.
|
||||
In addition to this, there are also a handful of mechanics that work a little differently in RCT2, compared to RCT1. This includes interest calculation (in RCT1, it's around 1.33%, in RCT2, it's always an integer percentage) and park value calculation. For this reason, park values are adjusted when loading RCT1 saves and scenarios in OpenRCT2, usually with a factor 10.
|
||||
|
||||
Reference in New Issue
Block a user