News
Scenome 23.6 — 2/12/2023
Release details are described below.
- Scenome Platform. Performance improvements to readback system. Previously, some of the min/max searches could be a little slow for very large readbacks. This system has been streamlined and should be more performant during readback creation and editing.
- Scenome Platform. Upgrade to the readback property editing system. This upgrade was made to <TextureReadbackImageProcessor>, which is used to readback directly into a <Texture> object, as well as to all <DataCapture> classes such as <Float32ArrayDataCaptureReadTexture>, <Float32VectorArrayDataCaptureReadTexture>, and all similar. Previously, the property sheet start x/y and width x/y values were not constrained. However this sometimes made it difficult to configure readbacks. Now whenever you set start x/y, the width x/y will be automatically clamped to the maximum possible value. If the value is too large, you'll see the smaller value appear in the property sheet immediately.
- Scenome Platform. General upgrades to the readback system for reading back array textures, 3D textures, cube maps, and cubemap arrays. Some of the terminology in the property sheet has been updated to make the relationship between a property and the <Texture> element clearer. It's also easier to choose which array slice, cubemap face, or cubemap array layer-face you wish to readback.
- Documentation. Minor improvements and clarifications to the Raspberry Pi® exercises. New data interface documentation.
- Exporters. Updated <GpuTexture> resource management. It is now possible to use <GpuRender> to determine whether or not a <GpuTexture> object is resident on the GPU. The <GpuTexture> object GUID is used to uniquely identify the resource. Note that you can upload multiple copies of the same texture to the GPU, but you cannot do so via a single <GpuTexture> object. See also: changes to <GpuRender>.