How do you check what changes the AI makes between two consecutive ship design versions?

[Correcaminos]

I'm reviewing the auto-generated ship designs, and the AI often creates a “New Version” of a ship, but I haven’t found a quick way to see exactly what changed compared to the previous version (added/removed components, weapons, engines, etc.).

Do you use any practical method or a specific screen to compare two AI-generated designs?
How do you guys do it?

Thanks!

[Correcaminos]

I'm reviewing the auto-generated ship designs, and the AI often creates a “New Version” of a ship, but I haven’t found a quick way to see exactly what changed compared to the previous version (added/removed components, weapons, engines, etc.).

Do you use any practical method or a specific screen to compare two AI-generated designs?
How do you guys do it?

Thanks!

After digging into this for a few days, I think I’ve found the only practical way to check what changes the AI makes between two consecutive versions of the same ship design.

What I’m doing now is:



In the Ship Designs screen, I filter by the same ship type.

I enable the option to show obsolete designs along with the active ones.

This way, I can see all previous versions together with the new AI-generated version.

Then it’s just a matter of opening each design manually and checking the differences in components, weapons, engines, etc.

As far as I can tell, there is no built-in side-by-side comparison panel or summary of changes between versions, which would be extremely useful for understanding why the AI makes certain choices and for deciding which version to keep.

It would be great if a comparison tool or at least a “changes since last version” summary could be added in the future.
If anyone knows a more efficient method, I’d be glad to hear it — but so far this seems to be the only workable approach I’ve found.

[Xmudder]

This game spends far too much time upgrading and retrofitting ships and fleets. Further, the manual fleet creation only accepts the most recent models. Most of this is make work that wastes time and money and makes large fleets impossible to sustain,as they spend all their time upgrading.

Ships should be considered the same "generation" if they have the same hyperdrive and fuel capacity / range. So long as those are the same, they should be grouped together and not upgraded unless they have nothing to kill / invade (this included things too powerful to kill). Aquired ships should be grouped the same way - such ass when you kill a hive carrier, and get a bunch of pirate factions, they should auto group in to fleets with the same strategic characteristics.

Certain improvements should set off an upgrading binge, such as larger hull size, a different ( better) hyperdrive / engine, certain weapon improvements, or a new generation of energy that has different size requirements. The techs that will set off should be flagged in the research tree, and should include various weapon iterations. While designing new models are fine, upgrades should be postponed until they are relevant OR player requested.

Allow us to set the automation to always upgrade with new designs, never upgrade unless manually requested, and upgrade when certain techs are researched.

In my most recent game, I have 8 10k+ fleets, and 4 are retrofitting, 2 are refueling, 1 is loading troops, and one is moving to intercept the Hive. If I try to break them down into more smaller fleets so they actually kill things, the auto build fleet template will be useless, as it will ignore anything but the absolute most recent generation of ship, instead of grouping them by strategic characteristics, hyperjump speed and fuel.

I also don't want them upgrading until I reach "Torrent Drive" and then "Fusion Balance" (currently researching prerequisites) but that requires turning a bunch of automation off and then back on.

[Correcaminos]

This game spends far too much time upgrading and retrofitting ships and fleets. Further, the manual fleet creation only accepts the most recent models. Most of this is make work that wastes time and money and makes large fleets impossible to sustain,as they spend all their time upgrading.

Ships should be considered the same "generation" if they have the same hyperdrive and fuel capacity / range. So long as those are the same, they should be grouped together and not upgraded unless they have nothing to kill / invade (this included things too powerful to kill). Aquired ships should be grouped the same way - such ass when you kill a hive carrier, and get a bunch of pirate factions, they should auto group in to fleets with the same strategic characteristics.

Certain improvements should set off an upgrading binge, such as larger hull size, a different ( better) hyperdrive / engine, certain weapon improvements, or a new generation of energy that has different size requirements. The techs that will set off should be flagged in the research tree, and should include various weapon iterations. While designing new models are fine, upgrades should be postponed until they are relevant OR player requested.

Allow us to set the automation to always upgrade with new designs, never upgrade unless manually requested, and upgrade when certain techs are researched.

In my most recent game, I have 8 10k+ fleets, and 4 are retrofitting, 2 are refueling, 1 is loading troops, and one is moving to intercept the Hive. If I try to break them down into more smaller fleets so they actually kill things, the auto build fleet template will be useless, as it will ignore anything but the absolute most recent generation of ship, instead of grouping them by strategic characteristics, hyperjump speed and fuel.

I also don't want them upgrading until I reach "Torrent Drive" and then "Fusion Balance" (currently researching prerequisites) but that requires turning a bunch of automation off and then back on.

You nailed it, Mudder.

While I was looking for a UI solution to compare designs, your point about the strategic inefficiency of the current system is the real underlying problem.

I couldn't agree more. We desperately need a "Retrofit Doctrine" or Policy setting that allows us to dictate when the AI should trigger an automated retrofit. It is a strategic catastrophe to have fleets spending 80% of their time traveling to drydocks for minor +1 damage upgrades and only 20% actually operating or patrolling.

It would be a game-changer if we could set specific Retrofit Triggers, such as:

Logistical Sync: Only retrofit if the new design changes the Fuel Range or Hyperdrive speed (to ensure the fleet can still fly together efficiently).

Structural Changes: Only retrofit if the Hull Size/Class increases.

Capability Leaps: Only retrofit for significant component tier jumps (e.g., New Sensor generation), ignoring minor incremental tweaks.

Operational tempo is key in a game of this scale. Right now, the constant incremental retrofitting kills that tempo.

[FirstPappy]

Amen!