[FIXED] RTB (mission over) regardless of doctrine

[Frogs111]

Hello

I had problems with aircrafts RTB after using their strike munitions regardless of what weapon state doctrine I set.
And if I try to unassign units to stop them from RTB their status does become "unassigned" but after I un-pause they go back to "RTB (mission over)"
It seems to happen in every scenario, and I think it might have started happening after update v1.06.1328.12.

Example.PNG (1.87 MiB) Viewed 1851 times

In this Sinai Shootout 2022 scenario I tried playing around with missions and doctrines to try to fix it, but it still seems to happen.

Sinai Shootout 2022 why.zip

(852.72 KiB) Downloaded 27 times

Thanks in advance.

[Tred]

I'm having this problem too now. I like to micro-manage my forces and now, regardless of doctrine setting, after firing primary weapons many of my planes go to "mission over RTB" and start heading home when I want them to stay where I plotted them to.

I never noticed it happening before the latest update.

[jbgull.42]

--Deleted because fully off topic.--

[maverick3320]

I have the same issue as the OP.

[Tred]

Hi folks.

Was this zip submission adequate to establish this as a confirmed bug?

As I posted earlier, I like to micromanage, but not THIS much. Lol. I have a Korean conflict scenario I've made and every time my F16's fire their standoff missiles and I manually plot them to low altitude positions to be ready to intercept waves of UAV's and helicopters pouring across the DMZ, I find that since their primary missiles have been fired, after getting to the position and low altitude I want them at, they are RTB "Mission over" and climbing once again no matter the RTB settings.

It's so frustrating I've stopped playing hoping the next update will fix it. But I'm wondering if it has been confirmed as a bug or if I need to try reinstalling or something.

Thanks.

[blu3s]

Hi,

Could you provide a simple test scenario where this is happening?

Usually this type of behaviour is due to a missconfiguration between the Doctrine and the Loadout of the Aircraft.

To cancel a RTB just press U and plot a new course or assign a new task to the aircraft that is RTB (mission over)

[Tred]

Thanks Blu.

I'll try and set up some test scenarios later today when I get time and see if I can reproduce it. But it is the case that this behavior is new to latest update (1328.12). In my same scenario, my F16's never deviated from the spot and altitude I manually plotted them to with the no RTB setting, to "Mission over" and begin returning to base. They just stayed there and flew in circles like I wanted them to.

But I'll play around and try to reproduce...and hopefully overcome my computer ignorance to submit it successfully or let you know it's a non-problem after all. Lol.

[Swant]

Here is one example where a flight of F-35 B gets RTB (Mission over) status. Even if you cancel the RTB it will return immediately

[Tred]

Okay, so I reproduced it. Again, this never happened before the latest update.

Here my F16's have fired their AGM-158A JASSM's at North Korean positions after being manually plotted to get within range. They fire the missiles, but as soon as they hit their plot, they go to "Mission over" and RTB, even though I have the doctrine setting to NOT RTB after firing primary weapons. In all other versions of the game, the jets do as I want and sit at the plotted position at the correct altitude I tell them to and fly circles awaiting orders. Now, as soon as they hit the plot point, they RTB and gain altitude to do so.

CMO test 1.png (2.06 MiB) Viewed 1347 times

Here is from the same screen shot. The selected F16s are still on their original plotted course, but have already fired their JASSM's. As soon as they hit the end of the plotted course, they will go to "Mission Over" RTB, in spite of doctrine settings. I CAN plot them elsewhere, like to lower altitude closer to the DMZ to await North Korean helicopters, but again, instead of circling at the plot point and correct altitude, as soon as they get there, they will climb and go back to RTB.

CMO test 2.png (2.26 MiB) Viewed 1347 times

And now I'll attempt to save a zip file correctly so you can better evaluate.

Test Jan 2024.zip

(211.93 KiB) Downloaded 25 times

If it's a bug, I hope we can get it fixed soon. This totally messes with my micromanaged style of play.

Thank you!

[blu3s]

Thanks guys, it will be investigated.

[blu3s]

Logged #0015489

[Tred]

Thanks, blu.

I just ran a test with the new update and it appears this is no longer a problem. But I didn't see the log# included in the list of fixes. Did this make the cut?

[Nikel]

Must be this line without number.

• FIXED: Some ACs where not RTB

[Tred]

Must be this line without number.

• FIXED: Some ACs where not RTB

I dunno. My problem was that some of my aircrafte WERE RTB after firing their stand off weapons and wouldn't not go to "mission over RTB" when I plotted them to stay in a certain position, in spite of the settings.

I'm not complaining, mind you. I'm absolutely overjoyed it seems fixed in this update and I can play again. I'm just confused by not clearly seeing it in the fix list.

[Nikel]

Sorry, then there must be an error in the line.

[blu3s]

Thanks, blu.

I just ran a test with the new update and it appears this is no longer a problem. But I didn't see the log# included in the list of fixes. Did this make the cut?

Hi Tred, in the last test performed, the aircrafts were able to plot a new course even when they have RTB in their status. The RTB it's declared as WAD since per doctrine once you expend your primary weapons, the status should be RTB, but you can assign the unit to a mission or just plot another course with no problem.

Let me know if you encounter this issue (or another related)

Thanks.

[Tred]

Hi Tred, in the last test performed, the aircrafts were able to plot a new course even when they have RTB in their status. The RTB it's declared as WAD since per doctrine once you expend your primary weapons, the status should be RTB, but you can assign the unit to a mission or just plot another course with no problem.

Yes, that's what I'm seeing now with the new update, blu. I'm not seeing the "mission over" status like in the previous version (1328.12). Then as well as now, I can plot units after primary stand off weapons have been fired, it was just that whenever they got to the end of their plot, they then immediately began to RTB again (including climbing in altitude) instead of staying where and at the altitude they were plotted to.

They are not doing it in this update (at least on my first test). They are staying put, flying in circles at the properly plotted point and at set altitudes in "unassigned" status and NOT climbing and returning to base like in version .12. Which is what they always did in all previous versions before 1328.12. I'm quite happy.

But what changed? Did you folks fix it? Or did it just stop somehow with the new version?

Thanks again. So far, so good!

[Dimitris]

This should be fixed in the next update release.

[CHM]

This problem exists as of v1.07

[blu3s]

This problem exists as of v1.07

Can you please open a new thread with a suitable save to repro the issue?

Thank you