Skip to content

v4.4.8

Pre-release
Pre-release
Compare
Choose a tag to compare
@kevingpqi123 kevingpqi123 released this 20 Sep 06:13
· 2 commits to alpha/4.4 since this release

主要修改内容:
(1)鸿蒙版本完善:增加 PAGImageView,支持网络文件加载,完善鸿蒙硬件、软件解码

已知问题:

  • 对于 PAGImageView, 由于鸿蒙系统问题, 直接使用NativeImage的内存进行 lz4 编解码会产生性能问题,从而导致画面卡顿严重,目前暂时使用 bitmap 的内存,相对于其他平台性能会稍差一些;由于鸿蒙版本无法直接设置 NativeImage 在 NativeWindow 中的 Matrix,相对于其它平台,在缓存后,PAGImageView 在鸿蒙系统中目前无法完全脱离 OpenGL 渲染环境
  • 由于鸿蒙系统的软硬解存在设计缺陷,如只支持异步解码方式、解码后数据需要 copy 否则会出现画面错乱,因此在内存占用和性能方面会弱于其它平台, 这会导致含有 BMP 预合成的素材渲染会有一定的性能问题

(2)iOS 平台移除 PAGDecoder 和 PAGImageView 对于部分方法的入参限制
(3)修改部分 pag 文件渲染异常问题

Main revisions:
(1) Improvements for HarmonyOS version: adding PAGImageView, supporting network file loading, enhancing HarmonyOS hardware and software decoding.

Known issues:

  • For PAGImageView, due to issues with the HarmonyOS system, directly using NativeImage's memory for lz4 encoding/decoding will result in performance problems, causing severe stuttering. Currently, bitmap memory is temporarily used, which may perform slightly less than other platforms. Additionally, due to limitations in the HarmonyOS version, it is currently impossible to directly set the Matrix of NativeImage in NativeWindow. After caching, PAGImageView in the HarmonyOS system cannot completely detach from the OpenGL rendering environment.
  • Due to design flaws in the software and hardware decoding of the HarmonyOS system, such as only supporting asynchronous decoding and requiring data copy after decoding to avoid image distortion, the memory usage and performance will be weaker than other platforms. This can lead to performance issues when rendering materials with BMP pre-composition.

(2) Removing input parameter restrictions for certain methods in PAGDecoder and PAGImageView on the iOS platform.
(3) Fixing rendering anomalies in some pag files.