The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Patch, Kobayashi Maru 0.9/1.0, Galaxy Charts, GravityFX, console tracker, DS9FX, hull integrity percentage display, NanoFX2Beta, QBR, all mods included in those packages, and most all other minor mods.
Stability and speed are increased if windows-native libraries are used, especially the DirectX ones.
What does not
Does not recognize a pseudo-drive mounted in Wine settings, nor a mounted image file, nor the actual cd. A cracked executable must be used.
In combat, phasers have issues discharging properly, tending to get stuck in the phaser's elipse. This has a stutter-like effect on all ships that can use beam weapons. Stock vessels are affected. In tandem with inaccurate phasers, it makes beam weapons almost completely useless.
What was not tested
Any mod not listed that puts in features, not ships/textures, etc.
Additional Comments
All vessels that don't crash the game in windows do not crash in Wine. Negates the 'black screen of death' and simply crashes instead of hanging. Running in terminal with logging recommended if you can't get anywhere with console tracker.
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.
General Notes
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.
Installing Mods
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.
Note
The game seems to have problems with ATI Radeon cards. I use the
opensource driver, and have a very slow overall appearance of the game
(The same appears with the proprietary driver). Even the mouse pointer
does not move smoothly (As if the bug above is not resolved yet for ATI
cards??) Apart from being very slow, everything works, even the videos.
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.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Latest Wine, DIB and STBC
by Harley T. Davis on Monday July 16th 2012, 16:15
I know it crashes a lot, but I was seeing graphics that were really choppy. Adding the blend fix, though it has no effect on the actual graphics objects, seems to allow the DIBengine to take over some of the older styled calls for the graphics, and forward them properly on the mac. While the NEW DIB does run some games, this one won't render properly after 1.4.1 (on the mac) due to many of the graphics conforming to older standard formats, which don't match new calls yet (support is under development), so they render improperly, but even with the older DIB, I was getting worse graphics chop than ever before. However, by setting the graphics medium on a 256 card, and using the vertex blending method on RC5, I was able to get rid of most of the chop (motion blur doesn't work right either way).
I'm going to try the Maximum Warp Edition soon, to compare all of the modes. For most systems with 512 or greater, use medium settings (512) for graphics with limited opponents, and remember that this game was buggy to begin with. If you use XQUARTZ on mac, remember to install the package correctly and test small apps first. For Lion (10.7), you'll have a few issues. Just remember the screen needs to Override, then set to fullscreen, then set to current res, and force normal. You can do this with a custom exe to keep your setings palette at the ready, and set the wrapper to pull the XQUARTZ from the system, not the engine. Let the system window manager handle windows, but turn off decorations. You can toggle between windowed and fullscreen modes with cmd opt A, so if you wish to have smaller res to accomodate your vid card, set it in game. I suggest you don't as you won't be able to leave the window (only some systems); however at full current res, you can window it to leave the window temporarily to check other apps.
About last change of note
by Erik Andresen on Saturday May 16th 2009, 1:00
> well know that Kobayashi Maru 1.0 zip file, comes with subdirectories and files with different capitalization to the original files shipped on Bridge Commander 1.1,
Wrong. Show me at least one file that is.
> while this is not a problem when installing on FAT or NTFS filesystems (these filesystems are case insensitive), it can be a little trouble on Linux filesystem like ext3 or any other widely used on linux, because it will lead to duplicate filenames (with different capitalization) that will lead to missing features, or even crashes, so please install it into a FAT drive and then copy it into your Linux filesystem.
Also not 100% correct. Why VFAT does not allow to hold test.txt and TEST.TXT in the same folder, both filenames will be still different. So overwriting App.py with APP.py will result in a file now found error.
Also this problem is not limited to KM, but to many mods for BC.
