How expensive is setting parameters that haven't changed?

Unity
1

I habitually write code to remember the current value of FMOD parameters and only set them if they change. Both properties that hardly ever change (e.g.IsPlayerDead) and those that typically change every frame (e.g.RPMif the vehicle is not idle).

How important is that? Does FMOD already do it (FMOD 2.03)? It’s not a big deal but it’s still code I need to write and less code is good. I could imagine it affecting what gets logged in the profiler.

2

Speaking in generalities, it’s less computationally expensive to check whether a parameter has changed than to constantly set it to the same value. However, the computation cost of either option is ultimately negligible in almost all situations, so I’d recommend going with whatever works best for your workflow.