After a pitch-perfect, well choreographed introduction to Xbox One X way back in 2016, hopes were high that Microsoft could repeat the trick for the crucial reveal of Project Scarlett at this year's E3. New details were indeed unveiled, major claims were made - but Microsoft muddied the waters somewhat with messaging that still leaves us unclear about what the new box is actually about, how powerful it is and what the vision is that separates it from Sony's upcoming PlayStation 5, built from the same technological building blocks.

Let's confirm what is definitely on the table - spec points that with one exception are point-for-point the same as Sony's recent next-gen announcement. For starters, both boxes use AMD's new Zen 2 CPU core - the basis of the Ryzen 3000 products arriving for PC users next month. Meanwhile, Microsoft also revealed that AMD's next-gen RDNA-powered Navi technology delivers the graphics muscle for Scarlett - just as it does for the next PlayStation. The platform holder also announced ray tracing support for its new machine, a feature that's also found in PS5 - though Sony has been reticent to explicitly confirm actual hardware acceleration for the job (our money is on the affirmative though).

Then there's the SSD - another hardware point that Sony revealed first, with Microsoft following suit. Another aspect that ties together both platform holders' next-gen announcements is a lack of information on the graphics core. On top of that, there are some curious factoids in Microsoft's reveal that do need some clarification. Scarlett was defined as the biggest generational leap in console technology that the firm has delivered - but I do think it hard to see the computational leap from OG Xbox to the Xbox 360 being bettered. Meanwhile, the 16x increase in RAM allocation seen moving from Xbox 360 to Xbox One is highly unlikely to be surpassed. Then there's the notion of Scarlett delivering a 4x leap in 'processing performance' over Xbox One X. On the CPU side, this does seem likely but the idea of the machine delivering an equivalent of 24 teraflops of GPU compute is unlikely.

Based on our own information, along with teasing reveals within the Scarlett announcement trailer, here are my thoughts on the set-up of the box - well, one of them at least. Curiously, Microsoft is using very strange PR-speak to avoid the question of the leaked lower-end box, codenamed Lockhart. Another interesting aspect is that while the Xbox One X reveal effectively told us the RAM allocation, SoC size, teraflop count and even clued us in on the cooler, Microsoft is being a lot more coy this time around and there may even be some red herrings in the assets this time around.

This content is hosted on an external platform, which will only display it if you accept targeting cookies. Please enable cookies to view. Manage cookie settings A point-by-point breakdown of the Project Scarlett specs revealed by Microsoft - and hinted at in its reveal trailer.

CPU: AMD Zen 2 architecture AMD's Zen 2 technology has been confirmed for both Scarlett and PlayStation 5, but not a whole lot more. What we do know is that Sony has confirmed eight cores - a design foundation for the architecture - and thus it's likely that Microsoft will follow suit. The efficiency of the core has seen some fundamental improvements from its first-gen revision, but comparisons with the desktop PC versions seen so far can only go so far. It's unlikely that we'll get the 35MB of L3 cache announced for the new Ryzens, for example. The use of AMD's new scalable 'chiplet' architecture (where groups of eight cores can be clustered together for 16, or even 32 cores in total) also seems unlikely. Our understanding from sources is that Microsoft is also turning its hand to a fair amount of custom CPU design for Scarlett. The move from Jaguar to Zen 2 represents an actual generational leap, one which Microsoft seem intent on exploiting. There's talk of 120fps gaming, which would certainly soak up the CPU cycles but on the flipside, it also doubles the graphics requirement - one of the areas where we should expect the next-gen consoles to fall a little short. CPU-wise, there is one further takeaway. Some rumours had discussed a separate CPU and GPU within the new box, but Microsoft explicitly showed an integrated system-on-chip in its reveal trailer. Meanwhile, in a press briefing the day before the MS E3 briefing, AMD CEO Lisa Su confirmed that PlayStation 5 is also using a SoC, so the idea of discrete CPU and GPU components in either of the new consoles now seems highly unlikely. We do have some basic idea of area occupied by the Zen 2 cores within the 7nm processor - it's between 70 to 80mm2 - and this is useful information to have when considering the silicon budgets available to the platform holders in constructing their new processors. This content is hosted on an external platform, which will only display it if you accept targeting cookies. Please enable cookies to view. Manage cookie settings Halo Infinite: is this our first look at the kind of visuals we can expect from Scarlett?

GPU: AMD Navi and the RDNA architecture Microsoft marketed Xbox One X based on its six teraflop GPU, with peak compute also used to differentiate the enhanced consoles from their 2013 base equivalents - but I genuinely believe that the teraflop was is over now. The GPU's potency in terms of gaming performance can't be measured by its peak compute output in a world where the new Navi-based 9.75 teraflop RX 5700 XT is - according to AMD - 14 per cent more capable than the 13.7 teraflop RX Vega 64. And remember, Vega itself is a significantly different beast to the earlier GCN architectures on which the current-gen consoles are based, with its own performance improvements. With Navi, AMD takes the existing GCN compute unit and morphs it into the 'dual compute unit' - doubling up on ALU power while reducing latency and boosting cache. AMD is talking about a 25 per cent increase in IPC for Navi, which is equivalent to the boost delivered by a notional 80 CUs compared to 64. There is room to scale up further too, and AMD is expected to deliver a bigger, more powerful Navi GPU next year. All of which is to say: once compute figures do emerge, expect them to be lower than you might think, but rest assured that Sony and Microsoft can both still deliver great boxes. Returning to silicon area, the new Navi GPUs from AMD deliver a total of 40 compute units requiring a remarkable 10.3 billion transistors. The nearest last-gen PC equivalent is the 36 CU Polaris chip used in RX 570, 580 and 590 with a total of 4.7 billion transistors. Going back to the first-gen GCN used in the PS4 and Xbox One, 32 compute units required 4.3 billion transistors. Clearly, Navi's compute units are significantly more complex and more capable - and transistor count is another indication of potential performance. This content is hosted on an external platform, which will only display it if you accept targeting cookies. Please enable cookies to view. Manage cookie settings Presented in its entirety: Microsoft's next-gen console announcement, plus the Halo Infinite trailer.

Memory: GDDR6 confirmed - but not much else Microsoft's trailer presents the new SoC surrounded by GDDR6 memory, specifically 14gbps modules fabricated by Samsung. Beyond that, it's difficult to draw too many conclusions as there does seem to be some very odd properties in the memory set-up. While the 2016 Xbox One X reveal actually gave away most of the technical make-up of the machine, Microsoft has been more coy this time around, with obscured test motherboard shots, an Xbox One X mobo fake-out (that seems to be the green PCB viewed overhead in the trailer) and lavish use of depth of field photography to blur out a lot of the interesting details on the all-important SoC shot. However, drawing upon a 4K feed we captured direct at the Microsoft conference, two of the G6 modules come into focus enough for us to catch their precise part numbers, ending in 325BC-HC14 and 325BM-HC14. The 'HC-14' confirms 14gbps speed, but the two part numbers suggest a mixture of both 1GB and 2GB memory modules. Whether this is just Microsoft seeking to throw off people like me looking for clues on the make-up of the system remains to be seen, but this is certainly a strange set-up. Who knows, maybe we're looking at two 128-bit buses addressing 8GB and 4GB respectively? A straight 256-bit memory bus would deliver 448GB/s of bandwidth and if there is a 384-bit bus out of shot there, we'd be looking at a mammoth 672GB/s instead.