Autonomous Ground Force Tasking

[gromit190]

Sorry, I can't test this mission. It won't open. Probably since I'm on the (older) Steam version.

 

To be able to fix this bug, I'm gonna need some investigation from you guys.

[gunterlund21]

gromit is 1.15 ready I dont see the main lua. So Ive attached your old mission labelled 1.14. Problem with this mission is you reference a version of your lua as 1.9. If you use this nothing happens. Then I loaded in the lua labelled autogft_1.14 instead. This crashes immediately saying it cant find addgroup in your lua. So not sure what example to give.

example-1_14.miz

[gunterlund21]

Here is another version of 1.14. this has code in it that doesnt crash but no units move.

example-1_14.miz

[gromit190]

Hi,

 

You're right, there seems to be an issue with the 1.14 example. Not exactly sure what it is. But anyways, I fixed the example now with 1.15 code. Tested, does not crash for me.

 

(download 1.15 here)

 

Gonna test your (non-crashing) 1.14 example now

[gromit190]

Here is another version of 1.14. this has code in it that doesnt crash but no units move.

 

This mission works as it should for me. Units gets routes and moves as they should.

 

Let's take a different, minimalistic test mission (test.miz attached) for debugging. This mission works 100% for me. The unit gets a route, and it starts moving towards its target.

 

Please test this mission, and answer the following questions:

 

1. Can you load this mission to the mission editor without any error?

2. Does the unit get a route? (Play as tactical cmdr to see the route)

3. Does the unit move at all?

4. Are there any error messages in the log?

test.miz

[Taslehoff]

Hi @gromit190 I have run this on the beta version. The blue unit does not move but the flag for the routing changes to different locations. I tried advancing the time compression to see if it would move but no luck.

[gromit190]

Thanks! Can you try adding a unit to your mission, and give it a route? I mean the regular way, not using autogft. If that unit moves then there must be some kind of difference between a units "autogft route" and a regular route.

[gunterlund21]

 

This mission works as it should for me. Units gets routes and moves as they should.

 

Let's take a different, minimalistic test mission (test.miz attached) for debugging. This mission works 100% for me. The unit gets a route, and it starts moving towards its target.

 

Please test this mission, and answer the following questions:

 

1. Can you load this mission to the mission editor without any error?

2. Does the unit get a route? (Play as tactical cmdr to see the route)

3. Does the unit move at all?

4. Are there any error messages in the log?

 

ok downloaded the mission

1. mission loads into the editor with no issues

2. Unit gets a route but speed is set to 0

3. unit does not move at all

4. no errors in log see attached.

dcs.log

[gunterlund21]

did another test with adding a unit. If you place a unit outside of the starting circle and give it a waypoint it will move on its own. If you place them inside of the starting circle, they get routes but dont move.

[gromit190]

 

ok downloaded the mission

1. mission loads into the editor with no issues

2. Unit gets a route but speed is set to 0

3. unit does not move at all

4. no errors in log see attached.

 

Thanks!

 

Tried to find the bug tonight, but no joy. Will investigate this more later.

[gunterlund21]

keep up the good work Gromit we really appreciate it.

[MikiBzh]

Yes, thanks Gromit for that.

Much appreciated.

[gromit190]

I've isolated the problem at least.

 

What autogft does is it creates 2-6 waypoints (depending on the setup and how far it is until the next objective).

 

It will appear like the unit does not move at all but actually the first waypoint is just really close to the unit position. So it moves just a couple of meters to get to it in the beginning of the mission and then it stops.

 

For some odd reason, DCS only moves the units to the first waypoint and stops at it. It just ignores the next route waypoints.

 

Has anyone heard of other scripts experiencing a similar problem? Right now I'm going to test a regular route with 2 waypoints to see if that works.

[gromit190]

While I investigate how to properly fix this bug, you can probably use this version with a temporary workaround: https://github.com/birgersp/dcs-autogft/releases/tag/1.17

 

This might be a bit buggy, especially considering running on roads. But give it a go if you want.

 

Also if you have any information that would help me identify what has changed on the DCS scripting engine. Tried looking at the hoggit wiki but it gave no answers to why the autogft logic stopped working.

[gunterlund21]

Did you check on the dcs world discord channel. Do you have more detail on how you get units to move

 

[gunterlund21]

Hi Gromit. Tried 1.17 and this also did not work. No movement at all. Didnt see routing flags either.

 

[gromit190]

Okay. I did just to a quick test before generating 1.17 so I might have missed something. Will keep trying to solve it.

 

One thing I struggled with yesterday was creating a simple script that just gives a group some simple task (route). Because that would really help me debug this error, by comparing the task data that autogft generates with raw task data that is manually made and works. Will continue fixing this later.

 

BTW I am using the open beta version now for testing.

[gromit190]

Been trying to solve this. Honestly, there must be some kind of bug with DCS. I can't explain it any other way. For some reason it seems that the unit is only moved to the first waypoint in the route. But only if the route has more than 1 waypoint (?). This is the same case even when I script some route "manually" (not using autogft) for the units.

 

For those of you that have the bug, what DCS version are you using?

 

Please keep your eyes and ears open if anyone else has this bug. I tried asking on the mission editor channel on ED discord, but it seems idle.

[gunterlund21]

gromit did you submit a bug in the 2.5 forum?

 

[gromit190]

Hi all,

 

I just tested the Steam version, non-Steam version and open beta.

 

Steam version and non-Steam version works with autogft 1.18. I just tested a basic example and the example mission (which uses a lot of various features of autogft).

 

Open beta does not work. I don't know why, but there is some kind of bug where only the second waypoint of a two-point route will work.

 

For those of you that experience an error, please state what version of DCS World you are using.

 

Download autogft here.

[gunterlund21]

GROMIT Im running beta. If you break out your code that crashes and post it in the dcs forums Ill bet they will address it.

 

[Taslehoff]

Hi  @gromit190

 

Have you had any luck mate?

[gromit190]

Hi,

 

No, sorry. I probably won't spend time on investigating this further. I don't use the beta, so I am not really that dedicated to debugging it.

 

But when I checked, the error was that assigning waypoints in lua does not work the same way as it did before. So the scripting docs (what little there is) doesn't correctly explain how to create routes. (Unless they changed it since I last checked).

 

Whoever wants to investigate the bug, feel free. I and others would really appreciate it

Edited January 20, 2021 by gromit190

[gromit190]

I recently got back into DCS so I've started investigating the error again.

 

 

[gromit190]

Seems ED fixed the scripting engine again!

 

So everything should be in order now. Just tested the example mission myself on latest version of DCS World open beta.

 

https://github.com/birgersp/dcs-autogft/releases/latest/