http://bugs.winehq.org/show_bug.cgi?id=7446
------- Additional Comments From hverbeet(a)gmail.com 2007-16-02 15:10 -------
I think that warning is harmless, but you could try commenting out the line that
generates it (line 843 in dlls/wined3d/pixelshader.c).
The following line looks a bit more interesting, but doesn't necessarily have to
be a problem either:
fixme:d3d_shader:print_glsl_info_log Error received from GLSL shader
#2147483649: "Warning: built-in varying gl_TexCoord[0] has mismatched access
semantics between the vertex and fragment shader\n Link successful. The GLSL
vertex shader will run in hardware. The GLSL fragment shader will run in hardware."
Unfortunately there are currently also a few regressions that might be affecting
the game.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5788
------- Additional Comments From stefandoesinger(a)gmx.at 2007-16-02 15:01 -------
The DDBLT_WAIT flag fixme is harmless, in the worst case it causes performance
issues but should never stop an app from running.
Actually DDBLT_WAIT is perfectly implemented, wine cannot handle the absence
of this flag. So the fixme is wrong.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7446
------- Additional Comments From jrliggett(a)cox.net 2007-16-02 14:57 -------
Thanks for the info, Stefan. Actually, maybe it's not a GLSL problem, as Henri
pointed out to me that one of my eariler runs didn't GLSL enabled right, and the
screen was still black. With glsl done properly on the second run, I get the
same results. Is there an older version of fglrx that doesn't show this behavior?
Also I don't know if this is relavent, but it still looks odd to me: I looked
through the log (the one with GLSL properly enabled) and I got a lot of errors
that look like: "fixme:d3d_shader:print_glsl_info_log Error received from GLSL
shader #536870914: "WARNING: 0:1: extension 'GL_ARB_draw_buffers' is not
supported\n." But the odd thing is that I have the GL_ARB_draw_buffers extension
(it shows up in my glxinfo, as well as the one attached.)
Thanks again
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7451
------- Additional Comments From renekok(a)gmail.com 2007-16-02 13:51 -------
EDIT: That should be /dlls/gdi32/bitblt.c of course
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7451
Summary: Unreal Editor bitblt fails and crashes
Product: Wine
Version: 0.9.30.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-gdi-(printing)
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: renekok(a)gmail.com
The Unreal Editor (for Unreal Tournament) fails when you start it up. This is
the message from the editor:
Critical: appError called:
Critical: BitBlt failed: Success
Critical: Windows GetLastError: Success (0)
Being a hackish type of person I go into /dlls/bitblt.c and change the bitblt
function like this:
return ret;
to:
if (ret == 0)
ret = 1;
return ret;
and now it bleeding works. Of course that's a hack, not a real fix.
Ret = 0 seems to happen in this case when the first if-case ret is being set by:
ret = dcDst->funcs->pBitBlt( dcDst->physDev, xDst, yDst, width, height, dcSrc ?
dcSrc->physDev : NULL, xSrc, ySrc, rop ); that's line 72/73.
For some weird reason dcDst->funcs->pBitBlt( dcDst->physDev, xDst, yDst, width,
height, dcSrc ? dcSrc->physDev : NULL, xSrc, ySrc, rop ); returns zero, where it
probably should return 1. In fact most cases it does return 1, just in some
occasions it doesn't. I did some simple debugging for that.
I don't have the skills to find out anything else, it's all hocus pocus from
here on in. Let me know if I can help.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7446
------- Additional Comments From jrliggett(a)cox.net 2007-16-02 13:08 -------
Created an attachment (id=4963)
--> (http://bugs.winehq.org/attachment.cgi?id=4963&action=view)
New log file (hopefully using GLSL this time :)
Ok this one should be using GLSL. Don't know what happened last time :( I
skimmed through this one and see a lot of glsl type stuff in it, so maybe I did
this one right. And I didn't see "!!ARBfp1.0" in this one, so maybe that's a
good sign.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7448
------- Additional Comments From jisakiel(a)yahoo.es 2007-16-02 12:58 -------
OK, recompiled with CXXFLAGS = CFLAGS = "-march=pentium-m -mtune=pentium-m -msse
-msse2 -ggdb -fno-strict-aliasing -pipe", and with CCACHE disabled. As expected,
same problem happen, so this is another confirmation.
(thou I got interested in the fno-strict-aliasing... I still don't use to code
that low, so I didn't know anything about that... Now I am recompiling a couple
of packages that are a bit problematic, such as firefox).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=7105
------- Additional Comments From jonass(a)lysator.liu.se 2007-16-02 12:48 -------
Created an attachment (id=4961)
--> (http://bugs.winehq.org/attachment.cgi?id=4961&action=view)
using latest patch and WINEDEBUG=+cursor,+relay
Unfortunatly it seems like the patch did not work. The program crashes at the
same time and the log seems, to me, to be similar to the one without any patch.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.