Unity 2023.1 overwrites custom Fixed Timestep silently

If you had a custom Fixed Timestep prior to 2023, upgrading the engine will reset it back to the default value of 0.02. Well, I guess it doesn’t exactly reset it; your float value simply can’t be parsed anymore, so the engine defaults to using the standard value.

I used the term “silently” because this change isn’t reflected in the source control, which can lead to spending a lot of time searching for the cause of FPS drops or sudden clunkiness in physics (depending on how you utilize the fixed time).

Thank you for this.

I found that any changes from the default Audio Latency setting is being changed back to the default during the upgrades to 2022.LTS and the 2023 alphas, too.