I just misunderstood what you were talking about then. Yes, if you ditched Vulkan et al completely and just had a low-level API that was nVidia-specific, one that was ATI-specific, and one that was Intel-specific, that would be amazing, especially if it is the same PC/Mac.
-
-
I argue that data spec is the right way to do an async API like this. If you must translate the data in the driver, go ahead, but it is _much_ better than forcing (non-inlinable!!!) function calls every time. And over time, you can have cards take most of the data directly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
AMD and Intel already do this. They have low level data specifications, but you can't expect to have *one* for each vendor; you get one for each device. The result of open source communities writing common low level abstractions over these specifications is the GPU drivers :)
-
I absolutely can, and do, expect it. If they want to change the data format every ~2-3 years, be my guest, I can support many different output formats. In the meantime, the driver is welcome to mutate my data as it sees fit for forwards/backwards compatibility.
- Show replies
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.