Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Korsriddare on February 11, 2006, 12:32:00 am

Title: Error with launcher (v5.3)
Post by: Korsriddare on February 11, 2006, 12:32:00 am
A friend of mine is getting trouble trying to start her launcher.. she gets this error message:

AppName: launcher.exe    AppVer: 5.3.0.0    ModName: unknown
ModVer: 0.0.0.0    Offset: 676e692d
Title: Re: Error with launcher (v5.3)
Post by: bfobar on February 11, 2006, 02:24:46 am
I can't remember what my error message was from a launcher problem I had, but i deleted the launcher6.ini file and it fixed it, so I guess that file can get corrupted. The launcher will build a new one on next launch but all your old setting selections will be lost.
Title: Re: Error with launcher (v5.3)
Post by: Korsriddare on February 11, 2006, 06:25:30 am
Yeah, apparently it is the same problem, I sent her mine and it worked fine.
Title: Re: Error with launcher (v5.3)
Post by: WMCoolmon on February 11, 2006, 11:33:12 am
You should mantis this, so that someone will remember to take a look at it and try to prevent the corruption.
Title: Re: Error with launcher (v5.3)
Post by: bfobar on February 11, 2006, 09:55:17 pm
Mine occured when I was messing around with the default -spec_[stuff] flags so I attributed it to my fat fingers and not a bug. I'll do it if it happens again.
Title: Re: Error with launcher (v5.3)
Post by: WMCoolmon on February 11, 2006, 10:04:47 pm
Any kind of muck-up that causes weird behavior without an error or warning message that explains what happened should be reported to mantis. Especially file corruption, since people can lose hours of work or their entire system stability if the wrong file is corrupted. Granted I doubt that's a problem since the Launcher opens a very few specific set of files, but it's still a good idea to mantis it just in case.
Title: Re: Error with launcher (v5.3)
Post by: bfobar on February 12, 2006, 12:03:33 am
OK I threw up a bug report with what I remember.