GameNative logoGameNative Download
Home/Guides/Controls

GameNative Controls: Controllers, Touch Layouts and Shooter Mode

GameNative Controls: Controllers, Touch Layouts and Shooter Mode illustration

GameNative controls are where a PC game either starts to feel at home on Android or stays awkward no matter how well it runs. A Windows game expects a keyboard, a mouse or a standard gamepad. Your phone offers a touchscreen; your handheld offers sticks and buttons in a particular layout; your bag might hold a Bluetooth controller. GameNative gives you several ways to bridge those differences, including physical controller support, touch overlays, a custom control editor, an on-screen keyboard and a dedicated Shooter Mode. This guide explains each one, how they fit together, and which approach suits which kind of game.

Start With the Game's Native Input

Before configuring anything, find out what the game itself expects. This single question shapes every other choice.

  • Full controller support: many modern PC games, especially those also released on consoles, play perfectly with a gamepad. These are the easiest titles to enjoy on Android.
  • Partial controller support: some games accept a gamepad for movement but need a mouse for menus or inventory screens.
  • Mouse and keyboard only: strategy games, older role-playing games and many point-and-click titles were designed purely for a mouse and keyboard. These need touch controls or mapping.

Store pages and the game's own options menu usually tell you which category a game falls into. If a game has full controller support, a physical controller is almost always the best experience. If it is mouse-driven, touch input or a mapped layout will matter more.

Physical Controllers in GameNative Controls

GameNative supports physical controllers connected over Bluetooth or USB. Once Android recognises the controller, the app can pass its input to the game as a standard gamepad.

Bluetooth controllers

Pair the controller through Android's Bluetooth settings first, then open GameNative. Most modern controllers pair easily. If input feels delayed, keep the controller close to the device, reduce other Bluetooth traffic and make sure the controller's battery is not low.

USB and wired controllers

Wired controllers connected through a USB-C port or adapter avoid wireless latency and pairing issues entirely. They are a good choice for competitive or rhythm-sensitive games, and a good diagnostic step if a Bluetooth controller behaves oddly.

Android handhelds

Dedicated Android handhelds such as the AYN Odin series and Retroid Pocket devices have built-in controls. Many of these devices let you choose how their controls present themselves to the system. For PC games, setting the built-in controls to an Xbox-style gamepad mode generally gives the best compatibility, because PC games most commonly expect that layout. Check your handheld's own settings for the controller mode option.

Multiple Controllers and Player Slots

GameNative supports multiple controllers, which opens the door to local co-op and couch multiplayer for games that support it. Each connected controller occupies a player slot, much like on a PC.

  • Connect controllers one at a time and confirm each is recognised before adding the next.
  • If player one and player two appear swapped, disconnect both and reconnect them in the order you want.
  • Outputting to a larger display with a USB-C hub or casting setup makes shared-screen games far more comfortable.
  • Remember that local multiplayer increases load slightly, so performance settings such as a frame cap still matter.

Not every game supports more than one local player, so check the game's own multiplayer options.

The Touch Overlay

When no physical controller is available, GameNative's touch controls put virtual buttons and sticks on the screen. The overlay is useful for playing on a phone during a commute or for games where a few actions do most of the work.

Touch controls have natural limits. There is no physical feedback, your thumbs cover part of the screen, and precise simultaneous inputs are harder than on a gamepad. They work best for slower games, menus, strategy titles and turn-based play. For fast action games, a physical controller remains the better choice when you have one.

Using the Custom Control Editor

The custom control editor lets you design your own touch layout: which buttons appear, where they sit, how large they are and what they do. A well-built layout transforms a mouse-and-keyboard game into something comfortable on a touchscreen.

A practical editing workflow

  1. Play briefly first. Spend five minutes noting which keys and actions you actually use. Most games rely on a small core set.
  2. Place the essentials. Put movement on one side and the two or three most frequent actions under the other thumb.
  3. Add secondary actions at the edges. Inventory, map and pause can sit near the top corners where you reach occasionally.
  4. Size for your hands. Make primary buttons large enough to hit without looking. Shrink rarely used ones.
  5. Keep the centre clear. Avoid covering the area where important game information appears.
  6. Test and refine. Play a real section, notice where you miss presses, and adjust. Two or three rounds of editing usually produce a layout that feels natural.

Keep layouts simple. A screen crowded with twenty buttons is harder to use than one with eight well-placed buttons and the on-screen keyboard available for the rest.

The On-Screen Keyboard

Many PC games occasionally need typing: naming a character, entering a save name, using a console command or chatting. The on-screen keyboard covers those moments without forcing you to map every key. It also acts as a fallback for rarely used keys you did not want cluttering your touch layout. Think of it as the tool for occasional input rather than for moment-to-moment play.

The HUD and Performance Overlay

GameNative includes an on-screen HUD and performance overlay. While not a control in itself, it is part of the control experience because it helps you understand what you are feeling. If inputs seem sluggish, the overlay can show whether the frame rate has dropped, which often makes controls feel delayed even when the input itself is fine. When the overlay reveals low frame rates, lowering resolution or capping the frame rate in the game's container frequently improves responsiveness more than any control change could.

Shooter Mode and Relative Mouse Input

First-person and third-person shooters present a particular challenge. On a PC, aiming is done with a mouse, which reports relative movement: how far and in which direction you moved, not where the pointer sits on the screen. A simple touchscreen tap behaves more like an absolute position, which feels wrong for aiming a camera.

GameNative's Shooter Mode is designed for this. It adapts touch input to camera-style aiming, and it offers a relative mouse input option so that dragging your finger moves the view in the way a mouse would, rather than jumping the cursor to where you touched.

Getting Shooter Mode feeling right

  • Lower the in-game mouse sensitivity first if aiming feels twitchy. Fine adjustments are easier inside the game.
  • Use short, deliberate swipes for aiming rather than long sweeps.
  • Combine Shooter Mode with a virtual stick or physical controller for movement so one thumb moves and the other aims.
  • If the game has native gamepad support with aim assist, compare that experience with Shooter Mode and keep whichever feels better.

Keep expectations realistic for online shooters. Games with anti-cheat systems generally do not run in GameNative, so Shooter Mode is most useful for single-player campaigns and offline titles.

Steam Input Configuration

For Steam games, GameNative can generate Steam Input configuration. Steam Input is Steam's system for translating controllers into whatever a game expects, including mapping a gamepad to keyboard and mouse actions for games that never supported controllers. This can make older or mouse-heavy Steam titles playable on a controller without building a touch layout from scratch.

If a Steam game ignores your controller or uses the wrong button prompts, Steam Input settings are a good place to look. If a game already has excellent native controller support, you may not need Steam Input at all.

Per-Game Layouts

Because games differ so much, GameNative controls are best thought of per game. A layout perfect for a turn-based strategy game would be useless in a platformer. Build and keep a layout for each game you play regularly, and do not try to force one universal layout onto everything. When you switch a game between a phone and a handheld, you may also want separate approaches: touch-first on the phone, controller-first on the handheld.

Control Tips by Genre

GenreBest inputTips
Action and platformersPhysical controllerUse a wired or close-range Bluetooth pad; cap frame rate for consistent timing
First-person shooters (single-player)Controller or Shooter Mode with relative mouseLower in-game sensitivity; keep movement and aiming on separate thumbs
Turn-based strategy and tacticsTouch overlayTap directly on the map; add buttons for end turn and camera rotation
Real-time strategyCustom touch layoutMap hotkeys for unit groups; keep the centre of the screen clear
Point-and-click adventuresTouchVery little mapping needed; add an inventory button
Classic role-playing gamesTouch plus on-screen keyboard, or Steam Input on controllerMap quick-save, map and inventory; use the keyboard for naming
RacingPhysical controllerAnalog triggers make throttle control far easier than touch
Local co-opMultiple controllersConnect in player order; use a larger display if possible

Troubleshooting Common Control Problems

  • Controller not detected: confirm Android sees it, reconnect it, try a wired connection, and on handhelds check that the controller mode is set to an Xbox-style gamepad.
  • Wrong buttons: check the handheld's controller mode, the game's own control settings, and Steam Input configuration for Steam games.
  • Input lag: check the performance overlay; low frame rate often feels like lag. Lower resolution or cap the frame rate.
  • Camera spins or jumps: enable relative mouse input in Shooter Mode and reduce in-game sensitivity.
  • Touch buttons hard to hit: enlarge them in the custom control editor and remove ones you rarely use.

If a control issue persists, the official Discord server is the best place to ask. Mention your device, the controller model, the game and the store you own it from.

Frequently Asked Questions

Yes. Pair the controller in Android's Bluetooth settings and GameNative can use it as a gamepad. USB controllers are supported too and avoid wireless latency.

An Xbox-style gamepad mode generally gives the best compatibility with PC games, since that is the layout most of them expect. Check your handheld's settings for the option.

Yes, GameNative supports multiple controllers. Each one takes a player slot, and the game itself must support local multiplayer.

Shooter Mode adapts touch input for camera aiming in shooters, and its relative mouse option makes finger drags behave like mouse movement instead of jumping the cursor.

For Steam games, try the Steam Input configuration GameNative can generate. Otherwise, use touch controls and a custom layout built in the control editor.

Low or unstable frame rate often feels like input lag. Check the performance overlay, then lower resolution or cap the frame rate in the game's container.

Conclusion

GameNative controls reward a little planning. Start by checking what input the game was designed for, use a physical controller whenever a game supports one, and set handheld controls to an Xbox-style gamepad for the broadest compatibility. For mouse-driven games, build a simple per-game touch layout in the custom control editor and keep the on-screen keyboard for occasional typing. Shooters benefit from Shooter Mode with relative mouse input, while Steam Input can rescue older Steam titles. Combine those tools with steady performance, and most compatible games will feel natural in your hands.