Visiblement les drivers Nvidia ne supportent que partiellement L'Async Compute pour le moment. Commentaire d'un développeur de chez Oxide:
"Regarding Async compute, a couple of points on this. FIrst, though we are the first D3D12 title, I wouldn't hold us up as the prime example of this feature. There are probably better demonstrations of it. This is a pretty complex topic and to fully understand it will require significant understanding of the particular GPU in question that only an IHV can provide. I certainly wouldn't hold Ashes up as the premier example of this feature.
We actually just chatted with Nvidia about Async Compute, indeed the driver hasn't fully implemented it yet, but it appeared like it was. We are working closely with them as they fully implement Async Compute. We'll keep everyone posted as we learn more."
http://www.overclock.net/t/1569897 [...] t_24379702
Certaines personnes avancent des explications intéressantes mais sont-elles exactes ?
"Maxwell 2: Queues in Software, work distributor in software (context switching), Asynchronous Warps in hardware, DMA Engines in hardware, CUDA cores in hardware.
GCN: Queues/Work distributor/Asynchronous Compute engines (ACEs/Graphic Command Processor) in hardware, Copy (DMA Engines) in hardware, CUs in hardware."
http://www.overclock.net/t/1569897 [...] t_24380072
Je présume que tout cela n'est pas évident à vérifier
L'autre "hot topic" c'est la préemption pour la VR.
Certains développeurs se plaignent que cela marche très mal chez Nvidia.
Il y a eu plusieurs releases de drivers pour la VR sur le site dédié aux développeurs ces derniers temps, est-ce lié ?
http://wccftech.com/preemption-con [...] ic-nvidia/
Message édité par Nono0000 le 07-09-2015 à 21:35:12