I get games that don't support QR being patched to work with it, but what causes a game that works with QR then to not support it?
Is that how it works, if the dev doesn't set a flag, QuickResume doesn't work? Does the Xbox warn you if you switch from a non-QR compatible game to a new game?Maybe Devs/Pubs forgetting to make sure the QR Compatibility setting remains checked when they release their next update? Or devs/pubs getting reports about games misbehaving with QR and not finding a way of fixing the issue(s) so they toggle the QR Compatibility setting off in the meantime?
Is that how it works, if the dev doesn't set a flag, QuickResume doesn't work? Does the Xbox warn you if you switch from a non-QR compatible game to a new game?
It's not a massive issue for me because I generally only play one game at a time but I'd like to better understand the feature now that lockdown is easing and friends are talking about coming over to play games like it was 2019 or something!
Yes, it's a compatibility setting, that's up to the devs to set. Initially the legacy games were tested directly by Xbox teams and settings applied from there. This produced a bit of an initial backlog, but that should be sorted by now. They may test out new games if the setting isn't applied to see if it's compatible and apply it. Other compatibility settings are things like AutoHDR and FPSBoost. Though for FPSBoost there are different methods so it's less of a toggle and more of a method to apply. These various settings are contained in a text-based overall system specification file and is updated in the background periodically. It may also be updated upon new game install too. This file was posted on XboxEra or ResetEra in one of the earlier discussions, it's quite boring to look through after the initial glance.
No warning. It's exactly like the experience on last-gen consoles when switching between games or exiting/quitting games.
Auto HDR definitely requires testing by the dev or Microsoft because it alters the actual gameplay whereas quick resume could be viewed as a snapshot with memory in Vmware or a Checkpoint with memory in Hyper-v and should not really alter the game just let you bring the system back up to where it was originally.I wonder why auto hdr is still disabled on new games like Lost Judgement.
Auto HDR definitely requires testing by the dev or Microsoft because it alters the actual gameplay whereas quick resume could be viewed as a snapshot with memory in Vmware or a Checkpoint with memory in Hyper-v and should not really alter the game just let you bring the system back up to where it was originally.
On windows 11 auto hdr works for any game afaik. No issue yet.
I thought they'd possibly be using the same list for compatibility. It makes sense to me.
It was whitelist on March, I think. Then it became free for all (or Microsoft whitelist was added with loads of more entries). Even emulators runs with autohdr.Nah, there are lots of games not enabling autohdr in windows. Recent ones that I remember, Psychonauts 2, Diablo 2 resurrected, Kena. There are more I tried that didn’t work but it’s been while since I gamed on my PC so can’t recall specifics.
It was whitelist on March, I think. Then it became free for all (or Microsoft whitelist was added with loads of more entries). Even emulators runs with autohdr.
Some screens of the "keep in Quick Resume" feature going out to Alpha Xbox Insiders at 2PM PT today! Up to two games can be "pinned" so they won't be lost unless the game updates or you remove it. If you try to add a third game, you'll be prompted to choose which game to remove.