- Joined
- Dec 14, 2009
- Messages
- 12,451 (2.38/day)
- Location
- Glasgow - home of formal profanity
Processor | Ryzen 7800X3D |
---|---|
Motherboard | MSI MAG Mortar B650 (wifi) |
Cooling | be quiet! Dark Rock Pro 4 |
Memory | 32GB Kingston Fury |
Video Card(s) | Gainward RTX4070ti |
Storage | Seagate FireCuda 530 M.2 1TB / Samsumg 960 Pro M.2 512Gb |
Display(s) | LG 32" 165Hz 1440p GSYNC |
Case | Asus Prime AP201 |
Audio Device(s) | On Board |
Power Supply | be quiet! Pure POwer M12 850w Gold (ATX3.0) |
Software | W10 |
You haven't read everything that I said or you didn't pay enough attention. Vulkan uses low level functionalities taken from Mantle that are no longer hardware and platform dependent otherwise if it does contain hardware design specific functionalities like you claim it wouldn't work on hardware different from AMD's. An open source , cross platform low-level API , cannot be biased from a functional point of view towards a set of hardware , it either supports it or not. ( and there is definitely hardware that doesn't support it from both AMD and Nvidia ) . That is like saying assembly code is biased towards Intel because you can use AVX instructions that their chips are built to better support it. While we all know that is dumb , AMD is free to make a design that better fits those instructions as well without having to fight with an inherent bias for Intel . All these arguments against Vulkan as a viable medium for comparing performance can be literally had for every other API.
You misread my post. You initially said Mantle formed Vulkan, I was suggesting it wasn't that way as it would undermine your comment.
Vulkan has little (though not nothing) to do with Mantle. And my other point was AMD worked closely with Khronos to get the best out of it for their hardware. I read a lot about Vulkan and how AMD worked hard to make it work well for them.