nci / drishti

Drishti
MIT License
171 stars 39 forks source link

Drishti 3.0 crashes when loading a volume dataset after a surface #68

Open JuliaBehnsen opened 2 years ago

JuliaBehnsen commented 2 years ago

Great to see version 3.0 released! Unfortunately I immediatly found something to make it crash...

When loading a surface, and then a .pvl.nc dataset (drop and drag), the surface editor stays open, with the surface still shown. However clicking on the surface will make Drishti crash.

Also when loading a volume file first, and then a surface, the surface editor will open, with the surface, but the surface itself seems invisible. It can be moved etc, but I can't seem to make it show. (I think maybe you're not meant to open both a volume file and a surface at the same time?)

Opening two surfaces, one after the other, seems to work fine.

AjayLimaye commented 2 years ago

Currently, surfaces and volumes are not handled together in normal hires rendering mode. If you switch to Raycasting option you should be able to see both together.

Maybe I should clear all surfaces when volumes are loaded in order to reduce the confusion.

Cheers, Ajay

On Sat, Apr 2, 2022, 2:14 AM JuliaBehnsen @.***> wrote:

Great to see version 3.0 released! Unfortunately I immediatly found something to make it crash...

When loading a surface, and then a .pvl.nc dataset (drop and drag), the surface editor stays open, with the surface still shown. However clicking on the surface will make Drishti crash.

Also when loading a volume file first, and then a surface, the surface editor will open, with the surface, but the surface itself seems invisible. It can be moved etc, but I can't seem to make it show. (I think maybe you're not meant to open both a volume file and a surface at the same time?)

Opening two surfaces, one after the other, seems to work fine.

— Reply to this email directly, view it on GitHub https://github.com/nci/drishti/issues/68, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABMVVLV3THC2WED6QGEJ6SLVC4HEFANCNFSM5SI76OMQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>