So, since commit: 42619c1d2dfdd5c41e66049397e803b9d65e0283 (Merge branch 'ogl-tex2d') I've been seeing some issues on a few Nvidia cards, using the OpenGL backend (I only have access to NV GPUs atm, so I don't know if it also occurs on AMD).
First instance: OpenGL API - on a GTX 260 running (GeForce 314.22 Driver WHQL) Dolphin crashes to desktop when attempting to launch a game with any post processing shader enabled.
Second instance: OpenGL API - on a GTX 680 running ([GeForce R331 Game Ready Driver WHQL) Dolphin doesn't crash, but in the event log, it produces the warning "The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail." Again, the issue only occurs when trying to launch any game, with any post processing shader enabled in the OpenGL backend.
So, just to recap;
I've attached a backtrace of Dolphin from WinDbg below, up to the point when the event log produces the warning on a GTX 680. If anyone would like a look. (exception analysis @ end of log)
The point of this thread? - I'm wondering if anyone else has noticed, or actually experienced any of these issues?
If more info is needed, just specify. My own system is on profile page.
First instance: OpenGL API - on a GTX 260 running (GeForce 314.22 Driver WHQL) Dolphin crashes to desktop when attempting to launch a game with any post processing shader enabled.
Second instance: OpenGL API - on a GTX 680 running ([GeForce R331 Game Ready Driver WHQL) Dolphin doesn't crash, but in the event log, it produces the warning "The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail." Again, the issue only occurs when trying to launch any game, with any post processing shader enabled in the OpenGL backend.
So, just to recap;
- If Dolphin is launched with any setting, including the ones producing problems - it's fine. It only occurs when launching a game via Dolphin. Not launching Dolphin.exe itself.
- If Dolphin launches any game, with OpenGL, with post processing shaders disabled: no issue occurs.
- If Dolphin launches any game with OpenGL, with any post processing shaders enabled: Dolphin crashes to desktop on the GTX 260 system, and on a GTX 680 it doesn't crash, but produces an OGL OOM warning in the event log.
- If Dolphin launches any game with OpenGL, with post processing shaders disabled, and the game loads up. Then opening the config dialog, and enable a post processing shader: no apparent issues occur. It only seems to happen on startup.
I've attached a backtrace of Dolphin from WinDbg below, up to the point when the event log produces the warning on a GTX 680. If anyone would like a look. (exception analysis @ end of log)
The point of this thread? - I'm wondering if anyone else has noticed, or actually experienced any of these issues?
If more info is needed, just specify. My own system is on profile page.