DQM 3 Joker Fps Spike

Issue:
I encountered fps spike often when i move. I played DQM3 Joker before on citra android and it didn’t happened. There seems some configuration that i missing but i tried everything from check & uncheck the advanced graphic options, changing resolution to default, clock speed, and textures… the constant fps stutter just won’t dissapear… I noticed sometimes frame took 50++ms response time… Any idea what to fix? Or any info that i need to give?

System Information

  • Operating System: Windows 10
  • CPU: AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx 2.10 GHz
  • GPU: GTX 1650
  • Citra Version (found in title bar): Citra Nightly 1686
  • Game: Dragon Quest Monster 3
  • Screenshot of Issue (include the full Citra window including titlebar):

Diagnostic Log
Upload your log file as an attachment by dragging & dropping.
citra_log.txt (254.4 KB)

In order to save a copy of the log, follow this guide:
https://community.citra-emu.org/t/how-to-upload-the-log-file/296

System Information for Support

Client Version                                Nightly 1686 HEAD-6b2e7b7
Operating System                              Windows 10 (10.0)
CPU                                           AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx  
Graphics API                                  OpenGL 3.3.0
Graphics Renderer                             GeForce GTX 1650/PCIe/SSE2
GPU Driver Version                            461.40
CPU JIT                                       [x]
Hardware Renderer                             [x]
Hardware Shader                               [x]
Hardware Shader, Accurate Multiplication      [x]
Shader JIT                                    [x]
System Region                                 -1
Shader Disk Cache                             [x]

I did not find anything wrong in your log file. Please wait for a moderator to assist.

Btw, i tried using version Citra Nightly1524, the issue is not happened… But still wondering what’s wrong with the latest stable release

There is a regression caused by the core timing accuracy changes that were merged with Nightly 1544. Currently you will basically need to use Nightly 1543 as the latest.

Sorry for the inconvenience.

Thanks for the info :+1:

1 Like