Author Topic: FS2 Launcher is acting strange  (Read 1557 times)

0 Members and 1 Guest are viewing this topic.

Offline Kaze

  • 20
    • Steam
FS2 Launcher is acting strange
I purchased Freespace 2 from Steam, and then used the installer to download and install everything that FS2 Open v3.7.2 had to offer. However, when I opened the launcher to select the mods for the game engine to use, what I got was this:




The audio/joystick, speech, network and video tabs are all just as blank as the MOD tab as well. I wasn't sure if an fs2_open.log file would be useful in this situation but decided to try making one anyway, only to be halted by the lack of a "Run in window" option.




The FSO FAQ thread and a cursory glance through recent troubleshooting threads revealed no solutions or similar issues, so here I am. I would greatly appreciate any assistance on this matter.

 

Offline niffiwan

  • 211
  • Eluder Class
Re: FS2 Launcher is acting strange
Try clicking on the "Browse" button (in your 1st screenshot), then select the location that Freespace2 was installed to (presumably inside a Steam library?).  Once you've done that all the other buttons/tabs should work as expected.
Creating a fs2_open.log | Red Alert Bug = Hex Edit | MediaVPs 2014: Bigger HUD gauges | 32bit libs for 64bit Ubuntu
----
Debian Packages (testing/unstable): Freespace2 | wxLauncher
----
m|m: I think I'm suffering from Stockholm syndrome. Bmpman is starting to make sense and it's actually written reasonably well...

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: FS2 Launcher is acting strange
You see, the launcher asks the FSO executable which features it supports in order to know which command-line options there are; without a selected executable, it doesn't know what options to display to the user (wxLauncher has a much more helpful, "No FreeSpace 2 Open-based game has been selected" message instead of just not displaying anything, but the default Windows launcher is somewhat older).
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.

  

Offline Parias

  • 27
Re: FS2 Launcher is acting strange
To supplement the above answers, I'll also mention that I had behavior like this happen a couple of times when my A/V was blocking access to the EXE file (heuristics might sometimes erroneously flag it). If nothing else seems to be working and you are indeed browsing for the EXE, check your A/V logs or temporarily disable your scanner.