[ggjhfh]

Any help would be appreciated.  I'll describe the problem and then I'll describe my setup:

If I try to start the program with the Soulstorm's FS2_Launcher (3.1.3) the first thing I see is an error message that says "Flag file not found!  It appears that the application you have selected is not valid, the flag file that it produces in order to make the UI and other things cannot be found."  I click OK and the launcher loads.  I set the app path to the application and click launch.  The launcher closes and nothing happens (the launcher will stay open if I go to preferences and check "Stay Open After Application Launch."  If I try to manually open the application, nothing happens.  Nothing generates an error log (no errorlog.txt, fs.log, or fs2_open.log files).

I installed Freespace 2 from .iso files (I tried to buy the gog.com version but they rejected my valid credit card no matter what I tried) in a Windows partition with Boot Camp, updated it to 1.2, then copied it to the mac partition and ran Turey's installer (12.2.0) (it said there were errors installing Shivans and Twilight, but I don't think that would effect anything).  I selected the "The Works" option when installing.  I'm using the Inferno build, and I installed OpenAL.

I've been struggling with this for a while and can't figure it out.  I couldn't find any posts that resolved this sort of issue.  Anyone have an idea of what might be going on?

[General Battuta]

Eurgh. Hate this error. I recently helped debug a friend's Mac install with something similar.

Make sure that all those stupid little graphical settings with names like 'spec' have a number after them. If they don't, the launcher will crash out with no warning.

[ggjhfh]

Eurgh. Hate this error. I recently helped debug a friend's Mac install with something similar.

Make sure that all those stupid little graphical settings with names like 'spec' have a number after them. If they don't, the launcher will crash out with no warning.

Thanks for the response.  I tried making sure that all the graphical settings had a number assigned to them, but that didn't seem to change anything.

I forgot to include in my original post that I'm running OSX 10.5.8 on x86 architecture, in case that's relevant.

Oh, and I've also tried deleting multi-mission-pack.vp as per the instructions in the FAQ (http://www.hard-light.net/forums/index.php?topic=56279.0), but this hasn't helped.

Double-posting sucks. Triple-posting sucks even more. MODIFY, man! --Jeff Vader

[General Battuta]

Try selecting a debug log (ends in -d or -debug) in the launcher and running. See if you get an fs2_open.log. I know you said it wasn't generating logs but maybe you didn't have a d-build selected?

Also PM blowfish, he uses mac.

Also post screenshots of your FS2 folder and launcher settings?

[ggjhfh]

Try selecting a debug log (ends in -d or -debug) in the launcher and running. See if you get an fs2_open.log. I know you said it wasn't generating logs but maybe you didn't have a d-build selected?

Also PM blowfish, he uses mac.

Also post screenshots of your FS2 folder and launcher settings?

I tried using the -debug version, but it didn't generate a log either.  I'm attaching screenshots of my launcher settings and FS2 folder.  Thanks for looking into this.

Also, apologies to Jeff Vader for the multiposts from before; I hadn't realized we could modify our posts.

[attachment deleted by admin]

[General Battuta]

Try turning your color depth up from 16 to 32 and your resolution up to something like your desktop native.

[ggjhfh]

Try turning your color depth up from 16 to 32 and your resolution up to something like your desktop native.

Thanks for the suggestion.  I just tried this, then I tried running through every combination of resolution, aspect ratio, and color depth, but it didn't seem to change anything.

[General Battuta]

Grump. 

Where are our Mac people?

[Jeff Vader]

Just for teh kicks, try removing multi-voice-pack.vp.

Also, that "data\movies" folder is suspicious. If you've followed instructions regarding the cutscenes, they should be in a folder called "movies", which in turn should be inside that "data" folder.

Also, apologies to Jeff Vader for the multiposts from before; I hadn't realized we could modify our posts.

npnp. I may or may not add comments during the merge, depending on the current mood.

[ggjhfh]

Just for teh kicks, try removing multi-voice-pack.vp.

Also, that "data\movies" folder is suspicious. If you've followed instructions regarding the cutscenes, they should be in a folder called "movies", which in turn should be inside that "data" folder.

Also, apologies to Jeff Vader for the multiposts from before; I hadn't realized we could modify our posts.

npnp. I may or may not add comments during the merge, depending on the current mood.

Thanks.  I tried removing multi-voice-pack.vp and the data/movies folder, but it hasn't changed anything.  I think the data/movies folder came from Turey's installer; it's filled with .ogg files, which I didn't put there on my own.  It might have gone there because before I started the installer I copied the .mve files from the installation disks into a folder called "movies" in the "data" folder (I think there are some instructions somewhere that mention doing this, although maybe I did it in the wrong order).  So my thought is that maybe since the movies folder was already there, the installer made a data/movies folder instead, maybe.

[blowfish]

Huh.  The launcher doesn't seem to be reading the executable's flag file even after it has been selected.  Try redownloading the executables, just to see if they are corrupted.  If the launcher connecting correctly with the executable, it should look something like the attached screenshot.  You will also see a flags.lch file listed in your root FS2 folder (/stuff/Freespace2/ in your case).

[attachment deleted by admin]

[ggjhfh]

Huh.  The launcher doesn't seem to be reading the executable's flag file even after it has been selected.  Try redownloading the executables, just to see if they are corrupted.  If the launcher connecting correctly with the executable, it should look something like the attached screenshot.  You will also see a flags.lch file listed in your root FS2 folder (/stuff/Freespace2/ in your case).

This worked, thanks!  After redownloading the application files, the launcher had the additional flags available and the game was able to launch properly.