Hi,
running urt 4.1.1 on mesa (the free/open-source/official linux OpenGL implementation) results in:
1) The following messages being output at startup:
339 glXSwapIntervalSGI(interval = 0) = 6
339: warning: unsupported glXSwapIntervalSGI call
Perhaps urt uses the extension without checking for it first?
2) The following messages being spammed once a frame (anyway, more than once a second, they quickly flood the terminal and impact performance):
27093 glLockArraysEXT(first = 0, count = 0)
27093: warning: glGetError(glLockArraysEXT) = GL_INVALID_VALUE
27094 glUnlockArraysEXT()
27094: warning: glGetError(glUnlockArraysEXT) = GL_INVALID_OPERATION
27099 glLockArraysEXT(first = 0, count = 0)
27099: warning: glGetError(glLockArraysEXT) = GL_INVALID_VALUE
27100 glUnlockArraysEXT()
27100: warning: glGetError(glUnlockArraysEXT) = GL_INVALID_OPERATION
...
Ignore the 'number:' prefix, It's an artifact of replaying GL traces with apitrace. (https://github.com/apitrace/apitrace)
These messages either capture a bug in urt or a bug in mesa; they occur with both mesa 7.11 from debian unstable, and mesa git; and with all the mesa drivers I tested: r600g, nouveau/nvfx, llvmpipe and softpipe (the latter should be close to a reference OpenGL implementation).
I think they are worth checking out.
Cheers,
Advertisement
Page 1 of 1
Urt GL errors reported by mesa
A couple of errors reported by mesa the devs may find useful
#3
Posted 06 November 2011 - 07:12 PM
cyrus, on 05 November 2011 - 03:35 PM, said:
Had this problem last week. Resolved by re-installing my nVidia drivers. I think there was a mesa update that borked the nVidia drivers. Recompiled against the new mesa version and all was well.
I reported these messages just because FS devs may find them useful. There are a number of broken GL apps out there, and the proprietary drivers (NVIDIA and AMD) silently ignore the faulty GL calls, so you can't really find out bugs using them. Anyway, yeah, the game works fine for me, bugs or not :-)
Cheers,
Page 1 of 1