All modded versions
MAXIMUM WARP EDITION v3.2
Supermod 3 single player upgrade; modding your own ships etc with a text editor...
KM is buggy in singleplayer, but works well in QB and multi with 512 or higher video ram; 256Vram is buggy at medium graphics in any size, and low graphics work okay, but crash out a lot more frequently than supermod; but it does play
Original game works as before;
The Mod Editors that come with the Maximum warp edition were checked. The texture editor based ones don't work well, you're better off using a 3drender\mesh blender app to grab values from surface and internal areas and place systems and other adds in the ship hardpoint file based on that; torpedo editing works okay in BCUT, and any text-file style edits to the py files work unless they are done with wrong numbers etc that break the other functions.
Maximum Warp launcher works if you've set up the right visual parameters for your system, and you've edited the options.cfg file to match your screen size (start with 1024x768 and then alter it in-game and then quit game from the button on the menu). I made my own launchers, so I could control the screensize and other aspects, apply command line args etc.
I used the latest wineskin.
What does not
Installer will try to "Publish data" and enter an endless loop.
The mod-editors that work with the ship renderings don't work properly. Some may get other results, but I think it's system dependent or card dependent. USing a Vertex Blending mod to the engine helped but it was still useless.
What was not tested
Advanced modification using a 3d renderer was not tested, though it is the recommended method for modding ship hardpoints and adding systems without buggy play.
winetricks d3d9, vcrun2010, common controls, wsh versions (all), vbrun, .net1 to dotnet3.5 one step at a time, refresh the wrapper each step and kill the wine processes, then move forward. I also added fonts, directplay, set directdraw to opengl. I added other runtimes, seemed to reduce the amount of crashes, and I added python interpreter and comtypes. when modding, it may crash on next run, maybe more than once, but it will come back once all init.py files have run, and you should remove any pyc whose py is modded (remove all from that folder is better).
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 17.04 "Zesty" amd64 (+ variants like Kubuntu)||Jun 28 2017||2.11||N/A||Yes||Silver||Bruno Oliveira|
|Show||Debian GNU/Linux 7.x "Wheezy"||Jul 16 2012||1.4.1||N/A||Yes||Platinum||Erik Andresen|
|Current||Mac OS X 10.7 "Lion"||Jul 17 2012||1.4||Yes||Yes||Platinum||Harley T. Davis|
|Show||Mac OS X 10.7 "Lion"||Jul 16 2012||1.4-rc5||Yes||Yes||Gold||Harley T. Davis|
|Show||Ubuntu 11.04 "Natty" i386 (+ variants like Kubuntu)||Oct 03 2011||1.3.24||Yes||Yes||Gold||Athrun|
This section is mainly focused on Bridge Commander mods
Feel free to discuss any tweak, problem or performance fix here
When reporting a test result please add your video card, driver version and mod version tested, thank you.
Installing Bridge Commander
Bridge Commander installs and updates to 1.1 without problems from original disc.
The Black Screen of Death / Fatal Errors
For good or ill, the old Black Screen of Death will not normally come up, but will instead tend to crash the game entirely while in wine. It is thus a good idea to run the game from terminal, as this will prevent wine from closing immediately and allow you to better troubleshoot these types of issues. Keep in mind that this may have odd effects on game play, depending on several factors such as distro, wine version, other programs running, modules loaded, etc. If you do get the Black Screen of Death though, it can be handled as usual.
Keep in mind that you may come across case errors when installing or self-modifying mods, ships, or other mod content. Case errors will normally crash the game entirely in wine, and having Console Tracker in your install will allow you to more rapidly identify and correct such errors. Generally, case error issues are just a pain in the arse. Keep an eye out during extraction and verify you aren't getting case duplicates.
Helpful Debugging Tools
ScanBC, an abandoned project started by USS Sovereign. It's quite rough, and should be considered a program in beta.
Console Tracker, by USS Frontier. A must-have for all modded installs.
Using the SDK
It is strongly advised to do the actual modding from a Windows machine, or at least a virtual machine such as VMware Player. Most 3rd party modding tools do not work well in wine and for the exception of the AI tool (which can be run from a python console), the sdk is similarly affected.
Because of driver problems, Intel video cards which are commonly used in Laptops will be too slow for this game.
Nvidia cards with the closed source driver are working fine.
If you have problems with Sound try the set Audio Quality to High: For this open options.cfg in a Text editor and change
ProviderReserveList=LowQualitySoftware to ProviderReserveList=HighQualitySoftware
Kobayashi Maru users can change this under Game Options.