Status update of a couple issues

[José Fonseca]

On Wed, Oct 3, 2012 at 8:22 PM, Anthony Lombardi
<tonyjlombardi at gmail.com> wrote:
>
> Does anyone know the status of implementing the support of Direct3D 10 or
> 11 with the retracer?

Implementation has not started and there is no ETA.

There's not much work involved here (essentially fork and adapt
retrace/d3dretrace.py for D3D10/11), but it's not a priority for me,
and I have been the only person interested in D3D support so far.

Given that Direct3D has PIX, the only reason I have been pursuing D3D
support on apitrace is due to a vague wish of using the same apitrace
tools for everything, and because PIX sometimes refuses to record
certain applications. But D3D10/11 is not a priority for  me now. I
have a long queue of patches to integrate into apitrace.

> Or the status of making the retracer start and stop at arbitrary points in
> the trace?

It's not possible to skip all calls up to an aribitrary point, as side
effects will be necessary later on.

Carl Worth has been working on a tool for automatically trimming a
subset of calls (OpenGL only), which effectively does what you want:
trim all calls that are irrelevant for a given range of interest. I
have not integrated his work on master yet. Please look into the
mailing list archive for further details.

Jose