[vtkusers] vtk 3.1 contouring problem (bug?)

[Dimitris Agrafiotis]

I tried it and got the same behaviour.

Dimitris


On Thu, 29 Jun 2000 07:43:54 -0400 Charles Law <charles.law at kitware.com>
wrote:

> I have been planning to look into this, but have not had the time.
> 
> Try replacing vtkMarchingCubes with vtkSynchronizedTemplates3D.  Do you get 
> the same behavior?
> 
> Charles.
> 
> At 11:50 AM 6/26/00 +0100, you wrote:
> >Dear All
> >
> >This is the second time I am sending this letter.
> >I have written a program in Visual C++ that allows the user to
> >visualize multiple surfaces from the same dataset by choosing more than
> >one isovalues. The program was running fine under vtk 2.4, but when I
> >switched to vtk 3.12 the following problem occured. If I select to
> >visualize more than one surfaces then things are slowed down
> >tremendously (in fact nothing moves) even if the new surface has only a
> >few polygons. Also the surface extraction and rendering of the second
> >surface seem to take ages. I didn't have any problems with vtk 2.4 (I
> >could actually visualize up to 5 surfaces with no problem - only limit
> >was the number of triangles)and I have no idea why this happens.
> >The pipeline fragment of the program is the following:
> >
> >vtkMarchingCubes* mcFilter = vtkMarchingCubes::New();
> >         mcFilter->SetValue(0, isoDlg.m_nIsoValue); // user value
> >         mcFilter->SetInput(histogram.accumulate->GetInput());
> >         mcFilter->Update();
> >
> >vtkStripper* stripper = vtkStripper::New();
> >         stripper->SetInput(mcFilter->GetOutput());
> >
> >vtkPolyDataMapper* Mapper = vtkPolyDataMapper::New();
> >         Mapper->ImmediateModeRenderingOn();
> >         Mapper->ScalarVisibilityOff();
> >         if (!this->representation)
> >                 Mapper->SetInput(mcFilter->GetOutput());
> >         else
> >                 Mapper->SetInput(stripper->GetOutput());
> >         Mapper->Update();
> >vtkLODActor* Actor = vtkLODActor::New();
> >         Actor->VisibilityOn();
> >         Actor->SetMapper(Mapper);
> >         this->Props->AddItem(Actor);
> >
> >// Delete objects
> >         mcFilter->Delete();
> >         stripper->Delete();
> >         Mapper->Delete();
> >         Actor->Delete();
> >
> >where Props is of type vtkPropCollection. So whenever the user chooses
> >a new isovalue a new actor is added to the collection of actors.
> >All the actors in the collection are added to the
> >one and only renderer.
> >Is there some sort of bug in vtkMarchingCubes of the latest vtk
> >version? Maybe I am doing something wrong, but with vtk2.4 everything
> >worked perfectly. Please let me know if there is a solution to this and
> >if anyone had similar problems.
> >
> >Thanks in advance
> >Dimitris
> >
> >
> >
> >
> >----------------------
> >Dimitris Agrafiotis
> >University of Bristol
> >Department of Electrical & Electronic Engineering
> >Merchant Venturers Building
> >Woodland Road, Bristol BS8 1UB, UK
> >Phone:  (+ 44 117) 9545194
> >E-mail: d.agrafiotis at bristol.ac.uk
> >
> >
> >_______________________________________________
> >This is the private VTK discussion list.
> >Please keep messages on-topic. Check the FAQ at: 
> ><http://public.kitware.com/cgi-bin/vtkfaq>
> >vtkusers mailing list
> >vtkusers at public.kitware.com
> >http://public.kitware.com/mailman/listinfo/vtkusers
> 

----------------------
Dimitris Agrafiotis
University of Bristol
Department of Electrical & Electronic Engineering
Merchant Venturers Building 
Woodland Road, Bristol BS8 1UB, UK
Phone:  (+ 44 117) 9545194
E-mail: d.agrafiotis at bristol.ac.uk