# When importing data on 3dslicer version 5.0, the data displayed is different from the original data
**URL:** https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702
**Category:** Support
**Tags:** segmentation, dicom
**Created:** [December 13, 2022, 7:04am UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702 "2022-12-13T07:04:39Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@FUFU](https://discourse.slicer.org/u/FUFU)
#### Post date: [December 13, 2022, 7:04am UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/1 "2022-12-13T07:04:39Z")
For example, when I imported dicom data on 3dslicer on version 4.8, it would show the mark traces of layers 162 to 167.
But if I run the same dicom data on version 5.0, it only shows traces of data from layers 163 to 167.That means the mark 162 is not visible
Another problem also occurred: When running on version 5.0, the 156th layer name appeared twice and the 155th layer name was omitted, which would not have occurred with the same dicom data running on version 4.8.The following two figures show the problems above version 5.0
This page count problem came up a few times, but I checked that the renaming in my folder was OK
Although this problem is sometimes small, but the problem is a few pages at a time, it is still affected.Thank you all.
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [December 13, 2022, 1:15pm UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/2 "2022-12-13T13:15:27Z")
I’m not sure what you mean by ‘mark traces’. Can you clarify? It would be best if you could share a deidentified example to get the best advice.
---
### Author:  [@FUFU](https://discourse.slicer.org/u/FUFU)
#### Post date: [December 14, 2022, 1:15am UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/3 "2022-12-14T01:15:03Z")
This is the doodle trace of the segmenteditor paint function.
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [December 14, 2022, 6:49am UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/4 "2022-12-14T06:49:54Z")
Have you loaded DICOM data using the DICOM module?
---
### Author:  [@FUFU](https://discourse.slicer.org/u/FUFU)
#### Post date: [December 15, 2022, 7:06am UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/5 "2022-12-15T07:06:51Z")
yes I use DICOM module
---
### Author:  [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [December 15, 2022, 2:08pm UTC](https://discourse.slicer.org/t/when-importing-data-on-3dslicer-version-5-0-the-data-displayed-is-different-from-the-original-data/26702/6 "2022-12-15T14:08:01Z")
We are not aware of any issues regarding loading of clinical CT images. If there is any difference compared to previous versions, then most likely Slicer-5.2.1 provides the correct result.
> [@FUFU](#):
>
> Another problem also occurred: When running on version 5.0, the 156th layer name appeared twice and the 155th layer name was omitted,
This is the correct behavior when slice spacing is varying throughought the image (either because it was acquired with varying slice spacing to save dose; or because a few files were corrupted or misplaced).
Have you received any message about varying slice spacing when you loaded the image? Is there a `... acquisition transform` in the scene after you loaded the image?