First Round Wrong Axis

Bug #332717 reported by yarrt on 2009-02-21
2
Affects Status Importance Assigned to Milestone
Armagetron Advanced
Status tracked in Trunk
0.2.8
Wishlist
Unassigned
Trunk
Low
Unassigned

Bug Description

If you enter a server with a multi axis map (more than 4) the client might still use 4 axes for the first round. Not sure if the bug has been fixed, as with current Betas the bug did not occur that often. If I see it again, I'll try to upload a recording.

Most people report this as lag. But you can actually only see 4 axis aligned walls and the the cycle is showed on 4 axises first, then some correction from the server arrives (I guess) and the real cycle orientation is shown.

Manuel Moos (z-man) wrote :

This would be affecting 0.2.8, right?

yarrt (yarrt) wrote :

yes. sorry. Confirmed for 0.2.8.2.1 (on chicos styball). It does not happen everytime thought - might be a race condition / depends on message order ?. not sure about 0.2.8.3_beta1 if I observe it again, I'll report it here.

Manuel Moos (z-man) wrote :

Yeah, it's definitely message order. Axes in maps should not be problematic, but if axes (or map size) settings only arrive on the client after the grid has been created, stuff like that can happen. There are no real safeguards against it, but clients should sync before they create the grid and thus avoid this in 99.9% of all cases.

A real solution would be if the server would delay sending the gGame object responsible for creating the grid until all settings are transmitted. I give this bug a low priority for now and will attempt that on the trunk; the settings system has sufficiently diverged for merge hell issues.

Changed in armagetronad:
importance: Undecided → Low
Manuel Moos (z-man) wrote :

It's only a problem on hack servers that throw you into the action immediately. Therefore, probably not worth fixing in 0.2.8. Maybe it'll be possible to backport the trunk fix.

Luke-Jr (luke-jr) wrote :

Doesn't this problem affect spectators as well?

Yann Kaiser (epsy) wrote :

It would appear this can't happen on a 0.4 server. I'm assuming it was fixed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers