Author Topic: WXlauncher not applying settings on nightly  (Read 1636 times)

0 Members and 1 Guest are viewing this topic.

WXlauncher not applying settings on nightly
Using wxlauncher-0.12.0-rc.2 and latest nightly 21-3-2017 (but it started with some earlier nightly).

If I change any setting in launcher and launch the nightly build the setting change is not applied at all. Things like mod selection, joystick, resolution.
The changes are saved somewhere. launcher still remembers them after restarting.

To make changes apply I need to launch 3.7.4 once. After this I can switch to nightly.

 

Offline m!m

  • 211
Re: WXlauncher not applying settings on nightly
Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

 
Re: WXlauncher not applying settings on nightly
MediaVP 2014 was set as active mod with 3.7.4. Then I changed active mod to Silent Threath: Reborn and launched 3.7.5 debug. Game launches with MediaVP 2014 as active mod.

Odd thing: Your link claims that the log should be in %appdata%\HardLightProductions\FreeSpaceOpen\data with 3.7.5 but it was in \freespace2\data\ .

[attachment stolen by Russian hackers]
« Last Edit: March 22, 2017, 05:55:47 am by hirmuolio »

 

Offline Makhpella

  • 27
  • Kharak is burning!
Re: WXlauncher not applying settings on nightly
I don't know much about reading logs, but could you check your mod.inis? Whatever it is you're trying to run, STR, I believe you said, that's not what's actually loading.
Code: [Select]
-mod MediaVPs_2014,MediaVPs_2014
Also, I haven't used debug recently, but 3.7.4 logs are supposed to go to Freespace 2 folder, while 3.7.5 logs should go to appdata. I don't know, ask someone else.
'I'm from the marksman school of conversation.' -Kovacs

 
Re: WXlauncher not applying settings on nightly
Mod ini look normal
Code: [Select]
[launcher]
modname      = MediaVPs 2014;
image255x112 = FSU-MVP.bmp;
image182x80  = FSU-MVP_small.bmp;
infotext     = Freespace II - SVN MediaVPs;
website      = http://www.hard-light.net/;
forum        = http://www.hard-light.net/forums;
mantis      = http://www.hard-light.net/mantis;

Code: [Select]
[launcher]
modname      = Silent Threat: Reborn v1.4 - MediaVPs 2014;
image255x112 = fsport-str.bmp;
infotext     = As the Great War rages on, you've been commissioned by Galactic Terran Intelligence for special intelligence operations.  Your objectives are to contain the Shivan onslaught and preserve the fragile Terran-Vasudan alliance.  But a series of suspicious events cloud the GTI's spotless record.  Is the GTI setting you up or are the Shivans spreading their evil rage?;
website      = http://fsport.hard-light.net/website/str/;
forum        = http://www.hard-light.net/forums/index.php?board=140.0;

[multimod]
primarylist = fsport-mediavps_2014;
secondarylist = fsport,mediavps_2014;

3.7.4 lists the mod only once in the log. 3.7.5 lists it twice even when it should run only mediaVP 2014.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: WXlauncher not applying settings on nightly
Using wxlauncher-0.12.0-rc.2
Are you sure about that? The behavior you're describing really sounds like you're running wxLauncher 0.10.1.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: WXlauncher not applying settings on nightly
Are you sure about that? The behavior you're describing really sounds like you're running wxLauncher 0.10.1.

Yes. Reinstalled just to be sure.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: WXlauncher not applying settings on nightly
What's in your %APPDATA%\HardLightProductions\FreeSpaceOpen\ folder?
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 
Re: WXlauncher not applying settings on nightly
What's in your %APPDATA%\HardLightProductions\FreeSpaceOpen\ folder?

fs2_open.ini in "HardLightProductions\FreeSpaceOpen"
cmdline_fso.cfg in "HardLightProductions\FreeSpaceOpen\data"
empty players folder in "HardLightProductions\FreeSpaceOpen\data"

 
Re: WXlauncher not applying settings on nightly
When I launch 3.7.4 the command line parameters are saved to file in "D:\GOG Games\Freespace 2\data\cmdline_fso.cfg".
When I launch 3.7.5 the parameters are saved to file in "\AppData\Roaming\HardLightProductions\FreeSpaceOpen\data\cmdline_fso.cfg"
But the 3.7.5 still use settings that were saved in "D:\GOG Games\Freespace 2\data\cmdline_fso.cfg".

 

Offline m!m

  • 211
Re: WXlauncher not applying settings on nightly
Do you have the portable settings mode enabled in the launcher? If yes, disable that and try again.

 
Re: WXlauncher not applying settings on nightly
Do you have the portable settings mode enabled in the launcher? If yes, disable that and try again.
Portable on or off doesn't change anything.