Soldato
Where are the AIBs, im not seeing them on the site at all.
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Do a new thread for the AIBs.Do you want me to update the RX6000 review thread with the AIB model reviews,or start a new one?
Nobody has them listed. Due to lack of stock.Where are the AIBs, im not seeing them on the site at all.
Nobody has them listed. Due to lack of stock.
One thread is fine
Nope nothing for actual order. Not that i would have at those prices.
I updated the old one!Do a new thread for the AIBs.
They are up now on the OCUK websiteI thought Gibbo said he was going to list them with prices but you just couldnt buy any till later on or whenever?
AMD runs DXR 1.1, Nvidia DXR 1.0, both consoles run DRX 1.1 even if not by name also on the PS5, DXR 1.1 was codeveloped between Microsoft and AMD.
DXR 1.1 uses Inline Ray Tracing, which requires a completely different approach to Ray Tracing at the hardware level and DRX 1.1 is far more flexible and efficient than the legacy DRX 1.0 Nvidia use in Turing and Ampere.
Games need to be code for either DRX 1.1 or DRX 1.0, they are backwards and forwards compatible they just don't run efficiently when not properly coded for one or the other, as i keep saying all games other than Dirt 5 are RTX games, or DXR 1.0, which will work on RDNA2 GPU's but almost in a "safe mode" state.
AMD and Nvidia use entirely different ways of Ray Tracing, AMD's GPU's will never run RTX, or DXR 1.0 games properly because the hardware in RDNA2 GPU's is not natively compatible with the code Nvdia use (DXR 1.0) and far from AMD and Microsoft catching up with Nvidia they are already ahead of Nvidia, Nvidia will be using DXR 1.1 in their next generation of GPU's and unless Nvidia pay developers to use the old DXR 1.0 from here on out they will be making RT games with DXR 1.1.
https://devblogs.microsoft.com/directx/dxr-1-1/
NVIDIA's DirectX 12 Ultimate Certified Driver Now Available - First Driver To Support DXR 1.1
Pre-Release Driver 450.82 For Windows 10
This preview driver is intended for developers testing their applications with DirectX 12 Ultimate. This driver supports DXR Tier 1.1, Sampler Feedback, and Mesh Shaders.
Game Ready for DirectX 12 Ultimate
The new Game Ready Driver provides full support for the new DirectX 12 Ultimate graphics API. This includes support for DirectX Raytracing (DXR) version 1.1 as well as support for mesh shaders, sampler feedback, and variable-rate shading (VRS). Additionally, this driver supports Hardware-accelerated GPU Scheduling when used with the Windows 10 May 2020 Update.
The way NVIDIA sees it, DirectX 12 Ultimate "codifies GeForce RTX's innovative technologies as the standard for multi-platform, next-gen games."
https://news.developer.nvidia.com/dxr-tier-1-1/DirectX Sampler Feedback, meanwhile, is "a hardware feature for recording which areas of a texture were accessed during sampling operations." It's supposed to assist with two scenarios--Texture Streaming and Texture-Space Shading--to reduce the load times caused by rendering the highly detailed graphics found in many games.
source https://developer.nvidia.com/blog/best-practices-using-nvidia-rtx-ray-tracing/Inline ray tracing (DXR 1.1) August 10, 2020 before the 30 series or the 6800xt releases
Use well-unified hit shading with inline ray tracing. As hit shaders are not invoked based on hits, all shading happens inline in the shader that casts rays. This means that classic shader optimization practices apply. I strongly recommend using unified hit shading that allows handling of different geometries with a common code path and avoiding übershaders with lots of divergent code. When multiple different shading models are required, I recommend using DispatchRays.
Use the hit specific system values for bindless resource access with inline ray tracing. As bindings in hit records are not available, geometry-specific bindings must be provided by other means. Accessing resources in unbounded descriptor tables based on the hit-specific system values such as InstanceContributionToHitGroupIndex and GeometryIndex is a good practice. I recommend avoiding indirections in accessing index, vertex, and material data when possible. For example, reading a resource index from a buffer based on system value like InstanceID for selecting an index buffer may cause latency that is difficult to hide.
Prefer the compile-time ray flags. Both compile-time and runtime ray flags can be used with inline ray tracing. I recommend preferring the compile-time flags when possible, as they may enable beneficial compile-time optimizations.
Monitor the register consumption of the query objects. After initialization, the query objects must hold state for the ray traversal when the shader is executing code that may continue the traversal. This consumes registers and complex user code may limit occupancy sooner than usually. The situation is similar to executing any-hit shaders in a DispatchRays pass. Variables initialized before using the query object and used after that may consume additional registers.
Consider thread group reordering to improve coherency. When using inline ray tracing from a compute shader, the default row major assignment of the dispatched thread groups to GPU for execution often does not result in optimal performance. Coherency of the memory accesses done by the thread groups simultaneously in execution on GPU can be improved by manually reordering the thread groups. For more information about reordering, see Optimizing Compute Shaders for L2 Locality using Thread-Group ID Swizzling.
They are up now on the OCUK website
https://www.overclockers.co.uk/pc-components/graphics-cards/amd/radeon-rx-6800-xt-series
They are up now on the OCUK website
https://www.overclockers.co.uk/pc-components/graphics-cards/amd/radeon-rx-6800-xt-series
Heh
Did you noticed BTW that the 3080 with RT is about 35% faster than the 2080ti. The same amount as without RT.
So seemingly the uplift under RT is negligible compared to Turing.
Ampere cards - as it seems at the moment - just faster, bigger Turings. They are as much faster as they need more power, RT and rasterization performance scales the same. (Except for veeery RT oriented games like Quake or Minecraft) They are not bad cards by any means, but after the biggest hype in the past few years, they are very underwhelming.
I would say it is has been slightly underperforming compared to nvidia in performance as well as stocksAmd trading blows in performance and now in stock levels
Feel bad for everyone that was sat there with their wallets open
I would say it is has been slightly underperforming compared to nvidia in performance as well as stocks
Please stop making things up.
So just to clarify did OCUK have no stock of the 6800XT or was it as it good as none
They didn't put any up.
There's a thread Gibbo put up about this - they got so much flack from having low volumes, huge backlogs and pre-order queues on the other releases that happened in the last few weeks, that they decided to hold off until they had a decent amount of stock. They got very few cards in for today and just thought it wasn't worth it.
(IMHO a very sensible move, rather than open it up and get screamed at)