Hi Sebastian, > Von: sebastian ordas [mailto:[email protected]] > > I´m trying to link MITK with VTKEdge. To this aim, I need to buld MITK > with vtkCVS > Has anyone managed to run a MITK application with vtkCVS?
Your mail got me intrigued, so I tried and succeeded ;-) > Apparently, the library is somehow prepared to deal with the Peeling > issue > > //BUG (#1551) added settings for depth peeling MITK is compatible with VTK5.2 since revision #15409 (e.g. it links and runs). It uses the depth peeling mechanism, but this is currently hardcoded. We will make that configurable in the future. MITK also compiles and runs with the current CVS checkout of VTK. > > In my case, I modified mitkSurfaceMapper2D to use vtkPointLocator > instead of vtkPKdTree > and also use PolyDataNormals instead of PPolyDataNormals Why did you do this? This doesn't seem to be connected to VTKEdge. > So far so good: everything compiled fine and I was able to use e.g. > vtkKWEVolumeMapper from vtkEdge in mitkVolumeDataVtkMapper3D > (I had to modify the CMakelist, of course, but nothing serious) > > But the problem comes at runtime: the application crashes in debug and > release with a message > > "Run-Time Check Failure #0 - The value of ESP was not properly saved > across a function call. > This is usually a result of calling a function declared with one > calling convention with a function > pointer declared with a different calling convention." > > I´m running on windows XP using QT4 This sounds like you used different compilers for some of the libraries that you linked together. Here is what I did (all in Windows XP, Visual Studio 9): - CVS checkout of VTK, compiled with shared libs ON, and QVTK with Qt3, debug build - SVN checkout of VTKEdge, compiled with shared libs ON, debug build - svn checkout of MITK, use Qt3, CVS version of VTK and ITK 3.10.2, all debug builds - because I was too lazy to edit the cmake files, I just added the VTKEdge include directories, libs and linker directory to the mitkCore Project - in mitkVolumeDataVtkMapper3D.cpp: - added #include "vtkKWEVolumeMapper.h" - changed m_HiResMapper = vtkKWEVolumeMapper::New(); (also changed data type of member in the header) - erased all m_HiResMapper->XXX() calls - compile mainapp as debug (including QmitkVolumeVisualization functionality) - start, load Pic3D example dataset - change to QmitkVolumeVisualization, activate volume rendering. This produces loads of error messages on the console, but it also produces a fast(!) volume rendering of the volume in the 3D window. Looking at the CPU load and update rate of the rendering, this is definitely the vtkEdge GPU based renderer at work. The console error messages propably originate from the fact that I did not set the correct parameters and did not provide a transfer function. But it works without crashes. We will incorporate proper vtkEdge volume rendering support in the next weeks. Best regards, Jochen ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
