Hi there, On further investigation. The mapper I require mitkGPUVolumeMapper3D is defined in module MapperExt, and added at runtime by mitkIOExtObjectFactory. This is auto-loaded using microservices. So, in MitkWorkbench it was working, whereas in our app it was not.
The reason was that very early on, effectively in a function called from main, we had a function called RegisterNifTKCoreObjectFactory which called mitk::CoreObjectFactory::GetInstance()->RegisterExtraFactory(mitk::NifTKCoreObjectFactory::New()); So, this seems to be upsetting the auto-loading feature. If I remove the call to RegisterNifTKCoreObjectFactory, the volume renderer works! In my mind, we are not trying to do anything clever here. Our object factory was once (a long time ago,… in a land far far away etc), based upon mitkSegmentationObjectFactory. It looks to me that this class was once instantiated via a call to registerSegmentationObjectFactory, but now this appears not to be the case, or i can’t find the code that registers that factory. So, Im clearly missing one more link. Should I be auto-loading all factories? Or can I still use the old approach? Thanks Matt On 13 Aug 2014, at 07:47, Clarkson, Matt <[email protected]<mailto:[email protected]>> wrote: Hi All, I just took a look at this. Im using a short int image. In our application that uses volume visualisation, the volume rendering does not work. But if i switch to the MITK-build folder of the MITK compiled within our superbuild, and activate the MitkWorkbench, then the volume rendering does work on the same image. On the console I can see that MitkWorkbench outputs: [3.734] [mapper.vr] initializing cpu-raycast-vr (vtkFixedPointVolumeRayCastMapper) (8 threads) whereas our application does not. Does this problem have something to do with the way mappers are registered. Has this changed between 2013.09 and 2014.03, as we recently did an upgrade. Is it something to do with dynamically loading the mappers as a module? Do I need to register some factory? Can anyone help? Many thanks Matt On 11 Jul 2014, at 09:56, Goch, Caspar Jonas <[email protected]<mailto:[email protected]>> wrote: Hi Miklos, what is the pixel type of the image you are trying to render? There is a known issue regarding floating points between 0 and 1 (and to an extent larger floats, as the threshold selection box does not actually display the selected threshold, but you can still move it using the cross). I just tested it on a short image and it worked fine (on a branch based on commit 470f04e). Best, Caspar Von: Miklos Espak [mailto:[email protected]] Gesendet: Donnerstag, 10. Juli 2014 16:28 An: mitk-users Cc: Zombori, Gergely Betreff: [mitk-users] Volume rendering broken in 2014.03? Hi, I am trying to use the Volume Visualisation view, but not able to turn on the 3D rendering at all. I selected an image, ticked in the checkbox on the top of the view, but it did not have any effect. I tried it in the MitkWorkbench, too, with the same result. Has anybody noticed this? Has it been fixed already, eventually? If yes, which branch could I use? If not, is it planned to fix it for the upcoming release? Cheers, Miklos ------------------------------------------------------------------------------ Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft_______________________________________________ mitk-users mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
