3d land is painfully laggy, even on a considerable robust system

The primary issue is that the game ramps up and down speed a considerable amount very often. going from really long stutters to short ones, the frame rate is pretty much all over the place. Sometimes for a solid 5 seconds the fps is doing fine at a 100%, then goes down to 50% for less than a second, then back to 100% and then sometimes it just dies… like loading into the menu from title screen, the fps goes from 100% to then 25% for a second or two, then back to 100%
I’m not running anything considered weak hardware, so this is pretty concerning.

System Information

  • Operating System: windows10
  • CPU: intel i7-8700 3.20GHz
  • GPU: RTX 2060
  • Citra Version: nightly 1463
  • Game: Super Mario 3D Land

Diagnostic log
citra_log.txt (92.4 KB)

System Information for Support

Client Version                                Nightly 1463 HEAD-3b1b8b7
OpenGL Vendor                                 NVIDIA Corporation
OpenGL Renderer                               GeForce RTX 2060/PCIe/SSE2
OpenGL Version                                3.3.0
GPU Driver Version                            445.75
Enable Hardware Renderer                      [x]
Enable Hardware Shader                        [x]
Hardware Shader, Accurate Multiplication      [ ]
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.

  • Enabling Accurate Multiplication is recomended in certain games. If you are experiencing graphical glitches, try enabling this option.
  • You are using open source system files for Mii data. This will appear as your Mii having broken graphics, but will not affect the stability of the game. In order to resolve this, please refer to our guide on dumping system files. https://citra-emu.org/wiki/dumping-system-archives-and-the-shared-fonts-from-a-3ds-console/

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

Okay will check that out.