| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0006141 | Spring engine | Lua | public | 2019-02-20 14:02 | 2019-02-20 15:12 | ||||
| Reporter | Doo | ||||||||
| Assigned To | |||||||||
| Priority | low | Severity | minor | Reproducibility | always | ||||
| Status | resolved | Resolution | no change required | ||||||
| Product Version | 104.0 +git | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0006141: Spring.MoveCtrl.SetMoveTypeData errors on movectrled units - No way to check beforehands if a unit is currently movectrled? | ||||||||
| Description | When using movectrl for certain units in certain situations (ie, a landing phase of 20s at game start where the unit is slowly descended from 1800 height to ground height, or when planes are movectrled to land on air repair pads), Spring.MoveCtrl.SetMoveTypeData will error and sometimes crash the gadget/script that ran it. As far as I know, the "fix" is simply to disable movectrl before calling this function. But then, i haven't find a way to get the current movectrl state before doing so, so that i can restore it if it was enabled before. Is there a way to have this function work on movectrled units? Or maybe grant us with a MoveCtrl.GetState => boolean MoveCtrlEnabled that we can use to decide wether or not we will change the movetype data, disable and reenable movectrl, or just reschedule the change to when movectrl is disabled? | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | |||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Kloot (developer) 2019-02-20 14:19 |
> i haven't find a way to get the current movectrl state MoveCtrl.IsEnabled(unitID) |
|
Doo (reporter) 2019-02-20 14:52 |
Oh, nice - this helps alot! Although, it seems to be undocumented on wiki (https://springrts.com/wiki/Lua_MoveCtrl), maybe it's a little too recent? Thanks anyway ! |
|
Kloot (developer) 2019-02-20 15:12 |
been around since forever, the docs just have random holes in them. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-02-20 14:02 | Doo | New Issue | |
| 2019-02-20 14:19 | Kloot | Note Added: 0019743 | |
| 2019-02-20 14:52 | Doo | Note Added: 0019745 | |
| 2019-02-20 15:12 | Kloot | Status | new => resolved |
| 2019-02-20 15:12 | Kloot | Resolution | open => no change required |
| 2019-02-20 15:12 | Kloot | Note Added: 0019748 | |
| Issue History |