reported 2.8 AI Pathing of ground UNITs (esp mobile SAMs e.g. SA13) cause crash when trying to EXIT out of mission unless vehicles are moving.

[TEMPEST.114]

I've just done a full clean / repair on DCS 2.8 latest version from today, also no mods, no scripts. 

The game hangs when I hit 'quit' from the in-game menu when inside my F14. 

Other aircraft is fine. 

[TEMPEST.114]

I just added an F18 to the Supercarrier and I couldn't exit out of that aircraft back to the game menu...

Maybe it's a supercarrier issue? I'll try again with the Forrestal / Stennis.

Also hangs on Left Shift R to restart mission

UPDATE: Still hangs on leaving the Stennis and Forrestal

Edited November 2, 2022 by Elphaba

[Flappie]

Please reproduce the issue, then attach your dcs.log file (Saved Games/DCS.../Logs/dcs.log).

[TEMPEST.114]

I've been debugging the mission (no mods, no scripts, just vanilla units).

I thought it was the F14, then the carriers. 

This mission is about 3 months old. It's been played about 3 or 4 times and every time it's worked perfectly until 2.8

I have found the unit that was causing the issue. It was two RUSSIAN SAM SA-13 Strella 10M3 "Gohper" TEL units that are driving 'off road' over the mountainous area in southern Chile on the South American map. When I remove those two units (they were for LANTIRN target practice) then everything works normally and the game doesn't hang/crash on exit. 

When I run the mission with them in and try to exit. It just hangs until windows gives up on it and forces me to close it. 

I've deleted them. Saved the mission as a new name, and then re-added the same units but as new units and tried the mission - and it crashes again.

It's something about those units...or the terrain...

Tried it with SA-8's and it still crashes. Remove those two units and mission / game works normally... Has something changed with the terrain?

 

Replaced them with T90's and it still crashed... BUT when I was looking at the T90's at mission start the lead just span in place 360 degrees and stopped - despite the first waypoint being miles away. Then about 2.2 mins into the mission they started moving - and once they were moving I tried to quit and everything is okay. Is this related to the newly broken 'goToWaypoint' tasking bug just introduced in 2.8?

 

I then put the SA13's back in and again the first unit spun in 360 degrees but didn't move and they never moved even after 15 mins. The engines were running and it was rotating anti-clockwise very, very slowly, but they never moved and when I tried to quit, DCS hung. 

I'm now thinking that there is something screwy going on with pathing for AI units (ground/sea) that's getting stuck in a some loop and killing DCS if you try and quit whilst it's stuck. 

Edited November 3, 2022 by Elphaba

[Flappie]

That, sir, is an excellent bug report.

Can you please attach your mission file?

[TEMPEST.114]

6 hours ago, Flappie said:

That, sir, is an excellent bug report.

Can you please attach your mission file?

Not a 'Sir'. I thought the name and the photo would have been enough of a clue... 

I'll pull it out and attach it.

[TEMPEST.114]

Okay, so this mission has the red SA13's unhidden so you can F7 to them. 

You will see they don't do anything - never move. They might (VERY) slowly rotate in place but basically don't do anything.

If you try to quit the mission, it will hang DCS and crash it (eventually).

If you replace them with T90's they will not do anything properly for a while (try and quit and again you will crash). 

But, once they start moving you can quit and it works normally.

Removed the red convoy entirely and you can quit immediately with no problem. 

There are no 'goToWaypoint' commands in this mission of mine, but in other ones (and in ones by other members) if you do specify a waypoint to go to the units will stop at that waypoint and not continue on to the next one.

BrokenBow.miz

[Flappie]

My apologies, Captain! I did not know the Elphaba  character until now, and I was browsing on my tiny mobile phone, on which I would not be able to tell between Monroe and DiCaprio.

Many thanks for the mission file. Crash reproduced and reported.

Here's what we can read in the log file:

2022-11-07 07:31:46.528 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!!

 

Edited November 7, 2022 by Flappie

[TEMPEST.114]

18 hours ago, Flappie said:

My apologies, Captain! I did not know the Elphaba  character until now, and I was browsing on my tiny mobile phone, on which I would not be able to tell between Monroe and DiCaprio.

Many thanks for the mission file. Crash reproduced and reported.

Here's what we can read in the log file:

2022-11-07 07:31:46.528 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!!

 

 

No worries...

I saw that too, many times - not just in this mission but in many missions, and aside from the obvious typo (TAKES rather than MAKES correct?) Is this something that has been added in 2.8 that waypoints are now limited on length or numbers?

[Flappie]

On 11/8/2022 at 2:40 AM, Elphaba said:

Is this something that has been added in 2.8 that waypoints are now limited on length or numbers?

I don't think so. I saw the exact same error message, typo included, in previous reports.

[mousepilot]

Hi everyone,

Just wanted to add that I'm also experiencing this issue.
 

2023-10-22 14:57:32.010 WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!!

2023-10-22 14:58:09.010 WARNING LOG (2004): 30 duplicate message(s) skipped.

This happens after I set some units to "move" using the Controller.setTask() function.

Edited October 22, 2023 by mousepilot

[Flappie]

Yes, the message is triggered whenever DCS is struggling to determine the shortest path to the destination. It can happen when the destination is:

1. Very far away
2. And/or over mountains without roads

Which terrain was it? What were the location of the vehicle and the destination point?

[mousepilot]

It's off-road terrain, but the destination is close to the origin point.

[Flappie]

Can you please attach your mission so I can reproduce the issue?