[drewnoakes]

The ear's whole function is to detect differences in patterns. This is how we identify the direction of sound with only two ears. For our ears, a delay of 30ms is an eternity.

The eyes on the other hand have very little response to this. Some will say they can spot a 15ms vs 30ms visual delay easily, but this is an open debate rather than an obvious fact. A 15ms delay in audio is noticeable to almost anyone.

Different senses, different sensitivities. Comparing them isn't very instructive.

[setzer22]

Your 15/30ms is close to the timings of 30 vs a 60fps videogames. While testing for a single frame you'd probably get very mixed results, most people can distinguish the pattern of when the framerate drops from one to the other. That looks more close to me to the audio example, since it's a constant stream of visual information.

[CapsAdmin]

I think this is actually more to do with timing than audio.

I've made a jumping mechanism for a game that makes you move faster if you jump right when you hit the ground again. This system does not give any audible cues as to when you should jump. When something in this system is slightly off, ie keyboard latency, jump height, gravity, etc. You can't time the jumps properly and you're left feeling that you somehow just can't do it but can't really pinpoint what the problem is exactly.

I think the same applies to many games. Especially fighting games.

With that said, I don't think writing code is about timing. I think it's nice when an editor feels very responsive, but I don't think it necessarily makes me more productive.