Citra: Pokemon Super Mystery Dungeon: Bad RGBA8 texture pointer in H/W renderer

[j-selby]

At commit: 7ed97fb
Game save (just beyond the personality test): 00174600.zip

_This is unrelated to the CAM service timing issue. The camera is only used on the first launch and can be avoided by using a savegame._

Super Mystery Dungeon crashes when attempting to read a bad texture pointer. This occurs every time the opening sequence is viewed, about ~30 seconds in. This only occurs in the H/W renderer. This also occurs in exactly the same manner in at least the next scene, involving your character's reflection in the water.

Log - nothing before this point, and immediate crash after outputting this (on further analysis, this also appears irrelevant, as other occurrences don't throw any warnings):

[  63.809003] HW.GPU <Critical> core\hw\gpu.cpp:GPU::TextureCopy:336: zero input width
[  63.809657] HW.GPU <Critical> core\hw\gpu.cpp:GPU::TextureCopy:336: zero input width

Screenshots:

[JayFoxRox]

The existing posts which help users to workaround this issue have been moved into a new forum topic.
(If a developer is looking into replicate this issue I'd also recommend checking that topic.)

[IchigoMait]

The game plays now fine without crashing while using hardware renderer, I'm using the Citra Bleeding Edge build 0.1.405 (HEAD-c017065). Thx for letting us know of a fix wwylele*.

[hcorion]

Was apparently yuriks that fixed this, via https://github.com/citra-emu/citra/pull/2799

[j-selby]

Fix hasn't been merged yet into master, hold your horses.

[Gynlod23]

what do i do for this problem? i dont understand

[JayFoxRox]

Wrong. PR 2799 does not indicate version 2799. Also as @j-selby noted, this patch is not available in nightly builds yet. It is being tested in recent Bleeding Edge builds, but it might not be in all of them.

Can't you just wait a couple of weeks until the fix is ready for users and leave this issue-tracker to developers?
If you have questions about progress you should ask on the forums or discord (= user targeted), not github (= developer targeted).

(Edit: Pointless comments and discussion removed)

DO NOT POST ON GITHUB UNTIL YOUR COMMENT HELPS TO SOLVE THE ISSUE.

[j-selby]

Bug has been fixed as of 045d0b5. Closing...