Citra Frame drops

FPS drops:
Frames drop to 0% after finishing a combat in any Pokemon game I’m playing. This just started to happen since a few days ago, never had this issue before. It happens right after any battle, inbetween the cutscenes where the page goes black and comes back into the open world. This is where the frames drops to 0 and shows down below the “Nan ms” instead of a number.

System Information

  • Operating System: Windows 10 x64
  • CPU: Intel Core i7-7700HQ CPU @ 2.80GHz (8RAM)
  • GPU: NVIDIA GeForce GTX 1050 Ti (4GB)
  • Citra Version (found in title bar): Citra Nigthly 1463 and Citra Canary 1636
  • Game: Pokemon X, Ultra Sun, Alpha Sapphire
  • Screenshot of Issue (include the full Citra window including titlebar):
    citra_log.txt (105.6 KB)

Diagnostic Log
Upload your log file as an attachment by dragging & dropping.

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                                Canary 1636 HEAD-d29b4f1
OpenGL Vendor                                 NVIDIA Corporation
OpenGL Renderer                               GeForce GTX 1050 Ti/PCIe/SSE2
OpenGL Version                                3.3.0
GPU Driver Version                            391.25
Enable Hardware Renderer                      [x]
Enable Hardware Shader                        [x]
Hardware Shader, Accurate Multiplication      [x]
Hardware Shader, Geometry Shaders             null
Enable Shader JIT                             [x]
Enable Vsync                                  null
System Region                                 -1

Here’s some issues I found with your log that might help.

The coretiming 2.0 change caused a regression unfortunately so try Nightly 1422: https://github.com/citra-emu/citra-nightly/releases/tag/nightly-1422

You should update the drivers though: https://www.geforce.com/drivers/results/158759 select clean install in the installer.

Thanks, It does seems to be working properly now! Changed to 1422 like you said.