Emulator Issues #4638
closed
Invalid Call? Problem on Dolphin r7633!
0%
Description
What's the problem?
I just try and enlarge the window and then suddenly I get this message ----) Invalid Call? I for not taking the window larger. This has not happened before
Dolphin version with the problem (as it appears in the title bar, Ex.: "R
4779" or "R 6403M"):r7633
(optional) Dolphin version that does not have the problem:
Operating system and version:
32-bit or 64-bit: Win7 64bit
Game ID (as it appears in game properties, Ex.: "GZ2P01" or "RSBE01"):
Build command-line (not on Windows):
Was the ISO a plain dump from disc, compressed and/or scrubbed?
Please provide any additional information below.
Specifications:
Processor: Intel Core i5 760 Quad-Core 2.80Ghz 8MB Cache memory.
Graphics Card: NVIDIA GeForce GTS 450 1GB
DirectX 11, OpenCL, DirectCompute, OpenGL 4.0
Memory: 4GB 1333 MHz.
Operating Systems: Windows 7 Ultimate Service Pack 1 64bit.
Updated by William79371 over 13 years ago
This applies only Direct3d9 not Direct3D11. in Direct3D11 it's just fine.
Updated by florian98.rg over 13 years ago
This happens to me while recording with Fraps
Updated by MayImilae over 13 years ago
Happens to me on r7637 x64, on win7x64. Try to go full screen, invalid call. Have to kill dolphin with the task manager.
Updated by William79371 over 13 years ago
Yes, quite right it is completely the same with me Dolphin crashes and I have to use task manager and get Dolphin completely away.
Updated by MayImilae over 13 years ago
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?
Updated by Nolan.Check over 13 years ago
- Status changed from New to Accepted
- Issue type set to Bug
- Category changed from gfx to ui
- Relates to usability set to Yes
Reproduced. There are probably some non-managed pool resources that aren't getting destroyed when we recreate the device. I'll try to find it.
Updated by Nolan.Check over 13 years ago
Issue 4701 has been merged into this issue.
Updated by Nolan.Check over 13 years ago
- Status changed from Accepted to Work started
Is this fixed in r7671?
Updated by bastos.eder over 13 years ago
Whoops! Sorry for the duplicate issue. Will try new revision ASAP.
Updated by MayImilae over 13 years ago
r7671 works. Maximize, minimize, and resize all without invalid call or crashes. Looks fixed to me.