3D model not showing up/not centerable anymore

Hey,
I just finished making an awesome 3D model after many hours and then suddenly the 3D image disappeared and now whenever I load up the Project, my 3D section does not work; Initially there is the cube without a 3D model in the center, but once i make one single left click in the 3D area, it is going away. I cant center view it, no lines appear when i try to toggle on 3D cube and 3D axis lable, nothing shows up. Current version is 5.6.2 - please tell me this is fixable and my data is now lost :frowning:

I also already tried to use the “Refocus camera on this point” option in the CT data but it did not solve the problem.

Could it be that my 3D image and center is so far out of my screen, that i cant even see it anymore? Even scrolling madly into one or the other direction didnt solve it for me… Is there a way to complete recenter it? I can also make a video for you if that helps.

Or maybe is there a way to just reopen the dicom images and import my segmentations again? Because if I use them over the same Dicom images i could just create a new project if that makes sense?

When I enter a new project the 3D viewer works normally, but once I open the scene from this project I can not happen to find my 3D model…

Any help is much appreciated! Thank you in advance!!

I have had this bug but only a few times. Restarting Slicer always solved the issue. I couldn’t track it down though. I suggest saving the scene into MRB, restart Slicer, and load the scene.

Thank you for your reply, I already reloaded the scene several times, which did not solve the problem. I now also tried saving it into an .MRB file, and opened the .MRB scene, but it also did not solve the problem. Do you perhaps have any other solution to this problem? Something like creating a new project but reopening the Segmentations in there - if this is even possible?

Maybe try loading the MRB in the latest preview version. If that does not solve the issue then if you can share the MRB we can take a look.

Thanks for the answer, I have been fiddling around with the file the past weeks and work has been really time consuming so its been a while but I couldn´t come up with a solution yet. If you´d still be up for having a look at it, it would really be much appreciated. Just let me know how we can get in contact?

I think you could help most with:

  • Downloading the 5.8 stable
  • Creating a scene using sample data that produces this issue when loading

If you have a scene that you cannot publically share, you can send me a cloud drive link in private message, but I’m even busier nowadays than normal so not sure when I can take a look. If you manage to reproduce this in a way that can be shared, then anyone in the community will have the possibility to use it for fixing.
It is also possible that 5.8 does not produce the issue any more…

You can narrow down the issue by saving the scene in .mrml format - and all the nodes as additional data files. After this, restart Slicer and instead of loading the scene (.mrml file), load each data file one by one. If you see that after loading a specific file the application starts to misbehave then you known that something is wrong with that file and we can investigate it further, focusing on that single file.