Why my frame rate is stuck at 60 FPS

If you've already followed getting the most out of uncapped frame rates and you're still stuck at 60, it's usually one of these four things.

The app itself caps its frame rate

Some Android apps enforce their own internal frame limit regardless of what the host allows. There's nothing Emulade can override here since the cap is inside the app's own render loop. This is the most common cause and unfortunately not fixable from Emulade's side.

Your laptop is on a power-saving profile

Battery-saver modes throttle the GPU on most laptops, which caps frame rate as a side effect. Plug in and switch to a performance or balanced power profile, then relaunch the instance.

A background instance is competing for cores

If you have more than one instance running, an idle one can still take CPU time away from your active session. Check Settings, then Performance, then Core Pinning, and confirm the foreground instance has dedicated cores.

Your display is running at a lower mode than you think

Some cables and adapters silently negotiate a lower refresh rate than your monitor supports. Check your display's own settings menu or your OS display settings to confirm it's actually running at the mode you expect before assuming Emulade is the problem.