View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001006 | Spring engine | General | public | 2008-08-21 00:26 | 2010-02-09 20:00 |
| Reporter | satirik | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | not fixable | ||
| Summary | 0001006: 0.77a1 test replay BA 6.31 - target not in los causes firing at random direction | ||||
| Description | * force fire doesn't work * luaui doesn't work * not sure but when the unit was not in los it was firing at random direction | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Checked infolog.txt for Errors | |||||
|
|
attached a replay reproducing the problem; not sure if it's a problem at all, maybe it's intended behavior, but it's a little overbroad. |
|
|
CWeapon::Update() is probably at fault when calculating the target position for units just outside LOS, the error offset can be quite substantial. I don't feel like changing it though, weapon code is not very transparent (pull one thread, unravel another). targetPos = helper->GetUnitErrorPos(targetUnit, owner->allyteam) + lead; targetPos += errorVector * (weaponDef->targetMoveError * 30 * targetUnit->speed.Length() * (1.0f - owner->limExperience)); |
|
|
yeah, I agree this isn't such a big issue to change it days before release. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-08-21 00:26 | satirik | New Issue | |
| 2008-08-21 00:26 | satirik | File Added: unnamed.sdf | |
| 2008-08-22 15:42 | imbaczek | Note Added: 0002479 | |
| 2008-08-22 15:42 | imbaczek | Summary | 0.77a1 test replay BA 6.31 => 0.77a1 test replay BA 6.31 - target not in los causes firing at random direction |
| 2008-08-22 15:43 | imbaczek | File Added: weird_shooting_out_of_los.sdf | |
| 2008-08-22 17:14 | Kloot | Note Added: 0002480 | |
| 2008-08-22 17:18 | imbaczek | Note Added: 0002481 | |
| 2008-08-23 03:05 | Kloot | Status | new => confirmed |
| 2010-02-09 20:00 | Auswaschbar | Status | confirmed => closed |
| 2010-02-09 20:00 | Auswaschbar | Resolution | open => not fixable |
