|
|
| Reporter | Google_Frog | |
|---|
| Assigned To | Kloot | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | resolved | Resolution | fixed | |
|---|
| Product Version | 98.0.1+git | |
|---|
| Target Version | | Fixed in Version | 104.0 +git | |
|---|
|
|
| Summary | 0004620: maxSpeed with SetGroundMoveTypeData relies of CMD_SET_WANTED_MAX_SPEED and fails to work correctly. |
|---|
| Description | Changing maxSpeed for ground units seems to rely on CMD_SET_WANTED_MAX_SPEED, this makes it vulnerably and buggy in a few ways.
If a unit is moving at a certain speed and has its maxSpeed changed it only notices when it is given a new order.
This has been broken since at least 91.0. My workaround has been to call SetGroundMoveTypeData every 3 frames for every affected unit. This workaround seems to be slower with the dev engine (and is slow regardless) so I would like to be able to remove it.
The tag 'requestedSpeed' looked promising but apparently it is incompatible movetype data for SetGroundMoveTypeData. |
|---|
| Steps To Reproduce | Get https://github.com/ZeroK-RTS/ExampleMod
Spawn slowtank. This tank switches between slow and fast mode every 8 seconds. Due to this bug the speed which it travels at depends on when its move order was given.
Spawn blockedtank. This tank sets itself to be slow 8 seconds after it is created. There is a gadget which blocks CMD_SET_WANTED_MAX_SPEED for this tank. It will always travel at its original speed, effectively ignoring SetGroundMoveTypeData.
|
|---|
| Tags | No tags attached. |
|---|
|
|
| Checked infolog.txt for Errors | |
|---|
|
|
| Attached Files |
|
|---|
Relationships 
Relationships