Henri Verbeet wrote:
This is essentially the situation that caused problems with reusing the initial GL context.
dlls/d3d9/tests/device.c | 65 ++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 65 insertions(+), 0 deletions(-)
Hi Henri,
- hr = IDirect3D9_CreateDevice(d3d9, D3DADAPTER_DEFAULT, D3DDEVTYPE_HAL, hwnd1,
D3DCREATE_SOFTWARE_VERTEXPROCESSING, &present_parameters, &device1);
- ok(SUCCEEDED(hr), "Failed to create a device, hr %#x\n", hr);
This one seems to fail on a lot of boxes, currently only VMware and ATI so it seems. NVIDIA and Intel seem to be fine though (for now as only a few tests are in).
Is D3DERR_NOTAVAILABLE an acceptable error? If so than the ok() message can be easily extended (maybe with an extra skip() message?).
Could you have a look?
2009/7/3 Paul Vriens paul.vriens.wine@gmail.com:
Is D3DERR_NOTAVAILABLE an acceptable error? If so than the ok() message can be easily extended (maybe with an extra skip() message?).
Probably, although you can also just remove the test if it causes a lot of failures. I added it because this situation exposed a bug in wined3d's initialization code, but it's not by itself critical for anything.