The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results (selected in 'Test Results' table below)
What works
Installation works without problems, the usual bunch of warnings is written to console during the installation process but it works.
Playing the game is another story. You have to disable a lot of quality options (pixelshader and stuff) to get it playable without visual errors. This is not an option with current graphics cards.
It's playable but not really enjoyable :-)
What does not
I mainly tested the game with details all set to maximum. This results in some issues with varying severity.
Bullet time mode is unusuable because the post-processing effects result in a screen with solid color displayed (some changes in color). You can't see the game scene anymore, so it's useless and the game gets exceptionally hard without this feature. Not playable anymore if you ask me (what's Max Payne without bullettime anyway?)
Next mirror reflections don't work properly (bugreport was already filed). This is not a huge problem but destroys the atmosphere of the game.
Another visual error is lighting brightness bugs on most character models. A proper bugreport for this bug exists (something to do with pixelshader implementation).
The last visual error that is currently present is a shadow bug, also very annoying.
What was not tested
Finishing the demo, I only played up to the middle of the warehouse scene.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
S3TC and open-source graphics drivers
by Tobias Jakobi on Sunday September 5th 2010, 9:40
A lot of people using open-source / mesa OpenGL drivers seem to have trouble getting the game (or even the demo) running. After the intro movie the game quickly crashes at the loading screen.
This mostly affects the people with integrated Intel cards, but should also become a problem when opensource drivers for nVidia and Radeon (ATI/AMD) hardware become more common.
If you're experiencing these crashes during the loading screen and you're using a open-source mesa driver then the chances are high that you have no S3TC compression/decompression library (libtxc_dxtn) installed and mesa is therefore disabling S3TC completly.
The Max Paxne 2 engine seems to rely on the S3TC texture formats being always available and can't handle the case when these formats are not advertised by the driver. There is a fix and a workaround for the problem.
The fix is installing libtxc_dxtn on your system (keep in mind that you need a 32bit compile). I'm not going to describe how to do this, just use your favorite search engine for the steps.
The workaround is forcing mesa to advertise the texture formats even when the said library is not installed (the engine seems to be happy with this). You can do this e.g. with driconf. Launch this graphical config utility and select the tab 'Image Quality'. You should see an option "Enable S3TC texture compression even if software support is not
available" which is probably set to "off". Enable it and retry starting the game. It should work now, if not then you're probably facing a different problem.
Proposed wine settings
by Tobias Jakobi on Sunday November 2nd 2008, 19:02
It is recommended to set the OffscreenRenderingMode to "fbo" when playing Max Payne 2 (doesn't matter if full or the demo).
With the default setting of OffscreenRenderingMode ("auto", which maps to "backbuffer") wine hits some severe limitations, which are connected to the backbuffer dimensions.
When post-processing effects are enabled ingame (e.g. set to medium) the bullettime screen is cropped. Cropping is affected by the ingame resolution.
Also affected are motion blur effects during cutscenes.
If you REALLY need to use ORM="backbuffer", make sure you use a ingame resolution where at least on dimensions has a POT (power-of-two) size. This applies e.g. to 1024x768 or 1280x1024.
