bugWarzone 2100 Project - Bugs: bug #12363, Endlessly spinning droids - bug in...

Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #12363: Endlessly spinning droids - bug in moveGetDirection

Submitted by:  Per I. Mathisen <per>
Submitted on:  Sat Sep 27 21:15:14 2008  
Category: Engine: MovementSeverity: Important
Priority: 5 - NormalStatus: Confirmed
Assigned to: Dennis Schridde <devurandom>Open/Closed: Open
Release: svn/trunkOperating System: All
Planned Release: None

(Jump to the original submission Jump to the original submission)

Fri Dec 12 17:40:48 2008, comment #6:

Hm, not this weekend. The week afterwards maybe. (Currently quite stressed.)

Fri Dec 12 16:33:51 2008, comment #5:

devurandom - Any chance you could get the time to look at this bug?

Per I. Mathisen <per>
Project Administrator
Tue Sep 30 16:14:48 2008, comment #4:


this ticket looks like this bug based on looking at the video but i could be wrong

Sun Sep 28 16:32:48 2008, comment #3:

Scheduling for Fr, 03.10.
Do not wait if that is too late.

Dennis Schridde <devurandom>
Project AdministratorIn charge of this item.
Sun Sep 28 15:13:00 2008, comment #2:

I suggest you look at the patch. Merely making it trigger the comparisons is apparently not enough.

Per I. Mathisen <per>
Project Administrator
Sun Sep 28 00:45:53 2008, comment #1:

Would an epsilon comparison suffice there?
Or is the inner logic of that code flawed entirely?
I once wrote that code, but I would be glad if someone else could fix it. (devaway and stuff...)

Dennis Schridde <devurandom>
Project AdministratorIn charge of this item.
Sat Sep 27 21:15:14 2008, original submission:

There is a subtle bug in moveGetDirection() that results in droids that spin endlessly in circles, going nowhere. The problem occurs when a droid gets a path, but is nudged off course, so that it appears closer to the second waypoint in the path than the first. When moveGetDirection tries to interpolate a direction for it between the two waypoints, it sends it in a circle between the two, since it does not understand that it could be closer to the second waypoint than the first.

Savegame that reproduces the bug is attached.

Also attached is a nasty hack to fix the problem.

Per I. Mathisen <per>
Project Administrator


Attached Files
file #4831:  spin.tar.gz added by per (231kB - application/x-gzip)
file #4832:  spin.diff added by per (1kB - text/x-patch)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -unavailable- added by devurandom (Posted a comment)
  • -unavailable- added by per (Submitted the item)
  • -unavailable- added by per

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.


    Error: not logged in



    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sun Sep 28 16:32:48 2008devurandomAssigned toNone=>devurandom
    Sat Sep 27 21:15:14 2008perAttached File-=>Added spin.tar.gz, #4831
      Attached File-=>Added spin.diff, #4832
      Carbon-Copy-=>Added devurandom
    Show feedback again

    Back to the top

    Powered by Savane 3.1-cleanup