# Volume rendering file shows up as changed in Save dialog directly after opening an mrml scene

**URL:** <https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979>\
**Category:** Development\
**Tags:** bug\
**Created:** [November 1, 2024, 11:08am UTC](https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979 "2024-11-01T11:08:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MMMPPPMMM](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@MMMPPPMMM](https://discourse.slicer.org/u/MMMPPPMMM)\
**Post date:** [November 1, 2024, 11:08am UTC](https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979/1 "2024-11-01T11:08:35Z")

</div>

Hello

It seems to me like a bug that the \*.vp volume rendering file shows up as changed in Save dialog directly after opening an MRML scene?

Find an example here: [Upload Files | Free File Upload and Transfer Up To 10 GB](https://easyupload.io/9mbf6h)

 ![Test_VR_Status](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/c/b/cbf736ffb6e2cdca65731761a81d4db942aece43.jpeg)

Tested with Slicer 5.6.2 r32448 / f10cd8c

Kind regards

---

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [November 1, 2024, 7:35pm UTC](https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979/2 "2024-11-01T19:35:13Z")

</div>

Yes, that’s probably a bug in the code that manages the `ModifiedSinceRead` property of the node. It would be great if someone has time to dig in and fix this. To start it would be good if you could file an issue to track it.

---

<div class="post-metadata">

**Author:** ![MMMPPPMMM](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@MMMPPPMMM](https://discourse.slicer.org/u/MMMPPPMMM)\
**Post date:** [November 4, 2024, 8:52pm UTC](https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979/3 "2024-11-04T20:52:41Z")

</div>

Done

> <https://github.com/Slicer/Slicer/issues/8030>
>
> \## Summary
> The \*.vp volume rendering file shows up as changed in Save dialog di…rectly after opening an MRML scene.
> Probably a bug in the code that manages the ModifiedSinceRead property of the node.
> 
> !\[cbf736ffb6e2cdca65731761a81d4db942aece43\](https://github.com/user-attachments/assets/ffc63ecf-e01c-4d93-a611-cb9076679aab)
> 
> \## Steps to reproduce
> 
> Download the example scene: \[Upload Files | Free File Upload and Transfer Up To 10 GB\](https://easyupload.io/9mbf6h)
> 
> 1. Open the scene
> 2. Open the Save Dialog
> 
> \## Environment
> \- Slicer version: Slicer 5.6.2 r32448 / f10cd8c
> \- Operating system: Windows 11

---

<div class="post-metadata">

**Author:** ![jamesobutler](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/jamesobutler/32/7511_2.png) [@jamesobutler](https://discourse.slicer.org/u/jamesobutler)\
**Post date:** [November 4, 2024, 10:49pm UTC](https://discourse.slicer.org/t/volume-rendering-file-shows-up-as-changed-in-save-dialog-directly-after-opening-an-mrml-scene/39979/4 "2024-11-04T22:49:11Z")

</div>

For reference it appears @lassoan has included a bug fix for this in:

> <https://github.com/Slicer/Slicer/pull/8029>