05-31-2018, 06:25 PM -
Can confirm that, unfortunately, the reintroduced issue still persists in rpcs3-v0.0.5-6882-87b510d5_win64 with the same "Blit request denied" error in the log as before.
UPDATE: Still no progress in rpcs3-v0.0.5-7024-cd59bc3d_win64, the game flickers the same way. No additional settings including "Force CPU Blit" influence the issue. The best that can be achieved is slowing the flickering a tiny bit.
The game is clearly NOT PLAYABLE in this regressed state, unless you want to break your eyes.
UPDATE 2: Despite a lot of work performed by kd-11 in "AAA fixes #4973", a PR that some have hoped should fix the issue, the same bug occurs without any changes in the most recent rpcs3-v0.0.5-7216-7915dcb2_win64 incorporating that PR. The game is still unplayable due to flickering.
It starts with:
E {rsx::thread} RSX: NV3089_IMAGE_IN_SIZE: Invalid blit dimensions passed
E {rsx::thread} RSX: Invalid framebuffer setup, w=0, h=0
Probably has to do with some initializing command failing.
UPDATE: Still no progress in rpcs3-v0.0.5-7024-cd59bc3d_win64, the game flickers the same way. No additional settings including "Force CPU Blit" influence the issue. The best that can be achieved is slowing the flickering a tiny bit.
The game is clearly NOT PLAYABLE in this regressed state, unless you want to break your eyes.
UPDATE 2: Despite a lot of work performed by kd-11 in "AAA fixes #4973", a PR that some have hoped should fix the issue, the same bug occurs without any changes in the most recent rpcs3-v0.0.5-7216-7915dcb2_win64 incorporating that PR. The game is still unplayable due to flickering.
It starts with:
E {rsx::thread} RSX: NV3089_IMAGE_IN_SIZE: Invalid blit dimensions passed
E {rsx::thread} RSX: Invalid framebuffer setup, w=0, h=0
Probably has to do with some initializing command failing.
This post was last modified: 08-18-2018, 01:44 PM by evilalex.
Edit Reason: No progress, despite hope placed on a recent PR by kd-11