libretro / libretro/RetroArch

Game paused by opening menu not reflected in network control interface GET_STATUS

Open
#12,379 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

The network control interface command returns a status indicator PLAYING or PAUSED to indicate whether the emulator is paused or not. This behavior is not accurate when the emulator is paused by opening the menu.

Expected behavior

When the core is paused for any reason, the status should be PAUSED, and PLAYING otherwise.

Actual behavior

When the game is paused due to switching away from the window with Pause Content When Not Active or by pressing the pause key, it correctly returns PAUSED. However, if the game is paused due to opening the menu with Pause Content When Menu Is Active set, it returns PLAYING even though the core is, in fact, paused.

Steps to reproduce the bug
  1. Enable the network control interface (network_cmd_enable = "true" in retroarch.cfg)
  2. Start a game.
  3. Open the menu, pausing the content.
  4. Run echo -n "GET_STATUS" | nc -u -w1 127.0.0.1 55355
  5. See GET_STATUS PLAYING...
Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.9.2 (bc23d070de)
Environment information
  • OS: Linux (Ubuntu 20.10)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the network control interface's GET_STATUS handling and how it observes the emulator's pause state. Reproduce with network_cmd_enable set to true, a running game, and the menu pause option enabled, then verify that GET_STATUS reports PAUSED while the menu is open and PLAYING otherwise.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.