http://bugs.winehq.org/show_bug.cgi?id=7914
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|directx-ddraw |directx-d3d
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=28562
Bug #: 28562
Summary: Plastic Animation Paper 4.0 doesn't start
Product: Wine
Version: 1.3.28
Platform: x86
URL: http://www.plasticanimationpaper.dk/files/pap_v4_0.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: gyebro69(a)gmail.com
CC: stefandoesinger(a)gmx.at
Classification: Unclassified
Regression SHA1: 8e79a7e6644fd6f1e0cfeb8b826e683d171d723a
Created attachment 36686
--> http://bugs.winehq.org/attachment.cgi?id=36686
plain terminal output
Users reported in the WineHQ forum that the application refuses to start in a
recent Wine.
http://forum.winehq.org/viewtopic.php?t=12970
Indeed, Plastic Animation Paper 4.0 is showing an error message when launching
with 1.3.29:
'Fatal error
Unable to set up graphics mode, graphics card must be capable of running
800x600'.
Actually, this is a regression, which happened between 1.3.27 and 1.3.28.
The problem with bisecting is that that the application is broken between these
2 commits:
http://source.winehq.org/git/wine.git/commit/76fecde8fb2d335e4855bec6d36ffe…
and
http://source.winehq.org/git/wine.git/commit/8e79a7e6644fd6f1e0cfeb8b826e68…
That was bug #28259, affecting several apps/games.
If I apply the patch (in commit [76fecde8fb2d335e4855bec6d36ffe16cbed04f3]) on
[8e79a7e6644fd6f1e0cfeb8b826e683d171d723a] then I receive the same error
message that the application produces in current git.
So I think the offending commit, preventing PAP 4.0 from starting, should be
8e79a7e6644fd6f1e0cfeb8b826e683d171d723a is the first bad commit
commit 8e79a7e6644fd6f1e0cfeb8b826e683d171d723a
Author: Stefan Dösinger <stefan(a)codeweavers.com>
Date: Sat Sep 3 21:06:11 2011 +0200
ddraw: Add some NULL pointer tests.
:040000 040000 91eec493c175fa65b5564a00127fa2e387b26f0d
25adf271715f048af26ebeba0626e0ac65ff2b71 M dlls
Added Stefan to CC.
I must also add that prior to 1.3.23, the application produces the same error
message on startup. So it only works between 1.3.23 and 1.3.28.
PAP 4.0 is now freeware.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=19146
Summary: The ClueFinders Reading Adventures Ages 9-12 crashes
on startup
Product: Wine
Version: 1.1.24
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: arethusa26(a)gmail.com
Created an attachment (id=22124)
--> (http://bugs.winehq.org/attachment.cgi?id=22124)
ClueFinders Reading Adventures backtrace
With today's Git (wine-1.1.24-421-ga3dbe3c), when trying to start the
ClueFinders Reading Adventures game, the application crashes instead of
starting normally as expected. Some fixmes of possible interest prior to the
crash were:
fixme:d3d_surface:surface_init Trying to create a render target that isn't in
the default pool.
err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for
DirectDraw!, expect problems
fixme:d3d_surface:surface_init Trying to create a render target that isn't in
the default pool.
Backtrace and +d3d,+d3d_surface log are attached.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=11416
Summary: Left or upwards scrolling in Traffic Giant corrupts
Display
Product: Wine
Version: 0.9.54.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: elicoten(a)live.co.uk
The game seems playable, and scrolling by moving the mouse to the right hand
side or bottom of the screen works as well as right click-dragging mouse the to
scroll downwards or rightwards it works. When you try to scroll left or upwards
the graphics get corrupted.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8384
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|directx-ddraw |directx-d3d
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=1248
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|directx-ddraw |directx-d3d
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7135
Austin English <austinenglish(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|directx-ddraw |directx-d3d
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=20898
Summary: Rayman 2: wine does not render "transparent color"
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: yradenac(a)free.fr
Created an attachment (id=25045)
--> (http://bugs.winehq.org/attachment.cgi?id=25045)
Screenshots of the bug
It looks like Wine 1.1.33 do not render transparency in Rayman 2.
It seems to be a regression: it used to work with Wine 1.1.24, but Wine 1.1.25
broke it and no recent version of Wine (including the current last 1.1.33)
fixes that bug.
I attach some screenshots to this report that show the bug: the right side is
1.1.24 with a correct rendering (notice the text and transparent water and
transparent sparks) whereas the left side shows the rendering of version 1.1.25
to 1.1.33 (notice the squares replacing the text and non transparent water and
black shadows and non transparent sparks).
The configuration tool that comes with the game (wine GXSetup.exe) shows the
following information:
- Renderer: "3 DirectX6 (1.0.0) DirectX 6 Driver"
- Driver: "DirectDraw HAL (display)"
- Device: "Wine D3DDevice using WineD3D and OpenGL (Direct3D HAL)"
selecting "RGB Direct3D emulation (Direct3D HEL)" for the Device do not "fix"
the bug.
I also attach the output of wine 1.1.33 when running Rayman2.exe.
Here is my configuration:
- up to date Ubuntu Karmic Koala 9.10
- NVidia GeForce FX 5600
- up to date driver nvidia 173.14.20
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=14745
Summary: wined3d BltOverride - blits from non-pow2 surfaces cause
issues without GL_ARB_texture_non_power_of_two
Product: Wine
Version: CVS/GIT
Platform: PC
OS/Version: Linux
Status: NEW
Keywords: testcase
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: alexd4(a)inbox.lv
Created an attachment (id=15241)
--> (http://bugs.winehq.org/attachment.cgi?id=15241)
testcase in form of a patch to ddraw visual test
If there is a blit from non-pow2 surface (e.g. 128x72) to screen which is
followed by a blit from pow2 surface (e.g. 128x128) to screen, then second blit
is rendered incorrectly. Presumably in the second blit the first texture is
used somehow, instead of second. So, for example, in the testcase instead of
red and green quads, both quads will be red. Also happens in a real game
(forsaken), where there are also blits from surfaces 128x72 and 128x128.
This only appears when there is no GL_ARB_texture_non_power_of_two. Probably
related to GL_TEXTURE_RECTANGLE_ARB. Affects cards like geforce 2 mx, and also
reproduced on geforce 6100 by disabling GL_ARB_texture_non_power_of_two in
directx.c. Tobias Jakobi kindly tested this on geforce fx with positive result
(bug observed).
This is as if somehow GL_TEXTURE_RECTANGLE_ARB stays selected, which may be
possible because blits do not apply states and so (afaict)
texture_activate_dimensions isn't called and GL_TEXTURE_RECTANGLE_ARB may stay
enabled in such case (again afaict, so far i couldn't find a place where it
would be disabled in case of consecutive blits). Yet, strangely, adding
glDisable(GL_TEXTURE_RECTANGLE_ARB) in BltOverride doesn't seem to help.
On geforce fx and geforce 6100 this is worked around by using orm=fbo (on
geforce 2 there is no fbo). Didn't verify that myself but Stefan said on irc in
fbo mode GL_TEXTURE_RECTANGLE_ARB is always used so this could explain why it
works (if it indeed is related to failure to "switch" from
GL_TEXTURE_RECTANGLE_ARB to GL_TEXTURE_2D).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.