OpenGL 4 haters need to try a few more graphics API's before they realize that the nature of the task of controlling an auxiliary computer sucks inherently. Talking to a coprocessor was already madness.
Näytä tämä ketju
My biggest complaint with OpenGL 4 is they they aren’t often willing to deprecate old patterns, and it leads to lots of needless confusion when trying to find how to do something. The answers usually start “because of OpenGL 1 back in the 90s...”
-
-
That and documentation per API level. Not that MSDN is perfect, but it is pretty essential. Vulkan specs and man pages are much tighter. http://docs.gl is a great alternative.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
-
-
It’s one thing I appreciate about OpenGL ES, especially 3.x, it’s many of the good bits of modern GL without some of the cruft. But some of the cruft remains :)
-
And es doesn’t stay up to date with the new features of gl4. I recently had to drop aggregate bind functions (glBindTextures, etc) because of es support. Also no texture views. =\
- Näytä vastaukset
Uusi keskustelu -
-
-
For me my largest frustration is that the default failure case is blackness. Like, forgot to enable the extension you are trying to use? No error, just blackness!
-
Tämä twiitti ei ole saatavilla.
- Näytä vastaukset
Uusi keskustelu -
-
-
Add this to the list: OpenGL error messages are real bad and different from driver to driver. With how vulkan has layers, and OpenGL can do similar function pointer injection, you'd think there's be an open source opengl validation layer.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.