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
Everything!
Tested with main campaign and Return to Na Pali and both were playable and all movies worked all the way through. I did experience one bug with Na Pali, but I'm not sure if it was a logic bug or not. (doors wouldn't open letting two baddies in and me out, had to restart from a recent save).
What does not
OpenGL would not work for me, I could not set whatever resolution I wanted, it would only show maybe a 640x480 part of the whole thing.
Diret3D worked great.
What was not tested
Nothing.
Additional Comments
For smooth gameplay I did have to add a "maxRate=60" in the Direct3D driver section of unreal.ini and I had to make wine run on just one CPU (since I have a dual core it was a little jerky) "taskset 02 wine unreal" (makes it run on the second CPU)
Unreal HOWTO
Installation
Run 'SETUP.EXE' on the disc, being sure not to install the old DirectX versions.
Patching
If you are going to be hosting a server, you will want to use the 225 patch to avoid a network incompatibility bug, otherwise players with the Gold version will not be able to join.
If you are just playing the game, you will want to use the 226f patch because it is compatible with most mods and the updated OpenGL renderers detailed below.
The stock OpenGL renderer was never really finished. However, you can replace it with an alternative that boasts new features.
http://oldunreal.com/patch/OMP-226-V0.2.zip
Extract 'OpenGLDrv.dll' and 'OpenGlDrv.int' to the '[installdir]/System' directory. Enable the renderer by setting "GameRenderDevice" to "OpenGLDrv.OpenGLRenderDevice" in '[installdir]/System/Unreal.ini'. If you happen to have the second Unreal Tournament disc, you can use high-detail textures. Read 'S3TCext.txt' provided with the zip file for instructions on how to convert and use the textures. For more information on tuning the renderer (anistrophic filtering, anti-aliasing, etc) refer to the OpenGL section in http://oldunreal.com/patch/Oldunreal-Multimediaupdate.pdf.
Issues
In more recent wine, using the software renderer may crash the game with a segmentation fault. Use the OpenGL renderer detailed above, or set "GameRenderDevice" to "D3DDrv.D3DRenderDevice" in '[installdir]/System/Unreal.ini'.
For users of some intel or ati/amd graphics drivers, the game may display a black screen upon startup. Set the registry key "HKEY_CURRENT_USER>Software>Wine>AppDefaults>Unreal.exe>Direct3D>OffscreenRenderingMode" to "backbuffer" to fix this.
This game is based on an older game engine and may run at erratic speeds. This is usually due to the high performance of modern systems, but is also complicated by things like cpu frequency scaling and multicore processors. Before starting the game, change to the performance cpu frequency scaling governor, and if neccessary, limit the game to one core/cpu. If you are using the enhanced OpenGL renderer, you can have it limit the frame rate by setting "FrameRateLimit" to "60" and/or "SwapInterval" to "1" under the "[OpenGLDrv.OpenGLRenderDevice]" section in '[installdir]/System/Unreal.ini'.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Native Binary available
by Martin Gernhard on Saturday November 14th 2009, 18:20
Still too fast? Reduce to one CPU/core
by Martin Gernhard on Saturday November 14th 2009, 6:11
In addition to "-cpuspeed=XXXX" it may help to restrict wine to using 1 CPU. At least that seems to improve things for me. For example, on a "AMD Athlon(tm) 64 X2 Dual Core Processor 5200+" I'm using:
schedtool -a 0x1 -e wine Unreal.exe -cpuspeed=2800