Just installed FSO. Ran into some weird issues. :: Freespace 2 General Discussions

Store Page

Freespace 2

All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

Freespace 2 > General Discussions > Topic Details

Delta_Assault has Freespace 2

17 Oct, 2021 @ 11:49am

Just installed FSO. Ran into some weird issues.

So I decided to come back to my old favorite space sim FS2 and get the new FSO. I'd last checked out FSO about ten years ago or so. Obviously a lot must have changed. I went and downloaded the FSO installer. Looking at the install options, it said that AVX had optimizations, so I went and got the AVX executable instead of Standard. I went with the wxLauncher for the launcher. Then I downloaded the 4.5.x MediaVPs.

I started up the wxLauncher and then went into Advanced Settings. I didn't know about the different lighting presets, so I just decided to go with "Baseline recommended." However, when I started the game, two msgs popped up:

Unrecognized command line parameter -spec_exp.

Unrecognized command line parameter -ogl_spec.

Then the game started and everything worked fine when I played through some missions. Well, almost fine. The game didn't seem to recognize my Xbox 360 controller at all, so I had to use Xpadder to get it to work.

I'm just wondering why I'm getting these two popup messages at the start? Did I do something wrong?

The author of this topic has marked a post as the answer to their question.
Click here to jump to that post.

Originally posted by The E:

You aren't doing anything wrong, and nothing will break for you. We recently did a cleanup of the commandline flags the engine accepts, and those two were amongst the ones we removed (because under our new lighting model, they didn't actually do anything)

< >

Showing 1-3 of 3 comments

PointBlank 22 Oct, 2021 @ 1:47pm

Probably the launcher is just a bit out of date and tries to set some obsolete graphics options. I don't use the launcher, and it's been a while since I ran this the last time, but I can see I had removed those options from my "launch script" the last time I played. Probably nothing to worry about. At least it's safe to say it's not any issue related to AVX optimizations.