Re: weird "An impossible ALUT error condition was, reported?!?" problem
Sammy Fischer <[email protected]>
| Newsgroups | gmane.comp.lib.openal |
|---|---|
| Message-ID | <[email protected]> |
On Sunday, 11 April 2010 10:37:58 Chris Robinson wrote: >It looks like you're using alutGetErrorString to get a string of an AL error. > IIRC, alutGetErrorString is only for ALUT's error codes. If you want to get a > string from alGetError's return value, use alGetString (similarly, use > alcGetString for alcGetError return values) Thanks Chris. For some reasons I thought alutGetErrorString() would return alGetString() too. I corrected the code, and the actual error is "AL_INVALID_NAME". Still weird, but at least it's something to work from and not even a gamestopper. Now I should be able to figure out where it's coming from. bbye _______________________________________________ Openal mailing list [email protected] http://opensource.creative.com/mailman/listinfo/openal