[natethomas]

Not exactly. For example: In 2048 I press and hold start. Immediately the game is paused in-game, then after a second the OSD pops up (currently without pausing the game, but that is trivial to change). When the OSD is closed, we return to 2048 which is still on the pause screen. Start must be pressed again to resume gameplay.

The discussion here is how to improve this flawed behavior. Basically when start is pressed, we need to *not* send the press to the game and pause the game loop when the OSD is opened. The question is, how, when and for how long do we send a regular start press to the game?

Hm, interesting. My initial thought is one that's probably pretty hacky, so probably not ideal. What if exiting the OSD simply sent the pause button signal again, as long as the long pause was used to call it up in the first place? If a separate remote called up the OSD, the behavior would not happen. So yes, you do go to the pause screen in the game, but it's gone when you dismiss the OSD. The biggest disadvantage I see to doing this, off hand, is screenshots could be a real hell. But I'm not sure what other issues there might be.