The Virtual console wads keep giving me errors on trying to load them. All have errors pointing to the videobackends forlder.
I've tried D3d11, OGL & Vulkan (I own 1070 GPU)
I keep getting a message "Ignore and continue"
I've tried ignore - I've tried ignore for session - I've tried No.
They all cause dolphin to crash out
Any sensible Ideas please, would be appreciated.
Thanks
Frank
Could you post the exact text of the error (or at least of one of the errors if there are multiple ones with different text)? Also, it would be helpful to know the version of Dolphin that you're using.
(03-15-2019, 02:05 AM)JosJuice Wrote: [ -> ]Could you post the exact text of the error (or at least of one of the errors if there are multiple ones with different text)? Also, it would be helpful to know the version of Dolphin that you're using.
Will do - I'll run it now
I'm trying OpenGL for this test.
they all come on line
43
353
355
C:\buildbot\release\win-x64\build\source\core\videocommon\abstractstagingtexture.cpp
C:\buildbot\release\win-x64\build\source\core\videobackeds\ogl\ogltexture.cpp
Does that make sense?
Frank
The build is
5.0-9751 : Branch: master : Revision: 011ecd92e8e2b0b78471cc7ad394b6ed1f7a451e
Frank
Dolphin
5.0-9779
Branch: master
Revision: 96fec2eb708648d6b75da0d2a523c2c7c9d5088c
Now getting same errors, but on different Lines
42
738
740
Also, It just seems to be the Arcade WADS now - is that any help?
Updated to latest version - ran my tests again. Still crashes out on Arcade WADS - Here's all the details (Sorry if it's all boring)
D3D
43: videocommon\abstractstagingtexture.cpp
216: videobackends\d3d\d3dtexture.cpp
218: videobackends\d3d\d3dtexture.cpp
OGL
43: videocommon\abstractstagingtexture.cpp
353: videobackends\ogl\ogltexture.cpp
355: videobackends\ogl\ogltexture.cpp
Vulkan
43: videocommon\abstractstagingtexture.cpp
734: Videobackends\vulkan\vktexture.cpp
736: Videobackends\vulkan\vktexture.cpp
All with Synchronous (Ubershaders) with compile before playing option ticked.
Dolphin Version: 5.0-9861
Branch: master
Revision: 5a10707a37ba6828aec97a646fc22ed0bd0be0c3
Frank
Should be fixed in latest master.
Yup
That seems to be working fine now - Thanks for that
Frank