This page gives you an overview over the recent API changes.
Versioning Policy
- The major version number names the overall API version. It is incremented on wide-ranged API changes. There is absolutely no downward compatibility guaranteed: The compatibility of the API is usually broken when this version number is incremented.
- The minor version number is incremeted on API changes that might break downward compatibility, but only locally, s.t. only a few tweaks are neccessary - if any - in order to upgrade.
- The patch version number is incremeted on such changes that neither of the two prior rules apply to: Full downward compatibility is guaranteed, thus one should always try to use the most recent patch version.
Change Log
API Version 3.0.1
- Moved
helpers::VolumeGridHelper::DEFAULT_MAX_SEGMENT_BYTESIZE
to helpers::VolumeGridHelperBase::DEFAULT_MAX_SEGMENT_BYTESIZE
.
- Moved
helpers::VolumeGridHelper::nativeResolution
to helpers::VolumeGridHelperBase::nativeResolution
.
- Fixed partitioning bug in helpers::VolumeGridHelper that caused odd texture sizes in some cases.
- Fixed bug in helpers::VolumeGridHelper::createNode that caused wrong locations for tail segments.
- Fixed bug in presets::VolumeRenderingStage that caused crashes when textures had no corresponding samplers, i.e. they were unused.
- presets::VolumeRenderingStage now suppresses artifacts that appear when rendering grids with many segments, e.g. \(8 \times 8 \times 1\) and more.
API Version 3.0.2
API Version 3.1.0
API Version 3.2.0
API Version 3.3.0
API Version 3.3.1
- Fixes bug which may have caused volume data being rendered slightly displaced due to padding (up to one voxel).
API Version 3.3.2
- Fixes a six-year-old bug in presets::VolumeRenderingStage which caused rendering artifacts at specific angles when rendering strongly anistropic volumes. There was a work-around previously implemented which, however, was not 100% reliable, and came at the cost of forcing a sample rate twice as high as specified. Since this work-around has been removed now, the specified sample rate is used (which effectively is twice as low as before). This means that same rates must be doubled to yield the same results as before (note that the effective sample rate will be the same then, meaning that rendering performance will be the same, in terms of both quality and time, but without the artifacts). presets::VolumeRenderingStage::DEFAULT_SAMPLE_RATE has thus been doubled.