Hey! So I'm not sure if this is duplicate or not. But I saw something similar in older threads. So when processing input in fixedUpdates you can sometimes get two updates after another, which creates empty inputs fixedFrames. I saw some stuff about framerate independent inputs, anyone if this is something that is toggable as of yet, or a feature to come?
Yup, that'd be expected. It'll track MonoBehaviour.FixedUpdates. Should be fixed in the next package. Or more precisely, in the next package, timeslicing of events in fixed updates should work as expected, i.e. events should be processed in fixed updates in sync with how their timestamps correspond to update timeslices.