Enforcer's results, quoted by retrorgb, that put the M30 BT in the 21ms range and place the M30 2.4GHz at 3.6ms feel correct to me. This is something that other tests confirm. Here the 8bitdo M30 BT and 2.4GHz Switch and Mini are claimed to be the same and they are definitely not the same. While you can never make a ms estimate by gut feeling you can tell if a controller is the same or slower than another controller when they are apart far enough. Sadly Porkchop's results go against my own experience with these gamepads. It is a much more difficult to get right field than meets the eye. Unless everyone uses uniformly the same hardware and methodology then the possibility of severe discrepancies will always be there, since it's truly a micro zone.įor sure and I appreciate the effort people put into lag testing. Thus, sorry, but from my experience with all these controllers using 1ms polling on MiSTer Porkchop's numbers do not appear correct at all to me.Ĭommon problem with all these lag tests, not only input ones, which is why I always take them with a pinch of salt. The M30 2.4 Switch and Mini is much faster than the BT, too while according to the spreadsheet it should be virtually identical to the M30 BT (11ms vs 10.8ms). I have both and the M30 BT is definitely slower than the Retrobit.

Question is: Who is right?ĮDIT: The 8bitdo M30 BT is claimed to have 11ms while the Retrobit Saturn 2.4 is claimed to have 16ms. Porkchop's procedure seems pretty solid, thus it should be correct, but that is the case for inputlag.science and others, too. The Retrobit Saturn Wireless feels much more snappy than what the measurements show, but that is speaking from my gut feeling.īut, if you compare Porkchop's values for the M30 2.4GHz (Switch and Mini) that Jorge_ did (10.8ms average lag) to another test (3.6ms average lag). The values on Porkchop's spreadsheet feel kinda off, compared to other tests.

Controller input delay test