Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] ~5% Performance degradation in v1.2.80 vs. v1.2.78 in Zelda: Tears of the Kingdom #560

Open
usr20210909 opened this issue Jan 21, 2025 · 4 comments
Labels
bug Something isn't working

Comments

@usr20210909
Copy link

Description of the issue

Average FPS in latest v1.2.80 is around 5% lower than in previous v1.2.78 when benchmarking Legend of Zelda: Tears of the Kingdom (v1.2.1) in the Great Sky Island area.

Image

Image

Image

Reproduction steps

  1. Travel to Great Sky Island
  2. Remove all clothes and weapons (for consistent benchmarking)
  3. Run internal UltraCam flyby benchmark using "G" on the keyboard
  4. Start capturing of frametimes using CapFrameX (v1.7.2) when flyby has started
  5. After benchmark is done, remove last view seconds of recording when benchmark has finished but CapFrameX was still capturing

Repeat several times, select best benchmark results.

Log file

Ryujinx_1.2.80_2025-01-21_20-38-02.log

Ryujinx_1.2.78_2025-01-21_21-15-02.log

OS

Windows 11, version 24H2

Ryujinx version

1.2.80

Game version

1.2.1

CPU

AMD Ryzen 7 7800X3D

GPU

NVIDIA GeForce RTX 4070 SUPER

RAM

64GB

List of applied mods

UltraCam v2.6 (MaxFramerate = 120, Width = 2560, Height = 1440, ShadowResolution = 2048)

Additional context?

DRAM size set to 8 GB for stability when running at 1440p.

@usr20210909 usr20210909 added the bug Something isn't working label Jan 21, 2025
@GreemDev
Copy link
Member

Not sure what would have caused this. Maybe the update to .NET 9? Oh well

@usr20210909
Copy link
Author

I thought .NET 9 is going to improve the overall performance.

@GreemDev
Copy link
Member

I thought .NET 9 is going to improve the overall performance.

Yeah, exactly. I don't make changes to the core emulation. Idk what else would have caused this.

@Otozinclus
Copy link
Contributor

Maybe you can compare a few major Canary releases, to get more information about when this regression happened? Like, comparing the latest Canary with .net8 vs the first with .net9 could be useful to know

@Ryubing Ryubing deleted a comment from Sincasios Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants