I'm addressing some performance issues with a DX terrain viewer app,
and have a question about how DX handles invalid connections.
If you run Include on regular 2D grid with cull=0 and
position-dependent data, Include creates "invalid positions" and "invalid
connections" components.
However, Include destroys the "invalid connections" component (for
position-dependent data; at include.c:656) while wrapping up leaving only
"invalid positions" (the opposite happens for connection-dependent data).
Why does Include remove "invalid connections"? Is there a reason not
to just leave it?
In this case, other modules downstream (e.g. Map, then Render) then
have to rebuild "invalid connections" via a call DXInvalidConnections().
If this component were still attached to the field, it appears that this
overhead could be eliminated.
As an example: each redundant DXInvalidConnections() call on this
sample 1233x1409 grid takes about 13 seconds.
Randy
--
Randall Hopper (mailto:[EMAIL PROTECTED])
Lockheed Martin Operation Support
EPA Scientific Visualization Center
US EPA MD/24 ERC-1A; RTP, NC 27711
