VolumeViz
Interactivity improved in slice rendering
In previous versions of Open Inventor, many hangs could be observed when interacting with an ortho slice or an oblique slice with large volume data (i.e. at least several gigabytes). Any change that needed to update a large part of the slice to render potentially led to hangs. These use cases provide a non-exhaustive list of circumstances where hangs could easily occur:
If the position and orientation of the camera is drastically change in a 3D volume, an ortho slice might need a full update of its textures.
When an ortho slice is used to render a very large 2D dataset, the camera displays only a small detail of the 2D image, then translates to another detail far from the current one.
If the slice number of an ortho slice is changed to a new position where many textures must be updated.
If a resource parameter is changed, such as an increase of the SoLDMResourceParameters::maxMainMemory or SoLDMResourceParameters::maxTexMemory.
Such use cases have been improved, creating a much better interactivity and user experience.
In this context, the default value of SoLDMResourceParameters::tex2LoadRate has been decreased from 640 to 100. The higher the tex2LoadRate, the higher the probability of observing hangs. Reducing the value of text2LoadRate reduces the risk of a hang when using tiles with large dimensions.
Open Inventor 2024.1.2
- .NET
- #OIV-4968 In Open Inventor .NET, multiple useless debug dlls are provided in the release sub folder \assemblies\arch-xxx-Release
- Core
- #OIV-4665 Multiple and subsequent allocations and deallocations of Open Inventor shapes can lead to a crash.
#OIV-5123 The time to first render a scene graph that contains a large number of SoTransformSeparator was very long. It is now reduced, for instance the time to first render a scene of 40000 SoText2 under 40000 SoTransformSeparator is divided by 25. – CAS-45100
#OIV-5144 The FPS was sometimes very low with Visual Studio in debug mode. Significant improvements are now possible with Visual Studio 2022.
#OIV-5147 Some shapes may be invisible when a specific number of shapes is added to the scene graph. – CAS-67447
#OIV-5182 Lazy CPU memory deallocation when parts of the scene graph become unused. Even if the memory is deallocated late, that looks similar to a memory leak on very large scene graphs. Now the memory is deallocated immediately
- Doc
- #OIV-5125 Some images in the reference manual were not readable correctly if you use dark mode on your web browser.
- RemoteViz
- #OIV-4885 When rendering using RemoteViz, long messages sent by the client are not received by the server. – CAS-44935
#OIV-5195 When rendering using RemoteViz, long messages sent by the client are not received by the server.
- Text3
- #OIV-5128 Significant hangs occurred with scene graphs containing a few hundred of SoText3 and after resizing the render area
- Transparency
- #OIV-4894 The rendering of a scene graph containing mostly opaque shapes was significantly slow if using the SORTED_OBJECT transparency type.
#OIV-5003 Incorrect display when rendering a scene graph containing semi-transparent Open Inventor shapes mixed with OpenGL custom nodes. – CAS-45218
#OIV-5199 The rendering of RGBA SoVolumeData objets are different from legacy Open Inventor 9.
- Viewer
- #OIV-5106 SoTransformation nodes used in multiple render areas are not always rightly taken into account during the rendering. That leads to incorrect shape renderings and weird camera clipping plane side effects. This can be easily observed with any SoDragger or SoTransformManip instance shared by multiple viewers.
- VolumeViz
- #OIV-5141 The node SoVolumeRender might be render incorrectly and undetermined when the tile size selected was too large for the graphic board capability.