Matrix Games Forums

Hi,

I was testing a scenario and tried to launch some MiG-23s. They had a loadout with R-23Rs and R-60s. The side doctrine was set to "use default" for the weapon state RTB setting. Looking at the DB viewer, this is Shotgun for the AA loadout on the MiG-23 (one engagement with BVR weapons and then withdraw).

The aircraft took off, but immediately began to return to base.

I then tried changing the doctrine setting manually to "Shotgun (expend all BVR weapons and RTB)", not "default" which I assumed might be the issue.

The aircraft showed the same behavior.

I previously reported a similar issue, but it was an error on my part in that I had selected a setting using BVR weapons when the aircraft did not carry them- https://www.matrixgames.com/forums/view ... 5#p5141535

However, this time the issue occurred while the weapon state RTB doctrine was set to default, and then occurred again when set to a proper setting matching the loadout.

I have attached the scenario in question. I was originally running the last official update, but upgraded to the new hotfix (.18) to see if that was the issue. I also upgraded the DB to the latest (505). The same issue occurred.

I also tried assigning the aircraft to a mission to see if that was the issue, because originally I was planning to manually launch and control them. The same behavior occurred even when assigned to an AA patrol.

Thank you.

Hi Sunlit, when I set the CAP missions weapon state to "inherited: use loadout setting" in the scenario you provided it works just fine. If you do that from the start of your scenario are you still seeing the same behavior?

I tried setting up a new CAP mission just now, with the default doctrine for weapon state RTB, and I get the same results. I attached the same scenario but saved after I tried it again.

Notice that the two MiG-23s from the 85th Guards IAP are on final descent for landing. Their status shows "RTB (Winchester)" despite the mission having just begun and both being fully armed.

Isn't it this problem: https://www.matrixgames.com/forums/view ... ?p=5135507

It should be solved with new database which was available with patch 1328.16

EDIT: I see it is different issue.

Hi, I tested another mission in the editor to see if it worked, and I'm unable to reproduce the issue. It only occurred specifically with that "Air Operation" scenario I made.

I don't know what happened, maybe the scenario I made (Air Operation) is corrupted somehow?

I think this can be written off as "unable to reproduce" or whatever. Thanks for the help and sorry if this wasted time!