A question on garrison units and game performance/load times.

[Ivan_Moscavich]

I've noticed a trend that garrison units seem to be just renamed units from the general rosters. Garrison spears being light hoplites for example. The stats seem either exactly the same in some cases, or practically the same in others.

My question is, does having these units which are fundamentally renamed version of existing units have much impact in performance?

Would it improve the game's load times if all garrison units were simply the same units as what they are based on?

If every german garrison spear unit was levy spearmen, if garrison greek spears were just hoplites. Would the removal of such duplicate units in all cases improve any performance?

It's just something I'd been thinking about, I have no idea the impact it would have, or lack of impact for that matter.

[Simon.Fitoussi]

I'm no computer wizz but by Jove I think the boy's on to something here. That probably explains why only siege battles lag. It's like loading mirror images from head to toe instead of cut and paste which has just got to be faster... These CA devils ruined us again lol.

[Augustusng]

I'm no computer wizz but by Jove I think the boy's on to something here. That probably explains why only siege battles lag. It's like loading mirror images from head to toe instead of cut and paste which has just got to be faster... These CA devils ruined us again lol.

Nope, siege battle lag has nothing to do with garrison units. Besides, DeI's garrison units are custom, not vanilla units. Siege battle lag is primarily (as far as I understand) because of pathfinding in cities, which uses your CPU, not GPU.

And I think the load times are more to do with DeI's scripts than the units.

[Ivan_Moscavich]

Nope, siege battle lag has nothing to do with garrison units. Besides, DeI's garrison units are custom, not vanilla units. Siege battle lag is primarily (as far as I understand) because of pathfinding in cities, which uses your CPU, not GPU.

"Today, 07:45 PM"
"Today, 07:45 PM"

Do we flip a coin to see who ninjaed who?

I 'think' Dresden or another staff member at some point said that the massive number of new units did have an effect on the load times coming out of battles.

Which is where my question is directed. Getting back into the game faster instead of waiting for load times that can sometimes be several minutes worth.

Why CA didn't choose to just keep everything cached as far as the strategic battle map is concerned, I have no idea.

[Ivan_Moscavich]

I'm fairly sure the siege battles lagging are almost entirely due to pathfinding errors.

The way it is now, each individual unit is repeating it's decision cycle in the programming far more rapidly than it should because it doesn't have a clearly delineated path for the logic to follow on what to do.

The best way to describe it in an analogy is, you give someone a task to walk to a wall that is ten feet away. But every half inch they turn around, and ask you where you wanted them to go.

At least I think that's why the computer bogs down during points in siege and combined naval/land battles.

But the load times could be affected by the duplication of units that only appear in seiges, hence my question here.