Remember me

Lost Password?

Register now!


Who's Online
73 user(s) are online (55 user(s) are browsing Forums)

Members: 2
Guests: 71

TearsOfMe, walkero, more...

Support us!


Report message:*

Re: Porting apitrace

Subject: Re: Porting apitrace
by Hans on 2019/3/29 11:52:09

So it should be 2 modules, one for ogles2.library and another one for warp3dnova (?)

Yes. 3 modules if you want to log the raw OpenGL calls for GL4ES, but lets not get ahead of ourselves. We need to get something working first.

And probabaly making "tracing" will be easy, harder will be replaying and viewing.

Yes, the tracing will be easier than playback.

The documentation says that you can log calls on one machine/OS, and play it back on another. So as far as OpenGL is concerned, it would already be useful with just the call logging working.

Of course, having to copy logs to another machine for playback and analysis would suck, so we want the playback and GUI working too.

But even pure "tracing" for both libraries will be also nice to have, it will then dump the lists of ogles2/ w3d calls with their arguments / offsets , and even that info will help to see when and how many and what was called

Yes, even just having the call logs would be useful.


Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project