- Joined
- May 8, 2016
- Messages
- 1,846 (0.61/day)
System Name | BOX |
---|---|
Processor | Core i7 6950X @ 4,26GHz (1,28V) |
Motherboard | X99 SOC Champion (BIOS F23c + bifurcation mod) |
Cooling | Thermalright Venomous-X + 2x Delta 38mm PWM (Push-Pull) |
Memory | Patriot Viper Steel 4000MHz CL16 4x8GB (@3240MHz CL12.12.12.24 CR2T @ 1,48V) |
Video Card(s) | Titan V (~1650MHz @ 0.77V, HBM2 1GHz, Forced P2 state [OFF]) |
Storage | WD SN850X 2TB + Samsung EVO 2TB (SATA) + Seagate Exos X20 20TB (4Kn mode) |
Display(s) | LG 27GP950-B |
Case | Fractal Design Meshify 2 XL |
Audio Device(s) | Motu M4 (audio interface) + ATH-A900Z + Behringer C-1 |
Power Supply | Seasonic X-760 (760W) |
Mouse | Logitech RX-250 |
Keyboard | HP KB-9970 |
Software | Windows 10 Pro x64 |
Sorry to interpret it like dxdiag tool do ("DDI Function 11.4") ?Get this into your head: it will not be fixed, because the information that is there is CORRECT.
You just interpret it differently.
Microsoft's dxdiag tool must be "mad" to say Fermi is not working in DX12 mode (sarcasm).
Here's a thing to know :
Say hello to DirectX 11.3 - LINK.
It was released along side DirectX 12 in Win 10, and it supports some of DX12 features.
^I agree, that those features are supported by Fermi (with current driver), and they are indeed part of DirectX 12.
My problem ?
They are not enough for actual DirectX 12 support.
Hence we have Fermi with "DDI 11.4" in dxdiag tool, and Kepler with "DDI 12".