Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: jdjtcagle on August 21, 2004, 03:08:10 pm
-
Uhmmm...
First off my launcher or build will not work, because it fails to read the flag file...
So I get a new build and launcher, acknowledge the flag is back, click the laucher and it like deletes the flag... which then brings me back to the same problem
Any help?
Please?
-
:blah:
-
Same thing has always happened to me. The Launcher has selective memory for flags, it seems, especially -ambient_factor. Best thing to do is select your flags, then copy and paste the resultant command line in the Launcher into a shortcut to use instead.
-
Soooo if I take this command line: -ambient_factor 90 -allslev -query_speech -spec -glow -pcx32 -jpgtga -phreak -ship_choice_3d -2d_poof -snd_preload -query_speech -d3d_bad_tsys and then put it in the launchers shortcut target, then it would load right when I click it? :confused:
Where the heck did my flags file go :blah:
-
no into a shortcut to fs2open.exe
-
Originally posted by jdjtcagle
Soooo if I take this command line: -ambient_factor 90 -allslev -query_speech -spec -glow -pcx32 -jpgtga -phreak -ship_choice_3d -2d_poof -snd_preload -query_speech -d3d_bad_tsys and then put it in the launchers shortcut target, then it would load right when I click it? :confused:
Where the heck did my flags file go :blah:
Try deleting flags.lch and then open launcher.exe again.
Btw you have -query_speech twice.
-
Ok, it still does the same thing... :blah:
I really need to get some things done this weekend so I would like to know how to fix it, but I'll remain patient
Thanks for pointing that out, Overlord
The flag file disapeared from my main Fs directory. I got it back once, but I got the error and it disapears again
-
You have to choose the right .exe at the top of the launcher.
-
I know...
Ok here's how it goes:
1. I click the launcher
2. I get little please inform Microsoft of the error screen
3. Then a message cannot read flag file
4. chosoe a EXE (if there's not already one selected)
5. Click on go and get another "please inform Microsoft of the error screen"
-
I had this error not a while ago. I dont know how I managed to fix it though :/
I reinstalled launcher, exes, and FS2. But that wasnt the exact solution I think
*goes off to think.
-
I am so SICK of reinstalling... :(
-
:blah:
your really going to make me reinstall...
-
just create a shortcut... say
C:\Games\FreeSpace2\fs2_open_shadow_2.exe -ambient_factor 90 -allslev -query_speech -spec -glow -pcx32 -jpgtga -phreak -ship_choice_3d -2d_poof -snd_preload -query_speech -d3d_bad_tsys
just change the folders to yours and voila.
-
I already tried it...
-
press start then enter regedit
to get to the registry.
hkey_local_machine-->software-->volition-->freespace2
there u will see CmdLineOption, change this to what u desire.
for example :
double click onCmdLineOption
copy and paste this
-ambient_factor 90 -allslev -query_speech -spec -glow -pcx32 -jpgtga -phreak -ship_choice_3d -2d_poof -snd_preload -query_speech -d3d_bad_tsys
EDIT: if CmdLineOption doesnt exsit than create new binary,
named as CmdLineOption .
-
Followed your instructions... it's already there
-
Then clear that field. And try the launcher again.
-
nope...
-
Okay. I've just reinstalled FS2_Open and now I'm getting the same error. Some builds don't report the error but as soon as I swap back to Taylor's build it comes back. I'm playing about and I'll see if I can find a fix.
-
Problem solved :D
This is a very easy error to make if you reinstall FS2 (Which is how I got it) or if you're overzealous when tidying up your FS2 folder.
Basically it's caused by trying to run one of Taylor's builds without the devil.dll, ilu.dll and ilut.dll files it wants.
What happened to me was that before reinstalling I threw everything in a big folder called Storage and moved it out of my \Freespace 2 folder. When it was time to reinstall FS2_Open I dragged the exe back into the correct folder but forgot about the dll files :rolleyes:
-
only thing I'm missing is the flags file...
-
Maybe you have old dll's or they've gotten corrupted. Try redownloading Taylor's build or simply use Phreak's radar build and see if that helps.
-
He never mentioned using one of taylor's builds, unless it was implied?
jd, try running FS2 without any flags, directly from the FS2 directory without the launcher - see if that allows it to run. If it does, make a shortcut to that file, and add the flags to the end of the command line one by one, testing it after each. Remember to use the right build if you have multiple ones in your directory. I think the launcher and flags issue is a separate one
-
Kara: haven't used them yet...
Didn't work anyway
Sid: Vanilla Fs2?
Funny, I just tried to run Coolmons builds and it worked!!!
But 3.6 vanilla or taylors doesn't work...
-
Originally posted by SadisticSid
He never mentioned using one of taylor's builds, unless it was implied?
I figured that since his problem sounds exactly like mine and mine was only with Taylor's build and was caused by the dll's that there was a good possibility that it was the same problem as I had.
After fixing this problem I did briefly have another problem caused by the movies until I remembered to turn off the movie code but since 3.6 isn't working I doubt that the cause is the same thing.
-
In a attempt to avoid reinstall, I finally got the launcher to work...
But any build I already tried before is infected and wont work, is there any way to fix that?
-
How did you get things to work?
-
First I deleted all builds (except the Vanilla Fs2.exe, then I ran Vanilla Fs2.exe, gave me a couple of errors, which is normal because I have SCP stuff in my folders. Got out of the load up screen and the launcher would now work...
Now I need to figure out how to get SCP builds to work...
-
Can you get me a snapshot of your FS2 folder? I still suspect something is wrong there. The problem is too similar to mine to have a completely different cause.
-
Ok...
(http://img19.exs.cx/img19/9219/Untitled-184.jpg)
-
Were you using the 5.2 Launcher ?
-
yes
-
Where is your FS2 Open exe ?
-
And why are your Fred 2 options showing in the filename?
-
FsOpen EXE is whatever I decide to download, newer or older
Fred 2 options is: From the shortcut... "D:\Program Files\FreespaceSCP\fred2_open_r -fredhtl -mod Inferno.exe" -fredhtl -mod Port
P.S. The reason it says -fredhtl -mod Inferno.exe" just don't worry about that :o
-
Running with 2 -mod options won't help :)
-
I said ignore it!!! :p
I'm not, I originally added it to the end of the shortcut name, until I found out I was doing it wrong... Just never changed it back
-
skippy: however running "-mod moda,modb" will do you good
-
You do realize that adding the command line options to the filename of the program does nothing, right?
-
Of course, although it took me a while to figure it out... When I figured it out, I was/still am too lazy to remove it
-
Hmm then...
Try deleting flags.lch and cmdline_fso.cfg, this should completely reset everything on command-line options in the launcher. (Flags selected seem to be saved in the .cfg file)
-
Didn't reset...
And now my launcher is screwed up again...
-
:nervous: Sorry.
Short of reinstalling, you can do something of a reset...move everything besides the vanilla FS2 VPs, the launcher, and the exes, to a different directory. (It might be easier to move the aforementioned to a new directory, and rename the folders so the new one is the same as the old Freespace 2 directory)
At that point, check the registry keys and make sure nothing's amiss (maybe post a screenshot of 'em in the forums and ask if you're not comfortable with registry editing) then run FS2. Everything should be generated from scratch, and you can move mods and stuff back in as you want them. Once FS2 stops working again, you can figure out what caused the problem.
-
Ok, I'll try... :)