but what I am thinking is - why were we hit with the issue?what about the other 438294209384092390 applications out there?IMO, drivers shouldn't change behavior all of a sudden.
If that improves openal support on mac and linux, I'd kill for it to be in. I recently abandoned java sound (because it's HORRIBLE these days, no pan and gain controls!?) in favor of OpenAL only, but some people (mainly mac it seems) can't get that to run.
we're not supporting openal-soft for mac, since no one has done a CoreAudio backend for openal-soft
Quotewe're not supporting openal-soft for mac, since no one has done a CoreAudio backend for openal-softDoes this mean no more sound support on Mac? It seemed to work fine before (as far as I could tell).
Out of curiosity, what's the proper way to create a display context now? I've just been using Display.create(PixelFormat) and Display.create(). Has this changed?
The legacy context creation routines can only return OpenGL 3.1 contexts if the GL_ARB_compatibility extension is supported, and can only return OpenGL 3.2 or greater contexts implementing the compatibility profile. This ensures compatibility for existing applications. However, 3.0-aware applications are encouraged to use wglCreateContextAttribsARB instead of the legacy routines.