Jump to content

Recommended Posts

Posted

DCS 1.5.5.60338.212

 

Hello,

 

Is it possible that the "follow" task is broken with this update as well?

 

I've been trying to set it up without any success, I did the same in DCS 2.0.4.59428.142 and it works fine.

 

I'm joining the mission file for both versions, 1.5 and 2.0. In a nutshell, what they do

- it is a SP mission - just a basic test, don't expect anything fancy ;)

- there is one group with the player, one CAP group for the AI

 

The interesting waypoint for the AI does this:

- orbits until a user flag gets the value 1

- follows the player's group (until last waypoint of the player's group)

- switches to a waypoint (and goes on)

 

There are a few debug messages to indicate the transitions. In 1.5, I see that the "follow" task doesn't last, it directly shows the message I've put before then after this task.

 

In 2.0, it remains in the "follow" task, and very obviously follows the player's group.

 

Did I do something silly with the 1.5 version? Or is this an issue with this task?

 

Thanks

M-2000C.Kobuleti.Follow.miz

M-2000C.Follow.miz

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

Edited a little bit. It works.

 

I thought Follow command worked with "Last WPT" but it doesn't. Perhaps if it follows another AI. Now it's another trigger zone at player WPT2 that sets flag 2 to true when the player enters the zone..So, I used stop condition "User flag is true - 2" on the Follow command. Then comes the Switch Waypoint command that sends the Follower to his WPT3.

 

Open the mission up, look at how I set it up and enjoy :) :smartass:

 

There may be other ways to go about this but this is the way I chose.

 

 

MAYBE, if the PLayer was another AI and not a player. You would not have to use the stop condition, but the "Last WPT" stop condition set to WPT2 would work as intended.

M-2000C.Kobuleti.Follow.miz

GPU: PALIT NVIDIA RTX 3080 10GB | CPU: Intel Core i7-9700K 4,9GHz | RAM: 64GB DDR4 3000MHz
VR: HP Reverb G2 | HOTAS: TM Warthog Throttle and Stick
OS: Windows 10 22H2

Posted

Thanks!

 

... but that doesn't work with me. What version of DCS do you have?

 

I directly get the second message (Player reached WPT2. Follower resuming own navigation. Pushing to WPT3, Batumi, Long Final, RWY), and it doesn't follow.

 

So that's what I feared, that's something else that broke with the latest updates :/

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

Thanks for the confirmation! I reported that in the bug section.

 

If Chrisofsweden is with a previous version of 1.5.5, that would also confirm the bug appeared at the same time as the "part of group in zone" trigger problem, which is very likely.

System specs: Win7 x64 | CPU: i7-4770K | RAM: 16 GB | GPU: GTX 980 Ti 6 GB | Thrustmaster HOTAS | MFG rudder pedals | SATA3 SSD | TrackIR

Posted

Yep....since following occurs at the group level, and player flights are no longer recognized as groups, it stands to reason that following would be broken for player flights...

 

Hoping we'll see a patch this Friday to un-bork this latest update, it is definitely making a lot of problems for a lot of people.

  • 6 years later...
  • 9 months later...
Posted (edited)
On 10/29/2023 at 12:35 AM, dorianR666 said:

lol, follow task (ai chasing player) still doesnt work

7 years now

 

Not sure what you're talking about, but here the follow action works just fine... (and it has for as long as I can remember)

Made two test missions:

  1. AI1 start in orbit, when AI2 is in triggerzone flag=1, AI1 start follow AI2, when AI2 is at WPT2, AI1 stops following (works like a charm)
  2. AI1 start in orbit, when player is in triggerzone flag=1, AI1 start follow player (the "LAST WPT" tickbox in the follow action menu, only works for AI-follow-AI)(but you can very simply make the AI stop following you by adding another trigger/flag)

 

 

AI follow AI test mission.mizAI follow player test mission.miz

 


 

Edited by sirrah
  • Like 1

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

Posted (edited)
36 minutes ago, sirrah said:

AI1 start in orbit, when player is in triggerzone flag=1, AI1 start follow player (the "LAST WPT" tickbox in the follow action menu, only works for AI-follow-AI)(but you can very simply make the AI stop following you by adding another trigger/flag)

yeah last wpt is what i was doing

but thats still a bug

 

i find that dcs mission scripting is full of these subtle bugs that are absolute time sink to discover and find work arounds for.

Edited by dorianR666

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

Posted
1 hour ago, dorianR666 said:

yeah last wpt is what i was doing

but thats still a bug

 

i find that dcs mission scripting is full of these subtle bugs that are absolute time sink to discover and find work arounds for.

 

Not sure if it's a bug.

Perhaps DCS AI is just not able to determine when/if a player/client reaches a certain waypoint. But as I mentioned in my previous post, it's super easy to just add another trigger/flag to have the AI stop following you.

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

Posted
42 minutes ago, sirrah said:

Perhaps DCS AI is just not able to determine when/if a player/client reaches a certain waypoint.

it works with escort though

CPU: AMD Ryzen 5 1600X

GPU: AMD RX 580

Posted
1 hour ago, dorianR666 said:

it works with escort though

Ah I see 🤔

Strange indeed then (shouldn't be a showstopper for mission building though)

System specs:

 

i7-8700K @stock speed - GTX 1080TI @ stock speed - AsRock Extreme4 Z370 - 32GB DDR4 @3GHz- 500GB SSD - 2TB nvme - 650W PSU

HP Reverb G1 v2 - Saitek Pro pedals - TM Warthog HOTAS - TM F/A-18 Grip - TM Cougar HOTAS (NN-Dan mod) & (throttle standalone mod) - VIRPIL VPC Rotor TCS Plus with ALPHA-L grip - Pointctrl & aux banks <-- must have for VR users!! - Andre's SimShaker Jetpad - Fully adjustable DIY playseat - VA+VAICOM - Realsimulator FSSB-R3

 

~ That nuke might not have been the best of ideas, Sir... the enemy is furious ~ GUMMBAH

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...