QC Quirk

[wsmwsm]

Every so often, immediately after starting a standard QC dogfight, I instruct the wingmen to attack a specified aircraft and for some unknown reason, get the "can't comply" response(s). They are in the air and unengaged and there is no explanation for this.

The only way to then fix this problem is to delete the uisel, restart, reset everything and move on.

Doesn't happen a lot but is annoying. There seems to be a connection to using driveable vehichles shortly before switching to a QC dogfight, but that I am not certain of that. Seems to occur when using ETO more than MAW, PTO, etc.

Has anyone else experienced this and is there a fix of sorts?

 

[italflyer]

check the loadout of your aircraft. Usually for dogfight choose "mpty" or "nothing" or something similar.

 

[wsmwsm]

That's not it. I can run a QC mission without a problem, end the flight, then return to the same mission without changing any aspect of it. . . but after targeting and requesting an attack, I get the "can't comply" response. And I always run with the loadout clean.

 

[MajorMagee]

Sometimes they're just out of position, or they've already become engaged with defending themselves.

 

[Daiwilletti]

There have been a number of threads on this subject over the years....unfortunately I can't remember the thrust of them
The loadout thing is one that was raised as a possible solution. Another aspect to this is that in the xdp file, a loadout is sometimes associated with a particular mission type. Try editing the mission types for the loadouts in the xdp of the aircraft you are using in the qc mission and see if this helps?