Bug Rate Over Distance Multiplier

Hi!

I have an issue where I set:

Code (CSharp):

1. smallHeartsEmissionModule.rateOverDistanceMultiplier = smallHeartsRateOverDistanceMultiplierCollected;
2.  

1. If I set it to 0, it will not show anything, good!
2. If I set it to any number higher than 1, it will work so 2 or 100 spawns correctly
3. BUG: If I set it to anything lower than 1 it will not work. Even setting it to 0.00001f will not work. It seems to spawn as if it's always 1.

NOTE: The rateOverTimeMultiplier works.

Am I missing something?



Thanks!

 

Case #: 1352410

Thanks!

 

So it seems like QA couldn't reproduce it. I don't know when this happened, but it might have happened in beta 5 of 2021.2 or was always happening and I just never noticed?

Now when I change rateOverDistanceMultiplier, it changes the rateOverDistance?

Here is the code:

Code (CSharp):

1. [ExecuteInEditMode]
2. public class NewBehaviourScript : MonoBehaviour
3. {
4.     private ParticleSystem ps;
5.     public float hSliderValue = 1;
6.  
7.     void Start()
8.     {
9.         ps = GetComponent<ParticleSystem>();
10.     }
11.  
12.     void Update()
13.     {
14.         var emission = ps.emission;
15.         emission.rateOverDistanceMultiplier = hSliderValue;
16.  
17.         ps.transform.position = new Vector3(Mathf.Sin(Time.time) * 2.0f, 0.0f, 0.0f);
18.     }
19. }

NOTE: Thanks for moving my post! I now know where to post particle system issues

Thanks!

 

Oh okay! I guess I was thinking of the multiplier as taking whatever you have in that field in whatever mode and just multiplying it by the multiplier instead of having to change the actual values. That way you could say 0.5f or 2 and get twice or half the speed.

If I wanted to do that (just use the multiplier and not change the actual rate over distance), I need to change them into curves and then use the multiplier.

Because yeah, when I have between two constants, it will change the right most constant. Not what I expected but I am glad I know now and hopefully this will help others!



Thanks!

 

It really would be great if we had an overall scalar modifier like MousePods was expecting, which carried through the emission rates of ALL children. For example, a chunk of code could accept any particlesystem prefab, and adjust a master "spigot" to ramp it up and down without really knowing much about the structure of the prefab itself. Now I have to construct a new dictionary every time the car tire hits a different material with a different prefab, just so I can memorize all of the original emission rates and apply them back as traction allows.