Manta Interactive Ray Tracer Development Mailing List

Text archives Help


Re: [MANTA] non-const intersect function


Chronological Thread 
  • From: Steven Parker <sparker@cs.utah.edu>
  • To: Hansong Zhang <hansong@sgi.com>
  • Cc: "'manta@sci.utah.edu'" <manta@sci.utah.edu>
  • Subject: Re: [MANTA] non-const intersect function
  • Date: Tue, 21 Jun 2005 15:06:49 -0600
I think that this is the perfect case for mutable data members. It just needs to be thread-safe.

Steve


On Jun 21, 2005, at 2:48 PM, Hansong Zhang wrote:

Hi Steve,

I see a need for non-const intersect() functions and wonder if anyone has encountered this need before. Basically, in the volume renderer, bricks of the volume can be out of the memory or may be in the memory but in a compressed form. The brick could also be in the memory, uncompressed, but is not at the right resolution you want it at the moment. When a ray goes through a brick and requires data at a particular resolution, it may cause a change in the data (i.e. previously unavailable data being pulled in and cache being replace/refreshed). This would require a non-const intersection function. Is there a way around this in Manta currently?

Thanks,
Hansong




Archive powered by MHonArc 2.6.16.

Top of page