Bug 54833 - Do we have "Jesus unit" support ?
Summary: Do we have "Jesus unit" support ?
Status: RESOLVED FIXED
Alias: None
Product: boson
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR major
Target Milestone: ---
Assignee: The Boson Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-18 23:27 UTC by Felix Seeger
Modified: 2003-02-24 11:04 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Seeger 2003-02-18 23:27:03 UTC
Version:            (using KDE 3.1.9)
Compiler:          gcc version 2.95.4 20011002 (Debian prerelease)
OS:          Linux (i686) release 2.5.60bk1

Sometimes units run away to a magic point outside the map.
They will drive through buildings and over water.

At the moment I don't have a real reproducer for it. But sometimes it happens.
I played Basic 2.
Comment 1 Andreas Beckermann 2003-02-19 19:40:32 UTC
I can confirm this problem. 
I've just had a ship (on basic2, btw) that had been nearly destroyed (I could not see an 
explosion or the - it was selected and had a small part of the health bar left) and went out 
of the water to the border of the map. 
 
It seems that either advanceMoveInternal() or similar gets called without calling 
advanceMoveCheck() after it (must NEVER happen!) or setVelocity() gets called 
somewhere outside advanceMove*() (must NEVER happen either). 
 
I cannot explain it with anything else. 
 
CU 
Andi 
 
Comment 2 Rivo Laks 2003-02-19 21:47:26 UTC
I have also had it once or twice. Problem may be that velocity is not reset before moving is 
stopped. You must always do setVelocity(0, 0, 0); when you stopMoving(). Maybe setVelo 
should even be put to stopMoving... Anyway, if you don't reset it, unit will keep moving. It also 
happened month or two ago, but then I fixed it, but I might have missed something. I'll take a 
look at moving code tomorrow. 
 
Rivo 
 
Comment 3 Rivo Laks 2003-02-24 11:04:19 UTC
Ok, it should be fixed now. If you experience it again, reopen this bug report. 
 
Rivo