Edit Wine Registry for Video Card
If you dont set your video card info wine will just use what I guess are preset defaults, like 64 mb of video memory
Run the command below and it will open a Wine version of regedit.
regedit
Now browse to the HKEY_CURRENT_USER / Software / Wine / Direct3D folder.
If the Direct3D key folder does not exist then you can create it yourself:
* 1. Right-click on the Wine folder icon.
* 2. Select New > Key from the pop-up menu.
* 3. Name the new 'folder' key "Direct3D" without the quotes.
Once you find or create the Direct3D key you can enable shaders in Wine:
* 1. Select the Direct3D key folder icon.
* 2. Right-click the mouse in the pane to the right to open the right-click menu.
* 3. Use the right-click menu command New > String Value to create each of the following key pairs:
OffscreenRenderingMode pbuffer
UseGLSL enabled
VideoMemorySize 512
These are only the tried-and-true recommendations; the following sections explain what you can try for optimising performance.
This guide has been tested with a Nvidia 9600 Gt with 512MB of RAM, and it performs well. Cards with less shader operations per second may have unacceptable framerates.
[edit] VideoMemorySize
Wine does not currently have a way of knowing how much memory your video card has. Thus, specifying it on registry is the way to go. Set the VideoMemorySize to whatever you currently have (e.g. "128" for 128MB card, "256" for 256MB card, etc.)
[edit] UseGLSL
This option is required for most earlier releases of Wine, though it might be redundant after 0.9.49, where it became enabled by default.
Note that many games will not run unless your card and its driver support GLSL.
[edit] OffscreenRenderingMode
In the bleeding-edge versions of Wine, OffscreenRenderingMode setting is a tradeoff between performance and stability. Also, it's a tradeoff between one set of bugs and another set of bugs. You should pick whichever setting causes less problems for you.
pbuffer or backbuffer
This is the recommended setting for OffscreenRenderingMode (since Wine 0.9.32). It will likely result in slightly better performance and picture quality. Regrettably, in certain situations and certain Wine versions pbuffer might cause more crashes. Pbuffer is preferred for the well tested 0.9.38. (NOTE: pbuffer and possibly backbuffer are working again in wine version 1.0-rc2. However, there is a bug which causes the screen to occasionally flip upside down for a split second)
fbo
This is the stable setting, and the only setting that works for Wine versions before 0.9.32. It will give a tolerable performance, and will be less likely to crash. If pbuffer causes problems for you, you can go back to fbo. Due to the exterior cell boundary crash bug, fbo is the preferred setting for the bleeding-edge Wine versions.



