Issue: well like the title says it im trying to play DQMJ3 and i get fps drops and the loading screens are so long because i get 0 fps in loading not sure why
Enter a description of your issue here, in full detail.
Operating System: Windows 10
CPU: AMD Ryzen 5 3600X
GPU: Nvidia GeForce RTX 2060
Citra Version (found in title bar): Citra Nightly 1554
Game: Dragon Quest Monsters Joker 3
Screenshot of Issue (include the full Citra window including titlebar):
Enable Shader JIT and keep Accurate Multiplication enabled or you will end up crashing due to a bug with Disk Shader Cache when Accurate Multiplication is turned off. Since you have had it off for awhile you should clear the cache so it can be built up corrrectly from scratch. To do that do the following:
First, SORRY to revive this old thread, I actually found 3 posts with this exact similar issue… for the same games (Dragon Quests Monsters 2 and Jokers 3)
I find it very odd that any recent Nightly OR Canary version of Citra simply cannot run either of those games properly… I get 30 (or) 60fps EASILY locked 100% of the time (running on a 9600k at 5ghz, 32gb ddr4 and a 2070rtx)
The problem is always on any screen transition or loading, when using a recent citra version, it takes way longer, there is an audio glitch repeating, fps drops to 0, frame latency gets in the thousands and as soon as the loading is done, everything is back to being perfect… dropping cpu to 30% did improve the situation slightly (any lower and the game crashed), but still not to the level or speed of the citra build from 1 year ago!
I have also tried messing with shader cache, Accurate Multi and many other settings but nothing seemed to improve it either…
Anyone has any suggestion?
Thanks for your time and have a nice day!
That is what I have been doing… I just find it completely crazy that this has been going on for more than a year with zero progress… there have been 500 commits/updates to Citra since then… And there is no workaround to using a recent version without having to deal with that bug?
Are they even aware of that issue? Anyone looking into it? Anything we could do to help out?