KNULLI DS screen controls: swap screens and use touch input

The controls that differ

On devices without analog sticks, KNULLI documents Function + Select to toggle the D-pad mapping for uses including the DS touch cursor. Identify the device's Function button in its own input documentation.

Open KNULLI's shortcut table for the illustrated layout buttons. Advanced-Drastic uses Function + D-pad Up for the next arrangement and Function + D-pad Down for the previous one. At the home screen, Select → View user manual provides the on-device reference.

A Pokémon lower-screen check

1. Record KNULLI version, DS emulator and exact game build. Keep known progress backed up.
2. Use a menu where both screens provide useful information. Check whether text and status details are readable together.
3. Try screen swapping, then return to the original arrangement. Record which view lets you identify both screens reliably.
4. Move the touch cursor and select a harmless lower-screen menu option. Check that the intended control receives the click.
5. If a cursor-mode toggle changed the D-pad, return to movement mode and verify walking and menu navigation.

This is an investigation you can perform, not a confirmed Pokémon performance result. Use the parts of your game you actually need rather than judging the setup from its title screen alone.

When swapping works but touch does not

Screen selection, cursor movement and cursor click are separate observations. Record each one and check the correct emulator's controls. Avoid changing the firmware and emulator simultaneously while diagnosing a single missing action.

For a microphone-dependent section, consult that game's instructions and compare them with the emulator's documented input. Check the game's response to the documented microphone input.

Do not apply RetroArch hotkey rules automatically

The custom-hotkey guide covers KNULLI's RetroArch customization path. Use the standalone emulator's own controls. Use the settings-layer guide to investigate supported options and persistence.

If changing emulator, verify your cartridge-save format and Continue separately. Do not treat an old emulator state as a guaranteed transfer format.

Choose a layout for the task, not just the title screen

Start with three ordinary tasks: reading text on the main screen, locating an action on the lower screen, and returning to movement afterward. A view that looks clean in a screenshot can still require frequent switching during real menu use. Compare the layouts using the same tasks.

For Drastic, test L2 in your current view, then Function + L2 to change between single and dual views. For Advanced-Drastic, the documented next/previous layout shortcuts are Function + D-pad Up and Function + D-pad Down; L2 swaps screen order. Keep the emulator name beside your notes.

These acceptance checks are suggestions for your own use. They do not establish a frame rate, touch-comfort score or best layout for every handheld.

Worked example: the cursor moves but selecting does nothing

1. Confirm which screen is the DS lower screen. Swapping screen order does not change which original screen owns touch input.
2. Move to the center of an available, non-destructive target. Choose an action you can recognize and reverse, rather than testing on a save/delete prompt.
3. Use the documented touch-click action for the selected emulator and observe the result.
4. If the target responds, move away and repeat once. If it does not, note whether the cursor, target or input action is the uncertain part.
5. On a device using the D-pad cursor toggle, return to movement mode before evaluating walking controls.

If the D-pad now moves the cursor instead of your character, revisit the mode toggle first. Repatching the game is a different investigation and does not answer which input mode is active.

Keep microphone input separate from touch selection

The shortcut table distinguishes Drastic's microphone action from its touch click. Advanced-Drastic documents R2 for touch/microphone behavior. Record the emulator and the exact action you attempted; do not assume every microphone-dependent game task can be completed merely because a shortcut is listed.

For a game section that explicitly requires a microphone, collect the creator's or game's instructions for that task. State the expected visible reaction and what actually occurred. If those requirements are unclear, leave compatibility undocumented instead of describing the input as a verified solution.

Retest three actions after changing the DS emulator

Use the two emulator columns above as separate control references. When comparing Drastic with Advanced-Drastic, write the selected emulator beside the layout you see before pressing anything. The old button habit is not a reliable record of the new selection.

1. Read: open the same harmless menu and identify which displayed region is the original lower screen.
2. Select: move to an available lower-screen target and try the active emulator's touch action. Record movement and selection independently.
3. Return: leave the menu and check ordinary walking. Check that ordinary walking still works.

Keep the comparisons short and task-specific. If reading works but selection does not, retain the working layout while investigating touch. If both work but controls change after reboot, add that timing to the record rather than repeating the whole installation.

For boot behavior after the switch, use the resume/runtime comparison. For configuration scope, use the owner table.

Choosing a DS path

Return to the DS handheld guide for screen and touch considerations. Separate documented paths include Steam Deck melonDS layouts and melonDS Android save checks.

KNULLI documentation checked 6 Oct 2026.