From: Paul Brewster (p.f.brewster++at++larc.nasa.gov)
Date: 11/07/2001 06:56:42
I'm beginning to work on an application that uses satellite data to
generate terrain data with camera images texture mapped onto it. I can
straight-forward generate geodes, geosets, and geostates to handle this,
but this obvious problem is that the data set is very large and will not
fit into memory.
I know this is a well-known problem with various solutions to it, and I
just don't know these solutions. pfASD's and clip textures look to be
the Performer answer to this. Is this correct? Other than reading man
pages and looking at source code, is there an easy way to learn this?
Are there other methods out there?
What I'm thinking is that this is something that has been done many many
times. By now there should be a simple plug-away answer to this.
I had another quick question. I thought I saw that Performer 2.4
supports multi-texturing. I assume this means that I can map several
textures to the same geometry. Is this supported on IR2 and IR3
machines?
Thanks for any help.
Paul Brewster
Data Visualization and Analysis Lab
NASA Langley Research Center
This archive was generated by hypermail 2b29 : Wed Nov 07 2001 - 06:56:34 PST