I don't have a link but I remember reading* this also. It also makes sense. The Tourist runs at 6k on Series X and 8k on PS5, and PS5 has higher pixel fill rate. We are talking about resolutions no other shipping console game runs at and the most obvious on paper advantage of PS5.
Not really related to the discussion but I'm just going to say it. DX12 sucks. Its actually pretty awful all things considered. Not a fan.
It shouldn’t; it’s just takes longer for MS to get their kits out. A single piece of hardware kit to profile 2 systems.
I think a notable item comes down to OS differences here. Xbox has an extra step that it still needs to create a container for the game to run in. With SN its going direct to PS5.
And very hard to get shader compilation stutter on console.
First time I hear about SN and VS. Can anyone educate me?
VS does the coding.
VS is MS's Visual Studio. That's where you write the lines of code and it has functions to facilitate that. To make the code run, you need to 'build' it, translating the high-level human-readable code into lower-level machine-compatible code. SN is the company (and collection of systems including third parties) that manages that for Sony. These tools track performance and track down issues, but they integrate within Visual Studio so you can run them from that interface instead of needing another program.
Mate, this is to most miserable description of VS I've ever seen!
I can only assume that you worked somewhere where it wasn't really setup properly.VisualStudio is the core IDE (integrated development environment) used by most software developers, it's used by Nintendo, Microsoft and Sony for their consoles SDKs. As Shifty unenthusiastically explained, it's the principle interface where you write code, but it's incredibly extensible and from this one interface you can connect to your team's shared code, audio, visual and other assets libraries along with support documentation for middleware libraries. You can compile, target and deploy code to connected or remote hardware and have that code provide debug information to VS-connected tools to profile performance by monitoring various hardware utilisation.
Fair enough, but the way you describe VS could be used to describe vi!
How any IDE is setup, but particularly VS in modern times is 95% about how it's been configured and what it does for the programmer. A bare bones install is barely better than contextual formatting editors like GoldED from the 1980/90s. But I've used VS where you could make tiny tweaks to massive codebases, deploy compilation to local hardware configured specifically to do nothing by compute codebases near-instantly, return the binary and deploy to whatever target hardware you are working with.
You absolutely can produce projects from Unreal Engine 4 or 5 without writing a single line of code, but it's going to be quite limited to what Unreal supports out of the box.
But sometimes they are the same people, and they manage to produce a performant application on one platform and not on another.
