trimming an API trace leads to invalid opengl states during playback
Felix Schwarz
felix.schwarz at oss.schwarz.eu
Fri Mar 20 02:07:32 PDT 2015
I tried to trim a trace [1] recorded by apitrace. When replaying the trimmed
trace I get some error output on my console about invalid OpenGL states.
>From reading the mailing list + some other sources I seems to me as if
trimming is known to be buggy in some cases and there is very little dev time
available to fix these issues. Is it worthwile to open a github issue anyway?
Assuming that apitrace's trimming may fail to work correctly in some cases I
was wondering if it is possible to create equivalent C code from a trace? That
way I could trim the OpenGL calls manually. Is that possible? Are there any
tools to help with such an approach? Is it feasable building something like that?
Felix
[1] https://dl.dropboxusercontent.com/s/hc6v7gdcshj4ljd/eu4.trace-lockup.xz?dl=0
Warning: replaying this trace with the r600g mesa driver (not radeonsi) may
lock up your computer.
More information about the apitrace
mailing list