You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Play asks before updating a game (#7): when nxnative has new code for a game's build, Play no longer rebuilds right away. It says what the update brings: how many new commits, which ones are for this game, whether every shader is translated again, and how long the last update took, the Mac app included. Then it asks: Update Now, or Play Current Build to play straight away. Playing the current build leaves nxnative where it was, so the other games don't fall behind. In Console Mode the controller answers. Settings › General can always update first, as before, or always play the current build. Rebuild and Update All Builds still take the latest code.
Changed
NX Play's own lines in the log are blue, so they stand apart from nxnative's output: which save a play uses, the game settings it passes, nxnative updates, rebuilds and the like. nxplay in a terminal does the same; set NO_COLOR to turn it off.
Fixed
Play asks which save to use when the Mac app has its own (#8): a Mac app opened from Finder before NX Play shared its save keeps a save of its own. Play used to start the app with NX Play's save without saying so, so progress made in the app looked gone. While the two saves differ, Play now asks: NX Play's save, the Mac app's save, or the newer one. Nothing is copied or deleted; the other save stays as it is. Tick Don't ask again to keep the answer for the game, and use Ask Again in Game Settings to undo it. In Console Mode the controller answers. The log now names the save each play uses.