PC Release of the game Braid.
Game is also available on Steam.
Old test results
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)
Pretty much everything.
I've been using Steam version of the game to do the tests and it seems to run pretty well in you happen to install and run it under clean Wine prefix. Messing with some wined3d-related registry entries like changing "AlwaysOffscreen" to "enabled" or forcing game into using builtin d3dx9_*.dll could render the game into unplayable state but it's just the usual "shoot yourself in the foot" problem.
Game requires native d3dx9_36.dll (actually d3dx9_39.dll but Wine's builtin implementation of this lib forwards almost all calls to d3dx9_36.dll so one could easily use native version of any among these) to run. For Steam version of the game this library gets auto-installed as the part of DirectX redist installation - Steam client would proceed with automated install on the first attempt to run the game inside the given Wine prefix.
What does not
There's a minor bug with one having to press both shift keys to move a puzzle piece. This bug is not essential as (a) it's easier to use mouse for solving puzzles and (b) it's not a big deal to hold one shift key and briefly press and release another one to pick a puzzle piece.
What was not tested
Everything was tested, I had played the whole game through - it's not that long really.
Giving it "Platinum" rating as Steam auto-install required native DLLs so it is "works perfectly out of the box" situation from the users perspective.
AMD FX 8120 CPU @3.1GHz, 8GB DDR3 RAM, GeForce GTX 550 Ti GPU with 1GB VRAM, nVIDIA Binary Driver v.275.09.07, linux kernel 188.8.131.52-3.lx2.fclx2.i686.PAE (it is kernel 3.1.10 which had been rebranded by Fedora devs to version 184.108.40.206).
Thank you very much for wishing to spend some time on improving AppDB.
I have to warn you that general AppDB policies forbid (a) accepting test results for patched Wine versions and (b) forbid accepting results obtained from PoL-driven Wine installations, only "vanilla" unpatched Wine or Wine that had came by default with your distro are considered to be valid. I'm really sorry for that, but it is the way it currently is.
For more details feel free to read discussion on wine-devel mailing list that held place around the 16th of May, 2012.
Aside from the requirements above your test results should comply with some simple rules to be accepted:
Please, test an application under fresh clean wineprefix;
Include exact specs of the computer you had tested an app on (CPU, GPU, amount of RAM and VRAM) in the "Extra Comments" section of the report;
Specify versions of essential software components, most notably: is your system 32bit or 64bit, what is the version of the GPU display driver you use and what is the version of the OS kernel;
Include detailed information on the native dll overrides you had to use in order to get the game working. If you had installed dlls yourself - include complete information on the sources of dlls and the exact steps you took to install them.
Thank you in advance!
General info about playing Braid under Wine
This game is known to run exceptionally well (i.e. at "Platinum" level) under Wine as long as (a) native d3dx9_36.dll is used and (b) you use closed-source GPU drivers provided by GPU chipset vendor (assuming that you use a card based on nVIDIA or ATI/AMD GPU). There might be problems like low FPS, incorrect rendering or game crashes in case you use OSS drivers. Recent versions of OSS driver for Intel GPUs are known to perform sufficiently well, while nouveau or radeon open source drivers might cause troubles.
Steam version of the game auto-installs DirectX redist for you when your try to start the game up for the first time in a new Wine prefix. Retail game version also comes with bundled DirectX redist and it usually install it into the prefix as a part of the game setup process.
Installing DirectX is essential as the game fails to work properly (and crashes to desktop) in case Wine's built-in d3dx9_36.dll implementation is being used (as of Wine 1.5.5; it might get fixed in future Wine versions). In case you happen to find yourself in a situation when the game crashes soon after start up - most probably it could be "fixed" by installing native d3dx9_36.dll into the Wine prefix. One of the easiest ways to do it is to use "winetricks" script (google about what is it, from where could it be downloaded and how to properly install and use it) by executing "winetricks d3dx9_36" in the terminal window. Be sure to export correct path to your Wine prefix in case non-standard one being used (i.e. run «export WINEPREFIX=<full path to Wine prefix you use>» prior to invoking winetricks).
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Jake ward on Tuesday August 17th 2010, 7:44
dll override in game's directory
by S Johnson on Saturday July 10th 2010, 17:46
Braid only requires d3dx9_36.dll to be placed in the game's directory. Adding other dll's via winetricks or registering dll in winecfg is unneccessary.
Sound stuttering happened rarely but was resolved by restarting pulse audio. Kill pulse with 'pulseaudio -k'. Check if killed with 'ps -ef | grep pulse'. Restart with run dialog (ALT-F2) and 'pulseaudio -D'
wtf it freezes the OS
by Lo'oris on Thursday January 28th 2010, 8:36
Installed demo through steam.
At first run it installed some directx stuff, as mentioned in the test result.
Then it hang. It hang the whole mac.
Tried again, hang again.
The only way out is a hard reset, no key combination worked, only the mouse pointer kept moving (it was the windows pointer) but was completely unable to do anything.
wtf, an app shouldn't be able to takeover all the input this way.
folder and finally, in Wine's configuration utility (in terminal, the command "winecfg"), go to "Libraries" tab, press "Add" and select d3dx9_36.dll from the list. Then, edit it and change it to "native". Apply changes and exit.
This is for the game to start, or else it will complain that d3dx9_36.dll is missing. By the way, Windows users seem to have a similar problem.
b) I am not sure if this is a universal problem but after I exit the game, the resolution is messed up and then I have to kill the X server to fix it.
What I'm doing to prevent this is part of what Bontas Marcel has suggested.