I'm sorry, this is in the wrong section as I initially thought this was a SVN Build problem but it's not, it's now a computer problem.
I've been away from my computers for a while and the last time I had Dolphin was r7607. I updated to r7613 and I find that enabling OpenCL in DirectX9/11 crashes any game or Wii menu upon startup with 'Dolphin.exe has stopped working' and your usual send/don't send choices. The Windows 7 Professional x64 was freshly installed since I had r7067 and the machine was joined to a new domain with roaming profiles. I don't see how this could be a problem. I'm going to downgrade back to the old versions and see if I can track down where the problem began. In the meantime, anyone else having this problem?
Microsoft Visual C (x64) was installed and up to date as well as all Windows updates and ATi's Catalyst drivers. I can confirm this is now happening in all builds. Don't know if this is helpful, but Windows throws this up too:
Files that help describe the problem:
C:\Users\%username%\AppData\Local\Temp\WER6B7F.tmp.WERInternalMetadata.xml
C:\Users\%username%\AppData\Local\Temp\WER82D7.tmp.appcompat.txt
C:\Users\%username%\AppData\Local\Temp\WER8355.tmp.mdmp
Unhandled Exception
Code: 0xE06D7363
Call stack info:
0xFE0FA49D : ?
0x258BF760 : ?
Unhandled Exception
Code: 0xE06D7363
Call stack info:
0xFE0FA49D : ?
0x259FF410 : ?
In GPU-Z, the OpenCL box is ticked for my graphics card and my DirectX is up-to-date.
Normally, ordinary CPU texture decoding is acceptable, but then add a DSP-LLE on thread to the CPU. Then add another Wii controller for 2+ player games. It's going to struggle. Which is why I'd love to get OpenCL working again. Could anyone help me out please?
I'm going to try downgrading my ATi drivers to previous versions to see if this will fix the problems.
I've been away from my computers for a while and the last time I had Dolphin was r7607. I updated to r7613 and I find that enabling OpenCL in DirectX9/11 crashes any game or Wii menu upon startup with 'Dolphin.exe has stopped working' and your usual send/don't send choices. The Windows 7 Professional x64 was freshly installed since I had r7067 and the machine was joined to a new domain with roaming profiles. I don't see how this could be a problem. I'm going to downgrade back to the old versions and see if I can track down where the problem began. In the meantime, anyone else having this problem?
Microsoft Visual C (x64) was installed and up to date as well as all Windows updates and ATi's Catalyst drivers. I can confirm this is now happening in all builds. Don't know if this is helpful, but Windows throws this up too:
Files that help describe the problem:
C:\Users\%username%\AppData\Local\Temp\WER6B7F.tmp.WERInternalMetadata.xml
C:\Users\%username%\AppData\Local\Temp\WER82D7.tmp.appcompat.txt
C:\Users\%username%\AppData\Local\Temp\WER8355.tmp.mdmp
Unhandled Exception
Code: 0xE06D7363
Call stack info:
0xFE0FA49D : ?
0x258BF760 : ?
Unhandled Exception
Code: 0xE06D7363
Call stack info:
0xFE0FA49D : ?
0x259FF410 : ?
In GPU-Z, the OpenCL box is ticked for my graphics card and my DirectX is up-to-date.
Normally, ordinary CPU texture decoding is acceptable, but then add a DSP-LLE on thread to the CPU. Then add another Wii controller for 2+ player games. It's going to struggle. Which is why I'd love to get OpenCL working again. Could anyone help me out please?
I'm going to try downgrading my ATi drivers to previous versions to see if this will fix the problems.
CPU: AMD Ryzen 5 4600H | GPU: AMD Radeon RX 5500M | RAM: 16 GB | OS: Windows 10 Enterprise x64 (build 21H2)