Microsoft will optimise their own first party IP (Forza 7) on their Xbox One consoles more than on PC of course can't just use Forza 7 as a comparison.
Here's something I threw together in about 30 seconds, its missing OS and KB/mouse but you can get a builders OS license for around $40 and KB/mouse runs $20 for a basic setup. Its already under $600 and thats without any sales/discounts (I have seen the i3 go for under $100 and the GTX 1060 for around $200 at palces like MicroCenter)
The point is that something like this will easily outpace the XOX and will certainly be much cheaper around November when the XOX is actually out for sale.
This will outpace nothing. It doesn't meet minimum requirements forza 7.Here's something I threw together in about 30 seconds, its missing OS and KB/mouse but you can get a builders OS license for around $40 and KB/mouse runs $20 for a basic setup. Its already under $600 and thats without any sales/discounts (I have seen the i3 go for under $100 and the GTX 1060 for around $200 at palces like MicroCenter)
The point is that something like this will easily outpace the XOX and will certainly be much cheaper around November when the XOX is actually out for sale.
Sold out on Newegg and prices have jumped $50. I intermittently sell on ebay and used RX 480 8GB currently go for $350-450. I bought my aib partner RX 480 8GB for $259 at release last year. Ethereum ruined it for gamers.
Dude's gonna install Linux on his PC without a KB/M. No need for KB/M, gamepad, Blu-Ray, or HDMI cable. Sounds like paradise.
I got $548 for your components after shipping. Add $90 for Win10, $45 for BD Drive(X1X has UHD 4k drive), $45 for 1TB hdd, $20 for KB/M, $50 for gamepad, and $5 for HDMI cable. TOTAL = $803
It would take about 10 years of Xbox live to get it to $300 (in the price everyone always buys them at least, heck if you let it expire for a few weeks the Xbox even offers you for less than that in Brazil), but you also get large sales from subscribing so it's not like it's all a wasted money.
I agree with this...
---
Not true. The XBO X has a unified memory architecture and only about 8GB of its 12GB of memory were accessible to games iirc They might have bumped that to 9 recently. Either way, a big chunk of that 9GB isn't used as GPU memory.
RX 480/580 4GB and GTX 1060 3GB are out of the question due to a lack of VRAM. Even PS4 base model games were using around 3GB out of 4.5GB available for VRAM. 6-8GB VRAM will be used on X1X out of the available 9GB if the game is tied to XO and PS4.
I believe it's irrelevant because the catch for performance will be the GPU and VRAM, and most games built for consoles are extremely GPU-dependent especially with the focus on 4K and supersampling.
I have a r7 265(aka 7850) and at 1.8TFLOPS it was never drama that it performed like PS4. DOOM is a notable exception that takes a massive overclock to 1175MHz to match PS4.
Yes that's something to consider.
Ark Survival dev also compared it to a GTX 1070 along with Digital Foundry. I have a RX 480 and Forza Apex and I was simply sharing my experience.
I disagree. You need both to get a clear picture along with more info on the hardware. That's why I mentioned Gears 4 and The Witcher 3.
If it was more they'd be telling us.
Digital Foundry: Can you go into depth on the wins asynchronous compute gave you on the consoles and any differential there between PS4 and Xbox One?
Jean Geffroy: When looking at GPU performance, something that becomes quite obvious right away is that some rendering passes barely use compute units. Shadow map rendering, as an example, is typically bottlenecked by fixed pipeline processing (eg rasterization) and memory bandwidth rather than raw compute performance. This means that when rendering your shadow maps, if nothing is running in parallel, you're effectively wasting a lot of GPU processing power.
Even geometry passes with more intensive shading computations will potentially not be able to consistently max out the compute units for numerous reasons related to the internal graphics pipeline. Whenever this occurs, async compute shaders can leverage those unused compute units for other tasks. This is the approach we took with Doom. Our post-processing and tone-mapping for instance run in parallel with a significant part of the graphics work. This is a good example of a situation where just scheduling your work differently across the graphics and compute queues can result in multi-ms gains.
This is just one example, but generally speaking, async compute is a great tool to get the most out of the GPU. Whenever it is possible to overlap some memory-intensive work with some compute-intensive tasks, there's opportunity for performance gains. We use async compute just the same way on both consoles. There are some hardware differences when it comes to the number of available queues, but with the way we're scheduling our compute tasks, this actually wasn't all that important.
Digital Foundry: Will we see async compute in the PC version via Vulkan?
Billy Khan: Yes, async compute will be extensively used on the PC Vulkan version running on AMD hardware. Vulkan allows us to finally code much more to the ;metal'. The thick driver layer is eliminated with Vulkan, which will give significant performance improvements that were not achievable on OpenGL or DX
Digital Foundryo you foresee a time where async compute will be a major factor in all engines across formats?
Billy Khan: The time is now, really. Doom is already a clear example where async compute, when used properly, can make drastic enhancements to the performance and look of a game. Going forward, compute and async compute will be even more extensively used for idTech6. It is almost certain that more developers will take advantage of compute and async compute as they discover how to effectively use it in their games.
Digital Foundry: What are your thoughts on adopting Vulkan/DX12 as primary APIs for triple-A game development? Is it still too early?
Axel Gneiting: I would advise anybody to start as soon as possible. There is definitely a learning curve, but the benefits are obvious. Vulkan actually has pretty decent tools support with RenderDoc already and the debugging layers are really useful by now. The big benefit of Vulkan is that shader compiler, debug layers and RenderDoc are all open source. Additionally, it has full support for Windows 7, so there is no downside in OS support either compared to DX12.
