[vtkusers] re: slow volume visualization

[Lisa S. Avila]

Hello Dean,

If you are not achieving the frame rates you see in VolView, then you 
probably have not downsampled your data far enough.

Checking for events for aborting is a platform-specific thing. You'll need 
to implement this differently depending on what window manager you have, 
what you are using for your GUI, etc. In VolView, we have special code for 
Windows or X depending on your platform.

You probably don't want to abort on mouse motion, but on mouse button 
presses. Otherwise, the high resolution render will often be cancelled.

Lisa


At 10:24 AM 6/27/2001, Erin Willson wrote:
>I have successfully compiled vtkdll.dll with Borland C++ Builder vers. 5 on
>a machine with:
>
>Pentium 4, 1.5 GHz, 512 MB RDRAM, ATI RADEON 64 Mb graphics card, running
>Windows 98 SE
>
>I am visualizing 3D medical data using vtkLODProp3D with texture mapping.
>In my console test app, I'm getting inferior interaction rates compared with
>those attainable with VolView or with David Gobbi's Atamai python scripts.
>I realize this issue has been brought up before but there wasn't much detail
>on what could be done.  I have tried the suggestions found in the FAQ but
>found them ineffective.  Could we have a peek at some of the coding of
>VolView that handles LOD?
>
>Also, how would one tie AbortCheckMethod() to poll for mouse movements so
>that rendering of a higher res texturemapper would be aborted (in C++) ?
>Any thoughts or help would be greatly appreciated.
>
>regards,
>
>Dean Inglis
>
>
>_______________________________________________
>This is the private VTK discussion list.
>Please keep messages on-topic. Check the FAQ at: 
><http://public.kitware.com/cgi-bin/vtkfaq>
>Follow this link to subscribe/unsubscribe:
>http://public.kitware.com/mailman/listinfo/vtkusers