AnandTech: Xbox One vs. PS4 - Hardware comparison


Recommended Posts

Yeah that's what he said over at gamasutra. He also said that the ps4 team could've used a 128-bit bus coupled with edram on chip to have onpar bandwidth performance like the setup they have now. But Microsoft isn't using edram anymore (like they did in the 360) but they're now using esram which is faster and power efficient.

Anyway one console maker has laid out their internal hardware details while the other has not so its quite hard to compare and contrast we can only guess. One more week and we should see how the games look on both platforms.

A lot of people including you thinks that the more stream processors you have then its the better but when you take into consideration the nvidia fix 650ti boost which has 768 stream processors CONTINUOUSLY best the amd 7850 with over 1000 stream processors then you'll know that those aren't the end all be all. There's a lot more going on.

http://www.xbitlabs.com/articles/graphics/display/radeon-hd-7790-geforce-gtx-650ti-boost_3.html#sect4

I know they aren't using EDRAM but ESRAM is very similar in function like you said it just saves power and is lower latency at the cost of being more complex circuitry hence needing more space on the die.

You can't be serious trying to compare two completely different architectures it's almost as laughable as your way of working out TFLOPs, the only reason we can compare xO to PS4 is because they use the exact same series of GPU just one with less CUs and is the exact same reason why we can't compare PS3 to 360. There isn't a lot more going on, you just want there to be.

I know they aren't using EDRAM but ESRAM is very similar in function like you said it just saves power and is lower latency at the cost of being more complex circuitry hence needing more space on the die.

You can't be serious trying to compare two completely different architectures it's almost as laughable as your way of working out TFLOPs, the only reason we can compare xO to PS4 is because they use the exact same series of GPU just one with less CUs and is the exact same reason why we can't compare PS3 to 360. There isn't a lot more going on, you just want there to be.

I used the nvidia card as a reference to show stream count isn't everything.

Granted the way I calculated th tflops was wrong. I had a feeling it was so I asked for correction ("prove it" that's what I said)

I don't think you understand.

Compare a 650Ti to 660Ti which is roughly the same as comparing 7770 and 7850 stream count wise, you get the same performance gap.

You can't compare two different architectures as one may be more efficient than the other, the xO and PS4 use the same AMD Jaguar CPU and the same AMD Southern Islands 7xxx series GPU, one has more CUs disabled than the other.

There's no denying that the PS4's GPU is more powerful. I don't agree with Microsoft's decision to weaken their GPU so they can save some money and bundle a Kinect 2. Multi-platform titles will likely look and perform the same because developers must cater to the lowest common denominator in terms of performance (Xbox One). However, exclusive titles will likely look better on the PS4 simply because it has better GPU hardware. The PS3 was more powerful than the Xbox 360 this generation but it was also very hard to develop for. That won't be the case in the next generation because the architectures are near-identical.

Whether you want to decide on which console to buy based on the specs alone is your choice. I think it's better to consider more things like game selection, developer support, and other unique features to each console (e.g. Kinect 2 vs. PS4 Eye).

Money.

Multiplatform developers can't be seen to be favouring one console over the other by making one have noticeably better graphics there would be a sh*tstorm if CoD for example ran better with better graphics on PS4 over Xbox One.

They code with the capabilities of the slowest system in mind which is why PS3 was dragging down the quality of graphics this generation.

First party devs will continue to squeeze every last ounce of performance out of their respective system, but multiplatform games will always be inferior graphics wise.

What money?

A sh*tstorm created by who?

Many games do look better on the 360, and there was no real sh*tstorm.

I wouldn't call it favouring one system over another, I would call it taking advantage of what you have been given to play with. Shouldn't any potential sh*tstorm arise when that isn't happening? I know if I was Sony, and I kept seeing my machine intentionally underutilised, I'd be ****ed, as should their users be.

The way I see it with the current gen, is that it was too hard to develop for the PS3 first, and then have the 360 port be up to scratch, so yes, they did go with the lowest common denominator, but now that the architecture is the same, there is no excuse, and the games engines should be able to scale without issue.

Sh*storm by people who buy the consoles.

If I bought a game for my generic weak console after seeing screenshots and videos for the game played on generic powerful console I would be p*ssed that my game runs worse than the next persons purely because he bought Box B and I bought Box A. I may even go as far as not buying their games anymore. Publishers don't want this situation so they code for the lowest common denominator and port that game across.

The differences between 360 and PS3 multiplatform games were minor at best, maybe some choppy framerate issues or blurry graphics on PS3 but for the most part they looked the same.

The performance gap between Xbox One and PS4 theoretically is the difference between 1080p30 and 1080p60 at the same detail levels or the PS4 could look noticeably better with more effects turned on at 1080p30.

No developer is going to have their game running at 60FPS on one and 30FPS on the other, it would be a PR nightmare, people argue about PS3/360 graphics this gen and they are near identical, imagine what would happen next gen if one looked a lot better than the other.

I'm not saying its right but that's the way it works.

It's not that simple, each box has its own exclusive franchises, the same reason I'm buying a PS4 for Uncharted, Gran Turismo, etc... which should take advantage of every last drop of performance, multiplatform will always be coded for the lowest common denominator graphics wise.

Well then buy Box B, isn't that what console wars are partly about?

Developers will still sell the same amount of games, but just more on one box, than the other.

For most people, their buying decision is based on exclusives like Halo, Uncharted, Forza, Gran Turismo, and more. Developers have to create a consistent experience on multiple platforms otherwise they'll be perceived as favouring one over the other. Something like that could push away potential customers that don't own a console that plays the better-performing version.

once again talking out the rare huh mart? anyway its a common misconception that multi-platforms are coded for the lowest then ported up. most times they're coded for the easiest platform then ported over to others, other than that they're ported down, not up. I mean, you can look at it this way: it's easier to take details out of a picture than to add in.

What are you talking about? What TheLegendOfMart has said is true. Ease of development is a factor but performance is an even bigger factor. A competent development team wouldn't make version A of their game run well on console A but not on console B. They'd try to make it run well on console B so both consoles have a consistent experience. This has been true for the Call of Duty games as well as others like Elder Scrolls V: Skyrim and Mass Effect 3. Also, it doesn't apply to just consoles. In this generation, PC gaming has suffered the most when it came to multi-platform titles. A gaming PC is likely to be more powerful than the Xbox 360 and PS3; however, often times developers make games that have low-res textures, a 30 FPS limit, and a lack of PC-specific features (e.g. quick saving/loading).

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
      594
    2. 2
      +Edouard
      187
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      74
    5. 5
      Steven P.
      67
  • Tell a friend

    Love Neowin? Tell a friend!