CYCLE_DELAY being less than 0.01 causes cycle to freeze

Bug #1037363 reported by LOVER$BOY
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Armagetron Advanced
Undecided
Armagetron Advanced Alpha Project
0.4
Low
Unassigned

Bug Description

While in Alpha Project LOVER$BOY's Hells Racing, it's original cycle delay was set to 0. Sometimes when a player hits the rim walls, they get stuck and are unable to move again.

After wards, the same server was tested with the delay set to 0.01 and the problem has stopped somewhat.

Related branches

LOVER$BOY (zodiacsohma)
Changed in armagetronad:
status: New → Confirmed
assignee: nobody → armagetronad-ap (armagetronad-ap)
description: updated
Revision history for this message
Yann Kaiser (epsy) wrote :

We could clamp it to have 0.0001 or something as minimum. 0 makes no sense to begin with.

Revision history for this message
LOVER$BOY (zodiacsohma) wrote :

Are you sure 0.0001 wouldn't freeze the bike if a racing server is to use it?

Revision history for this message
Armanelgtron (armanelgtron) wrote :

The most likely reason I can think that this may have happened is that the cycle's trail length must be higher than 0, meaning you can get stuck on your own walls when turning by a wide angle. In order to have no trail on your cycle you have to have CYCLE_FIRST_SPAWN_PROTECTION on and CYCLE_WALL_TIME set to a decently high value.

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

Other bug subscribers