Volume Property json file is incorrectly saved

I Load a 16bit unsigned dataset, set up its volume rendering properties such as

  1. Use shift slider
  2. Change the material preset to a non-default one (the second brightest)
  3. Remove some points from the scalar mapping and shift the colors aroun

At this stage I have perfectly fine rendering. if I save this file to disk and reload and assign this new volume property, the rendering dissappears as the scalar opacity flat lines (all points are 0.0). Reproduces on today preview build on mac.

I asked copilot what is different between the unmodified VP and the one saved and it said:

Works.vp.json effectiveRange: [0, 65535] (full 16-bit range). doesntwork.json effectiveRange: [3800, 69335]. 69335 > 65535 — outside the actual data range. The min 3800 also chopped off the (0, …) and (2.22e-308, …) baseline points, which probably explains why the start of the tent is gone in the broken file. If effectiveRange was edited in the UI (or auto-recomputed from “current threshold” rather than data range), the saver may have culled all control points outside that range — including the peak’s left base — leaving just a flat-zero function.

Not entirely sure what that means, I hope it is helpful. But there is clear bug in saving.

If you want the original volume I used, it is here: https://github.com/muratmaga/Bumblebee_Stained/releases/download/v1/Bumblebee.nrrd

@lassoan @Sunderlandkyl

A bug report was submitted, let’s continue the discussion there: