<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Stefan Dösinger a écrit :
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap="">It would be better to post requests like this to <a class="moz-txt-link-abbreviated" href="mailto:wine-users@winehq.com">wine-users@winehq.com</a>
</pre>
</blockquote>
I note that for the next problem, thanks<br>
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap=""><!---->The fglrx driver you mentioned doesn't work any more on those cards. PPracer
has problems too: Start the "Doing" course. Head to the yellow arrows on the
left. They will disapper when you come really close.
</pre>
</blockquote>
I do not find the problem but i think i do not find where you find it,
i will search a next time<br>
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap=""><!---->So it basically worked with the open source driver?
</pre>
</blockquote>
Yes, without displaying the mouse and it's very slow (as if you were
playing a game with direct rendering to No). But with dri, i have
1200fps and with ati 1900fps for common glxgears, there is a
significative difference.<br>
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap=""><!---->You hit the bug ati introduced with 8.19.10. I think it's related to opengl
display lists, and I've reported it to ati months ago. Didn't get a reply so
far
</pre>
</blockquote>
So, i have just reported them the problem and explain that it works
with dri, so i hope they will make something to correct it....<br>
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap=""><!---->These are harmless, they are fixmes from the direct3d initialization. Some
render states aren't supported by wines d3d implementation, but when wined3d
initializes, it sets them to the default value, which causes such messages.
The last three fixmes are fixed in the current cvs version, and they are
harmless too
</pre>
</blockquote>
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap=""><!---->EvictManagedTextures is a windows-related video memory management thing, and
it won't have much impact too. If it has, then it will only show slightly
reduced performance for a few secounds after loading. It should remove the
managed textures from the video card, to make the memory free for new
textures.
</pre>
</blockquote>
Ok, thanks for the informations
<blockquote cite="mid200603310924.34665.stefandoesinger@gmx.at"
type="cite">
<pre wrap="">WineD3D has serious performance problems, somehow related to textures. I hope
that I can debug them during the weekend, but I can't give garantees. These
problems seem to be related to textures. My tests with 3dmark2000 show that
texture rendering should be 10 times faster than it is.
I hope I could help you,
Stefan
</pre>
</blockquote>
I do not need garantees, i know that it's difficult to make something
work correctly. I hope we can help you, not the contrary :-)<br>
Christophe<br>
</body>
</html>