| 00:25.48 | *** join/#bzflag infobot (~infobot@208.53.50.136) |
| 00:25.48 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.14 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19953 |
| 00:25.49 | *** mode/#bzflag [+v infobot] by ChanServ |
| 00:34.42 | macsforme | am I missing anything from this list of things that contribute to lag? I have: roundtrip time from the shooting player to the server, roundtrip time from the targeted player to the server, processing time on the server itself, dead reckoning interpolation delay, and delay between frames on both clients |
| 00:37.30 | macsforme | I realize that some of those things aren't technically lag, but I want to include anything that makes a visual impact |
| 00:40.57 | blast007 | latency might be a better term |
| 00:40.59 | macsforme | (as far as a visual hit on the shooting player's side not resulting in an actual hit) |
| 00:59.05 | BulletCatcher | Don't forget the processing time on both clients. |
| 01:01.10 | BulletCatcher | I think it is safe to ignore the travel time of light from the display to the retina, which varies according to distance. ;-) |
| 01:02.13 | BulletCatcher | moves his face a foot closer to the display to reduce lag by 1 nanosecond |
| 01:05.25 | the_map | but you have to factor in the increased angle that your eyes have to travel, inducing extra wasted time |
| 01:08.55 | BulletCatcher | nods |
| 01:12.42 | spldart | JC :rolleyes: & :lolz |
| 02:19.52 | *** join/#bzflag infobot (ibot@208.53.50.136) |
| 02:19.52 | *** topic/#bzflag is https://BZFlag.org || http://ohloh.net/p/bzflag || https://bzflag.org/help || Channel Logs: http://infobot.rikers.org/%23bzflag/ || 2.4.14 released! https://forums.bzflag.org/viewtopic.php?f=62&t=19953 |
| 02:19.52 | *** mode/#bzflag [+v infobot] by ChanServ |
| 05:16.18 | *** join/#bzflag moriarty (~m01qa1dq@unaffiliated/moriarty) |
| 05:16.31 | *** part/#bzflag moriarty (~m01qa1dq@unaffiliated/moriarty) |
| 10:07.44 | macsforme | "delay between frames on both clients" would be the processing time, or perhaps more than the actual processing time |
| 10:08.40 | macsforme | 60 FPS is 17ms between frames |
| 13:20.58 | BulletCatcher | The relevant lag or latency component is the interval between the time a client receives a packet and the time the next frame is drawn with data from that packet. |
| 13:21.02 | BulletCatcher | That interval is the sum of the CPU-limited processing time and any delay resulting from vsync or energy saving. |
| 13:21.06 | BulletCatcher | The exact amount of vsync/saver delay will depend on synchronization with the display clock. |
| 13:21.08 | BulletCatcher | On the sending side, I don't know whether vsync/saver delays apply to mouse clicks and keystrokes. |
| 14:30.36 | *** join/#bzflag AAA_awright (~aaa@ns4001783.ip-198-100-144.net) |
| 14:47.15 | *** join/#bzflag AAA_awright (~aaa@ns4001783.ip-198-100-144.net) |
| 20:48.54 | *** join/#bzflag alezakos (~kongr45gp@bzflag/developer/alezakos) |
| 22:04.58 | *** join/#bzflag spldart (~james@bzflag/contributor/spldart) |
| 22:04.58 | *** mode/#bzflag [+v spldart] by ChanServ |