| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0003877 | Spring engine | General | public | 2013-06-29 03:59 | 2016-11-27 05:20 | ||||||||
| Reporter | PepeAmpere | ||||||||||||
| Assigned To | |||||||||||||
| Priority | normal | Severity | feature | Reproducibility | always | ||||||||
| Status | feedback | Resolution | reopened | ||||||||||
| Product Version | 94.1.1+git | ||||||||||||
| Target Version | Fixed in Version | ||||||||||||
| Summary | 0003877: parametrization of vehicles reverse | ||||||||||||
| Description | Current engine reverse is not usable, works just for small distances (no matter how it is calculated now). I would like to add option that will set the maximalDistance for which reverse will be used if next move order target is behind the unit. There would be modrule in modrules.lua reverseDistance = <integer> if 0, default pathing decision is used (current defaults) if more, its compared with orderDistance of next move order each time units execute new move order: if (orderDistance less then reverseDistance) and (orderPosition is between 4th and 8th oclock with given unit rotation), then reverse is used for unit else default pathing decision is used | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Checked infolog.txt for Errors | |||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
FLOZi (reporter) 2013-06-29 22:19 |
Better per unitdef than a (ugly) modrule |
|
PepeAmpere (reporter) 2013-06-30 02:37 |
yes, you are true. But modrule is still needed for selection that i dont want to use default pathifinder choice of move |
|
PepeAmpere (reporter) 2013-07-04 02:50 Last edited: 2013-07-04 02:50 |
Is this hard to implement? For sure there will be needed one new unitDef, optional/possible one new modrule and update current reverse code to use this value. |
|
Anonymous (viewer) 2016-02-05 22:28 |
Fix d532e97328a21382682874d427048f24748ce985 committed to develop branch: fix 0003877 (via the SetGroundMoveTypeData interface), repo: spring changeset id: 6543 |
|
PepeAmpere (reporter) 2016-11-27 05:20 |
maxReverseDistance is ignored by already reversing vehicles - i guess the error is on line 2408 in the comparison logic values Repro ===== 1) Run Spring 103.0 with dev nota from commit (https://bitbucket.org/notagame/nota/commits/36556ff2f813c6f2bd5fd9285e33bb40d368c6ac) 2) /cheat 3) /give 20 correap 4) give it move which results in reverse 5) give it move which goes over whole map 6) (x) observe they still reverse over whole map Btw, Reaper gets whats in unit def + Spring.MoveCtrl.SetGroundMoveTypeData(unitID, {maxReverseSpeed = ud.speed * 0.6, minReverseAngle = 110, maxReverseDist = 500}) once it is spawned. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-06-29 03:59 | PepeAmpere | New Issue | |
| 2013-06-29 22:19 | FLOZi | Note Added: 0010947 | |
| 2013-06-30 02:37 | PepeAmpere | Note Added: 0010948 | |
| 2013-07-04 02:50 | PepeAmpere | Note Added: 0010960 | |
| 2013-07-04 02:50 | PepeAmpere | Note Edited: 0010960 | View Revisions |
| 2016-02-05 22:28 | Changeset attached | => spring develop d532e973 | |
| 2016-02-05 22:28 | Anonymous | Note Added: 0015634 | |
| 2016-02-05 22:28 | Anonymous | Status | new => resolved |
| 2016-02-05 22:28 | Anonymous | Resolution | open => fixed |
| 2016-11-27 05:20 | PepeAmpere | Status | resolved => feedback |
| 2016-11-27 05:20 | PepeAmpere | Resolution | fixed => reopened |
| 2016-11-27 05:20 | PepeAmpere | Note Added: 0016913 | |
| Issue History |