summaryrefslogtreecommitdiff
path: root/docs/README_if_game_crashed_on_OSX.txt
diff options
context:
space:
mode:
authorbjarni <bjarni@openttd.org>2004-12-07 17:27:55 +0000
committerbjarni <bjarni@openttd.org>2004-12-07 17:27:55 +0000
commitbad25dec0ec8b95e535ce7440102ca4d92934d56 (patch)
tree5dad698e83b748ef574997fe74c5b85fa18705b3 /docs/README_if_game_crashed_on_OSX.txt
parent051134ac9f88ec88bfd7bbd1bc209ccd42dffbcc (diff)
downloadopenttd-bad25dec0ec8b95e535ce7440102ca4d92934d56.tar.xz
(svn r971) Mac: updated text files and added the link files from the releases
Diffstat (limited to 'docs/README_if_game_crashed_on_OSX.txt')
-rw-r--r--docs/README_if_game_crashed_on_OSX.txt6
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/README_if_game_crashed_on_OSX.txt b/docs/README_if_game_crashed_on_OSX.txt
index a9ef215f0..23bbe5796 100644
--- a/docs/README_if_game_crashed_on_OSX.txt
+++ b/docs/README_if_game_crashed_on_OSX.txt
@@ -2,10 +2,8 @@ Since you are reading this, OpenTTD have crashed. This file tells you how
to fix the most common problems or make to make a bug report, that the
developers can use to track down the problem
-The first thing you need to do is to get the error message. You can access OSX's build-in log by double-clicking Crash_Log_Opener. OTTD will do that if that file is present in the same folder as OTTD and is not renamed. However, major crashes can prevent the autoopen feature and you have to do it manually then
-If Crash_Log_Opener doesn't work you can view the log by opening Console inside Applications/utilities.
-
-If you use the Console app, you should look at the buttom of the console.log window
+If it is an assert, OpenTTD will open the console for you, if it is truly a crash, you have to do it yourself. The Console is located at /Applications/Utilities/Console.
+The problem is near the button of the page
The problems are as follows:
NOTE: build from source means to download the source and compile