-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
Particle turbulence behaves very differently in 4.1.dev3 #77491
Comments
I was able to get the turbulent look in both, but I had to change the scale for some reason. I don't know why this difference is showing up. No changes to the scale value curve were merged since 4.0, and the same is the case for how it's effectively used. |
Edit: Disregard my original comment below, I was looking at the wrong image when I copied your settings. I was able to produce the same results as you by changing the noise scale as well - which I agree is an odd change. The scale characteristics are bizzare - there's basically no effect at either end of the value range - it needs to be right around 3.0 to see any turbulence, and even then, small changes centered around that value seem to result in wildly different visual behaviour.
|
^ found the solution! |
Glad to hear it! Do you know if this change would also resolve #74541? It may be worth taking a look at while you're in the same headspace having just solved this one. |
Godot version
4.1.dev3.official [a67d37f]
System information
Windows 11 [Vulkan]
Issue description
The work performed in #77154 drastically changed the visual characteristics of particle turbulence. I am no longer able to get the same "turbulent" behaviour that existed before these changes - no matter which turbulence settings I change. Please let me know if there's something I'm missing about the new implementation that would give this result.
Steps to reproduce
To reproduce this is fairly simple:
Minimal reproduction project
No sample project provided, as the reproduction is quite simple to replicate.
The text was updated successfully, but these errors were encountered: