Orbis (PS4) devkit docs leak; 8GBRAM, 2.2GBVRAM, new Controller


Recommended Posts

That's most likely true but there's always hope. The more RAM, the better.

Not really, there are several rumours floating about including rumours from current developers that the Durango RAM setup is less than ideal.

Take it with a grain of salt but some have said that the framebuffer can only register 1Gb of ram per frame, 2Gb for 3D.

Also have a read here, a developers eye view of both consoles, he isn't privy to next gen specs but gives his opinion on the current rumoured specs. Below is Durango.

Working here assuming the Eurogamer Article is close to correct. On this platform I'd be concerned with memory bandwidth. Only DDR3 for system/GPU memory pared with 32MB of "ESRAM" sounds troubling. 32MB of ESRAM is only really enough to do forward shading with MSAA using only 32-bits/pixel color with 2xMSAA at 1080p or 4xMSAA at 720p. Anything else to ESRAM would require tiling and resolves like on the Xbox360 (which would likely be a DMA copy on 720) or attempting to use the slow DDR3 as a render target. I'd bet most titles attempting deferred shading will be stuck at 720p with only poor post process AA (like FXAA). If this GPU is pre-GCN with a serious performance gap to PS4, then this next Xbox will act like a boat anchor, dragging down the min-spec target for cross-platform next-generation games.

With how good the Sony engineers have been at shrinking the PS3 OS but continuing to add more to it, I'd be much happier with faster memory (and CPU/GPU ;)) over more. 4GB is much more than the PS3 with it's strangely split 512mb.

Or I will put it this way, we're not seeing more than 4GB of DDR5 as it'll give near another ?500 PS3, which I hardly see Sony wanting this time around. I think it'll launch at ?349/399 across two SKUs.

Not really, there are several rumours floating about including rumours from current developers that the Durango RAM setup is less than ideal.

Take it with a grain of salt but some have said that the framebuffer can only register 1Gb of ram per frame, 2Gb for 3D.

Also have a read here, a developers eye view of both consoles, he isn't privy to next gen specs but gives his opinion on the current rumoured specs. Below is Durango.

That's very troubling. I really hope Microsoft doesn't drop the ball with Durango. I assumed the GPU would be similar to the PS4's GPU (based on AMD's GCN architecture). It just doesn't make any sense for them to use something older like AMD's VLIW4 architecture (e.g. Radeon HD 6000 series).

Not really, there are several rumours floating about including rumours from current developers that the Durango RAM setup is less than ideal.

Take it with a grain of salt but some have said that the framebuffer can only register 1Gb of ram per frame, 2Gb for 3D.

Also have a read here, a developers eye view of both consoles, he isn't privy to next gen specs but gives his opinion on the current rumoured specs. Below is Durango.

That's one thing i was worried about since long before these reports on the specs started coming. That Microsoft would include some kind of edram again, and also once again not make it big enough.

With how good the Sony engineers have been at shrinking the PS3 OS but continuing to add more to it, I'd be much happier with faster memory (and CPU/GPU ;)) over more. 4GB is much more than the PS3 with it's strangely split 512mb.

Or I will put it this way, we're not seeing more than 4GB of DDR5 as it'll give near another ?500 PS3, which I hardly see Sony wanting this time around. I think it'll launch at ?349/399 across two SKUs.

PS3 OS currently uses just 50Mb, I think theres a bit of breathing room with 512Mb :p

The RAM itself isn't split, Sony learnt their lesson with PS3, it will have one big 4Gb Unified chunk but 512Mb will be reserved for OS function.

There are unsubstantiated rumblings that Sony could free up RAM like a desktop PC does, it could unload everything unnecessary and just run whatever functions of the OS you would need while running a game, which could bring the OS limit down to 256Mb or possibly less.

That's very troubling. I really hope Microsoft doesn't drop the ball with Durango. I assumed the GPU would be similar to the PS4's GPU (based on AMD's GCN architecture). It just doesn't make any sense for them to use something older like AMD's VLIW4 architecture (e.g. Radeon HD 6000 series).

I hate saying it, but the current rumours are that both consoles will be using GCN, Orbis will have 18GCN Compute Units, and Durango will have 12GCN Compute Units. 1.8TF compared to 1.2.

PS3 OS currently uses just 50Mb, I think theres a bit of breathing room with 512Mb :p

The RAM itself isn't split, Sony learnt their lesson with PS3, it will have one big 4Gb Unified chunk but 512Mb will be reserved for OS function.

There are unsubstantiated rumblings that Sony could free up RAM like a desktop PC does, it could unload everything unnecessary and just run whatever functions of the OS you would need while running a game, which could bring the OS limit down to 256Mb or possibly less.

It would be stupid for Sony to use non-unified memory. They couldn't add support for cross-game chat to the PS3 for that reason. Most of the RAM was already pre-allocated to games and couldn't be re-allocated to the OS.

I hate saying it, but the current rumours are that both consoles will be using GCN, Orbis will have 18GCN Compute Units, and Durango will have 12GCN Compute Units. 1.8TF compared to 1.2.

Okay, that's good. I was afraid Durango would use a non-GCN GPU. A difference of 600 GFLOPS coupled with slower RAM means Durango is clearly inferior. In terms of raw processing power, Durango's GPU is close to the Radeon HD 7770 (1.28 TFLOPS). And Orbis' GPU is a little faster than the Radeon HD 7850 (1.76 TFLOPS).

Sony looks like they're going to have an edge over Microsoft with exclusives. Cross-platform games will obviously cater to the lowest common denominator (Durango).

PS3 OS currently uses just 50Mb, I think theres a bit of breathing room with 512Mb :p

The RAM itself isn't split, Sony learnt their lesson with PS3, it will have one big 4Gb Unified chunk but 512Mb will be reserved for OS function.

There are unsubstantiated rumblings that Sony could free up RAM like a desktop PC does, it could unload everything unnecessary and just run whatever functions of the OS you would need while running a game, which could bring the OS limit down to 256Mb or possibly less.

Yeah I know what I was trying to convey was I think 4GB of RAM will be fine for Sony to fit the PS4 OS into with how well they've done on the PS3 considering most of it's actual OS features were backported in, and the OS shrunk a lot in size. That would be a good way to work, but when it comes to in-game menus/soundtracks and other stuff, Sony need it to be mandatory out of the door for each developer. The PS3 ended up a mess with a lot of games as things weren't ready from the get go.

Maybe MS need more RAM to put 1080p adverts on the next Xbox dashboard :p

Yeah, the Orbis is meant to have 7970M 'based' GPU, which is a desktop 7870 at 7850 clocks.

It should be a little faster than the Radeon HD 7850.

Radeon HD 7870 (1000 MHz) = 20 compute units = 1280 shader processors

Radeon HD 7970M (850 MHz) = 20 compute units = 1280 shader processors

Radeon HD 7850 (850 MHz) = 16 compute units = 1024 shader processors

Radeon HD 7770 (1000 Mhz) = 10 compute units = 640 shader processors

Orbis (800 MHz) = 18 compute units = 1152 shader processors (based on this)

Durango (? Mhz) = 12 compute units = 768 shader processors (see above link)

They lowered the GPU's clock speed to 800 Mhz (from 850 MHz) and removed 2 compute units. Regardless, it's still much better than the Durango's measly 768 shader processors. A difference of 384 shader processors is a lot to developers.

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

    • No registered users viewing this page.
  • Posts

    • qBittorrent 5.2.2 by Razvan Serea The qBittorrent project aims to provide a Free Software alternative to µtorrent. qBittorrent is an advanced and multi-platform BitTorrent client with a nice user interface as well as a Web UI for remote control and an integrated search engine. qBittorrent aims to meet the needs of most users while using as little CPU and memory as possible. qBittorrent is a truly Open Source project, and as such, anyone can and should contribute to it. qBittorrent features: Polished µTorrent-like User Interface Well-integrated and extensible Search Engine Simultaneous search in most famous BitTorrent search sites Per-category-specific search requests (e.g. Books, Music, Movies) All Bittorrent extensions DHT, Peer Exchange, Full encryption, Magnet/BitComet URIs, ... Remote control through a Web user interface Nearly identical to the regular UI, all in Ajax Advanced control over trackers, peers and torrents Torrents queueing and prioritizing Torrent content selection and prioritizing UPnP / NAT-PMP port forwarding support Available in ~25 languages (Unicode support) Torrent creation tool Advanced RSS support with download filters (inc. regex) Bandwidth scheduler IP Filtering (eMule and PeerGuardian compatible) IPv6 compliant Available on most platforms: Linux, Mac OS X, Windows, OS/2, FreeBSD qBittorrent 5.2.2 changelog: FEATURE: Use D-Bus to show file in file managers (Chocobo1) #24340 BUGFIX: Fix friendlyUnitCompact precision calculation (vafada) #24323 BUGFIX: Remove all top-level folders (glassez) #24333 BUGFIX: Use proper API for checking exit status (Chocobo1) #24349 BUGFIX: Delete stale lockfile when hostname mismatch (TurboTheTurtle, glassez) #24363 BUGFIX: Fix wrong removal procedure of watched folder paths (Chocobo1) #24413 BUGFIX: Don't reannounce before interface changes are applied (glassez) #24447 BUGFIX: Use Latin script for Bosnian locale name (Andy Ye) #24342 WEBUI: Fix performance of global checkbox toggling (tehcneko) #24316 WEBUI: Fix Safari transfer list header misalignment (Piccirello) #24377 WEBUI: Fix error when submitting magnet before metadata loads (Piccirello) #24378 WEBUI: Use correct row id when updating Rss Downloader feed selection (Chocobo1) #24402 WEBUI: Use SameSite=Lax for session cookie to fix cross-site login (Piccirello) #24422 WEBUI: Bring back properties panel expand/collapse button (vafada) #24430 WEBAPI: Only use X-Forwarded-Host header when reverse proxy support is enabled (Chocobo1) #24457 RSSS: Fix "RSS Smart Episode Filter" RegEx (nathanon-akk, glassez) #24398 RSS: Fix previously matched episode format (glassez) #24452 WINDOWS: Fix Python fallback search path (TurboTheTurtle) #24325 WINDOWS: NSIS: Allow to install x64 binary on ARM64 (Chocobo1) #24358 Download: qBittorrent 5.2.2 | 41.1 MB (Open Source) Download: qBittorrent 64-bit installer (qt6) | 43.6 MB Links: qBittorrent Home page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Weechat. https://weechat.org/
    • they should stop making bad games that no one asked for
    • Nice rant! Expletive after expletive after expletive. Poor petal, I've touched a nerve. Would you like a tissue to wipe those tears away. Btw, nice one calling Neowin trash. Why would you stick around when you disrespect this site and the people behind it? Just go away if you feel that way.
  • Recent Achievements

    • Veteran
      branfont went up a rank
      Veteran
    • Reacting Well
      Almohandis earned a badge
      Reacting Well
    • First Post
      Cosminus earned a badge
      First Post
    • One Year In
      ThatGuyOnline earned a badge
      One Year In
    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      +Edouard
      183
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Steven P.
      87
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!