In the end, it seems smart delivery wasn't just a marketing term for crossbuy by Microsoft, my Xbox Series X hasn't installed any Xbox One version of a game supporting Smart Delivery since launch.Nice, Sackboy kept installing from the disc while having the updated PS5 version
Nice to see I'm not the only one dealing with this: the Wi-Fi was glorious before the last update (it is not anecdotal: just after updating, the thing started to lose connection after a while). Before, it was stable and fast, specially when downloading stuff.
In my case, the Wi-Fi lasts longer than yours, but it will always fail and if you try to force it to reconnect, it'll give you the "Something went wrong" (NW-102216-2 code) message at the test connection thingy.
Reminder that the PS5 has now been out for 3 months and still doesn't support VRR.
:(
I haven't had a disc in the system in a while, so I'm not sure if it's still doing it, but it was mostly doing it when I was playing a "free upgrade" game to check if the disc was still there I think.I never noticed my disc spinning hourly, is that the norm to everyone? I'm a bit worried reading this thread.
I would think it's meant for the free upgrade stuff so people don't just borrow a disc from somewhere and then have a free PS5 game once their get rid of the disc?
I've only been playing Division 2 since the update but that game is very dark now. I hope it's not across all games. :(Is it true this update introduced a black crush across all video settings?
Damn :( I hope they are aware of this and don't take too long to fix it.I've only been playing Division 2 since the update but that game is very dark now. I hope it's not across all games. :(
My Remote acts up from time to time too, I had to reboot my Ps5 for it to start working correctly again.My ps5 media remote stopped working after this update. I've tried changing the batteries and re-connecting the remote to the ps5. It had been acting up a little bit before the update tho, saying things like this device is not supported, but it still worked until today.
Most games run at locked 60, the list of games that can go to 120 and could take advantage of VRR is pretty short. Even the NIOH remaster is mostly locked at 120 in that mode. It's low on the priority list.Reminder that the PS5 has now been out for 3 months and still doesn't support VRR.
:(
I honestly wouldn't expect it for a couple years or so. It's an even more niche feature than 1440p and Sony doesn't implement stuff in a hurry.Reminder that the PS5 has now been out for 3 months and still doesn't support VRR.
:(
Yeah, the games have super long version numbers too. Annoying.Aww shit why are they going with this weird versioning...... it makes no sense!!
Just saw your post. I was seeing the same errors you were and weeks before the last system update.I was commenting earlier that my PS5 media remote died right after installing this update... but after leaving it alone for a few days (with the batteries out if that matters) and then trying a third set of batteries that were freshly charged it is working normally again.
This update only fixed the lack of volumetric fog on the PS5.Yeah it looks like Division 2 was just fixed.
" Patch 1.31 on PS5 adds in the fog and screen space reflections that were missing in version 1.30. The black crush also seems to be fixed on PS5 with patch 1.31. "
This update only fixed the lack of volumetric fog on the PS5.
On the Ubisoft forum, the Community Manager confirmed that this update was to fix the missing volumetric fog on the PS5.
Black crush is continues to be a problem in Division 2, it is an issue with Hitman 3 (Dartmoor, and Berlin are far too dark). Control is another game that continues to be far too dark (but at least runs without constant crashing like the XSX version). I have all three of these games on both the PS5 and XSX and the black crush continues to be an issue on the PS5. This needs to be addressed by Sony and people need to stop making excuses and suggesting people raise their brightness levels.
The batteries that come with it are extremely light, I assume they have a very small capacity. My remote has been working fine but it still occasionally gives that error about connecting it to the console or that it isn't supported. But it still works.Just saw your post. I was seeing the same errors you were and weeks before the last system update.
In my experience it is related to the batteries being low on juice. I was confused because it was glitching only after a couple months of light daily use. Once I put a fresh pair of batteries in, I was able to pair it again and it's worked great ever since.
My theory was that the batteries that come with it were old, low, or the remote just pulls a lot of energy and thrashes batteries quickly.