[Trivial Psychic]

So you may have seen that I have been experiencing problems with CTDs in many campaigns, despite using what I believed to be the newest builds.  I say "I believed", since I was downloading the newest ones, extracting them into my freespace folder and selecting the last one seen in the launcher.  I wasn't however, comparing the filename of the one I just extracted to the latest one listed in the launcher.  Today however, I noticed that after extracting the latest build and opening the launcher, I see that there is nothing newer to select.  Upon comparing the latest listed build in the launcher to what I've got in the fs2 folder, I see that its not listing anything newer than April 1st.  I've even deleted every build prior to the 3.7.4 RC1, and it still won't show the newer builds.  I've tried updating the WxLauncher to 0.11.0 and it still ignores all new builds.  What could be causing this?  Could I simply run the exe directly and assume that all of my command lines options and other settings in the launcher will be activated as well?

Update:

Well, the good news is that as long as I have run a build through the launcher with the desired command line settings and mod selections, any exes run directly will retain these preferences.  Secondly, it seems that the post April 1st builds are having a better time with the CTD problem I'd been experiencing.  Unfortunately, it doesn't solve the fact that the launcher is ignoring new builds, which will make it difficult if there are any changes to command line options on newer builds.  A solution to this would still be appreciated.

[AdmiralRalwood]

Can you take a screenshot of your "FS2 Open executable" dropdown?

FYI, upon launching, wxLauncher writes the commandline options to the cmdline_fso.cfg file in your data folder. Any changes made to this file by hand won't be reflected by wxLauncher, but it can be manually edited.

[Trivial Psychic]

Here's my launcher screen, and I also included a grab of my freespace2 folder.


[attachment DELETED!! by Strong Bad]

[niffiwan]

Maybe I'm missing something but I can see the build labelled "4fa84ee" in your wxLauncher dropdown, and that build in the 2nd screenshot has a last updated date of 1st May?

There is an issue that the build ordering scheme doesn't currently fit in with the wxLauncher build sorting scheme, which makes it hard to see what builds are more recent... probably needs an update to wxLauncher to recognise that specific format and order by the date in the filename rather than the git hash (which by definition is not ordered in any way).

[Trivial Psychic]

[facepalm]
OK.  I guess I just assumed that the launcher would know that the newest one would be newer than the one at the bottom and tag it on there.  Is there any way to adjust the launcher or the build generator so that the launcher always aligns in the builds in order of date or build stepping, (3.7.4, 3.7.5, 3.7.6, etc.) and then by date within?

[niffiwan]

Don't worry, you're not the only person to have been caught out by this!! 

Yes, it should be possible to modify wxLauncher, it just needs someone to pick it up & do it.  I think the last time it was discussed it was decided that this was the best option, since the current build naming scheme means the builds auto-sort when displayed in explorer (which by default sorts alphanumerically on the filename).

[AdmiralRalwood]

If nobody else gets around to it before me, I can try figuring out wxLauncher's build parsing (need to teach it about AVX builds anyway).

[Trivial Psychic]

Thanks.  On the subject of the launcher, why did the "launch FRED" option get removed?

[AdmiralRalwood]

Thanks.  On the subject of the launcher, why did the "launch FRED" option get removed?

It's not removed; it's just hidden by default. Hit F3 and it should show up, IIRC.

[Trivial Psychic]

While I'll be a monkey's distant genetic cousin!  Thanks again!