PS3 Vs. X360 - Why do PS3 FGs have input lag compared to X360 versions?

Oh... I have no idea. Old PS3 problems? Many people say that slowdowns (obvious ones like UMvC3) only happen on the fat PS3's. How true this is? No idea.

 

Round 2!

/thread

 

Old topic I know, but I've been doing lots of work on input lag recently. I have created my own testing system, which I have been using on lots of different games. Details are here http://forums.shoryuken.com/discuss...es-controllers-etc-20-4-pc-games-added#latest

Got around to testing VF today.

https://twitter.com/noodalls/status/858884742300565506

Basically, VF5 on PS3 (60.4ms), VF5FS on PS3 (60.3ms) and VF5FS on X360 (64.4ms) are almost exactly the same speed. VF5FS on X1 emulation (78.9ms) is about a frame slower. I don't have PS-Now here so no way to test that. Will probably get Yakuza 6 at some point if it's cheap enough in Japan.

 

The tests tend to vary by about 1ms between takes. The 4ms is a bit more than that. My theory (unproven) is that the X360 polls the controller less frequently than the PS3, so that even though the games are running at the same speed, the response to the controller will be a bit more spread out and on average a touch slower.

 

I used the Brook UFB across the three different consoles. I haven't found a faster PCB than this yet.

Edit - typo

 

Thanks for testing this, I had been meaning to do a formal test for a while but never got around to it.

 

I do commands every 30F to try to avoid overlapping commands. The move I used was Pai's standing . I almost got caught with the change in speed from VF5 to VF5FS (i10 to i11).

The numbers down the side tell you how late or early in the frame when the button is pressed. So when the button is pressed with 16.66ms left (i.e. right at the beginning of the frame) it will take 3F+16.66ms to occur (eight times). When the button is pressed at the half way point (8.66ms elapsed, 8ms remaining) 90% of the time it will take a further 3F+8ms (58ms) to respond and 10% of the time it will take (66.6 + 8) 74.8ms to respond. When the button is pressed in the final ms of the frame, it will always (10/10) take 1ms+4F = 67.6ms to respond.

 

https://twitter.com/noodalls/status/858884742300565506

So,you are correct that Nil refers to a dropped input. For something like X360 VF5FS where only a single dropped input has occurred, I don't think this is anything to worry about. Further, it appears around the time of the change from 3F to 4F, suggesting that the command has fallen in between the two input windows.

The way I send inputs its quite specific, lasting for exactly a frame. Given that the position at which inputs are read is not exactly the same each time, what has likely happened is that the input has come just a bit too late for the 3F window, but also ended a bit too early for the 4F window, hence it misses both. Realistically, if I held the inputs for longer than a frame, it probably would have just registered as a 4F input.

It's worth mentioning, I don't include the missed commands in the calculation of the averages, so games/controllers that drop a lot of commands are probably calculated to be a bit faster than they actually are.

Something like this might make it a bit clearer.

https://twitter.com/noodalls/status/818239281122529281




Now, if you look at the Zero delay controller for PS3.

https://twitter.com/noodalls/status/845863324478717952

Missed commands all over the place, 23/96 commands missed. This is definitely a problem. Interestingly, this controller had never been tested for input lag before, as lacking common ground makes it hard using standard methods.