DCS World Ver 1.2.2.7286 - Uncontrolled option box and action

[MadDog-IC]

Something I think needs fixing.

 

If you set a farp with AI controlled ka-50 to:

 

• Take off from ramp and have set the UNCONTROLLED OPTION ENABLED and then change your mind and change the waypoint to Take off from runway the UNCONTROLLED OPTION DISAPPEARS, but remains in effect, causing AI craft not to start automatically on mission start.
  

Mission Editor needs to force the Uncontrolled tick box off when changing back to Take off from runway, or leave it displayed so you can see that it is enabled (But I am thinking it isn't suppose to be available under those conditions).

 

 

Cheers, Ian.

[USSR_Rik]

Confirmed, thanks.

                    ["helicopter"] = 
                   {
                       ["group"] = 
                       {
                           [1] = 
                           {
                               ["modulation"] = 0,
                               ["tasks"] = 
                               {
                               }, -- end of ["tasks"]
                               ["task"] = "CAS",
                               ["uncontrolled"] = true,

 

Good catch!

[USSR_Rik]

Fixed in internal version.

[MadDog-IC]

Fixed in internal version.

 

 

Thank you, whilst playing with the previous problem had other issues:

 

senario:

4 Flights of USA ka-50 on 4 farps, all Ai. One Flight on automatic start up at 7:0:0/0, the rest set to a later Start of 7:0:0/999 and Activated at different intervals during the mission via flag triggers.

 

When using the delayed starts for other flights, the flight that started automatically at mission start tends to behave differently in regards to flight to waypoints and other tasks and or commands. Some of the farps that the ka50 leave from become marked as enemy (do show as USA in map) and are attacked by some of the friendly AI ka50's.

 

Attacking of farp will also happen if any flight has the ROE set to Weapons Free, or OPEN FIRE, WEAPONS FREE and also if HOLD FIRE is set they will still fire at enemy.

 

Really can't nail it down what is going on in mission as apart from that, but as soon as those farps look like enemy, a flight ignores all waypoint programming, drops everything, races back to the farp, unloads all of it ordinance onto the farp.

 

This is a real mission killer as you can imagine. I setup a ai flight to mimic a player playing the mission, so I can test all logic in the mission to make sure it works, but when the mission editor and basic program has so many fundimental issues, it is all but impossible to solve, if it is me doing something wrong or a bug.

 

Anyway thanks in advance

 

Regard, Ian