I did record the apitrace for the issue, but due to Apitrace' issue 234 the replay is super slow if you do not use "apitrace replay -b xxx.trace".Yggdrasill wrote:No, I have been intending to do so for a while and then never got around to it. It doesn't help that apitrace and other tools result in just garbage output that is not relevant.
The only clue I have is the commit where it was introduced and the fact that the issue seems to intensify as more text appears on the screen, but that latter observation may be incorrect.
Simple main menu trace: X3TC_slow_apitrace.trace
Full trace with enabling/disabling overlay: X3TC_overlay_bug.trace
Code: Select all
...
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
Mesa: User error: GL_INVALID_OPERATION in glUniform4("_gl_LightSource[2].attenuation"@8 has 3 components, not 4)
...
If you replay the apitrace you can actually see that the scene in the main menu and the scene without ingame-overlay there are many more frames drawn than the one with the overlay enabled.