Matrix Games Forums

According to Turtrial Message, when Strike#3 using all CBU105 but not destroy Target3, you can turn on A/G Strafing and use the gun against them. But Strike#3 always automatically RTB and don't follow the order. Even if you press the U clear command beforehand, it won't work. Did I do something wrong? Or is this a bug?

Save file

In the old video on the internet, I found that when pressing the U button, the plane would enter a state called RTB order cancelled after reaching fuel/weapon state, but now this state does not appear.

There should be a doctrine setting called "Weapon State RTB." Try setting that to "No aircraft do not RTB when weapon state is reached" (before launching on the mission) and see if that helps.

boogabooga wrote: Mon Feb 05, 2024 3:29 am There should be a doctrine setting called "Weapon State RTB." Try setting that to "No aircraft do not RTB when weapon state is reached" (before launching on the mission) and see if that helps.

This is not a problem with the doctrine. I confirmed with my friend that he could cancel RTB by pressing U while playing before, without changing the doctrine at all. And this bug is not present in Steam old 32 bit legacy version.

3579663494,

change the doctrine, as boogabooga advised, then press U. It works.

ClaudeJ,
Changing the doctrine is effective, but in reality, there should be no need to change that, as the tutorial tells you. In 32bit legacy version on Steam. I haven't changed any doctrine except for A/G Strafing, all I need to do is just press U, then completing the strafing task, and press B to RTB the aircraft again. It's very simple. （Pay attention to the status of the aircraft）

So when the situation is correct, there should be a function where you can order an aircraft in RTB status to cancel RTB and perform tasks independently without changing the doctrine, all you need is just pressing U and B keys. This ran correctly just a few months ago.

https://www.youtube.com/watch?v=lD3xT7F5Cqg&t=1454s
look this video in 23:00

https://www.youtube.com/watch?v=tDfAQo8jzlk
and this video in 18:32 and 22:10

I think you are right that there has been a change... seems that the Winchester/RTB condition is detected continuously now instead of just once.

I would agree that the old way was slightly more desirable, but the new way is workable, in case the fix for this breaks something else.

3579663494,

what do you think about simply learning the current gameplay?
And that the scenario should be updated to reflect the new correct way to play.

PS:

Strike 2 Target update

By now you should note a couple of things:

· Strike #1, once his ammunition was expended automatically returned to base (RTB), you can change this behavior through the doctrine interface but for now we will leave it alone. And

For efficiency's sake, I've opened a new report topic with a simple solution suggested, see: [1328.14] Strike Tutorial #1, instructions outdated. Quickfix. - Matrix Games Forums

Cheers and happy holidays

ClaudeJ,
If it's really the current gameplay, I accept it, but what I want to know is, why did this feature change? At least in my opinion, the original approach is much better, which is why I see it as a bug.

And there is another issue besides this, in Winchester status, when you change the doctrine and press the U key then directly command the aircraft to attack with gun, the aircraft will not execute it. You also need to manually adjust the flight path and altitude to fly the plane around the target (this problem is not present in the original way). So is this also the current gameplay? It is not mentioned in the tutorial.

Another interesting point is that in bingo status, you can directly press U to cancel RTB without changing the doctrine. It seems that the new gameplay is only suitable for Winchester.

Isn't the 32-bit beta a beta version or something?

For clarity's sake. What I would suggest would be to open a new thread where you specifically ask if the behavior you are observing, that you are describing in the middle paragraph of your post just above this one, is Working As Designed.
Convoluted threads with multiple issues tend not to get the attention you would want, as far as I have observed.

ClaudeJ wrote: Thu Feb 08, 2024 6:21 pm Isn't the 32-bit beta a beta version or something?

NO, in 32-bit legacy version everything was fine. It's the current version 1328.14.
When I first played this tutorial, I changed the doctrine but it still didn't work, and then I realized this problem.
The bingo status was also tested by me in the current version.

I am tired of distinguishing gameplay from bugs and finding the right way to do. There are other issues with the strike tutorial besides what I have listed, but I have given up.