http://bugs.winehq.org/show_bug.cgi?id=8051
Peter Beutner p.beutner@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |p.beutner@gmx.net
--- Comment #25 from Peter Beutner p.beutner@gmx.net 2007-12-16 15:50:31 --- (In reply to comment #22)
(In reply to comment #21)
1)As it seems there isn't really a "software processing mode" in wined3d (right?),
Correct
that might be a problem. The game seems to be constantly switching between software and hardware processing :/.
Oh indeed, the sdk says it is internal and should not be used. That will be tricky. Note that we must not look at the windows code to find out what it does. We can try to find out what it does by writing tests, and looking at what Sim2 wants.
everything I did so far is catching the segfault in winedbg and hit disas. That is enough to guess the functions in the vtable and the number of parameters.No windows code involved.
Demo is still completely unusable though because of rendering errors(most notably the sim isn't rendered at all).
Could be because of the shader constant problems. Does Sims2 ever set anything else but 0/0/0/0 to any constant > 224?
not that I have seen it
(In reply to comment #24)
I did some testing with it long time ago : http://www.nabble.com/add-stub-for-Direct3DShaderValidatorCreate9--28d3d9-29...
guess I will just try to send my stub version and see what happens ;) btw. at least here the function is loaded via GetProcAddress so the comment to your patch might have been wrong as well.
-
wine-bugs＠winehq.org