Metlivi Blog

How to Tell Whether an Apple Watch Emulator Game Needs Two Buttons at Once

If a virtual-pet game in an Apple Watch emulator seems to ignore an action, test whether the original game expects a button combination before blaming the watch or the emulator. Check the game’s instructions, verify each mapped button by itself, then repeat the same action with both inputs overlapping. If only the overlap works—and the emulator documents support for simultaneous input on your watch version—you have evidence of a real chord requirement. If sequential presses also work, the action may instead depend on timing, mapping, or a different game state.

October 15, 20266 min readBy Metlivi Editorial Team
Section 1

What counts as a simultaneous press?

A simultaneous input, often called a chord, means two game buttons are held down during some of the same moment. It differs from pressing one button and then the other, even with almost no pause. A manual may describe a combination such as A+B; an emulator translates those virtual buttons into touch targets, crown input, or other controls.

For virtual-pet games, combinations may appear in a minigame, a selection screen, or a special action. Don’t infer a chord merely because a pet or menu didn’t respond: the game may require a particular screen, a selection to be confirmed, or a button to be held for a minimum time. The title and version matter, so use the instructions for the specific game rather than assuming every game on the same console behaves alike.

Section 2

Start with the game’s own instructions

Look for the manual, in-game help, or a reliable guide for the exact game and version. Search its instructions for button names and symbols joined with “+,” “and,” or wording such as “press together.” Note whether the text says to press, hold, or release the buttons, and in which screen or situation the combination applies.

If the instructions show separate actions for each button but say nothing about a combination, that is not proof that no chord exists. Try the likely action only in a safe, repeatable setting: a menu or minigame where a mistaken input won’t overwrite a save or trigger a consequential choice. When available, make a save state before experimenting. Emulator features vary, and ArcEmu’s App Store listing, for example, describes save states and Apple Watch multi-touch support, but not every emulator has those options. ArcEmu on the App Store

Section 3

Confirm the emulator’s button mapping

Open the emulator’s control or ROM settings and record which on-screen or crown input corresponds to each original button. A layout can move or remap controls, so a remembered A+B combination is not useful if the current mapping assigns A or B somewhere unexpected. Test each candidate button alone in a predictable context and watch for a visible response, such as a menu moving or a selection changing.

Also check the emulator’s version and its watch-specific feature notes. For example, ArcEmu’s current App Store listing says it supports multi-touch and the Digital Crown on Apple Watch; its version history says multi-touch support was added in version 2.0. That establishes the emulator’s advertised support, not that every pair of buttons, screen layout, or watch configuration will work identically. ArcEmu version history and feature list

Section 4

Run a controlled A/B test

Use the same screen and repeat the same game action, changing only whether the inputs overlap. First press the suspected buttons one at a time, with a short pause. Then try the pair together, holding both briefly. Repeat each attempt a few times and note what the game displays or does; a single missed tap is weak evidence on a small touchscreen.

Keep the test simple: if the suspected combo is A+B, verify A alone, B alone, A followed by B, then A+B with overlap. Avoid adding movement, extra taps, or a long hold during this comparison. If a pet minigame has an obvious success indicator, use that response; otherwise, return to the same menu state between attempts so you are comparing like with like.

Interpret the result cautiously. If the game’s instructions specify A+B and repeated overlap succeeds while sequential taps do not, that strongly supports a chord requirement. If neither version works, check the game state and mapping before concluding anything about simultaneous input. If sequential presses work too, the action may accept either timing or the first input may change the state for the next one.

Section 5

Separate input limits from mapping or timing problems

Apple Watch accepts taps, touch-and-hold gestures, swipes, Digital Crown turns, and—in some models—other hardware inputs. Apple’s user guide describes these as distinct interaction types; it does not promise that every app or game can use every gesture in any combination. The Digital Crown is also system-controlled in some respects, so don’t assume that pressing or turning it can act as an extra game button unless the emulator offers that mapping. Apple Watch: Use buttons and gestures

A useful diagnosis is to compare input channels when the emulator offers them. If the same virtual buttons work together on an iPhone or iPad but not on the watch, the watch’s touch surface, emulator implementation, or watch-specific layout may be the limiting factor. If the chord fails on both devices, revisit the game’s instructions, current screen, and mapping. This comparison narrows the cause; it does not by itself identify a software defect.

Section 6

Try a practical control workaround

If the chord is confirmed but difficult to perform, check for a supported alternative: a remappable control, a hold or sustain option, or a crown mapping that lets one input stay active while you tap another. ArcEmu lists button hold/sustain and Digital Crown input among its features, but whether those options help depends on the exact button pair and the app version. Read the emulator’s own instructions before changing a layout, then test the revised controls in a low-stakes screen. ArcEmu features

If there is no suitable workaround, try the same game action on a device with a larger touch display or a supported controller. That is a practical fallback, not proof the game itself is unplayable on the watch: some actions may be optional, rare, or replaceable with another in-game route. Keep the original mapping available so you can restore it if the change makes ordinary pet care or menu navigation harder.

Section 7

A quick decision rule

Call it a likely simultaneous-input requirement when three things line up: the game’s instructions specify a combination, each mapped button works on its own, and repeated overlapping presses trigger the expected response when sequential presses do not. If one of those checks fails, treat the result as unresolved and investigate the game state, mapping, timing, or emulator’s watch support before deciding the watch cannot handle the action.

Section 8

Sources

Related reading

Keep exploring this topic