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

    • Less powerful than a PS5 at twice the price! I wonder if they use that for marketing? Totally DoA.
    • Astra 0.6.1 Beta by Razvan Serea Astra is an audiophile music player designed for local music libraries, supporting MP3, FLAC, WAV, AAC, OGG, M4A, OPUS, WMA, AIFF, and more via FFmpeg. It offers gapless playback with pre-buffering, multichannel audio remapping, and Dolby Atmos decoding, ensuring albums play seamlessly while maintaining high-fidelity sound. Astra features real-time DSP visualizers powered by a native C++ engine, including an oscilloscope, spectrum analyzer, and vectorscope. A fully parametric 10-band EQ with live frequency response, built-in presets, and AutoEQ headphone calibration import lets you precisely shape your sound. Playback controls include shuffle, repeat, and drag-and-drop queue management, while the library automatically extracts metadata, album artwork, and supports global search, favorites, and recently played tracking. Additional features include output device selection, delay calibration, customizable themes, fullscreen and mini-player modes, Discord Rich Presence, optional Last.fm scrobbling, and an opt-in local API for integrations. Astra delivers a complete, high-quality desktop audio experience with no telemetry, accounts, or streaming. Astra 0.6.1 Beta changelog: Lyrics Initial XLRC support via @boof2015/xlrc 0.2.0 (#131) XLRC sidecar scanning, manual import, and renderer support Word timing, furigana, translations, voice labels, and translation-priority controls for XLRC Fullscreen lyrics overhaul with additional layout polish Manual lyrics editor with LRC, XLRC, and plain-text modes Drag-and-drop lyrics import plus sync offset controls Clickable synced lyrics for seeking, with popout and transport lyrics updates (#138) Fixed lyrics info sidebar scrolling (#138) Added a workaround for LRCLIB instability Metadata & Library Metadata editor rebuilt as a side panel Virtual DB metadata overrides and optional direct file tag writing Bulk metadata editing for title, artist, album, album artist, genre, year, track/disc numbers, and artwork Undo/redo support for virtual metadata edits Clear overrides action and default save-mode preference Artist page grid view added, with later design and sizing refinements Improved Jump to Playing with smart source, queue, album, artist, and library track targets Fixed smart source jump behavior Playlists Fixed VLC-style M3U import failures (#127) Added playlist export to M3U/M3U8 (#118) Improved imported playlist path resolution and missing-entry preservation Shuffle added to playlist pages (#121) Remove tracks directly from playlist views (#128) Fixed create-playlist-from-track modal closing when clicking inside it (#137) Multi-select quality-of-life fixes Right-click context menus no longer clear multiselections UI & Navigation Fixed UI scaling regressions in sidebar and home surfaces (#122, #123) Fixed transport bar regression (#126) Fixed horizontal scrolling on Home and Library rails Fixed artist grid sizing while searching Updated playlist action buttons and related layout polish Additional fullscreen lyrics visual adjustments Visualization Scopes and visualizers now respect UI scaling settings (#155) Added shared canvas sizing logic for correct DPR/backing-store behavior Canvas sizing tests added for visualizer scaling regressions Discord RPC Discord Rich Presence activity structure refactored Compact status can prioritize title or artist Profile info line can show file info or album Title and artist links can target YouTube Music, Last.fm, or be disabled Optional small Astra badge for cover-art presence Configurable “clear when paused” timing Added Discord activity tests Scrobbling Fixed custom Last.fm2 API profiles being accidentally blocked Expanded scrobbler profile protocol handling coverage Stability & Tests Added/expanded tests for XLRC parsing, lyrics presentation, metadata editor state, playlist import/export path handling, artist grid layout, horizontal scrolling, canvas sizing, and Discord RPC activity building Download: Astra 0.6.1 Beta | 138.0 MB (Open Source) View: Astra Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How does it compare to the "SeeStar S30 Pro" and the "Vespera PRO 2"?
    • Indeed. And note that those units are MUCH cheaper than this new Steam Machine...ahem.
  • Recent Achievements

    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
    • Week One Done
      mnsgroup earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      209
    3. 3
      PsYcHoKiLLa
      100
    4. 4
      Michael Scrip
      85
    5. 5
      neufuse
      69
  • Tell a friend

    Love Neowin? Tell a friend!