--- Aric Cyr <[EMAIL PROTECTED]> wrote:
> Tom Spear gmail.com> writes:
>
> >
> > Aric Cyr wrote:
> > >>>I took a look at the D3D_OK hack, and I believe the problem to be
> > >>>CheckDeviceFormat in wined3d/directx.c. This function should return an
> > >>>error if
> > >>>D3DFMT_D32 is checked
Hi,
On Thursday 22 December 2005 03:29, Aric Cyr wrote:
> Tom Spear gmail.com> writes:
> > Aric Cyr wrote:
> > >>>I took a look at the D3D_OK hack, and I believe the problem to be
> > >>>CheckDeviceFormat in wined3d/directx.c. This function should return
> > >>> an error if
> > >>>D3DFMT_D32 is
Tom Spear gmail.com> writes:
>
> Aric Cyr wrote:
> >>>I took a look at the D3D_OK hack, and I believe the problem to be
> >>>CheckDeviceFormat in wined3d/directx.c. This function should return an
> >>>error if
> >>>D3DFMT_D32 is checked for on cards which don't support 32bit depth.
> >>>Curre
Aric Cyr wrote:
I took a look at the D3D_OK hack, and I believe the problem to be
CheckDeviceFormat in wined3d/directx.c. This function should return an error if
D3DFMT_D32 is checked for on cards which don't support 32bit depth. Currently
it just returns OK for most formats though. This code
Tom Spear gmail.com> writes:
> Louis also hard coded D3D_OK into wine in the right spot and managed to
> get the program to go thru all benchmarks from 1-16, so wine is
> mis-reporting something there.
>
> If someone could take a look and propose a fix, it would be appreciated,
> seems to me
Hi, I was working on bug 3885 tonight, and am stuck now.. Could someone
take a look and test a couple of things?
I'm running 2.6 series kernel, and it keeps dieing into the debugger
before the main window opens.
I think that it will sart with builtin msvcrt with 2.4 series kernel,
bu
