AO 1945 - extremly laggy

[DefiantXYX]

Hello there,

i just noticed, Operation Barca, that the game is really laggy, especially when I select an aircraft with longe range. Might have something to to with the inscreased range of airplanes in this mission.
Worst unit is the Me 262, I got to wait 3-4 seconds when I select it. Game is almost freezing.
Anyone noticed something like that?

[Tassadar]

I believe Edmon had this in his 1944 campaign, where suddenly the same rig started to have trouble. I observed a bit of similar issues in very specific scenarios and a very careful speculation might be that it's got to do with the map scripts, not necessarily with factors like size. That said, larger missions are usually the more complex one as well, so this is not necessarily totally unrelated.

Another observation - while my PC is slightly dated at this point and a better graphics card could improve the situation, I feel like RAM is the main culprit behind the lag, at least based on Task Manager observations.

[Kerensky]

Operation Barca is definitely pushing the limits of scenario size and unit count and map dimensions that Panzer Corps 2 can comfortably handle.

If you're having performance issues on this map, I strongly suggest reducing terrain graphical settings to help relieve the load on your Computer, and most specifically, your GPU. It's a behemoth of a scenario, and the technical aspects of scenario size of this magnitude... is partly why we so rarely have such gigantic battles.

[adiekmann]

I've had similar issues - if not even worse - than you described. This has plagued me since AO42, but started getting worse whereby the D-Day scenario in AO44 even the AI turn drags along with my ground units, where it used to only affect my aircraft. My rig is as of last month 5 years old now, but it was a pretty high end gaming machine at time of purchase. Still too good to spent thousands on replacing it - yet.

Processor Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 3.70 GHz
Installed RAM 16.0 GB
GeForce GTX 1080 Ti (11 GB GDDR5X)

[Kerensky]

I've got 32GB RAM and a GTX 3080 in this PC, but these specs are WAY above the game's recommended specs.

[DefiantXYX]

I am running a high end machine, could play jedi survivor on max details.
I am almost done with the scenario, but it definately has to do with planes. All ground units are fine. AI turns are also fine.
Right now I also remember some lags in my 1943 rerun, but only with the Me262.
There might be an issue with the models, I dont know. And there is another bug, one of my Me262 got shot down by russian fighters.

[Kerensky]

You know, thinking about this and when this problem first seems to have started a few DLC ago...

There was a big change regarding calculation of aircraft movement. I recall at some point aircraft stopped using their location to calculate movement and moved to using the airfield they were based at to calculate their movement.

This was done to make edge cases where a unit on a certain part of an airfield not really be able to reach something it might normally have, purely by the virtue of which hex it happened to occupy.

Could there be some kind of conflict going on here? Some remnant of the old system conflicting with the new system? I dunno, just trying to think out loud. That sounds like something that could result in performance issues strictly involving aircraft. The game struggling to digest conflicting information between unit movement points and recalculating movement points dependent on the location of the base of that aircraft?

[adiekmann]

You know, thinking about this and when this problem first seems to have started a few DLC ago...

There was a big change regarding calculation of aircraft movement. I recall at some point aircraft stopped using their location to calculate movement and moved to using the airfield they were based at to calculate their movement.

This was done to make edge cases where a unit on a certain part of an airfield not really be able to reach something it might normally have, purely by the virtue of which hex it happened to occupy.

Could there be some kind of conflict going on here? Some remnant of the old system conflicting with the new system? I dunno, just trying to think out loud. That sounds like something that could result in performance issues strictly involving aircraft. The game struggling to digest conflicting information between unit movement points and recalculating movement points dependent on the location of the base of that aircraft?

The "easy" way to check that theory would be to experimentally have one of the software engineers reset the responsible code back to the way it was before and conduct an internal test. That could either confirm or rule it out. Of course, I don't really know how "easy" that would be to do.

Otherwise, with 32 GB of RAM...if you have no issues that could also be a simple remedy. I have two empty RAM slots on my motherboard...

I've always guessed it had to do with your GPU card, but it would even sometimes make the sound crack along with the animation/movement. I know they have been looking into this issue for some time, but I find it puzzling that they can't determine what the cause is or at least haven't shared it with us.

[Grondel]

You know, thinking about this and when this problem first seems to have started a few DLC ago...

There was a big change regarding calculation of aircraft movement. I recall at some point aircraft stopped using their location to calculate movement and moved to using the airfield they were based at to calculate their movement.

This was done to make edge cases where a unit on a certain part of an airfield not really be able to reach something it might normally have, purely by the virtue of which hex it happened to occupy.

Could there be some kind of conflict going on here? Some remnant of the old system conflicting with the new system? I dunno, just trying to think out loud. That sounds like something that could result in performance issues strictly involving aircraft. The game struggling to digest conflicting information between unit movement points and recalculating movement points dependent on the location of the base of that aircraft?

The "easy" way to check that theory would be to experimentally have one of the software engineers reset the responsible code back to the way it was before and conduct an internal test. That could either confirm or rule it out. Of course, I don't really know how "easy" that would be to do.

Otherwise, with 32 GB of RAM...if you have no issues that could also be a simple remedy. I have two empty RAM slots on my motherboard...

I've always guessed it had to do with your GPU card, but it would even sometimes make the sound crack along with the animation/movement. I know they have been looking into this issue for some time, but I find it puzzling that they can't determine what the cause is or at least haven't shared it with us.

since the issue is not persistent and happens evrytime it cannot be related to something that is fixed.
i noticed this laggy behavior for the first time when the move and combat prediction was changed. 1942 dlc if i remember correct, but u guys probs have a better log about that than my brain.
since movement is always the same, combat prediction would be where i would look first.

sers,
Thomas

[Bee1976]

since movement is always the same, combat prediction would be where i would look first.

sers,
Thomas

I would assume the same. Combat predictions for planes behave wierd sometimes. On some maps you get combat predictions for all enemies in range just after selecting the plane. And if that happensi sometimes even recieve combat predictions for enemies in fog of war and partisan units.

[Tassadar]

since movement is always the same, combat prediction would be where i would look first.

sers,
Thomas

I would assume the same. Combat predictions for planes behave wierd sometimes. On some maps you get combat predictions for all enemies in range just after selecting the plane. And if that happensi sometimes even recieve combat predictions for enemies in fog of war and partisan units.

I could swear the AI planes sometimes abuse this and target things outside their potential visibility, but I just might be missing some occasional visibility of my units as they travel...

[Wolfenguard]

i think it has something to do with the sound files or maybe the camo
have some lags if you get to the camo area of the units,
for the sounds, get the lags startet at i think year 43 especially when the new aircrafts get to the start

[DefiantXYX]

I had less lag in the maps after the huge ones.Might be a combination of different things like map size, units, range and combat-calculations, camo and sound.

[Nexus]

Same problem here. Selecting Aircraft occasionally freezes the complete game for 1-3 seconds, independent of which map.
Also hardware should be plenty (5950x, 6800xt, 32GB) and game runs completely smooth otherwise, so I assume some issue in the way the game handles range or target predictions.

[Rudankort]

With optimizations made in the latest version 1.9.x, I can no longer repro this issue on my end. Is anyone still having it with the latest update?

[Raganr129]

In addition to regular unpassable crashes on my device (posted in the tech issues/bug section), I will confirm this issue is still happening for me (Ryzen 7 3800x, RTX 4090, 32GB RAM). Every time I mouse to a new unit, or new hex, I will see in the little unit selector that a random Japanese battleship elsewhere on the map will initially be previewed, and selected if I click too fast. I usually need to wait ~5 seconds to properly have my own unit selected.

I would speculate that maybe every time the cursor moves, it's almost like the map and unit positions are being redrawn/recalculated in the background, and either the number of units in all 1945/1946 scenarios are too heavy for my device, or too heavy for Unreal? I don't know, dev isn't my lane, but my computer should be plenty powerful enough to play this.

[Rudankort]

In addition to regular unpassable crashes on my device (posted in the tech issues/bug section), I will confirm this issue is still happening for me (Ryzen 7 3800x, RTX 4090, 32GB RAM). Every time I mouse to a new unit, or new hex, I will see in the little unit selector that a random Japanese battleship elsewhere on the map will initially be previewed, and selected if I click too fast. I usually need to wait ~5 seconds to properly have my own unit selected.

We've just released an update 1.9.3 which should address the issues above. Please let us know if you still experience any issues after updating (main menu should display version 1.9.3a at the bottom of the screen).