-
-
Notifications
You must be signed in to change notification settings - Fork 18.9k
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
3D Particles Leads to FPS Drop #29973
Comments
Duplicate of #13954 and #17263 This issue is caused by the shader having to compile on the first frame it is shown. Here is a great youtube video explaining how to work around the problem. https://www.youtube.com/watch?v=Cg4ZT6X0ghs |
I tried without adding any Shader Material and still facing same problem. |
There is a spatial material on the object and a particles material for the particles. Both need to compile. In order to avoid the hiccup, you need to follow the steps in the video. i.e. Have the particles appear in the scene for a frame before the scene is loaded so that the shader compiles. |
I have a mian Scene that contains Instances Particles, I don't understand how to implement what you are suggesting? |
I switched to GLES2 and Converted Particles to CPUParticles and there no more glitches. |
I'm having this issue and been struggling to solve it for weeks already, and I applied the trick and I got it finally solved! |
Godot version: 3.1.2
OS/device including version: Manjaro Linux and Android Oreo
Issue description: When I Emmit Partcles for the First Time FPS Drops and game gliches. On Second time there is no issue. I createad a Particles Scene and then created instance of it in main scene using GDScript. I also tried it with Android and experienced the same problem.
Screenshots
FPS at Start
FPS at First Particle Emmition
Steps to reproduce: Open and run project provided by me and then and then hit "Enter" you will see FPS Dropping and Glitch. FPS count is at the bottum left of the Scene.
Minimal reproduction project:
ParticlesFPSDrop.zip
The text was updated successfully, but these errors were encountered: