"H. Verbeet" hverbeet@gmail.com writes:
This should prevent setting an incorrect draw buffer when an FBO is active.
It doesn't work here:
../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c && touch visual.ok visual.c:8465: Tests skipped: D3DFMT_G16R16F textures not supported visual.c:8465: Tests skipped: D3DFMT_G32R32F textures not supported visual.c:7449: Tests skipped: Card has unconditional pow2 support, skipping conditional NP2 tests visual.c:8326: Tests skipped: Only 1 simultaneous render target supported, skipping MRT test visual.c:5476: Test failed: vs_3_0 returned color 0x0000ff00, expected 0x00193366 visual.c:5479: Test failed: vs_1_1 returned color 0x00ff0000, expected 0x004c0066 visual.c:5482: Test failed: vs_2_0 returned color 0x0000ff00, expected 0x004c0066 make[2]: *** [visual.ok] Error 3
2008/7/29 Alexandre Julliard julliard@winehq.org:
It doesn't work here:
../../../tools/runtest -q -P wine -M d3d9.dll -T ../../.. -p d3d9_test.exe.so visual.c && touch visual.ok visual.c:8465: Tests skipped: D3DFMT_G16R16F textures not supported visual.c:8465: Tests skipped: D3DFMT_G32R32F textures not supported visual.c:7449: Tests skipped: Card has unconditional pow2 support, skipping conditional NP2 tests visual.c:8326: Tests skipped: Only 1 simultaneous render target supported, skipping MRT test visual.c:5476: Test failed: vs_3_0 returned color 0x0000ff00, expected 0x00193366 visual.c:5479: Test failed: vs_1_1 returned color 0x00ff0000, expected 0x004c0066 visual.c:5482: Test failed: vs_2_0 returned color 0x0000ff00, expected 0x004c0066 make[2]: *** [visual.ok] Error 3
I'll take a look. I just noticed
default:
drawBuffer = 0;
slipped in, although the fact that even has any effect probably points to a bug somewhere.