Datalink problem

[Auroraw]

Today I installed BS2 on my new PC, so I am using the latest version both of bs and world.

When I order my wingman to engage a datalink target, he says affirm and flies away, then after about 10 to 20 seconds he says rejoin.

I included a track, i'd appreciate it if somebody would take a look. Maybe i'm doing something wrong?

I appreciate your help!

Datalinkproblem.trk

[Devrim]

You didn't reset targeting mode system before sending.

 

Edit: No, sorry. You did (later). But according to my track replay, you're not completing the giving command. The last step, you should press F1 or F8. But you don't.

I see the 3. Main.Flight.Engage command list on the screen.

 

I clicked on Take Control and just hit F1. Pilot told the command and wingman did it...

Edited January 19, 2013 by Devrim

[Yurgon]

I haven't flown Black Shark in a while, but this problem is quite common in the A-10C and I also recall tons of stupid wingman behavior in earlier versions of Black Shark. My guess is that you guys didn't do anything wrong at all, but unfortunately I haven't really found a way to force AI wingmen to follow orders. :cry:

[Erforce]

Because it was mentioned somewhere that datalink bug was resolved since 2 months?

There was a large amount of threads about this.

[Erforce]

Sadly, i also tried to make a thread about known bugs in BS a while ago, but the few who responded just told me why i am playing with Electronic safeties disabled for the Engines... :surrender:

 

http://forums.eagle.ru/showpost.php?p=1565153&postcount=1

 

I'm still looking helpers for that though:smartass:

[tietze]

Sadly, i also tried to make a thread about known bugs in BS a while ago, but the few who responded just told me why i am playing with Electronic safeties disabled for the Engines... :surrender:

 

http://forums.eagle.ru/showpost.php?p=1565153&postcount=1

 

I'm still looking helpers for that though:smartass:

 

Having a known bugs list pertaining to the Black Shark module in DCS World is a really good idea. But:

 

• the thread needs to be put in the DCS World bugs forum
  
• a track documenting every bug should be present along with time bug surface in that track
  
• a description should illustrate the chain of events leading to the bug

 

One problem is that discussion sometimes swamps whether something is a bug or feature. Take the "shkval going nuts problem" or laser ranger showing different distances to target. Is it a feature of the simulation or a bug?