Retail version (including minor patches). Please mention the distribution platform (DVD, Steam, etc.) and game version in your test results.
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)
Installer - Sorta
What does not
What was not tested
Anything past the launcher
The installer hangs at the end when it tries to install the PhysX software. Tried to install PhysX software manually with no luck.
Once all the files are copied over from the installer, you can run the main launcher but if you try to run the game it crashes due to missing PhysX libraries.
Tested with 1.0.1, 1.1.31, and 1.1.32 with all the same problems.
Afterwards you can install them using the "daupdater.exe", which requires dotnet20 (.NET Framework2.0).you can install it using winetricks :
For 64 bits Users
In order to install the required components for Dragon Age DLC's, you will
have to create a 32 bits wineprefix and install everything there
(Dragon Age Origin included).
To create your 32 bits prefix : WINEARCH=win32 WINEPREFIX=/path/to/wineprefix winecfg
To start winetricks in that prefix : WINEPREFIX=/path/to/wineprefix winetricks
To run Dragon Age from this prefix : WINEPREFIX=/path/to/wineprefix wine /path/to/DragonAge/daorigins.exe
If you experiment any bug listed above, or any non listed bugs, please report it to wine bugzilla, specifying your wine version : http://bugs.winehq.org/
This will help wine team to solve them.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
crashes on loading screen—possible framebuffer problem?
by nskaran on Monday March 24th 2014, 13:13
hi! i installed the game today, and i encountered a black screen upon loading but i fixed that with winetricks strictdrawordering=enabled. now, though, i get to the loading screen with the dragon, the dragon gets halfway across the screen, and then it freezes. it's unresponsive so i have to force quit to get back to the Steam window, and the debugger is open but when i try to get details it just loads forever—so i can't offer the debugger output, sorry!
here is the terminal output at the point when i think it starts having the problem, though: pastebin.com/fgCX4U2z
is this related to an acknowledged problem? does anyone have an idea of how to fix it?
by rkfg on Thursday January 24th 2013, 13:11
I can't tell for sure yet but it seems that turning off the framebuffer effects eliminates these crashes when you open the inventory or such. I play with this option off for the second day and I haven't got a single crash while before it sometimes crashed right after opening the inventory windows for the first time! The error which accompanied the crash is still in the log but it doesn't affect the game anymore it seems:
fixme:d3d:context_check_fbo_status FBO status GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT (0x8cd6)
fixme:d3d:context_check_fbo_status Location SFLAG_INTEXTURE (0x40000).
fixme:d3d:context_check_fbo_status Color attachment 0: (0x16cd3a78) WINED3DFMT_DXT1 512x256 0 samples.
err:d3d:context_bind_texture >>>>>>>>>>>>>>>>> GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glBindTexture @ context.c / 1955