Performance Issues.

[Triticum0]

Mainly saw it during door transitions to mid 30's/50's

Door.lag.mp4

and when fighting enemies mid 40's.

Fight.lag.mp4

Doesn't occur on melonds

[MysteriousAeon]

Thanks for the report. I traced the main performance paths, and the strongest current suspect is the compute renderer's workload scaling at high internal resolution.

Could you try one controlled comparison using the same door transition or combat encounter?

Test A:

• Adaptive Widescreen: On
• HD Rendering: On
• Internal Resolution: 1x
• Texture Upscale: 1x

Test B:

• Adaptive Widescreen: On
• HD Rendering: On
• Internal Resolution: 4x
• Texture Upscale: 1x

Please restart the game between runs and use the same scene/camera/shot timing if possible.

The useful result is the minimum FPS or frame time during the exact same event.

If 4x is much slower than 1x, that would strongly support the compute tile/workload path, which may also be related to #19 and melonDS #2683.

If both settings slow down similarly, I'll look more closely at Tier-3/overlay execution, texture-cache work, and CPU-side runtime overhead instead.

[Triticum0]

Seem to effect 1x and 4x similarly was unable to redo the door test as I misconfiguration obs for some or the original testing and unwilling to rerun the test at 1x.

Test A:

Door lag (Performance drop are about same on both tests)

Large fight for morph ball (Slightly better performance than 4x)

1x.Fight.mp4

Test B:

Door lag

Untitled.Project.mp4

Going back seems to hitch more.

back.mp4

Large fight for morph ball

4x.Fight.mp4

[MysteriousAeon]

I tried to reproduce the slowdown locally using the same profiling setup, but the sampled door and combat intervals both stayed at about 59.5 FPS, so I don't have a matching slow case yet.

The videos appear to be around the Celestial Archives Meditation Room, likely entering from the Helm Room. If you still have a save from around that point, could you attach it here?

A save immediately before the affected door transition would let me profile the same game state locally without asking you to repeat the performance tests.

[mstan]

v0.4.2-alpha is live now, but I do not expect it to materially change this performance issue, but some changes to ndsrecomp's engine were done to improve static coverage. While not in the area you're at, I did manage to bring up frame rates in several multi-player areas that previously struggled with frame rate, so feedback if the issues persist on your end would be helpful.

https://github.com/mstan/MetroidPrimeHuntersRecomp/releases/tag/v0.4.2-alpha

I still have not reproduced the slowdown locally in the same area; my sampled door and combat intervals stayed near full speed. The most useful next item is still a save immediately before one of the affected door transitions or fights, ideally around the Celestial Archives / Meditation Room path shown in the videos.

With a save near the problem, I can profile the same state locally without asking you to repeat more manual performance captures.

[Triticum0]

Well it the first artifact you get and there no portals until after that point as that artifact benefit so no way to fast travel to the area before the fight so have to there manually with or without a save. Also tested it on other hardware and slowdowns where in same places.

[mstan]

Got it. Makes sense. I'll try to go through this area again myself to see if I can reproduce. If you are willing and able, you can give a try to https://github.com/mstan/MetroidPrimeHuntersRecomp/releases/tag/v0.4.11-alpha

This one creates richer diagnostics (it's a default on mod) that looks at both coverage and performance metrics you can send my way. Do bear in mind you're helping me experiment here, so I may end up needing another couple of runs to refine the process. If that's something you'd rather not participate in and would prefer to wait until things are a bit more fined, no worries. 👍

[Triticum0]

@mstan Where is log file I can't it being generated on boot is it no stored in the root folder?

[mstan]

Dammit, it looks like the stupid thing decided to store diagnostics in %appdata% instead of relative to the exe. Gonna cut a fix for that so it's actually somewhere people can find it. For now, you can find your work here at: C:\Users<your username>\AppData\Roaming\MetroidPrimeHuntersRecomp\diagnostics

@mstan Where is log file I can't it being generated on boot is it no stored in the root folder?

[Triticum0]

Here performance test at baseline (1x) other than hitching at loading zones, performance is now very stable 60. due to how you reading is calculated it 59 but felt much smoother at default settings (No mods).

here first log file

performance-20260825-233309.zip

[Triticum0]

At 4x resolution performance has improved but still getting dips to the 50's when more than 4 enemy's are on the screen.

Logs

Opengl (4x + adaptive widescreen)

performance-20260825-234556 + other log.zip

Software render (Ran fine)

Metroid Prime Hunters-coverage-20260825-235903-part00.zip

[mstan]

Thank you for the logs! Those are helpful. I've gone ahead and added some major performance overhauls to the recompilation. Would you mind to re-measure under 0.6.1 and let me know how it goes? https://github.com/mstan/MetroidPrimeHuntersRecomp/releases/tag/v0.6.1-alpha

[mstan]

Update, I made some additional performance changes in https://github.com/mstan/MetroidPrimeHuntersRecomp/releases/tag/v0.6.2-alpha Give this one a try if you haven't tried 0.6.1 yet.

[Triticum0]

I test performance is same or worse.

5700x + 3060ti
Metroid Prime Hunters-coverage-20260827-181119-part00.zip

7730U

diagnostics.zip

[Triticum0]

V0.6.3
5700x + 3060ti:
1x

1x.zip

4x

4x.zip

[mstan]

Thanks for the feedback. I've made another round of optimizations into 0.6.4 and would appreciate if you could give this one another try.

https://github.com/mstan/MetroidPrimeHuntersRecomp/releases/tag/v0.6.4-alpha