[vtkusers] Fwd: VTK is completely Slow

[David Doria]

On Tue, Jul 19, 2011 at 2:15 PM, Thiago Macedo <tmacedo29 at gmail.com> wrote:
> Hi,
>
> I'm developing a CAD based software. At some point, the
> app converts the 2D drawing into a 3D huge scene.
> The main problem is: It's very slow!
> I'm not using any complex algorithm neither complex structure. The
> 'translation' between 2D and 3D is very fast, and creates basic
> geometries. E.g..:
> A hydraulic tube is converted into a cylinder (vtkCylinderSource), the
> connection between 2 hydraulic tubes is a sphere (vtkSphereSource);
> A 2D line is converted into a 3D line (vtkLine)
> All of 3D entities has a mapper and an actor.
> I'm working with a lot of (closer than million) 2D entities, and the
> 3D scene is totally slow.
> I've tried to use all tips wrote in the wiki (
> http://www.vtk.org/Wiki/VTK/FAQ - How to handle large data sets in VTK
> ) and I have just a little improvement.
> I searched into the books (v5) and was not able to find anything to
> help me. I think it should be faster if I use simple structures like
> cylinders and lines like I'm doing.
> Is there a way to make it faster?
>
> Thank you in Advance
> Best Regards
>
> --
> Thiago B. Macedo

"All of 3D entities has a mapper and an actor."

I think that may be your problem. I would try useing the AppendFilter
(http://www.vtk.org/Wiki/VTK/Examples/Cxx/Filters/AppendFilter) to
create a single data set that you can create a single mapper/actor
from.

See if that help and let us know.

David