Re: [PATCH 0/1] MR3970: quartz/tests: Improve VMR9 ChangeD3DDevice test

[Zebediah Figura (＠zfigura)]

> I tried everything I could think of, but Windows absolutely refuses to present a frame after changing the D3D device, instead choosing to return various absurd errors (segfaults, deadlocks, out of memory, etc). I suspect the VMR9 is haunted.

This was for Kirikiri, right? How is that application using ChangeD3DDevice()?