Steam Deck DS screens too small? Configure melonDS for Pokémon

Choose the layout around your Pokémon menus

EmuDeck documents a default hybrid layout: a large top screen beside smaller views of both DS screens. Its layout menu also offers Natural, Vertical and Horizontal. There is no single layout established here as best for every Pokémon game.

These are proposed usability checks, not measured results. The tradeoff depends on your game, eyesight, input method and how you hold the Deck.

Open the documented layout settings

1. Check the EmuDeck controller profile selected for your launch path: direct game shortcut or frontend.
2. With that profile, use Select + R3 to leave fullscreen and reach the menu.
3. Under Config, inspect Screen layout and the related sizing, rotation and aspect-ratio settings.
4. Change one option, return to the game and repeat the menu and touch checks below.

If the shortcut does nothing, inspect the Steam Input profile before replacing unrelated game controls. EmuDeck documents screen swapping through L4 or R4 with its configured profile; verify that behavior on your setup.

Test the bottom screen, not only the title screen

Use a disposable session or an existing backed-up save. In battle, check that you can read each move name and target its lower-screen button without confirming a move accidentally. Next inspect the bag, party and any other screen your game uses regularly.

Repeat the test after swapping screens. Ensure you know which view receives touch input; a duplicated screen in a hybrid layout can be visually confusing. If touches select the wrong option, undo the last layout change and compare again. Do not assume a layout that looks tidy is comfortable in an actual battle.

For a ROM-hack starting point, Renegade Platinum is a DS catalog example. Follow its own patch requirements. Its presence here is not a tested Deck compatibility result.

Keep the settings after quitting

EmuDeck instructs using File → Quit after changing melonDS settings; exiting with the STEAM button can discard those changes. Reopen through the same launcher and confirm the layout and swap control still behave as expected.

Record your selected emulator and profile alongside the settings. If only one launch path behaves differently, compare the shortcut or frontend configuration before assuming the layout file is damaged. A direct standalone launcher and a core-based launcher need not use the same configuration.

Back up your working DS layout before a reset

EmuDeck documents standalone melonDS configuration at /home/deck/.var/app/net.kuribo64.melonDS/config/melonDS. Show hidden files in Dolphin to find .var, then preserve a copy of melonDS.ini outside the configuration folder. Close melonDS before editing files.

For a layout-only record, its guide lists WindowWidth, WindowHeight, WindowMax, ScreenRotation, ScreenGap, ScreenLayout, ScreenSwap, ScreenSizing, IntegerScaling, ScreenAspectTop and ScreenAspectBot. Copy your own values rather than treating the documentation's example as an optimal Pokémon preset.

After a reset, compare the new file with your layout record before restoring relevant entries. Reopen and inspect both screens and touch alignment, then use File → Quit to preserve the settings. This backup concerns standalone melonDS, not the RetroArch core or your cartridge saves.

If you need to start over

Record your current layout and back up configuration before resetting it. EmuDeck documents Reset Configurations for melonDS under Manage Emulators. A reset is broader than changing one screen option; inspect other settings again afterwards.

Changing a screen layout does not validate game speed, wireless trading or save portability. For cartridge-save transfer, use the DS save-transfer checklist. For platform choice and patch formats, return to the DS handheld guide.

Source

EmuDeck: standalone melonDS layouts, controller profiles and saving settings.

A practical layout comparison for a Pokémon session

Start in a familiar, low-risk area. Choose two layouts to compare, rather than cycling through every setting at once. Keep the same game, launcher and input method for both runs. A screenshot is useful for remembering the arrangement, but the deciding factor is whether you can read and operate the screens.

1. Overworld: read a dialogue box and inspect the map or lower-screen panel. Notice whether you must lean closer to read ordinary text.
2. Party: inspect a Pokémon's summary. Check small numbers and labels as well as large sprites.
3. Battle: read all move names before selecting one. If using touch, aim at a harmless menu first rather than learning touch alignment during an important turn.
4. Screen swap: swap once and return. Confirm which screen is enlarged and whether the controls still match your expectations.
5. Restart: quit using the documented route and repeat one menu check through your normal launcher.

For example, a player who mostly reads dialogue might prefer a larger top view, while someone who often selects moves by touch may value a larger lower view. This is a decision example, not a measured recommendation. Choose the arrangement that passes your own checks instead of copying a screenshot from another game.

Diagnose the symptom before changing another setting

A useful note records the symptom, launcher, emulator version, layout and the single change you tried. “Bottom-screen buttons are too small in the party menu” is easier to act on than “DS looks bad.” Restore the previous arrangement when a change makes the actual task harder.

Make a layout comparison you can repeat

Choose a task that actually uses both screens: read the map, select a menu item and return to the main view. Record the launch route, the layout before changing it and the control you used to reach the other screen. Change one layout option, then repeat the same task. Note whether the lower-screen target was visible and whether the input selected the intended item.

For example: the larger main view makes dialogue easier to read, but the player has to swap screens before choosing an item. That is a tradeoff to compare with both screens visible, not a universal best layout. If the setting disappears after relaunch, keep that as a separate persistence question. A readable screenshot alone does not show that every required touch action is reachable.

Use the local DS session notebook to download a plain-text record of your attempt. Blank fields stay unrecorded; the notebook does not diagnose your setup.

Continue with your setup

Steam Deck OLED: full overview · All Pokémon handheld paths