They say the high performance mode on all consoles should be avoided. Image quality really suffers here and there’s minimal performance difference in these modes and the 1440p modes that are also available.
Both balanced and resolution modes on current gen consoles have their merrits. Razor sharp at 4K in resolution mode but 30fps or 1440p/60fps is what they recommend.
Heads up for anyone interested, Epic is about to host a state of UE5 presentation
Digital Foundry gonna love this
Coalition gonna do miracles with this engine
That Alpha test looking good to be honest
That was a good show. I imwatching the whole thing now. I didn’t know it was on till it was posted here. The coalition stuff makes me excited for what they are going to make with gears 6 and after
Pretty much exactly as should have been expected, using the BL3 engine with TTWL content. Here’s the DF written article for BL3 current-gen update from 2020 as a base:
PS5: Dynamic 2160p at 30fps (common 1980p) or Dynamic 1440p at 60fps (common 1368p) Series S: Dynamic 1260p at 30fps (common 1152p) or Dynamic 1260p at 60fps (common 1152p) Series X: Dynamic 2160p at 30fps (common 2160p) or Dynamic 2160p at 60fps (common 1872p)
When I get this game it sounds like the 60fps mode is the one to go for. Very impressive they got the resolution that high. Any other differences in terms of visuals fidelity if you choose the 60fps mode over 30fps?
Can’t really tell from the vid, probs gotta wait for the DF breakdown
Biggest dub for x since Farcry 6. Ps5 closer to S. Shows you how much optimization matters.
Yep, I like to see these kind of results.
As I said on Twitter earlier, Lego Star Wars is absolutely gorgeous. A lot of people will throw it out thinking its a kids game and can’t possibly be “pushing” anything. Truth is, if you play it and examine it, it’s actually doing more than most games that release these days visually. From a pure technical point of view, its absolutely top shelf. The number of polygons they throw at some scenes is bonkers, and all at 60fps 4k dynamic.
The results fall in line with what I would think, in all honesty. As we move forward, games will need to do more at a decent pace, not less. While I still firmly hold this title in the cross gen period, it is a game that will benefit more from having more resources available, not less. So the results… While most see them as strange, I see them as falling in line. Even loading speeds, because low and behold, pure throughput is NOT the only think that’s important.
I know a lot will brush this off as a pointless examination, based on the game content, but really… Sooner or later design will catch up to what technology can do in these systems, and that’s when they will shine.
Well said, and I look forward to that a lot!
It’s definitely very impressive, especially when you consider the camera perspective, you can now roam around completely in third person and everything is 3D, whereas with previous LEGO games I don’t think you could really rotate the camera yourself and check out every object in full detail like you can now. Maybe Undercover was like this too? Not sure.
It’s good to see Xbox taking the lead, higher resolution as you’d expect and also doesn’t seem to drop frames like it happens in other games before. I just hope the game doesn’t have too many bugs. Me and my nephews have been playing all the LEGO games and each and every one of them from 360 to Xbox One games they had bugs, stuff that was never fixed. Some real bad ones too.
Can’t say i agree when on pc a 5700 xt / 3600 machine (approx equal if not weaker than a ps5) the game runs at well over 70 fps maxed settings at 1440p. Dropping on dynamic res to 1180p or whatever and still dipping at times well below 40 is not “falling in line”.
Even though its a ps5 game I suspect its mostly ps4 pro code running hence why theres no dualsense support, slower load times, etc.
No dual sense is a priority thing. It has rumble, that’s enough. Everybody makes out like the ps5 controller is gods gift to gaming, when the reality is it’s great for rumble but absolute horse shit for anything else. Those triggers? They turn right off, in any game, right away. Absolutely awful.
You talk about load times like it’s a MPH thing. You see a bigger number and assume that’s it? Both systems have their own ways of dealing with data, and the “number” isn’t actually as important as some rather interesting twitter personalities make out. Sure, if you use what’s available and nothing more, PS5 will lead quite easily here. However all being told, XSX can actually have an edge in a lot of cases when it’s actually fully utilised later down the road. (Here however, it remains to be seen what is actually done in the background. I don’t even think its doing anything more than pure grunt, certainly not XVA). But to suggest it’s obviously a bad port because of load times… that tells me a lot. The way a games file system and memory access is set up will dictate this, even on old games on current hardware. It’s why some games will load better on one, some on the other. When a game is designed from the get go for these systems (which load inherently different to last gen), you will see massive gains. But you’re talking about loading time differences here of SECONDS. When you reach this threshold of time, you no longer have to factor in solely “throughput speed” but also decompression, memory access etc… all things XSX handily beats PS5 in.
Your reply of your current (I assume) system is again a false equivalency. You don’t list memory type or speed, but I also assume it’s not directly set up in the same way a console is, what with it being a Pc. And as such, your performance will be different here.
The truth is this: right now, at this stage of the cross gen game, titles will trade blows on which system is “best” because of the difference in power and how that power is handled. Less CUs more speed will pretty much dictate most of the time that the ps5 will perform better in last generation implementations of engines, as there isn’t as much simulation us tasking to be done but a speed bump helps a lot. However forward thinking engines (larger scale ones in use across multiple projects as we have seen) will actually use the power available to them differently in a more modern way. In these cases, yes, you WIlL see performance gains from the XSX over the Ps5, and yes… It will be larger than a simple 1-2fps lead. Earth shattering? No. But better. Whether that means more effects, higher resolution, or more instances… who knows. It depends on the engine.
This game is very much a cross gen game, however it’s also a brand new engine that is likely set up in a way that’s forward thinking and will be used on future projects on current gen systems. As such yes, these results absolutely do “fall in line” with what I would expect. Both systems will continue to move forward and get better, and as we see the toolset mature and release on xbox, I expect that lead to not only be sustained, but also increase.
That said, this all ultimately falls on the developers, and I’ve seen developers give absolutely zero effort to xbox ports. PS5 on the other hand, is actually a far easier machine to currently work with, so getting great results out of it is actually a lot easier.
Here was my reference video. Not my system.
I’m not here to tout the DualSense or get your opinion on it I was merely pointing the absence of features in a ps5 native port as curious seeing as most native apps use it in some fashion.
I’m sure engines will evolve and make the best use of these systems, but no a game on ps5 hitting 3,326,976 pixels in the lower bound, with drops in framerate, vs a steady framerate at 8,294,400 pixels is not normal or indicative of any trend (especially not one that will widen). If the new engine was created to be forward thinking for the new systems it makes zero sense why it wouldn’t be thinking at all for PlayStation 5 lol. The load times aren’t significantly different, but just a curious outlier when even the Steam Deck loads faster.
Fyi I don’t even own a PS5 I just think you’re making some too bold of claims
Lower bounds in a scene where adaptive resolution kicks in due to an area the console itself falls short on versus higher bounds in a scene where the other console is more equipped for are not valid comparisons.
Don’t use lower bounds as your data point for comparison. Use averages. Both consoles have strengths and weak points in different ways. Your average result will be much more easier to understand if you haven’t worked with rendering engines before.
As for my overall opinion, it’s just that, an opinion. But you absolutely cannot use past examples as proof of anything, even pretty much everything that’s been released thus far, because none of it was made solely for how things are done NOW. Pretty soon, you will see engines all show they have moved to the new, better ways of handling memory, processing tasks and IO, and that’s when the consoles individual strengths (and their weaknesses) will show. But when that comes, you absolutely will see that the XSX will have more room to give better results.
I understand to some that’s another “wait wait wait” conversation point, but that’s just how technology is. We just had an absolutely monumental shift in how games are created. Put UE5 pipeline development up against UE3/4, and it’s night and day.
WOW!!! What a mess! Square Enix didn’t bother with this one.
