rsx: Fixes #3858
rsx: Fixes #3858
Conversation
kd-11
commented
Dec 4, 2017
kd-11
commented
- Avoid unprotecting memory unless writing is almost guaranteed to be near immediate. Should lower chances of race conditions on sections leading to corruption, but this is not a final fix. Should greatly reduce chances of encountering Regression: Demon's Souls graphical corruption #3754
- Fix for framebuffer setup - Ignore stencil flag if current depth format does not support stencil operation. Fixes some flickering in R&C 2 introduced in the last rsx PR
- Avoid unprotecting memory until just before we have to write the data - Avoids race conditions where the caller thread takes too long to enter the second phase and another thread accesses the "bad" memory
- Stencil flag is meaningless if surface does not support stencil
- Needs aliased paging to be implemented to fix properly or a re-entrant global IO lock
|
Was checking if this commit 547b6eb will help to reduce the chances of getting random texture corruption in ToCS2.
|
|
I got white screen from God of War 1 and II how to fix it? |
|
Crashed on P5 after around 30 minutes of playing. not sure if is exactly because of this version, reverting to old build that seems more stable. class std::runtime_error thrown: Halt Edit: played three times more and all of them crashed, all around 30 minute mark but the error was more similar to the one in the screen above (segfault reading at location), let me know if you need the logs of the seg fault, do not want to spam. Thanks. |
