Using Thor’s Second Screen for Nintendo DS and 3DS Games

Two displays need the right emulator support

Thor’s second screen is a natural fit for Nintendo DS and Nintendo 3DS games, but having two physical displays does not automatically put one emulated screen on each. The emulator must support presenting the game across separate Android displays, and touch input must reach the correct emulated screen.

A “dual-screen layout” option is not necessarily dual-display support. It may simply arrange both game screens inside one app window. Look for documentation or settings that explicitly mention a second display, external display, or separate-screen output. Availability and wording vary by emulator build and firmware — check your own device.

AYNTime is an independent community knowledge base, not affiliated with AYN. This guide focuses on a repeatable setup process rather than menu names that may change.

Check compatibility before changing settings

Start with one game you legally own and have dumped, using any required system files obtained legally from your own hardware. Pick something with an easy-to-reach menu and obvious touch controls.

Before configuring the layout:

• Confirm that your particular Android emulator build supports separate-display output. Do not assume every build or fork has the same features.
• Check whether the feature works for both DS and 3DS, or only the system that emulator handles.
• Run the game with the default layout first. Verify that it boots, produces sound, and responds to the physical controls.
• Record the emulator version and take screenshots of working settings before experimenting.

A launcher cannot add missing emulator support. Opening a game through a frontend may be convenient, but first establish that the emulator itself can use Thor’s two displays correctly.

Assign the screens deliberately

Where separate-display output is supported, use this sequence:

1. Open the emulator directly rather than through a frontend.
2. Find its display-output and screen-layout settings.
3. Enable the supported second-display mode.
4. Assign the emulated top screen to Thor’s upper display and the emulated bottom screen to its lower display.
5. Check which screen receives touch input.
6. Save the configuration, then close and relaunch the game to confirm it persists.

Treat these as configuration goals, not exact menu instructions. Some emulators expose display selection and layout separately; others provide a combined preset.

For DS, both emulated screens use a 4:3 aspect ratio. For 3DS, the top screen is wider than the bottom screen. Preserve each screen’s native proportions where possible rather than stretching both to fill their physical displays.

Black borders are not necessarily a problem: they can indicate that the image is being displayed without distortion. Start with a neutral layout before adjusting crop, scale, or screen emphasis.

Make touch input accurate

A correctly placed picture does not guarantee correctly mapped touch. On both DS and 3DS, the emulated bottom screen is the touch surface.

Test a menu with targets near the center and corners. If taps activate nearby items instead of the intended ones, investigate:

• Whether touch is assigned to the display showing the emulated bottom screen.
• Whether stretching, cropping, rotation, or custom screen placement has affected coordinate mapping.
• Whether an on-screen controller overlay is intercepting touches.
• Whether the emulator provides touch calibration or a documented input-mapping adjustment.

Restore the default layout before trying several fixes at once. Touch-coordinate errors and controller-button errors are different problems; remapping the directional pad will not fix an offset touchscreen.

An original DS stylus relies on a resistive touchscreen and is not a suitable default choice for a capacitive display. If you want stylus input, check Thor’s documented compatibility and use an appropriate capacitive stylus. Do not assume active-pen support.

Adjust for the game, not just the system

Some games put most of the action on the top screen; others depend heavily on the bottom screen or use both as one continuous scene.

• Keep both screens visible for games that require frequent cross-screen attention.
• Avoid excessive enlargement if it makes the other screen difficult to read.
• Use per-game layout settings when available so one unusual title does not change your whole library.
• For sideways-play titles, check rotation and touch mapping together. Rotating the image alone may not produce usable controls.

If the emulator offers a screen-swap shortcut, assign it somewhere unlikely to be pressed accidentally. Confirm whether it swaps output between physical displays or merely changes a layout inside one window.

Troubleshoot one variable at a time

If the second display is blank, first check the emulator’s output assignment and whether Thor has put that display to sleep. Restart the emulator after changing display settings if its documentation requires it.

If both game screens remain on one display, you may have selected a stacked layout rather than separate-display output. Recheck support for your exact build instead of searching indefinitely for a hidden switch.

For poor performance, return to a modest rendering resolution and disable optional visual enhancements before changing performance modes. Two working displays do not guarantee that every game will run well.

Finally, test relaunching from your frontend and resuming after sleep. Keep a known-good baseline and make ordinary in-game saves before experimenting; save-state compatibility can vary between emulator versions.

Got a better tip? Share your emulator build, working settings, and corrections with the AYNTime community.