Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: kudos on August 18, 2008, 03:41:17 pm
-
So, just as I booted up my FS2 Launcher today, it told me there was a new update available, so I downloaded and installed version 3.0.7. However, this version crashes on start up: after telling me "Unrecognized command line parameter, "-jpgtga", continue?" (which always happens, even the older version did that), it'll think for a few seconds, and then tell me that "The application FS2_Launcher quit unexpectedly..."
If there's no way to fix this, I'd love to just move back to the previous version I had it worked perfectly well... I don't remember what its number was. The only versions I can find to download that aren't 3.0.7 are 2.0.1 or 2.0.4.
If it means anything to anyone, I'm on a MacBook with Mac OS X 10.5.4
-
"Unrecognized command line parameter, "-jpgtga", continue?"
You've obviously switched from the 3.6.9 build to a 3.6.10 build. 3.6.10 builds have the jpg/tga textures enabled automatically, so there is no flag for them anymore. But since you have the flag in the command-line after using 3.6.9, the Launcher (or the game engine itself?) rants about it. Dunno about Macs but at least on Wind'ohs side clicking OK results in the Launcher removing the said flag and proceeding normally.
-
Hmm ... I've had random unpredictable crashes with newer versions of the launcher too. I find it fixes itself once you modify the flag file yourself (~/Library/FS2_Open/data/cmdline_fso.cfg) with TextEdit and restart the launcher. Thought this may not really be what fixes it. I'm not sure :nervous:
-
I wonder if deleting the file and letting launcher recreate it would work?
-
I encounter no problems with OS X Launcher 3.0.7, but that's probably because I'm using SCP 3.6.9.
-
Thanks for your help, everyone! I've gotten it working again.
First, I tried opening up the cmdline file and deleting the -jpgtga flag, which did get rid of the message telling me it didn't recognize it, but the launcher continued to crash on start up. So, I just deleted it and let the launcher create its own new one, like you said, FUBAR, and it seems to have solved my problem.
Thanks again!