Difference between revisions of "Documentation/3.6/ReleaseNotes"
From Slicer Wiki
Sam.horvath (talk | contribs) Tag: 2017 source edit |
|||
| (9 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| + | <noinclude>{{documentation/versioncheck}}</noinclude> | ||
| + | {{documentation/versionlist}} | ||
* [[Slicer3:3.6Release|3.6 Release schedule]] | * [[Slicer3:3.6Release|3.6 Release schedule]] | ||
== Known Issues == | == Known Issues == | ||
| − | * Multiple 3D View mode is only partially supported in version 3.6 (see [[Modules:MainApplicationGUI-Documentation-3.6#Notes_about_Multiple_3D_Views|this page]]. A more complete implementation is on the list for [[Slicer4]]. | + | * Multiple 3D View mode is only partially supported in version 3.6 (see [[Modules:MainApplicationGUI-Documentation-3.6#Notes_about_Multiple_3D_Views|this page]]). A more complete implementation is on the list for [[Slicer4]]. |
| − | * | + | * Due to a bug in the earlier implementation of hierarchical transform trees, multi-level nested transforms loaded from scenes created in version 3.4 won't behave as expected. Reversing the order of the transforms is required. |
| + | * Due to limitations in ITK's gdcm DICOM handling, Slicer is unable to output DICOM format data. We recommend saving new datasets in [http://teem.sourceforge.net/nrrd/format.html NRRD format] using the extension '''.nrrd''' from Slicer's Save Interface. Note that this currently impacts Slicer's remote I/O as well; multi-file DICOM volumes uploaded to a remote repository using the web services infrastructure will be collapsed into in a single DICOM file upon upload; however DICOM header information will be preserved. This behavior will be addressed in a software patch subsequent to the 3.6 release. | ||
| + | * The new [[Slicer3:GPURayCaster|GPU Ray Cast Renderer]] randomly produces transparent rendering (10% of the time) when the camera is inside the volume. It works fine when the camera is outside the volume. | ||
| + | * Restoring a scene that uses CompareView may result in the Crosshair not being initially displayed in all the CompareView viewers. A change in slice location may display the Crosshair correctly. | ||
== Platform Specific Notes == | == Platform Specific Notes == | ||
| Line 11: | Line 16: | ||
=== Mac === | === Mac === | ||
| + | * The new [[Slicer3:GPURayCaster|GPU Ray Cast Renderer]] crashes on MAC OS. This is due to Apple OpenGL drivers (see the [[http://www.vtk.org/Bug/view.php?id=10716 bug report]]) | ||
| + | ** Note: It's an OS limitation not an hardware limitation: The renderer will work fine on a MAC if Slicer runs under a virtual machines with a Windows or Linux OS. | ||
=== Linux === | === Linux === | ||
Latest revision as of 21:13, 19 January 2022
Home < Documentation < 3.6 < ReleaseNotes
|
For the latest Slicer documentation, visit the read-the-docs. |
Nightly 4.10 4.8 4.6 4.5 4.4 4.3 4.2 4.1 4.0 3.6 3.5 3.4 3.2 ALL VERSIONS
Known Issues
- Multiple 3D View mode is only partially supported in version 3.6 (see this page). A more complete implementation is on the list for Slicer4.
- Due to a bug in the earlier implementation of hierarchical transform trees, multi-level nested transforms loaded from scenes created in version 3.4 won't behave as expected. Reversing the order of the transforms is required.
- Due to limitations in ITK's gdcm DICOM handling, Slicer is unable to output DICOM format data. We recommend saving new datasets in NRRD format using the extension .nrrd from Slicer's Save Interface. Note that this currently impacts Slicer's remote I/O as well; multi-file DICOM volumes uploaded to a remote repository using the web services infrastructure will be collapsed into in a single DICOM file upon upload; however DICOM header information will be preserved. This behavior will be addressed in a software patch subsequent to the 3.6 release.
- The new GPU Ray Cast Renderer randomly produces transparent rendering (10% of the time) when the camera is inside the volume. It works fine when the camera is outside the volume.
- Restoring a scene that uses CompareView may result in the Crosshair not being initially displayed in all the CompareView viewers. A change in slice location may display the Crosshair correctly.
Platform Specific Notes
Windows
Mac
- The new GPU Ray Cast Renderer crashes on MAC OS. This is due to Apple OpenGL drivers (see the [bug report])
- Note: It's an OS limitation not an hardware limitation: The renderer will work fine on a MAC if Slicer runs under a virtual machines with a Windows or Linux OS.
