Hi all, I found bugs concerning the volume rendering, but unfortunately I cannot give you a receipt to reproduce for sure.
This is what I have done: - I loaded this volume: http://pubimage.hcuge.ch:8080/DATA/RATIB1.zip (~250 MB) - I turned on volume rendering. - I "played" a little with the 2D and 3D windows (scrolling through the slides, zooming in and out, turning the volumen and so on) I noticed the following: 1. Bug: After a while the 3D window is completely black. Nothing is rendered anymore. 2. Bug: Memory leaks: The more I play the more the memory usage increases (starting from 590 MB to 630 MB when the rendering window is getting black). 3. When I click the left mouse button in a 2D window, then it is like I clicked it in the 3D window. The quality gets worse and as soon as I release the mouse button it is rendered in high quality again. Seems to be unnecessary (it just slows down everything). 4. I am using a debug toolkit chain (vtk, itk, qt3, mitk, everything is compiled as shared) and it took 2:45 minutes to render the volume. Even in the release version it takes very much time. Some time ago, I implemented a small example just using vtk, itk and wxwidgets to load a volume and to render it and it was never that slow. So why is this function in mitk/mainapp that slow? What happens under the hood? (I noticed for example, that a copy of the volume is made) Regards Klaus -- Psst! Geheimtipp: Online Games kostenlos spielen bei den GMX Free Games! http://games.entertainment.web.de/de/entertainment/games/free ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
