fbo offscreen rendering appears to have been fixed in wine 1.1.24 which has just been released. Also X3R got fixed for me as well, in that the menu now renders and so do ingame textures, although all of the "normal" wine problems still exist. i.e. requires native libraries for movie playback, trading, etc. mouse is EXTREMELY laggy.
So those, apparently were actually wine bugs and not fglrx bugs.
GW still crashes as normal, and still wants to repair the archive every startup. The latter is definitely a wine bug, while I'm not at all sure about the cause of the former. In any even it now actually crashes in the loading screen itself instead of seeming to get as far as starting to render the playscreen.
My sleep & video playback & other assorted bugs remain which I'm still pointing the finger at fglrx for as in the sleep freeze problem disabling compiz/beryl works around that one.
@jdifool
The 192SP 260 is about the same price as the 4850 while the 216SP is c. $50 more which is not alot more, and it IS a better performing card than the 4850. The 216SP 260 IS going into my i7 build because of these drivers. (Briefly consider CF 4770s, but NOT with these drivers.)
So those, apparently were actually wine bugs and not fglrx bugs.
GW still crashes as normal, and still wants to repair the archive every startup. The latter is definitely a wine bug, while I'm not at all sure about the cause of the former. In any even it now actually crashes in the loading screen itself instead of seeming to get as far as starting to render the playscreen.
My sleep & video playback & other assorted bugs remain which I'm still pointing the finger at fglrx for as in the sleep freeze problem disabling compiz/beryl works around that one.
@jdifool
The 192SP 260 is about the same price as the 4850 while the 216SP is c. $50 more which is not alot more, and it IS a better performing card than the 4850. The 216SP 260 IS going into my i7 build because of these drivers. (Briefly consider CF 4770s, but NOT with these drivers.)
Comment