Jump to content

Recommended Posts

Posted

I have tested both the BS and A-10 in 1.2.1 and 1.2.0. The trigger logic for the "Prevent controls synchronization (on/off)" is broken. This trigger is especially useful for my training missions that start in the air.

 

Prior to these versions when you used the trigger to prevent the controls synchronization, the aircraft would start in the air at a specified speed and maintain that speed until the pilot would move the controls and take over.

 

For example, in my weapon training mission, the BS starts in the air during the introduction and then instructs the pilot on how to enter the auto-hover state. As soon as the pilot presses a control on the hotas or the keyboard it would turn off.

 

With the new versions it does not matter if the prevent controls trigger logic is on or off or even in the list of triggers because it simply does not do anything. As soon as the trainee enters the game, if their hotas was in the off position or idle state, they will practically enter a vortex ring state right after pressing play.

 

I also tried the trigger with the option in the settings disabled or active. It made no difference. Has this trigger logic changed or does it affect something different now?

 

You can test this in 1.1.1.1 by creating a mission and set a player controlled a-10 or BS in the game. Under triggers, set a mission start > no condition > prevent controls sync "on" trigger. Fly the mission.

DCS: A10C Warthog JTAC coordinate entry training mission http://www.digitalcombatsimulator.com/en/files/99424/

 

DCS: Blackshark 2 interactive training missions http://forums.eagle.ru/showthread.php?t=84612

  • Recently Browsing   0 members

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