Release notes

What’s new #

Content Development #

Data Binding Performance Tracing

Starting from this release, the performance of each data binding attribute can be inspected in the “Performance” tab of the Chrome Inspector.

For more details, see the documentation for Enhanced Performance Tracing

Core #

Simple Filters

We’ve enhanced how CSS filters are processed in Prysm. Previously, each filter (like brightness, sepia, etc.) would generate its own texture, which could quickly add up in complex DOM trees—especially when stacking multiple filters.

With this update, filters without any opacity effects (like transparency or alpha changes) are now intelligently merged into a single color matrix operation. This reduces texture creation, saves memory, and significantly improves rendering performance-especially in deeply nested or filter-heavy documents.

Note that the following filters would still create a texture:

• blur
• coh-axis-blur
• drop-shadow

Rendering #

Global GPU Resources Pool

With this version of Prysm, several of the internal rendering caches are getting merged into a single one - the global GPU resources pool. Previously, the Prysm’s rendering library had multiple caches that had to be adjusted and fine-tuned individually. Now there is a single such cache that can be controlled with a single target GPU memory number. For more information, see the “Global GPU Resources Pool” in the documentation on Internal Caches.

Releasing of the user background and global backdrop mask textures

Previously, Prysm was not releasing the Global Backdrop Filter Mask and the User Background textures properly upon the destruction of the corresponding. cohtml::ViewRenderer of a given cohtml::View. Now, when calling cohtml::ViewRenderer::Destroy, both of those textures will be destroyed through a renoir::BRC_DestroyTexture command in the rendering backend. For more information on the specifics, see the corresponding documentation for both of the features:

• Backdrop Filter
• Global Backdrop Filter

Removed support for explicit resource state transitions generated by the rendering library

We have deprecated the renoir::RendererCaps::SupportsResourcesStateTransitions field and the BRC_TransitionTextureState, BC_TransitionTextureState and BC_TransitionDSTextureState rendering backend commands as a result of dropping the support for explicit resource state transitions generated by Renoir. These state transitions will continue to be handled entirely in the backends.

Unreal Engine #

New delegates for modifying Library, System and View options

The Prysm integration for Unreal Engine now provides new ModifyLibraryParams, ModifySystemSettings, and ModifyViewSettings delegates for modifying all Prysm Library, System and View options.

ModifyLibraryParams, ModifySystemSettings, and ModifyViewSettings delegates are located inside ICohtmlPlugin.h, and are called right before creating a Prysm Library, System and View, passing a pointer to the already populated settings.

Migration guide #

Changes to binding of 64-bit integer values

Starting from this release, all 64-bit integer values are bound to JavaScript as BigInt. In previous versions Number was used if the value fits in Number.MAX_SAFE_INTEGER, otherwise BigInt. If your code counts on the old behavior, you can restore it by changing the View setting: Int64BindingMode to Int64BindingModeType::Mixed, however this is not recommended and the option will be removed in future releases.

Changelog #

Version 2.0.0.0 #