8000
Skip to content

fix(particle): handle floating-point precision in burst triggers - #19204

Open
ganjuwei wants to merge 1 commit into
cocos:v3.8.9from
ganjuwei:fix/particle-burst-float-precision
Open

fix(particle): handle floating-point precision in burst triggers#19204
ganjuwei wants to merge 1 commit into
cocos:v3.8.9from
ganjuwei:fix/particle-burst-float-precision

Conversation

@ganjuwei
@ganjuwei ganjuwei commented Aug 6, 2026
Copy link
Copy Markdown

Particle Burst determines whether the current frame crosses a trigger point using floating-point time. Account for precision errors during the comparison.

Reference: https://forum.cocos.org/t/topic/176928

Re: #

Changelog


Continuous Integration

This pull request:

  • needs automatic test cases check.

    Manual trigger with @cocos-robot run test cases afterward.

  • does not change any runtime related code or build configuration

    If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.


Compatibility Check

This pull request:

  • changes public API, and have ensured backward compatibility with deprecated features.
  • affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
  • affects file structure of the build package or build configuration which requires user project upgrade.
  • introduces breaking changes, please list all changes, affected features and the scope of violation.

Particle Burst determines whether the current frame crosses a trigger point using floating-point time. Account for precision errors during the comparison.

Reference: https://forum.cocos.org/t/topic/176928
@greptile-apps greptile-apps Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your trial has ended. Reactivate Greptile to resume code reviews.

@github-actions
github-actions Bot commented Aug 6, 2026
Copy link
Copy Markdown

Code Size Check Report

Wechat (WASM) Before After Diff
2D Empty (legacy pipeline) 1009838 bytes 1009838 bytes ✅ 0 bytes
2D All (legacy pipeline) 2675490 bytes 2675490 bytes ✅ 0 bytes
2D All (new pipeline) 2767226 bytes 2767226 bytes ✅ 0 bytes
(2D + 3D) All 10024224 bytes 10024227 bytes ⚠️ +3 bytes
Web (WASM + ASMJS) Before After Diff
(2D + 3D) All 16843286 bytes 16843289 bytes ⚠️ +3 bytes

Interface Check Report

This pull request does not change any public interfaces !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0