Talk:Feature levels in Direct3D

Optional features for Nvidia Pascal

Please stop inserting your conjectures about Nvidia Pascal to the optional feature matrix table. There is little use of having a column of mostly "unknown" parameters, and non-empty ones are not verifiable because there was no announcement or specification leak, and there are no actual cards to run the feature tests on. --Dmitry _{(talk•contibs)} 09:26, 5 August 2015 (UTC)[reply]

"Asynchronous shader engine" and "Dedicated compute engine"

Please stop adding this invented capability to the Direct3D feature matrix table. As I said in Talk:Direct3D/Archive 1#Edit war on "Async shaders", "Asynchronous shader engine" is a marketing term that only concerns internal microarchitectural details of the GPU but has absolutely no relation to the optional features of the Direct3D runtime - i.e. the capabilities enumerated with D3D12_FEATURE_DATA_D3D12_OPTIONS structure which is reported by ID3D12Device::CheckFeatureSupport method for each graphics card. Therefore "Async shaders", "dedicated shaders", and other terms you can invent, do not belong to the above table since they are not really feature options reported by the Direct3D runtime, according to MSDN documentation above.

If you really think these low-level details are relevant, you can add some descriptive text in clear prose to relevant articles, which would be either the Direct3D#Direct3D 12 section, GPU lists such as List of AMD graphics processing units, List of Nvidia graphics processing units, List of Intel graphics processing units, or articles on individual GPU series.--Dmitry _{(talk•contibs)} 22:30, 11 September 2015 (UTC)[reply]

Please stop inserting fancruft such as "asynchronous shaders", "multi-engine" etc. to the table of optional features. These are internal implementation details of the GPU architecture and WDDM drivers, and as explained above, they irrelevant in the context of feature levels and optional features of the Direct3D 12 API. --Dmitry _{(talk•contibs)} 15:04, 5 June 2016 (UTC)[reply]

Multi Engine is a part of DirectX12 features and should be listed. https://docs.microsoft.com/en-us/windows/win32/direct3d12/user-mode-heap-synchronization

Prefix-NA (talk) 05:25, 27 August 2019 (UTC)[reply]

Direct3D 12 optional feature support matrix by vendor/GPU series

Intel Broadwell support DirectX 11.2 — Preceding unsigned comment added by 2A02:2168:866:50D:0:0:0:1 (talk) 18:14, 5 November 2015 (UTC)[reply]

Broadwell and Haswell support Direct3D 12 in Windows 10 - so they do support Direct3D 11.3 runtime in Windows 10 by extension. 11.3 has all the "hardware" features of 12, except for resource binding model, multi-engine, indirect drawing, and a few more non-optional APIs. 11.2 runtime in Windows 8.1 does not have any "hardware" features exposed by Broadwell or Haswell. --95.28.27.124 (talk) 08:02, 4 May 2016 (UTC)[reply]

Nvidia does not currently have Resource Heap Tier 2

http://32ipi028l5q82yhj72224m8j.wpengine.netdna-cdn.com/wp-content/uploads/2016/03/Practical_DX12_Programming_Model_and_Hardware_Capabilities.pdf

Check page 41 of the slides for reference. These slides came from a Game Developers Conference and was presented by both Gareth Thomas from AMD and Alex Dunn from Nvidia. — Preceding unsigned comment added by 45.74.65.203 (talk) 06:43, 8 April 2016 (UTC)[reply]

This is strange because their drivers have always been reporting Resource Heap Tier 2 on Maxwell-2. I'll ask people to check this with the latest driver. --95.28.27.124 (talk) 08:02, 4 May 2016 (UTC)[reply]

Yep, Tier 1 with drivers 361.43 --Dmitry _{(talk•contibs)} 09:48, 5 May 2016 (UTC)[reply]

External links modified

Hello fellow Wikipedians,

I have just modified 2 external links on Feature levels in Direct3D. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 09:34, 30 December 2016 (UTC)[reply]

Gnc5 column

First the Page seems to be broken, with some wrong formatting of the column in latest FF desktop and Android. Secondly I doubt that the Data is correct, because it would be worse than the gnc4 column. Where is the source? Either add real data or the wrong(?) one should be removed. — Preceding unsigned comment added by 185.69.244.2 (talk) 16:31, 20 January 2017 (UTC)[reply]

Wrong Intel generations in the support matrix?

It says Ice Lake is 11th gen and Tiger Lake is 12th gen. I think Ice Lake is 10th gen and Tiger Lake is 11th gen. Tooltip is correct.

hacker Stemibellarose (talk) 22:07, 3 June 2022 (UTC)[reply]

Does not reflect the GeForce 40 series

Now that it's out (see [1] (in Chinese)), the sub-section "Support matrix" definitely should reflect it (I quite wonder whether they support stencil reference value from pixel shader or not), yet it is not reflected at all, which surprised me a lot. Hope that fellow Wikipedians with time and expertise can update the sub-section a.s.a.p. Thanks!--RekishiEJ (talk) 09:42, 29 September 2022 (UTC)[reply]

The feature support is pretty much the same as in Ampere and Stencil reference value from Pixel Shader is still not exposed by the driver. Tiled Resources could be on Tier 4 in the latest driver for Ada Lovelace, but I'm getting conflicting reports from different diagnostic applications. Fellix (talk) Fellix (talk) 22:57, 29 January 2023 (UTC)[reply]