Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Dada on April 18, 2010, 12:39:36 pm
-
I seem to be unable to run Freespace 2 Open. I'm not sure what I'm doing wrong, since I'm following the instructions on the wiki to the letter.
Here's what I've done:
1. Install Freespace 2 on Windows from original CDs
2. Update to version 1.2 using fs21x-12.exe
3. Copy updated Freespace 2 from Windows to Mac OS X
4. Run FreeSpaceOpenInstaller.jar, select my directory and choose "bare bones install"
5. Run installation, then install OpenAL
After downloading and extracting the files, the installer runs its course without any errors. I install OpenAL without any problems either. Then when I try to run FS2_Open-3.6.10.app, it immediately shuts down.
EDIT: nevermind, I noticed that inside the .app file, the FS2_Open binary actually does not have the +x mode set, which would prevent the .app from working. After setting the executable flag, it WORKED! :)
anybody who's got this same problem and is wondering how to fix it: open a Terminal, go to where your FS2_Open app is, and type: chmod +x ./FS2_Open-3.6.10.app/Contents/MacOS/FS2_Open (enter). Then run the app like normal.
-
I'd call this a support issue, so moved.
Other than that, excellent. People who ask for help and then solve their own problems before anyone can say anything are very much among the people who I respect.
-
You're right, sorry for putting it in the wrong place. It's very strange that the binary would not have the executable flag set, though. There's no way it could run like that under any set of circumstances, so this seems like a bug to me. Though I'm not too sure where to report it.
-
Well, I think this is the first time I've heard of this issue. Either you're the only one or other people just haven't said anything. I'd like some Mac people to say something about this before claiming that there is a bug with the Mac build downloaded by Turey's Installer.
-
Never heard of it. Could be the way the installer extracts the files? Or the way the zip is created in the first place, as opposed to the DMG other mac users normally grab. The zip might be frakking permissions, or the java zip handler could be doing it.