Announcing wxLauncher 0.9.1 public alpha
wxLauncher is a cross-platform launcher for the FreeSpace 2 Open engine. It is functionally equivalent to the Windows launcher. wxLauncher is currently known to run on:
- Windows (XP, Vista (x86/x64 RTM/SP1), and 7 (x86/x64 RTM/SP1) have been tested)
- Linux (Ubuntu 09.10 x86/x64 have been tested). For now, all Linux users will need to build from source.
- OS X (Intel-only, 10.5 and up, 10.6.8 and 10.7.4 have been tested). Thank you jg18 (aka Gay Vasudan)
Please post any issues, comments, or questions in this thread. All known issues can be found on the wxLauncher bug tracker
, but a brief list is below. Please keep in mind that this is not feature complete and there are outstanding glitches (which is why we want feedback, we want to know about them all).Important Known Issues
- Launcher does not read your current command line, so you will have to re-setup your command line before you launch FSO with wxLauncher.
- wxL currently does not properly handle cases where the default font/font size is unusually large. Some text may be cut off in such cases.
- [Windows] VS2010 cannot build wxLauncher; see "building instructions" below for more information.
- [Windows] wxLauncher does not display AA or AF controls because FSO on windows does not support the feature
- [OS X] Right after you change profiles or select an FSO executable to use, the flag checkboxes on the Advanced Settings tab will not appear until you interact with the tab somehow, such as by clicking or scrolling on the list.
- [OS X] The Activate and Info buttons don't always appear when you click on a mod. However, they are present and will work if you click on the space where they should be.
- [OS X] On Lion, wxL's list of resolutions may include reasonable-sounding resolutions that do not appear in System Preferences >> Displays (such as 640x480), as well as unusual/odd resolutions, such as 840x524.
users can download the installer from the downloads page
of the wxLauncher website. A debug installer can be found here
if you are having trouble. Windows users can also download the source code from the downloads page (only in a tarball, which 7-Zip
is able to open without problems).Linux
users can download a the source from the downloads page
. At this time, Linux must build wxLauncher from source. The ReadMe
has the build instructions.OS X
users can download a .dmg disk image from the downloads page
of the wxLauncher website. There is a debug disk image
if you are having trouble. OS X users may also wish to build wxLauncher from source; the ReadMe
has the build instructions. A source tarball is available from the downloads page.Building instructions
To build wxLauncher you will require CMake 2.8 and wxWidgets > 2.8.7 (though we have only really tested 2.8.10 and 2.8.11 on Windows and 2.8.12 on OS X). Full instructions on building wxLauncher are contained in the ReadMe.txt in the root of the source archive.Note
that VS2010 cannot
build wxLauncher. While CMake is able to generate VS2010 solution files, they are not generated correctly, leading to registry_helper not having the correct manifest settings applied, which results in wxLauncher being unable to launch FSO on Windows.Change log0.9.1 fixes:
- Support for the new sound code!
- Details are in the 0.9.1 post.
- All platforms now use the same code base
- Major changes to the layout
- Profile cloning
- FRED launching
- Lighting presets
- Multiplayer on Windows works!
- Details are in the 0.9.0 post.
The official commit log can be viewed here
For Windows and OS X users, if you run into problems getting wxLauncher to run, download and install the launcher built in debug mode ("Downloads", above). Post or PM the log (which is located in %AppData%\wxLauncher\wxlauncher.log
(Linux), or ~/Library/Application Support/wxlauncher
(OS X; note the space in Application Support
For Linux users, to build a debug version of wxLauncher, follow the build instructions as above, but when running CMake, ensure that CMAKE_BUILD_TYPE is set to Debug (cmake -DCMAKE_BUILD_TYPE=Debug).