Crash during sub move

[Bavre]

Hi,

I've repeatedly experienced crashes while moving subs in silent mode using waypoints. Not sure what the error message is trying to tell me. The screenshot below is from challenge ID 345624, but I've had the some occur several times in 337965, too.

[Hubert Cater]

I suspect this might have something to do with the mod you are running. Can you tell me if this is a graphical mod straight from the Community Pack? Or a customized version?

[Bavre]

Sorry for the delayed answer.

And yes its a compilation of Sipres Nato-Counter Mod and Welks Board Mod. I was not aware that a purely cosmetic mod could cause that.

[Hubert Cater]

Thanks for the follow up information and it could potentially cause an issue if the mods are not properly matched to the default graphics, e.g. each modified file does not have the equivalent width and height of the default originals. Reason being is that the defaults have had some changes implemented to them over the various patches, new sprites added and so on, and if the mods are not up to speed some issues may arise.

One way to confirm is to double check the modified files and look for differences, or to just try the same moves without the mod running to see if it works or not without the same crash occurring.

[Bavre]

I just found the corresponding error log:

[2021-11-09 22:17:56 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-11-09 22:17:56 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.22.02] FAILED(on_left_button_down): attached active as a
[2021-11-11 13:27:50 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-11-11 13:27:50 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.22.02] FAILED(on_left_button_down): attached active as a
[2021-12-15 13:25:33 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-12-15 13:25:33 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.23.00] FAILED(on_left_button_down): attached active as a


Doesn't this look more like a pathfinding issue?

Also the games are currently on hiatus due to christmas holidays, so this issue can absolutely wait.

[Taxman66]

Suggestion:
Turn the mods off and rerun the test.

[Bavre]

ORIGINAL: Taxman66

Suggestion:
Turn the mods off and rerun the test.

The problem is that while it only seems to happen under the above circumstances, I could not reliably replicate it. Most sub movements in silent mode don't cause crashes and I haven't figured out yet what makes the difference. The above picture is from an MP round that I was able to sucessfully complete on second try. I did move the sub in question in basically the same manner, but maybe on a slightly different path ???
Also note how weird the movement area of the sub in the picture is. IIrc the area I was about to move into contained a significant Royal Navy presence, maybe that has something to do with it?

Will try without the mod for now, though.

[Hubert Cater]

ORIGINAL: Bavre

I just found the corresponding error log:

[2021-11-09 22:17:56 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-11-09 22:17:56 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.22.02] FAILED(on_left_button_down): attached active as a
[2021-11-11 13:27:50 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-11-11 13:27:50 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.22.02] FAILED(on_left_button_down): attached active as a
[2021-12-15 13:25:33 PM] FAILED(calculate_shortest_unit_controlled_movement_path): attached active as a
[2021-12-15 13:25:33 PM; 6.2.9200; 2560x1080x32(1); SC3: WWII War in Europe v1.23.00] FAILED(on_left_button_down): attached active as a


Doesn't this look more like a pathfinding issue?

Also the games are currently on hiatus due to christmas holidays, so this issue can absolutely wait.

That does indeed look like a possible path finding issue, but to be sure, if the mod is off while you continue to play and test, that can at least help us to narrow it down as this is as you've mentioned not an easily repeatable error on your end.