View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0024691 | AI War 2 | Gameplay Issue | Apr 15, 2021 10:45 am | Jul 13, 2021 7:28 pm | |
| Reporter | Daniexpert | Assigned To | Chris_McElligottPark | ||
| Severity | minor | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 2.800 The Paradigm Shift | ||||
| Fixed in Version | Beta 3.310 Engineering Intelligence Injection | ||||
| Summary | 0024691: Engineers constantly changing target | ||||
| Description | Hello everyone, I noticed that, sometimes, when engineers have the option to choose to either assist factory or to assist the costruction of any building (turrets, infrastructures, etc.) they go a bit crazy. Engineers start doing one thing, all together, then, after 1 second, they change target and start going to do something else, then, 1 second later, they switch back to the previous assignment and keep doing this back and forth, spending most of their time travelling instead of actually assisting / repairing. It looks like an issue with their internal priority system, because they prioritize one thing, then immediately after, another one, even if the previous task hasn't been completed. In the image you can see the conga line of engineers that is unable to decide if they want to build the turret or assist the factory. I attached the autosave (check "Tyrann" system), but unfortunately I didn't manage to reproduce this behaviour. In 50 minutes of gametime, I've seen this happen twice. | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Thanks! * Fixed a longstanding bug in engineer move code that made them move in fits and spurts toward distant targets. ** Rather than moving gracefully from spot to spot (and going all the way there without being indecisive), their movement orders were instead "go 8/10ths of my assistance range and then reconsider who to even help." That... is not logic that makes sense or that is helpful. ** The logic was an accidental inversion. We calculated the angle from the engineer to the target, and then a point at that angle from the engineer that was 8/10s of the assistance range of the engineer. The engineer was told to go there. This is wrong/ ** Instead we now calculate the angle from the target to the engineer, and then a point at that angle from the target that is 8/10ths of the assistance range of the engineer. This properly gets the engineer to go in range, and then actually help the target. ** Engineers greatly prefer to help targets in range of themselves, so the odds of them getting indecisive like before is very very low. The problem was when they stopped in the middle and rethought things. ** Why 80% of their range? Well, because there are usually a clump of them. This gives them room to decollide without going back out of range. Them moving in a clump is actually one of the more efficient ways to get things up and running as fast as possible, so making room for that was always a good idea. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Apr 15, 2021 10:45 am | Daniexpert | New Issue | |
| Apr 15, 2021 10:45 am | Daniexpert | File Added: 2021-04-15 16_36_30-AIWar2.png | |
| Apr 15, 2021 10:45 am | Daniexpert | File Added: Autosave at 50m 0s - EngineersCrazy.save | |
| Jul 13, 2021 7:28 pm | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Jul 13, 2021 7:28 pm | Chris_McElligottPark | Status | new => resolved |
| Jul 13, 2021 7:28 pm | Chris_McElligottPark | Resolution | open => fixed |
| Jul 13, 2021 7:28 pm | Chris_McElligottPark | Fixed in Version | => Beta 3.310 Engineering Intelligence Injection |
| Jul 13, 2021 7:28 pm | Chris_McElligottPark | Note Added: 0062389 |
