shuffle2: It was late when I posted that, I didn't even really look at the trace log properly, just thought I'd get it done before going to sleep. I don't think it would even help all that much though tbh, as Dolphin is actually not launch crashing on my own gpu. Most people may not even notice the warnings in the event log, and just wait for the emu to oom and crash after x amount of time. Also seeing as most users have panic handlers disabled, they wouldn't know the cause of the crash either.
degasus: The issue begins occurring from commit: 6ed3f82affe9f866a580bcddfaa6f760f92a1b3e Rev: 4.0-442: OpenGL: attributeless rendering for postprocessing.
I can't test the code myself, I'm not at my own machine again, at the moment. But, unlikely as it was to be the vs. I did already try reverting the post processing vertex shader to the previous version, a few days ago, and that didn't seem to be it.
On the 260 (current machine I'm using right now.) It crashes with a 0xc0000005 access violation code, but no memory warning as it doesn't get to run long enough before the crash. No crash on my own card, but I get the warning. Possibly a memory issue?
degasus: The issue begins occurring from commit: 6ed3f82affe9f866a580bcddfaa6f760f92a1b3e Rev: 4.0-442: OpenGL: attributeless rendering for postprocessing.
I can't test the code myself, I'm not at my own machine again, at the moment. But, unlikely as it was to be the vs. I did already try reverting the post processing vertex shader to the previous version, a few days ago, and that didn't seem to be it.
On the 260 (current machine I'm using right now.) It crashes with a 0xc0000005 access violation code, but no memory warning as it doesn't get to run long enough before the crash. No crash on my own card, but I get the warning. Possibly a memory issue?