Signed-off-by: Akihiro Sagawa sagawa.aki@gmail.com --- dlls/ddraw/tests/ddraw4.c | 13 ++++++++++++- dlls/ddraw/tests/ddraw7.c | 13 ++++++++++++- 2 files changed, 24 insertions(+), 2 deletions(-)
{DDSCAPS_TEXTURE | DDSCAPS_3DDEVICE, DDSCAPS2_TEXTUREMANAGE, DD_OK,
DDSCAPS_SYSTEMMEMORY | DDSCAPS_TEXTURE | DDSCAPS_3DDEVICE,
DDSCAPS2_TEXTUREMANAGE },
What happens if you try to create a device on such a surface or assign it as a render target for an existing device?
I expect the answer to be somewhere between "driver dependent error code" and "BSOD", but it would be good to check.
On Sun, 29 Mar 2020 14:29:26 +0200, Stefan Dösinger wrote:
{DDSCAPS_TEXTURE | DDSCAPS_3DDEVICE, DDSCAPS2_TEXTUREMANAGE, DD_OK,
DDSCAPS_SYSTEMMEMORY | DDSCAPS_TEXTURE | DDSCAPS_3DDEVICE,
DDSCAPS2_TEXTUREMANAGE },
What happens if you try to create a device on such a surface or assign it as a render target for an existing device?
I expect the answer to be somewhere between "driver dependent error code" and "BSOD", but it would be good to check.
See https://testbot.winehq.org/JobDetails.pl?Key=68471 . In short, - Creating a device returns D3DERR_SURFACENOTINVIDMEM, - Setting as a render target returns D3D_OK.
However, the latter case is failed with DDERR_INVALIDPARAMS on Ryzen PC, AMD Radeon(TM) Vega 11 Graphics.
I also tested rendering target case in test_edge_antialiasing_blending(). It crashes after BeginScene() on Intel(R) HD Graphics 520, but on testbots it doesn't.
I'll improve the test based on these knowledge. Thanks for your comment.
Akihiro Sagawa