10.1.5

Fixes

Fixes clip planes on specific drivers (rendering issue on certain Android devices).

Includes other small fixes.

---

• fix: Make bad driver detection more specific for clip planes (#9714) 3ab91e096d ca52182
• fix(gl): Fix a memory leak in TextureGLImpl (#9663) 9e3db1f98f 10ae237
• fix: Find a workaround to compiler bug on Pixel 3 (#9729) 5ed9258760 55a921e

10.1.4

Fixes

Fixes the Rive Renderer (default on versions 10+) on certain ARM Mali devices. This would manifest as rainbow colored squares covering the screen. This was due to uninitialized pixel local storage, due to scant details in the specification.

Improvements

Includes the beginnings of the new threading model (not currently being used) which will ultimately replace the existing JNIRenderer setup.

---

• fix(gl): Fix uninitialized pixel local storage (#9638) fac712cc41 #279
• Fix Artboard List crash when layout siblings come before it (#9633) 18c9402bc3 5217843
• feat: First draft of a CommandQueue (#9620) 18dc7c390b 9e72a89

10.1.3

Fixes

Includes two crash fixes, one for null image textures when rendering and another regarding passing pointers to Yoga during layout.

---

• fix(renderer): Gracefully handle null image textures (#9600) 7dd9f91b4a 9ad165a
• Component list refactor pt1 (#9595) 126c53a0f5 3d2bc57

10.1.2

Fixes

Allows for Rive files with no state machine to advance the artboard.

• fix(playback): LinearAnimationInstances advance the Artboard when no StateMachineInstance is playing 966a68a08f 95f803a

10.1.1

Fixes

Android now properly integrates with the C++ runtime font fallback API, allowing for iterative font fallback searching. This means that fallback fonts will work as expected when missing glyphs need to pull from more than one fallback font.

Also includes ongoing work for Vulkan.

---

• feat(fonts): implement indexed font fallback strategy & getFallbackFonts() API d9437f7601 31f2d89
• feat(vulkan): Support all render target formats (#9527) 1014fd7fa4 3745707
• fix(vulkan): Fix input attachmens on AMD (#9513) e5dc0b989c 6ab21ab
• refactor(vulkan): Move shaders to a different cpp file d379a33
• feat(vulkan): Implement coalesced resolve 7efdfa1
• fix: update data binds when events from children are notified 7c8288f
• feat(vulkan): Use VK_IMAGE_LAYOUT_COLOR_ATTACHMENT_OPTIMAL c36c95c
• refactor(vulkan): Make RenderTargetVulkan more generic b30bc02
• fix: 32-bit Vulkan builds on Android 0c800b7
• refactor: Work out low level barriers at the RenderContext level 7284c55

10.1.0

Improvements

This release adds data binding, a significant new way of interacting with Rive files. For more information, see our Overview and Runtime docs.

• Android Data Binding 7a16a79

10.0.5

Fixes

• Fixed a race condition crash if the Rive file was set while drawing 4a64b95
• Fixed an OpenGL buffer race condition b001b21
• Textures now use pre-multiplied alpha, which may fix dark edges around alpha textures ad7c295

10.0.4

Improvements

This release removes the dependency on Kotlin Reflect by using Java reflection APIs. This reduces compressed DEX size by roughly 400kb. Additionally, the Kotlin version used is now 1.9, meaning if your project also uses 1.x, you should also see reduced DEX sizes.

Fixes

This release also numerical stability of rendering.

---

• feat(Android): Remove Kotlin Reflect and downgrade to Kotlin 1.9 a0b439f
• Revisit numeric stability for colordodge and colorburn 07ecc83
• Improve numeric stability of blend modes c247ac6

10.0.3

Fixes

Incorporating minor C++ runtime rendering fixes.

• More cleanups for Vulkan bootstrapping 54f8301
• Reduce the # of arguments required for Vulkan context creation 95b2979
• More Build Options 69f120c
• define rive::math::pi to be the same as m_pi b43936c
• Split up subpass from resource allocation for draw. Move draw limit check to before resource allocation occurs (and can fail) d97fd2d
• Vulkan - Atlas texture barrier fix 731ed90

10.0.2

Fixes

• Remove printmapping ProGuard rule 71245a9

Migration Guide

The removed ProGuard rule means that apps consuming the Rive library will no longer be forced to output their source map to out.map. If users would like to continue generating this mapping, they will need to re-add the following line to their progruard-rules.pro:

-printmapping <Your Map File Name>.map