http://bugs.winehq.org/show_bug.cgi?id=21726
Summary: Explicit access to and creation of front/back buffers for DirectDraw interfaces prior to version 7 needed Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P1 Component: directx-ddraw AssignedTo: wine-bugs@winehq.org ReportedBy: mikademus@gmail.com
In DirectDraw, the interfaces prior to version 7 allow the explicit creation of front and back buffers. In DirectDraw7, which is the last and latest ddraw implementation, this was changed.
Currently, the WINE implementation of ddraw seems to use the same functions for front/back buffer handling, function that seem to be based in the ddraw7 interface and prohibits explicit front and back buffers. This breaks a fair amount of older games which rely on earlier ddraw interfaces.
http://bugs.winehq.org/show_bug.cgi?id=21726
Michael mikademus@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |tasklist, winelib
http://bugs.winehq.org/show_bug.cgi?id=21726
Michael mikademus@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Blocks| |9008, 9190
http://bugs.winehq.org/show_bug.cgi?id=21726
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 |P2 Alias|frontbackbuffers | Severity|major |normal
--- Comment #1 from Vitaliy Margolen vitaliy@kievinfo.com 2010-02-15 08:48:16 --- Please provide example of the game, and the actual problem with that game. Of course make sure to test with latest Wine version.
http://bugs.winehq.org/show_bug.cgi?id=21726
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|tasklist, winelib | Status|UNCONFIRMED |RESOLVED Blocks|9008, 9190 | Resolution| |INVALID
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2010-02-15 08:49:12 --- Don't open beta bugs.
http://bugs.winehq.org/show_bug.cgi?id=21726
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED Component|directx-ddraw |-unknown
--- Comment #3 from Vitaliy Margolen vitaliy@kievinfo.com 2010-02-15 08:49:26 --- Closing
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #4 from Michael mikademus@gmail.com 2010-02-15 15:16:11 --- (In reply to comment #2)
Don't open beta bugs.
Sorry, I don't understand. Did I report it to the wrong version of WINE? What is the procedure, should I reopen it for another version? I've never reported a bug here before...
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #5 from Andrew Nguyen arethusa26@gmail.com 2010-02-15 15:19:45 --- Vitaliy meant to say metabug. In general, you should open bug reports for specific issues in a particular application. The page http://wiki.winehq.org/Bugs discusses some general guidelines for bug reporting.
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #6 from Vitaliy Margolen vitaliy@kievinfo.com 2010-02-15 20:09:43 --- Yes, meant "meta bugs". They don't help just add extra clutter and noise.
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #7 from Michael mikademus@gmail.com 2010-02-16 02:07:39 --- Ok, thank you for the help and pointers.
This kind of error, what is the proper forum to take them? I have located a todo wiki page for DX (http://wiki.winehq.org/DirectX-ToDo) where I was thinking of adding this, but if you know a better (or the correct) place, I'd appreciate if you pointed me there.
Thanks for your kind assistance :)
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2010-02-16 03:47:35 --- Do you have a specific application which doesn't work because of this problem?
Also please specify Wine version you have tested with.
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #9 from Michael mikademus@gmail.com 2010-02-16 04:29:47 --- (In reply to comment #8)
Do you have a specific application which doesn't work because of this problem?
Also please specify Wine version you have tested with.
I know of at least two games: Warhammer: Dark Omen (bug 9190), and Combat Pillows (bug 9008). It is possible that Fate Axis (recently closed bug 8232, game still not running, though) depends on this too.
Tested the two first games with WINE version 1.1.24 on Fedora.
http://bugs.winehq.org/show_bug.cgi?id=21726
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.1.24
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2010-02-16 05:20:24 --- (In reply to comment #9)
I know of at least two games: Warhammer: Dark Omen (bug 9190), and Combat Pillows (bug 9008). It is possible that Fate Axis (recently closed bug 8232, game still not running, though) depends on this too.
Why do you think that the problems in that games are caused by this? Are there bug reports for problems in that games?
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #11 from Michael mikademus@gmail.com 2010-02-16 14:36:24 --- (In reply to comment #10)
(In reply to comment #9)
I know of at least two games: Warhammer: Dark Omen (bug 9190), and Combat Pillows (bug 9008). It is possible that Fate Axis (recently closed bug 8232, game still not running, though) depends on this too.
Why do you think that the problems in that games are caused by this? Are there bug reports for problems in that games?
Yes, both games have bug reports where the dumps indicate they need explicit back and/or front buffers.
I remember coding games myself for DX5 and DX6 many years ago now, and I made heavy use of explicit access to front and back buffers. In fact, for DX games < v7 it was recommended practice for performance to create multiple back buffers and fill them progressively to use CPU cycles efficiently. DX3 games often blitted directly to the front buffer.
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #12 from Dmitry Timoshkov dmitry@codeweavers.com 2010-02-16 23:48:31 --- (In reply to comment #11)
Yes, both games have bug reports where the dumps indicate they need explicit back and/or front buffers.
Then there is no need to create duplicate bug reports.
http://bugs.winehq.org/show_bug.cgi?id=21726
--- Comment #13 from Michael mikademus@gmail.com 2010-02-17 02:50:13 --- (In reply to comment #12)
(In reply to comment #11)
Yes, both games have bug reports where the dumps indicate they need explicit back and/or front buffers.
Then there is no need to create duplicate bug reports.
Ok, procedure learned. Should we amend the bug report guidelines page with this, since as far as I found it wasn't mentioned anywhere?
The reason this post was made was because I though is suitable to describe a root cause, the fixing of which might hopefully solve a slew of other bugs. Especially since the apps/games affected tend to be older and not receive much attention.
But thank you for your time.