View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0025559 | AI War 2 | Bug - Gameplay | Sep 22, 2021 9:02 pm | Sep 24, 2021 12:27 am | |
| Reporter | vinco | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | Beta 3.700 Bulk Of The Great Refactor | ||||
| Fixed in Version | Beta 3.701 Natural Object Order | ||||
| Summary | 0025559: Error when moving to fleet not at current planet | ||||
| Description | I've been unable to reproduce this, but I triggered an error a bit after the attached save by sending my 0000002 combat engineer fleet to the system my 0000001 fleet's currently attacking, then double-tapping 2 while not on the planet on which the combat engineer currently resided. | ||||
| Tags | No tags attached. | ||||
|
|
Is there an error log? Can anyone else reproduce this? |
|
|
Terribly sorry... I thought I included a log, and I've since deleted my log. Reference saves attached. Though now I have a new problem... Telling group 2 to move to a new planet isn't making it move at all (done from the galaxy map. I'm trying to get it to move to the planet with the current assault by right clicking on that planet. Result: Engineer fleet 2 stops moving completely. Autosave at 10m 0s.savemet (110 bytes)
UK 739232991 600 VS37 <color=#66ffce>Easier </color> Full Ensemble Difficulty 7 2 <color=#0000fb>Vinco</color> |
|
|
Adding to the last note, now the engineer group won't travel across planets at all. Confirmed on reload. Adding new mantis. |
|
|
I'm trying, but I can't figure a way to reproduce it either. It seems like one of those super rare errors. |
|
|
Thanks! * Fixed an issue where NaturalObject (no owner) faction was not always set to faction index 0 anymore. This was something I was already aware of, but wasn't sure if it would be a problem. ** It turns out that this was a major problem, and would cause various ailments such as units not reacting to aggro and releasing units, to all sorts of other potentially unknown stuff. This will not fix existing 3.700 saves that had this problem, but any new saves will not have the problem. ** Additionally, this was causing units to not respond to move commands properly between planets. This again isn't fixed in existing 3.700 saves, but any new saves no longer exhibit the problem. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Sep 22, 2021 9:02 pm | vinco | New Issue | |
| Sep 23, 2021 9:37 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Sep 23, 2021 9:37 am | Chris_McElligottPark | Status | new => feedback |
| Sep 23, 2021 9:37 am | Chris_McElligottPark | Note Added: 0062808 | |
| Sep 23, 2021 11:18 am | vinco | Note Added: 0062811 | |
| Sep 23, 2021 11:18 am | vinco | File Added: Autosave at 10m 0s.savemet | |
| Sep 23, 2021 11:18 am | vinco | File Added: Autosave at 10m 0s.save | |
| Sep 23, 2021 11:18 am | vinco | Status | feedback => assigned |
| Sep 23, 2021 11:20 am | vinco | Note Added: 0062813 | |
| Sep 23, 2021 4:45 pm | Daniexpert | Note Added: 0062816 | |
| Sep 24, 2021 12:27 am | Chris_McElligottPark | Status | assigned => resolved |
| Sep 24, 2021 12:27 am | Chris_McElligottPark | Resolution | open => fixed |
| Sep 24, 2021 12:27 am | Chris_McElligottPark | Fixed in Version | => Beta 3.701 Natural Object Order |
| Sep 24, 2021 12:27 am | Chris_McElligottPark | Note Added: 0062825 |
