AnandTech: Xbox One vs. PS4 - Hardware comparison


Recommended Posts

What the bloody hell are you talking about, do you understand computer hardware AT ALL?

Things like antialiasing, anisotropic filtering, post processing, dynamic lighting ETC cannot be done in advance.

These enhancements can all be done to your textures in advance because you optimize for single resolutions and the scaling can be done on the fly pretty easily. There is enough "improvement quality" processing power to handle doing the same improvements to every pixel in order to do 1080p on both platforms.

Textures are resolution independent, try again.

Microsoft lost that money due to poor product design, it was nothing to do with using overly powered components. Powerful components do not destroy computers that have been properly designed.

That's just ignoring everything that one has to understand in building a system, they've learned from those design choices and chose not to make them again. Is it better to risk heat issues by over compensating or is it better to achieve design goals by having streamlined hardware tuned exactly to specification?

more hardware doesn't make better looking games if all the hardware can push the same 1080p displays. a GeForce 680 pushing a 1080p display would be a GeForce 680 wasting a lot of resources.

I'm sorry, but what you said is retarded. A GAME ON THE PS4 CAN RUN WITH BETTER DETAILS AT THE SAME FRAMERATE AND RESOLUTION AS THE XBOX BECAUSE THE HARDWARE HAS HIGHER SPECS.

So basically your just trying to say its perfectly fine for the Xbox One on @ 1080p/60 therefor the PS4 is overkill?

I'm saying that the memory speed won't matter, they were different design goals. Sony went GGDR5 and no EDRAM or ESRAM because they wanted something simpler. Microsoft on the other hand can achieve the same effective throughput by leveraging their positive experiences with eDRAM but using faster eSRAM and save money with GDDR3. Those are engineering choices. They're going to reflect system that behave nearly identical but have differing ways of achieving their desired end results.

In the end, I think the Xbox sounds like the better deal (and plan).
Sorry for off-topic, but I hope you guys will have an announcement to make about independent developers. As it currently stands Xbox One could be the only major gaming platform to not allow self-publishing, and I'd hate to see it lose that share of the cake. XBLIG/XNA had a lot of potential but was poorly managed, hopefully you'll have better plans this time around. :)

I'm sorry, but what you said is retarded. A GAME ON THE PS4 CAN RUN WITH BETTER DETAILS AT THE SAME FRAMERATE AND RESOLUTION AS THE XBOX BECAUSE THE HARDWARE HAS HIGHER SPECS.

If it only takes 700 shaders to process every pixel of a 1080p display, it doesn't matter if you have 1150 of them, only 700 are needed to get the job done.

Having MORE available doesn't mean you can DO more as you're still working with the same freaking data set..

Sorry for off-topic, but I hope you guys will have an announcement to make about independent developers. As it currently stands Xbox One could be the only major gaming platform to not allow self-publishing, and I'd hate to see it lose that share of the cake. XBLIG/XNA had a lot of potential but was poorly managed, hopefully you'll have better plans this time I'm around. :)

indy game development won't make or break the platform and even though Microsoft's solution has never been perfect, I've had ton of indy games to play and it hasn't been a problem.

If it only takes 700 shaders to process every pixel of a 1080p display, it doesn't matter if you have 1150 of them, only 700 are needed to get the job done.

Having MORE available doesn't mean you can DO more as you're still working with the same freaking data set..

On the Xbox, one pixel will be a block of color and on the PS4 the same pixel will have bouncing ######.

I'm saying that the memory speed won't matter, they were different design goals. Sony went GGDR5 and no EDRAM or ESRAM because they wanted something simpler. Microsoft on the other hand can achieve the same effective throughput by leveraging their positive experiences with eDRAM but using faster eSRAM and save money with GDDR3. Those are engineering choices. They're going to reflect system that behave nearly identical but have differing ways of achieving their desired end results.
It's hard to believe a system with 50% more shaders and much higher system memory bandwidth won't perform significantly better than one that only compensates with 32MB cache - and as Anand pointed out, it's not even clear whether that SRAM will be used as a cache buffer. Of course, you'll keep repeating the only purpose of bandwidth is being able to achieve 1080p/60fps and anything beyond that is pointless, but I guess I'm speaking for everyone else.

I'm saying that the memory speed won't matter, they were different design goals. Sony went GGDR5 and no EDRAM or ESRAM because they wanted something simpler. Microsoft on the other hand can achieve the same effective throughput by leveraging their positive experiences with eDRAM but using faster eSRAM and save money with GDDR3. Those are engineering choices. They're going to reflect system that behave nearly identical but have differing ways of achieving their desired end results.

Yeah i got that but why shoot down GDDR5, the price?

If it only takes 700 shaders to process every pixel of a 1080p display, it doesn't matter if you have 1150 of them, only 700 are needed to get the job done.

You really should read up on computer graphics instead of making simplistic arguments here. With more shaders available, you could do more shader passes or longer ones. This all translates in more image fidelity. Video games are not movies. They compute the picture you see on screen in real-time. There are many more variables to it than framerate and resolution.

It's hard to believe a system with 50% more shaders and much higher system memory bandwidth won't perform significantly better than one that only compensates with 32MB cache - and as Anand pointed out, it's not even clear whether that SRAM will be used as a cache buffer. Of course, you'll keep repeating the only purpose of bandwidth is being able to achieve 1080p/60fps and anything beyond that is pointless, but I guess I'm speaking for everyone else.

I don't see why its that hard to understand. You have a finite resource, a finite goal to achieve. Once you achieve it, anything in excess is simply non utilized resources.

In the IT/Programming world there is this long often and little understood theory that when you have a problem, you don't necessary throw more at it to get it done. You can throw more developers at a project and it may take longer, you can throw more computing cycles at it and it may take longer. If you look at things from a more simple approach and engineer for those simple solutions, they often work the best.

That absolutely holds true here.

1080p is a fixed resolution. 60fps is the goal for the refresh/frame rate. So you have a fixed pixel count, a fixed throughput of operations you need to achieve that if you exceed those fixed goals, you're just increasing idle time of wasted resources. You can't make something look better by having to shaders work on the same shading function as the end result is still the same end result.

Now if you need something LARGER than 1080p and you're looking for screaming refresh rates and processing more data, then yes, with more power you can process more data.

The point is, we're talking about fixed problems here that are easy to engineer for with modern hardware.

Heck, I don't see the PS4 Nor the xone having problem even doing 120hz 3d gaming at full resolution, i'm sure the frame interpolation for 3d is designed into the GPU

You really should read up on computer graphics instead of making simplistic arguments here. With more shaders available, you could do more shader passes or longer ones. This all translates in more image fidelity. Video games are not movies. They compute the picture you see on screen in real-time. There are many more variables to it than framerate and resolution.

I'm pretty sure Microsoft designed for some oversampling already. Remember, we're talking about displays where people set back 5+ feet and all that extra stuff is for not.. there are a ton of variables you ignore by focusing so much on PC gaming trying to translate to a console.

what would be the end result of over processing an image that still only has a fixed pixel fidelity?

1080p is a fixed resolution. 60fps is the goal for the refresh/frame rate. So you have a fixed pixel count, a fixed throughput of operations you need to achieve that if you exceed those fixed goals, you're just increasing idle time of wasted resources. You can't make something look better by having to shaders work on the same shading function as the end result is still the same end result.

The IMAGE present on the screen however is NOT FIXED. It has to be processed in realtime, and the better the hardware you process it with the more efficient the process is. It's a very simple premise, why the hell do you fail to grasp it so completely?

You really should read up on computer graphics instead of making simplistic arguments here. With more shaders available, you could do more shader passes or longer ones. This all translates in more image fidelity. Video games are not movies. They compute the picture you see on screen in real-time. There are many more variables to it than framerate and resolution.

You're wasting your time, he clearly is too deeply mired in his love of Microsoft to even pay attention for a second.

The only person he'd listen to is Brandon, but I doubt he'll care to set him straight.

The IMAGE present on the screen however is NOT FIXED. It has to be processed in realtime, and the better the hardware you process it with the more efficient the process is. It's a very simple premise, why the hell do you fail to grasp it so completely?

The image is still a fixed amount of pixels, if you can process every pixel and fill the display with 700 shaders, 400 more won't do squat.. why is that so hard to grasp?

If you have problems with image quality, you can address that with your texture and image pre/post processing and not really have to apply on the fly processing.. again, another beautiful feature of consoles having a single architecture to design for..

i'm off for beer.. you guys have fun! :)

You're wasting your time, he clearly is too deeply mired in his love of Microsoft to even pay attention for a second.

The only person he'd listen to is Brandon, but I doubt he'll care to set him straight.

I don't love Microsoft. i'll own both a ps4 and xbox.. I love engineering and building systems. I'd be fired if I over engineered for unneeded capacity. (and the same goes for under engineering)

Because you're wrong and obviously know sweet FA about how computer hardware or 3D rendering actually work.

I don't love Microsoft. i'll own both a ps4 and xbox.. I love engineering and building systems. I'd be fired if I over engineered for unneeded capacity. (and the same goes for under engineering)

Then I pity anyone you build systems for because you obviously know sod all about how these things actually work.

I don't see why its that hard to understand. You have a finite resource, a finite goal to achieve.

No, you do not. A video game is not a movie. It's not pre-determined what the frame will look like. It will only look as good as you can compute it to be given the speed of the hardware in the 1/60th of a second you have to render it.

You could render 10 baddies on-screen or you could render 100. If you're on a slower system you'll render 10, on a faster system you'll render 100. You could render blood on every creature, or just on the ones nearby. You could add specular lighting to those puddles behind you, or could not have the time to. You could do volumetric lighting of the sun rays between the clouds, or you could use a more simple lighting model that takes less resources to process. You could use 4x Multisample Antialiasing for extremely accurate removal of jaggies, or an approximate fullscreen FXAA, or none at all.

Have you ever looked at the graphical options of a game like Crysis 3? There's much more to it than resolution and framerate right? By enabling/disabling the right options, you can achieve 1080p/60fps on pretty much any video card; only, you'll not get the same foliage density, the same quality water rendering, the amount of props, particles, effects, etc.

Video games are not movies. What you see on-screen is what the hardware just computed on-the-fly in 1/30th or 1/60th of a second. Change the hardware, you change what you see. Because the PS4 has faster hardware, it's likely to do better-looking graphics, even though the resolution and framerate might be the same.

I rest my case.

  • Like 3

I don't love Microsoft. i'll own both a ps4 and xbox.. I love engineering and building systems. I'd be fired if I over engineered for unneeded capacity. (and the same goes for under engineering)

What engineer has absolutely zero awareness of the workload the systems he supposedly works on? Despite it being explained to you multiple times by multiple people, you're being far too pig-headed to accept that there is more to 3D graphics than a damned framebuffer.

It's not about Microsoft, it's not about Sony. It's about the simple fact you're flat out ignorant when it comes to 3D computer graphics.

  • Like 4
If you have problems with image quality, you can address that with your texture and image pre/post processing and not really have to apply on the fly processing.. again, another beautiful feature of consoles having a single architecture to design for..
Larger textures requires guess what? More bandwidth! Post-processing requires guess what? Shader power! It's ALL on-the-fly processing, it's called real-time rendering for a reason. Sigh.

No, you do not. A video game is not a movie. It's not pre-determined what the frame will look like. It will only look as good as you can compute it to be given the speed of the hardware in the 1/60th of a second you have to render it.

You could render 10 baddies on-screen or you could render 100. If you're on a slower system you'll render 10, on a faster system you'll render 100. You could render blood on every creature, or just on the ones nearby. You could add specular lighting to those puddles behind you, or could not have the time to. You could do volumetric lighting of the sun rays between the clouds, or you could use a more simple lighting model that takes less resources to process. You could use 4x Multisample Antialiasing for extremely accurate removal of jaggies, or an approximate fullscreen FXAA, or none at all.

Have you ever looked at the graphical options of a game like Crysis 3? There's much more to it than resolution and framerate right? By enabling/disabling the right options, you can achieve 1080p/60fps on pretty much any video card; only, you'll not get the same foliage density, the same quality water rendering, the amount of props, particles, effects, etc.

Video games are not movies. What you see on-screen is what the hardware just computed on-the-fly in 1/30th or 1/60th of a second. Change the hardware, you change what you see. Because the PS4 has faster hardware, it's likely to do better-looking graphics, even though the resolution and framerate might be the same.

I rest my case.

You can rest your case all you want, but the beauty of consoles is that they are engineered systems. You do design the game to fit the requirements of the platform you are developing for. Its one reason that set PC gamers in such an uproar is that their games were optimized for 360 and ported to pc.

I never said they were like movies, but any good developer is going to optimize their entire workflow to take advantage of the platform so that they don't have to do in post-processing what they can do in preprocessing.

and again, we're still working with finite conditions that are very easy to plan and engineer for especially since the hardware to get us here is well established and well known.

Also, look at the front page, people are so na?ve about Microsoft they think Microsoft couldn't have possibly engineered the hardware alongside AMD that they're debating the validity of something AMD posted.

Its mostly because you guys are just so fixated on what you want to hear, rather than the reality there of.

Do ANY of you work in computing field? processing? scaling? data operations? do any of you ever look at things from a mathematical perspective? Do you not realize the vast differences of a 1080p screen 5 feet from your face running at 1920x1080 and the different requirements thereof? comparing the engineering goals of a console connected to a TV to a video card connected to a computer display with differing goals and differing viewing angles is vastly vastly vastly different.

With a console, you absolutely optimize all all points. YOu don't need to develop for so many unknowns/resolutions/processors/gpus/drivers/patch levels/versions.. yaddy yaddy yadda

Larger textures requires guess what? More bandwidth! Post-processing requires guess what? Shader power! It's ALL on-the-fly processing, it's called real-time rendering for a reason. Sigh.

Stop and think here for a minute.. Please.

Let me ask you this. What are larger textures to you. Please think for a moment when you answer that question. Also, what does more bandwidth get you? What do you need to post-process so much? have you defined how excess post-processing makes a game better? Shader power? If you have enough shaders to do everything to begin with, over processing does what?

Nothing is hard about real-time rendering and both machines shouldn't break a sweat doing it at 1080p..

You do design the game to fit the requirements of the platform you are developing for.
Yes. Assuming developers take full advantage of each platform, they'll be able to do more with the PS4 than with the Xbox One, just like they'll able to do much more with either one of these consoles than with the 360 or PS3. Give engineers more powerful tools and they'll make better products.

Prerendering is well and good but it's not the magical solution to anything. You cannot pre-render shadows and you cannot pre-render antialiasing, for instance, both of which the PS4 might be able to do somewhat better than Xbox One.

Do ANY of you work in computing field? processing? scaling? data operations?
Yes, I'm a software developer with a bachelor in computer graphics and multimedia. I actually worked at EA with the Frostbite 2 engine. But I suppose if you won't trust PS4/AMD engineers to know what they're doing then why trust anyone with any kind of degree?
  • Like 3

I am more interested in the quality of the components and which console will last longer. LOL, there are 30+ year old Ataris that work still and many people's Xboxs and Playstations died within several years of using them!

This..

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      591
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      75
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!