I’m posting this because we spent an absurd amount of time troubleshooting a TOTK (Tears of the Kingdom) resolution problem where the 1080p → 1600x900 symptom was appearing in Eden, Ryujinx, and Citron while attempting to use the NX Optimizer mod — and we could not find a proper writeup anywhere that actually explained what was happening.

There are scattered comments online about TOTK / NX / UltraCam / emulator resolution weirdness, but we could not find existing documentation that clearly connected the symptoms, the real cause, and the fix.

So here’s our experience in case it saves someone else from the same headache.

What problem were we trying to solve?

We were trying to get real 1080p working in TOTK using TOTK Optimizer / NX Optimizer / UltraCam.

We had previously seen the same basic problem — selecting 1080p but not actually getting a 1080p internal render — in Eden, Ryujinx and Citron. The final fix described here was confirmed on Citron, but could likely be universally applied to all three emulators.

The issue was this:

• NX / UltraCam would let us select 1920x1080
• but the overlay on the right would still report Docked 1600x900
• or the game would behave like it was still falling back to x900
• sometimes backend edits looked like they were being ignored
• sometimes the mod seemed not to load at all

So this was not just:

“How do I increase resolution?”

It became:

Why does the game SAY one thing, but ACT like something else?

What we confirmed on our setup

This is what we personally confirmed working:

• Emulator: Citron
• Game version: TOTK 1.2.1
• Mod stack: NX Optimizer 3.2.0 / UltraCam Calamity 3.0
• System: Lenovo Legion laptop

Important note

We do NOT know for certain that this will work identically on every emulator or every mod stack.

We only confirmed it on:

Citron + TOTK 1.2.1 + NX/UltraCam

That said, we strongly suspect parts of this may help within Eden and elsewhere, because the issue seems tied to how the optimizer / UltraCam handles resolution and fallback behavior.

FURTHERMORE: We noticed using the 1.4.2 update of TOTK was a constant source of misery, negatively interacting with pretty much everything throughout this process.

Big discoveries

These were the parts that took the longest to figure out.

1) Dynamic resolution

Dynamic resolution was not the core reason the game kept reporting / behaving like x900.

So if you are blaming dynamic resolution alone, that was not the answer for us.

2) The “1080p problem” was NOT fixed just by setting 1080 inside NX Optimizer and hitting Apply

We could set 1920x1080 in the in-game NX / UltraCam menu, but the right-side overlay would still show:

Docked 1600x900

So seeing 1080 selected in the menu does not automatically mean you are actually getting 1080p.

The real test was whether the overlay on the right actually changed to:

Docked 1920x1080

3) Memory allocation breakthrough

Once we started testing resolution values directly through UltraCam’s INI config file, the mod finally gave us a useful clue:

“Not enough memory for resolution.”

Citron was set to 4 GB emulated DRAM.

Increasing it to 6 GB DRAM removed the warning and allowed UltraCam to accept the higher backend resolution.

That was the clue that led us to the scaling workaround explained below.

4) TOTK 1.2.1 was much more stable for us than 1.4.2

This may matter to some people.

On our setup, 1.4.2 was a nightmare and 1.2.1 was dramatically more stable.

So if you are troubleshooting crashes / freezes at the same time as resolution problems, rolling back to 1.2.1 may well be worth considering.

What fixed real 1080p for us

Here is the short version of the resolution fix.

A) Use the correct active config file

Make sure you are editing the active maxlastbreath.ini, not a dead copy in another Citron folder.

Our path looked like:

C:\Users\<YOUR USERNAME>\...\Citron Launcher\user\sdmc\UltraCam\TOTK\Config\maxlastbreath.ini

Your exact location may vary.

B) In the INI, before edits, make sure resolution is set to 1080

The key entries we used were:

[Resolution]
Width = 1920
Height = 1080
DisableFXAA = On
QualityImprovements = Off

We also kept the aspect ratio at 16:9.

TO CLARIFY: these 1920x1080 values are what the config initially/requested resolution looked like before the mathematical compensation we had to make, described below.

C) Increase Citron’s emulated DRAM allocation

Prior to editing the backend INI file:

On our system, 4 GB DRAM in Citron was not enough for the higher resolution behavior we wanted.

Changing that to 6 GB DRAM removed the memory warning and ultimately allowed our backend edits and the overlay to show:

Docked 1920x1080

If the overlay keeps snapping back to x900 behavior, make sure you've taken this step.

Always open TOTK and look at the right-hand overlay to verify what resolution is actually being rendered.

D) The 5/6 scaling quirk and how we compensated for it

This was the part that took the longest to understand, but ultimately fixed everything.

UltraCam 3.0 was not applying the resolution value literally on our TOTK 1.2.1 setup.

We found a consistent 5/6 scaling pattern:

• selecting 1920×1080 produced 1600×900
• selecting 1600×900 produced 1333×750

That told us the game was rendering at roughly 83.33% of the requested resolution.

So looking at NX Optimizer's INI file, even if it says 1920×1080, we had to compensate for that 83.33% scaling:

• 2304 × 5/6 = 1920
• 1296 × 5/6 = 1080

In other words, we asked UltraCam for:

Width = 2304
Height = 1296

so that the actual Docked render would land at:

1920×1080

Because the in-game custom-resolution fields were not accepting manual input, we edited UltraCam’s .ini config directly.

Performance notes

Once we finally got real 1080p working, the next fight was FPS.

Here are the biggest things we learned there.

Accuracy setting mattered a lot

For us:

• High caused a pretty big performance drop
• Normal gave a much better FPS result

So if you are chasing performance, don’t assume High is helping you just because it sounds better.

On our setup, Normal was the better choice.

Render distance mattered a lot

Reducing render distance gave us a major FPS improvement without destroying the image.

We ended up preferring something substantially lower than the max.

Shadow resolution is a tradeoff

If you want more FPS:

• lowering shadows helps
• but going too low starts to look ugly

We found 512 to be a reasonable performance-minded setting.

Dynamic Resolution did NOT cause the original fake-1080 problem

That said, you can still test it separately as a performance option if you want.

Just don’t confuse it with the actual resolution-lock problem, because for us those were two different issues — and we noticed a couple of guides online incorrectly conflating them.

Our recommendation if you are troubleshooting

If I had to compress this whole nightmare into a short checklist, I’d say:

1. Use TOTK 1.2.1 if you’re fighting stability too
2. Use Citron
3. Make sure you are editing the correct active maxlastbreath.ini
4. Set 2304x1296 in the INI if you're trying to achieve real 1080p
5. Verify NX / UltraCam is actually loading when you launch the game — and always look at the right-hand overlay to see what resolution TOTK is actually rendering at
6. Increase Citron’s emulated DRAM allocation from 4 GB to 6 GB
7. Check the right-side overlay, not just the resolution dropdown
8. If FPS is bad, lower Accuracy to Normal
9. Tune render distance and shadow resolution
10. Only trust the fix once the overlay truly says:

Docked 1920x1080

Why I’m posting this

Honestly, because this took forever and there was no single post we could find that said:

• why 1080p looked selected but wasn’t really applied
• why the overlay stayed at 1600x900
• why backend edits seemed ignored
• and how memory allocation turned out to be the real blocker

So this post is partly a fix, and partly a warning to the next person wandering into this swamp.

If this helps someone on Citron, great.

If it helps someone on Eden, Ryujinx, another emulator, or another TOTK optimizer setup, even better — but again, we are only claiming what we personally confirmed on our exact setup.

If people want, I can also post a cleaned-up settings list and/or the exact Citron graphics settings we ended up using.