I'm not sure how to convince people to do that though since they just moved _away_ from that by going from Mantle to Vulkan :/ So I'm afraid you would just end up with more layers of cruft here.
-
-
This is not substantially different from what they do now, since they do all the stuff behind my back anyway, just on a per-function call basis. For all we know, it might even be _more_ efficient to do back/forward-compat on whole buffers of invocation than per-function.
-
The difference, though, is on the cards I _am_ aware of, I can pass data properly that needs no molestation and that keeps driver participation to a minimum - no thread problems, no API versioning problems, no binding issues, no hiccups, no lazy eval at the wrong times.
- Show replies
New conversation -
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.