View Issue Details

IDProjectCategoryView StatusLast Update
0000533FSSCPlauncherpublic2006-06-03 10:49
ReporterARSPR Assigned Totaylor  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0000533: Launcher 5.3 converts "Enable specular" in a Custom Flag
DescriptionLauncher 5.3 saves "Enable specular" as a Custom Flag not as a list option. If I run Launcher 5.3 and I tick the "Enable specular" option it appears correctly in the first place of the command line (in the second place if there is a selected MOD). After pressing OK and exiting, when I open Launcher again, "Enable specular" is unticked and -spec has been added to the end of custom flag list. So in this way -spec is in the last position of Command Line.

If in this situation I retick "Enable specular" I get two -spec flags in the command line. If I exit and reopen the launcher then I get two "-spec" flags in the Custom Flag List and "Enable specular" is unticked again. And so on, every time I tick "Enable specular", the -spec flag is converted into a Custom one and the option is unticked.

I have posted this error in Hard Light Production Forum too.

I always get this error. It doesn't matter which version of FS2_Open.exe I'm using. I have tried it also with an without MODs, with OGL or D3D.

I do not have any mod.ini file (I do not use multimod feature at all).
Additional InformationHere is my actual command line where the 3 last flags are custom ones:

C:\FreeSpace2\fs2_open_T-20050807.exe -glow -jpgtga -nomotiondebris -rlm -dualscanlines -targetinfo -ballistic_gauge -smart_shields -ship_choice_3d -3dwarp -tbpwarpeffects -snd_preload -ambient_factor 75 -spec_static 0.6 -spec

I'm running a Spanish Windows XP SP2 but I've got numbers and curency in English format ("." as decimal separator and "," as thousand separator)

I have noticed that launcher uses two files "flags.lch" and "launcher6.ini". I attach them in a zip.
TagsNo tags attached.

Activities

2005-09-05 17:03

 

FreeSpace2.zip (2,303 bytes)

ARSPR

2005-09-22 18:59

reporter   ~0003451

Reminder sent to RandomTiger

In the HLP forum about "Launcher 5.3" you started, Overlord have posted more information about this bug. And it exactly happens to me.

Launcher 5.3 converts "Enable specular" into a custom flag whenever I have a -spec_xxx flag in the custom flags list.

If I delete "-spec_static 0.6" from the custom flags list then "Enable specular" is not changed into a custom flag anymore.

taylor

2006-06-03 10:49

administrator   ~0005735

Didn't realize it until now, but I fixed this last year. It wasn't actually a launcher problem but how FS2 parses the cmdline options.

Issue History

Date Modified Username Field Change
2005-09-05 17:03 ARSPR New Issue
2005-09-05 17:03 ARSPR File Added: FreeSpace2.zip
2005-09-05 19:34 taylor Assigned To => RandomTiger
2005-09-05 19:34 taylor Status new => assigned
2005-09-22 18:59 ARSPR Note Added: 0003451
2006-06-03 10:49 taylor Status assigned => resolved
2006-06-03 10:49 taylor Resolution open => fixed
2006-06-03 10:49 taylor Assigned To RandomTiger => taylor
2006-06-03 10:49 taylor Note Added: 0005735