Emulator

This applies only Direct3d9 not Direct3D11. in Direct3D11 it's just fine.

This happens to me while recording with Fraps

Happens to me on r7637 x64, on win7x64. Try to go full screen, invalid call. Have to kill dolphin with the task manager.

Yes, quite right it is completely the same with me Dolphin crashes and I have to use task manager and get Dolphin completely away.

Man I hope someone sees this.

Still present as of r7667. So, to settle this, I recorded EVERY window that appears. There was alot. If there is more information on the Invalid Call problem, I don't know what it is.

Remember to read from bottom to top. Thanks to photoshop it was possible to record and organize it, but it stacked them bottom to top and I didn't want to have to manually change them for hundreds of layers. Also, when one repeated alone a bazillion times, I just counted the number of times it appeared before it changed, and then put it as a notation.

http://img98.imageshack.us/img98/3787/invalidcalls.png

I tried it on 5 games in total. Just start the game (in DX9), maximize, crash. Every single one. I tried FzeroGX, Twilight Princess, Wind Waker, Okami, and Smash Brothers Melee. Happened every single time without fail. It should be noted however, that there were some slight variations. I recorded Okami and Twilight Princess in this manner. Twilight Princess is what you see in the image here. Okami's first dozen or so are the same (didn't compare too deep), but it's "CreatePixelShaderFromByteCode failed at Src\D3DShader.cpp 84" errors, when it had it's big bunch, it only had 21, versus the 89 present in Twilight Princess. Possibly do to the number of shaders used by the game?

Issue 4701 has been merged into this issue.

Whoops! Sorry for the duplicate issue. Will try new revision ASAP.

r7671 works. Maximize, minimize, and resize all without invalid call or crashes. Looks fixed to me.

Yeah it seems to be all set in r7671.