Xbox '720'/Durango Dev Kit Photos via IGN


Recommended Posts

Photos of a next-generation Xbox development kit have emerged online. The images were first spotted on the AssemblerGames forums when a user named DaE attempted to sell the kit for $10,000. At the time, the pictures were met with heavy skepticism and many assumed they were simply a hoax.

Now, however, Digital Foundry has spoken to ?multiple developers working on next-gen projects? as well as DaE himself and confirmed that the images are indeed a legitimate look at the hardware being used to develop games for Microsoft?s next-generation system.

Source

I'd say 2GB.. maybe 4GB. Have to remember most homes now are 1080P maximum resolution so no real need for high resolution textures, more could be spent on content and even 2GB would be a huge improvement over the PS3/360.

I don't think we can draw much on what the next Xbox will be like from the Dev Kit :/

However it is interesting that it's an Intel CPU considering the 360 used an IBM PowerPC.

I'd say 2GB.. maybe 4GB. Have to remember most homes now are 1080P maximum resolution so no real need for high resolution textures, more could be spent on content and even 2GB would be a huge improvement over the PS3/360.

I don't think we can draw much on what the next Xbox will be like from the Dev Kit :/

However it is interesting that it's an Intel CPU considering the 360 used an IBM PowerPC.

Well I only say 4GB assuming the next console will have a lifespan the length of the 360; so that would future proof it. Also, when 4k resolutions and displays come into play we will be glad if it's 4GB not 2GB ha

Well I only say 4GB assuming the next console will have a lifespan the length of the 360; so that would future proof it. Also, when 4k resolutions and displays come into play we will be glad if it's 4GB not 2GB ha

4K is pretty much irrelevant since it's guaranteed that neither 'next-gen' console will have remotely close to enough power to handle it.

Well I only say 4GB assuming the next console will have a lifespan the length of the 360; so that would future proof it. Also, when 4k resolutions and displays come into play we will be glad if it's 4GB not 2GB ha

There's no way the Xbox 720 will have the graphics power required for 4K resolutions, as even top-end dual-GPU PC setups can't manage that. It's very unlikely you'll even see 2K resolutions supported, even for graphically simple games. And that's without even factoring in the adoption rate of 2K/4K displays, which aren't as well supported as 1080p was at the launch of the X360 (and 720p was still in its infancy).

I wouldn't be surprised to see 2GB or less, as that would be up to four times the amount seen in the X360 and the speed will be considerably faster. The largest benefit could come from using SSD storage or a SSD/HDD hybrid drive, which would take a lot of pressure off the system memory. All they need is enough memory to handle 1080p in 3D (120Hz), with a little bit more for "future proofing" (as if such a thing is even possible).

I'm expecting to be underwhelmed with the specs of the next generation of consoles, as I really think they'll do the bare minimum needed to support 1080p / 3D. Sony took big losses last generation and Microsoft doesn't want to price itself out of the market either. With Microsoft looking to make Kinect mandatory - at least according to the last rumours I saw - I think they're looking to move away from sheer horsepower and focus on the experience.

4K is pretty much irrelevant since it's guaranteed that neither 'next-gen' console will have remotely close to enough power to handle it.

Could we at least expect to have native 1080p be the minimum? As opposed to the up-converting crappy textures like...nearly this entire generation of games, at least on the Xbox platform.

Could we at least expect to have native 1080p be the minimum? As opposed to the up-converting crappy textures like...nearly this entire generation of games, at least on the Xbox platform.

Exactly.

I think all we can expect with the "next gen" of consoles is actual 1080p support. There were hardly any games this generation that did support 1080p native, and those handful that did were more on the simplistic side graphically.

To add to this, I would be shocked if next gen consoles support true stereoscopic 3D in 1080p, as I really doubt they will have enough horsepower to render two scenes of 1080p simultaneously.

I also think the life span we have come accustomed to with consoles will be a thing of the past. Technology is just going to move at a much faster rate then it has in the past, so in order to keep up, the whole premise of a longer life span will be tossed out the window. At least that is my take on things.

Could we at least expect to have native 1080p be the minimum? As opposed to the up-converting crappy textures like...nearly this entire generation of games, at least on the Xbox platform.

Probably. As long as they don't go too cheap on the GPU, or cut too many corners on things releated to it(like how sony crippled the ps3's gpu by killing half its memory bandwidth).

...

I also think the life span we have come accustomed to with consoles will be a thing of the past. Technology is just going to move at a much faster rate then it has in the past, so in order to keep up, the whole premise of a longer life span will be tossed out the window. At least that is my take on things.

I won't pretend to be an expert in this area by any means, the only point I would made to this last statement (thanks for agreeing with my post btw) is that the longer the lifespan, regardless of tech advances, the easier it becomes to turn profits on 'aging' hardware like we're seeing with this current generation.

Devkits have more RAM than retail machines for debugging tools.

Exactly, but how much more? Anyone remember what the 360 dev kits have/had? I'm going to make a guess and say it was 1GB and the final had 512MB for us. So, who knows? There are lots of Xbox 720 rumors flying around the place but I'd also like to add that 4GB is now the norm on the PC side so the next Xbox should have at least 4GB to match. Back when the 360 came out PCs were just starting to move to 1GB as the shipping norm all those years ago. I think MS does a good enough job of matching the Xbox to the specs of the PC at the time of release. Hell the 360 had a better GPU than the PC for a few months at least till ATi released it's new GPU to the PC market.

Wild guess, I'd say it could be anything from 4GB to 8GB as well, remember that we could be in for even more cores and even more "power states" and also multitasking, if you follow the details in that leaked document from last month. So more ram is needed to do things like that, specially if they want to run other stuff while your game is playing.

Another interesting bit, what if not all of the RAM is for games? To date the xbox has let devs use and chop up the RAM as they needed but what if there's 2GB or something set aside just for the dashboard and apps so they can keep running? This would add to the RAM totals in the end.

Well I only say 4GB assuming the next console will have a lifespan the length of the 360; so that would future proof it. Also, when 4k resolutions and displays come into play we will be glad if it's 4GB not 2GB ha

Theres no chance that the next gen will do 4k, I think the target resolution will be 1080p/30fps with all the graphical effects enabled. 1080p/60 for arcade games and games that dont have demanding graphics.

Theres no chance that the next gen will do 4k, I think the target resolution will be 1080p/30fps with all the graphical effects enabled. 1080p/60 for arcade games and games that dont have demanding graphics.

I hope not. I'd rather not see another cycle where our goal is a mere 30fps and we can't even manage to do that most of the time.

I hope not. I'd rather not see another cycle where our goal is a mere 30fps and we can't even manage to do that most of the time.

I still don't understand why people have a hard time with 30fps. I would rather play a game at max settings averaging at 27-35fps than half settings and get 60fps. As long as the framerate is relatively consistent.

I guess it just comes down to what you want. 60fps, or high res textures? I am of the opinion that higher resolutions aren't really going to solve anything and that smooth animation/features are going to be key in making games look better. But I also don't feel that 60fps is a necessity.

I still don't understand why people have a hard time with 30fps. I would rather play a game at max settings averaging at 27-35fps than half settings and get 60fps.As long as the framerate is relatively consistent.

I guess it just comes down to what you want. 60fps, or high res textures? I am of the opinion that higher resolutions aren't really going to solve anything and that smooth animation/features are going to be key in making games look better. But I also don't feel that 60fps is a necessity.

This is consoles we're talking about, not a pc. A console game with a framerate bouncing between a gap as wide as you mentioned would not only be very noticeable, but would likely be quite annoying.

And honestly, i wouldn't mind if they cut back a little for a steady 60fps. Cause the games that do hit 60fps(forza 4 is a 60fps game that comes to mind) typically feel alot better due to things such as significantly less input lag than the games that "aim" for 30 but fail and run at 20-25fps most of the time instead(which is, unfortunately, most console games).

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

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • 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
      592
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!