View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0002680 | AI War 1 / Classic | Bug - Other | Jan 28, 2011 5:36 pm | Mar 23, 2011 2:13 pm | |
| Reporter | BluePhoenix | Assigned To | Chris_McElligottPark | ||
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.073 | ||||
| Fixed in Version | 5.007 | ||||
| Summary | 0002680: AI gathering ships on Dyson Sphere world | ||||
| Description | I have attached two saved games (from a different cam), spaced about one hour where the AI has gathered 800 Mark II ships on the world containing the Dyson sphere (Isilyrib, near the top right corner), and a further 1600 Mark II/IV ships on the two adjacent worlds (These numbers are for the later save, the numbers are 500 and 1000 ships respectively for the earlier save). This makes the impending CPA in the later save deadly, as all of the 1400 freed mark II ships come only from those three planets, despite there being plenty of mark II ships elsewhere. (And yes, the planet the Dyson sphere is on is unexplored and not on alert, I got those numbers using cheats) This issue seems to still exist on the 5.0 version of the game, as far as my limited testing goes. | ||||
| Tags | No tags attached. | ||||
| Internal Weight | |||||
|
|
|
|
|
|
|
|
Just curious. Did the threat suddenly jump up when you first scouted that planet? |
|
|
At the time the aforementioned CPA occurred, and the ships were freed, I had still not still not yet managed to get scouts that far, so the planet was never scouted in the first place. |
|
|
Dang it. I asked because I am wondering about a theory of mine that I could be completely wrong about but still am mentioning on many things related to minor faction attacks or weird threat. :P |
|
|
What issue? Getting owned? :D In one game I cleared a hub-planet with 7 adjacent planets, knowledge raided all adjacent planets and abandonded the hub-planet, after which the planets did stay on alert and did keep building up their fleets. When a CPA was called 4/5 of those CPAs ships came from that corner of space, which where quite a bit more than 1400 and mostly mark3 ships. I just had to make sure my 'defensive planet' was boosted enough to cope with it (0000003:0000005 (<- saying 'roughly 5')speedboosters, log2-CC, armor inhibitor and booster, range inhibitor(AI only), and Black Hole Machine, not to mention the number of turrets and Forts), overall I lost fairly little of my fleet (only bombers tend to go for the Forts and often succeed in taking a mk1 out while your busy fighting these rather large numbers of foes). Perhaps I do not understand the issue you are aiming at, but it sure does sound to me it is working as intended ... it makes you dirty your pants :) |
|
|
Actually the issue I am referring to is threat coming from nowhere on load and sometimes on scouting (or planetary vision in general). I suspect it has to do with minor factions on AI planets where humans are nowhere near. I could be completely wrong of course, but I am trying to gather evidence for or against it where I can. Anyways, AI ships "gawking" (because they can't attack it) at Dyson spheres was supposedly fixed LONG ago. Either it has come back, or maybe the gattlings it spawns are causing the AI to be a little too defensive. |
|
|
@Red Spot It is not the CPA that is the issue here, but rather the AI heavily reinforcing the planet containing the Dyson Sphere, along with the two adjacent planets (even whilst they remain un-scouted and un-alerted). In hindsight it probably not a good idea to mention that CPA. I only mentioned it as an example of how the build up of ships could cause problems later on. (That and I did get 'owned' by the CPA at my first try of surviving that CPA.) Edit: @TechSY730 I should have mentioned that the ships the AI is gathering are guard post ships, not special forces ships. I have also just checked the wiki and if the information it has on the Dyson Sphere is still accurate, the AI heavily reinforcing the planet is intended behaviour. What is not intended behaviour is the Dyson Sphere sitting dormant and not producing [i]any[/i] Dyson Gatling's, until it is brought out of cold storage. Normally the Dyson Gatling's will be preventing a large build-up of AI ships. |
|
|
The gathering is intended, but the dyson should have been engaging them some at least. This should help: * Previously, allied minor faction and zombie ships would just patrol around player planets endlessly, which was helpful for defense, but problematic for two reasons: first, that it could cause massive amounts of slowdown after many hours of them stacking up, and second, that it could cause massive buildups of AI stalkers, who never dare to attack the planets with so many defenders, which leads to something akin to stalemate situations. ** Thus the allied minor faction and zombie logic has been adjusted as follows: *** Neutral planets are now considered the same as allied planets, and the ships will patrol to them like any others. *** If there are more than about 100 of AI threat ships on an adjacent planet, the ships will also patrol to that planet to clean them off. *** If the human-allied team has more than a token military force (more than about 10 ships) on a planet, then these ships will patrol to there, to help aid in that attack. **** This allows for small raids to still happen with raid starships or whatever without assistance from these minor factions, but it enlists their help for larger-scale engagements. |
|
|
I have double-checked to see if the Dyson Sphere was indeed engaging the AI ships. It turns out that it does engage the AI ships, but only if I have at least one ship on its planet OR the command station of the planet it's on has been destroyed. In other words, it does NOT engage the AI ships (or even build any Dyson Gatling's) if the planet it is on is controlled by the AI AND there are no human ships on the planet (including scouts). Anyways I'll wait to see if those changes do make a difference or not before reopening this issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Jan 28, 2011 5:36 pm | BluePhoenix | New Issue | |
| Jan 28, 2011 5:36 pm | BluePhoenix | File Added: Autosave_2011_01_27_16_54_01.sav | |
| Jan 28, 2011 5:37 pm | BluePhoenix | File Added: Autosave_2011_01_27_20_07_51.sav | |
| Jan 28, 2011 5:39 pm | TechSY730 | Note Added: 0009786 | |
| Jan 28, 2011 5:47 pm | BluePhoenix | Note Added: 0009790 | |
| Jan 28, 2011 5:49 pm | TechSY730 | Note Added: 0009791 | |
| Jan 28, 2011 6:22 pm | Red Spot | Note Added: 0009805 | |
| Jan 28, 2011 6:23 pm | Red Spot | Note Edited: 0009805 | |
| Jan 28, 2011 6:25 pm | TechSY730 | Note Added: 0009806 | |
| Jan 28, 2011 6:26 pm | TechSY730 | Note Edited: 0009806 | |
| Jan 28, 2011 8:12 pm | BluePhoenix | Note Added: 0009810 | |
| Jan 28, 2011 9:17 pm | BluePhoenix | Note Edited: 0009810 | |
| Jan 28, 2011 9:20 pm | BluePhoenix | Note Edited: 0009810 | |
| Mar 23, 2011 11:27 am | Chris_McElligottPark | Note Added: 0011336 | |
| Mar 23, 2011 11:27 am | Chris_McElligottPark | Status | new => resolved |
| Mar 23, 2011 11:27 am | Chris_McElligottPark | Fixed in Version | => 5.007 |
| Mar 23, 2011 11:27 am | Chris_McElligottPark | Resolution | open => fixed |
| Mar 23, 2011 11:27 am | Chris_McElligottPark | Assigned To | => Chris_McElligottPark |
| Mar 23, 2011 2:05 pm | BluePhoenix | Note Added: 0011341 |
