Mirek wrote:
Ok, i just found why is it not working with this patch, and why is it
working without this patch. It is based on position of definition MOVA
in vertexshader.c, if MOVA is on after patch position it is not
working, but if i move line
{WINED3DSIO_MOVA, mova, NULL, 1, 2,
On 10/28/06, Mirek [EMAIL PROTECTED] wrote:
Yes I did that this way. I tried it three times as it is now in CVS
(3DMark 2003 and Flatout 2 not working) and three times without this
patch (only) (3DMark 2003 and Flatout 2 works just perfect).
Mirek
I see the same thing as Mirek, 3dmark03 is
I see the same thing as Mirek, 3dmark03 is totally broken now.
And yes I tested GLSL and ARB and before and after with the same results as his.
So yes, this is a major regression :D
Tom
Tom Wickline wrote:
I see the same thing as Mirek, 3dmark03 is totally broken now.
And yes I tested GLSL and ARB and before and after with the same
results as his.
So yes, this is a major regression :D
When testing with the GLSL backend, can you please do a +d3d_shader
trace, find the
Here is log with 3DMark running for about 3 seconds with patch and
without, trace+d3d.
http://www.czela.net/pub/Czela_Debian_2.5/mirek/wine/regression/3DMark03.tar.gz
Mirek
Ivan Gyurdiev napsal(a):
Tom Wickline wrote:
I see the same thing as Mirek, 3dmark03 is totally broken now.
And
Here is log with 3DMark running for about 3 seconds with patch and
without, trace+d3d.
http://www.czela.net/pub/Czela_Debian_2.5/mirek/wine/regression/3DMark03.tar.gz
There's no mova instruction in that log.
Ivan Gyurdiev wrote:
Here is log with 3DMark running for about 3 seconds with patch and
without, trace+d3d.
http://www.czela.net/pub/Czela_Debian_2.5/mirek/wine/regression/3DMark03.tar.gz
There's no mova instruction in that log.
...grep for mova, or for unrecognized or Unrecognized or
Ok, i just found why is it not working with this patch, and why is it
working without this patch. It is based on position of definition MOVA
in vertexshader.c, if MOVA is on after patch position it is not
working, but if i move line
{WINED3DSIO_MOVA, mova, NULL, 1, 2, vshader_mova,
Hi, i just installed latest version of wine and now 3DMark 2003 and
Flatout 2 is not working anymore, i look at the patches commited
yesterday and found this patch which is causing this regression.
Mirek
Am Samstag 28 Oktober 2006 10:35 schrieb Mirek:
Hi, i just installed latest version of wine and now 3DMark 2003 and
Flatout 2 is not working anymore, i look at the patches commited
yesterday and found this patch which is causing this regression.
In which way do they not work any more? Is there
Hi, screen is just black in those two apps, other apps (3DMark 2001,
2005, 2006, NFS MW, Oblivion, TRL, W3, WoW, Prey, Starcraft, Diablo 2,
GTA SA, HL 2 EO, HL, NFS 3, NFS 4, Turok, Ignition, Carmageddon 2,
Carmageddon 3, Pandemonium 2) works without any problem.
Here is screenshot from
The MOVA instruction is a 2.0 instruction, which cannot be fully
implemented in ARB.
However, the patch shouldn't have caused a regression - if you're seeing
a black screen with GLSL also, that means another patch is responsible
for this.
Mirek wrote:
I tried it three times with same result. Can someone else test if
3DMark 2003 is working with latest wine?
You shouldn't test if it's working now - test if it's working before the
MOVA patch, and if it's not working after the MOVA patch [ no other
patches in between ].
Yes I did that this way. I tried it three times as it is now in CVS
(3DMark 2003 and Flatout 2 not working) and three times without this
patch (only) (3DMark 2003 and Flatout 2 works just perfect).
Mirek
Ivan Gyurdiev napsal(a):
Mirek wrote:
I tried it three times with same result. Can
I tried it three times with same result. Can someone else test if 3DMark
2003 is working with latest wine?
Mirek
Ivan Gyurdiev napsal(a):
The MOVA instruction is a 2.0 instruction, which cannot be fully
implemented in ARB.
However, the patch shouldn't have caused a regression - if you're
15 matches
Mail list logo
