Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.x] Physics Interpolation - Fix 3D CPUParticle restart bug #92897

Closed

Conversation

lawnjelly
Copy link
Member

@lawnjelly lawnjelly commented Jun 8, 2024

Particles that were being emitted were having their data copied to previous particle data too early, missing some transform changes that could result in graphical anomalies in some situations.

Before

2024-06-08.11-51-33.mp4

After

2024-06-08.11-49-57.mp4

Notes

  • Fixes emitted particles being overly large for a frame in 3D platformer demo.
  • In retrospect this bug is obvious, was a no brainer to fix.

Particles that were being emitted were having their data copied to previous particle data too early, missing some transform changes that could result in graphical anomalies in some situations.
@lawnjelly lawnjelly added this to the 3.6 milestone Jun 8, 2024
@lawnjelly lawnjelly requested a review from a team as a code owner June 8, 2024 10:48
Copy link
Member

@Calinou Calinou left a comment

Choose a reason for hiding this comment

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

Tested locally, this seems to resolve the issue partially with particle interpolation. I still notice the particles teleporting on spawn in the Platformer 3D demo if I re-enable physics interpolation on the bullet scene's particles:

3d_interpolation.mp4

The particle scale wobbling is fixed now still.

Testing project: platformer.zip

@lawnjelly
Copy link
Member Author

lawnjelly commented Jun 9, 2024

Tested locally, this seems to resolve the issue partially with particle interpolation. I still notice the particles teleporting on spawn in the Platformer 3D demo if I re-enable physics interpolation on the bullet scene's particles:

That will (most likely) be a different issue (probably the lack of Node auto-restarts, rather than individual particle restarts). The artifact in your video doesn't actually appear on my 60hz monitor (even at 20tps) but it is likely it is lack of node auto-restart, possibly the Bullet/Sphere mesh instance rather than the particle system (you could also try hiding this to confirm).

I can't say 100% from my side as I can't reproduce, but it seems likely unless it is being introduced by this fix.

If you want to test that out try #92784 , which has this fix applied as part of it.

But really wanted this independently reviewed so we can get approved and merged asap (for 3.6) as it is separable, and doesn't change anything fundamental.

I'm thinking actually given the amount of testing that is finally happening, it might be worth still trying #92784 for 3.6, as these are all bug fixes rather than new features.

@lawnjelly
Copy link
Member Author

Already merged as part of #92784.

@lawnjelly lawnjelly closed this Jun 19, 2024
@AThousandShips AThousandShips removed this from the 3.6 milestone Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants