TimeWarp trigger cancels input

[LeTim42]

If pressed/released at the same moment as a timewarp trigger changes the time speed, this input is not registered. I found this bug when I played Eon in practice (it uses some timewarp triggers to fix music sync)
The way to reproduce this bug is to place a timewarp trigger on the fourth block to the right of the start of the level with any value other than 1.00 and press/release at this trigger

UPD: A level showing this bug clearly: 125337244

[LeTim42]

I just found that if you leave only the first branch in getCurrentTimestamp from windows.cpp, the bug disappears:

if (linuxNative) {
	// used instead of QPC to make it possible to convert between Linux and Windows timestamps
	GetSystemTimePreciseAsFileTime((FILETIME*)&t); // this works fine for me
} else {
	QueryPerformanceCounter(&t); // this causes the bug
}

UPD: It's a bad fix actually, it messes up the timewarp trigger effect

[LeTim42]

A few more things I found

• If you remove the line

stepQueue = {}; // shouldnt be necessary, but just in case

in buildStepQueue then all the inputs in my test level will be delayed a lot

• If you add the line

if (stepCount != 4) return;

at the beginning of buildStepQueue then the test level works fine for me (and the timewarp trigger works as expected too). Not sure if this fix will work for everyone with any settings