#Rewired unity forums full

However, in the case that a button was just pressed before pause and held during unpause, it would trick digital axis simulation into reporting the full value because of unscaled delta time not taking Time.timeScale = 0 into account in FixedUpdate.

#Rewired unity forums code

In your case, it would not after adding code to block the values from being queued while paused, because if the underlying button were not triggering the Action value to be non-zero on this frame, digital axis simulation wouldn't do anything. This section of code may or may not need yet more special case FixedUpdate pause code to handle. So as far as digital axis simulation is concerned, 20 seconds just passed in the last FixedUpdate frame while it was paused, which results in the digital axis sensitivity applying a gigantic delta time and yielding the full value of 1 instead of slowly ramping it up. This unscaled delta time is calculated using a real-time timer which is, again, not affected by setting Time.timeScale to 0. This does not use Unity's Time.unscaledTime which doesn't even exist in Unity 4.3, the oldest version of Unity Rewired supports. When calculating the digital axis value when the underlying button is True, sensitivity is multiplied by Rewired's own unscaled delta time calculation. However, I've dug into it and found the exact explanation and why disabling the Controller Maps doesn't help: I don't know if this is something you are interested in looking into or not, of course.Īgain, thank you for the outstanding support.Įdit: I forgot to mention that, even now, with my solution of delaying turning on the map for one extra frame, what happens is that when I turn on the map, the value immediately jumps to 0 (regardless of buttons pressed during the pause and the previous state of the input).Ĭlick to expand.IMO, it's basically a wasted effort to me to go in and determine exactly why every aspect of this is happening because all it really amounts to is investigating artifacts bubbling up as a result of the aforementioned button queuing during Time.timeScale = 0 issue, which is the root cause. However, if doing so together with setting Time.timescale = 0 as described above, these spikes happen. I tested a bit more and this discontinuity in the digital axis simulation is definitely not caused merely by turning a map on and then off. However, on the current version, this causes an immediate spike in the returned value, which is much more noticeable in gameplay. This contribution was so minor it was barely noticeable when playing. In fact, I think this is the only difference in behavior between the previous version of Rewired I was using (1.1.10.0) and the current version, now that I think about it and check an older build the 'returning true' for one frame after the unpause always worked like so, but previously it merely acted as a contribution to the digital axis and worked like we expect it to, making the value approach 1, -1 or 0. However, when unpausing, the value returned always immediately jumped to 1, -1 or 0, depending on the buttons pressed during the pause. In the example code I was using to test it, for example, I was enabling/disabling all maps during the pause, which should, I expect, unequivocally disable the action. It was simply the easiest solution to make it 'play nice' with some other bits of code in the game, but it might be time to revisit that decision and make a more proper solution. I know all about the pitfalls of getting input in FixedUpdate I had my own (dumb) reasons for doing it.