fixed Takeoff training mission semi-stuck on checking the gauges with 70%RPM

[virgo47]

During this training mission, I was previously informed I could use Num+ keys OR the throttle axis to increase the throttle.

I hardly know where the keys for the throttle actually are - I'm always using the axis.

And then I get to the RWY centerline and I'm informed about the RPM 70% test. I check everything and lower the RPM and... nothing happens. If I press Num- at this moment, nothing happens either, I have to get the RPM a bit higher, then press Num- for the mission to progress.

The event should not be bound to using the keys only, especially after I had the freedom of choice previously (which was the right thing, of course).

[Flappie]

Hi @virgo47. At first, I could not make it work, I'm not sure why. I tried again, still using my Warthog throttle, and it worked...

Edited October 13, 2023 by Flappie

[virgo47]

8 hours ago, Flappie said:

Hi @virgo47. At first, I could not make it work, I'm not sure why. I tried again, still using my Warthog throttle, and it worked...

So it is flaky somehow?

I'll get back to this and provide the trackfile, it was pretty reproducible in my case, I could repeat the test a few times and nothing, but I'll double-check and get back to you.

[Flappie]

Thanks. On my end, I'll try to understand how the mission script was made.

[virgo47]

I'm totally puzzled now. I tried today and couldn't reproduce it either, although previously I definitely managed to repeat it a couple of times - otherwise, I would not be able to figure out the "workaround" and I'd not dare to report it. So I guess it's "cannot reproduce" for now. Sorry about it.

If you see something suspicious in the script, cool, but while I'm not 100% sure it's OK, I can't do more about it now.

[Flappie]

Let's do it scientifically, then.

Here are the conditions to trigger the next action:

• The flag "12" gets activated by the previous step, which means it is out of the equation.
• The X:Cockpit argument is the one checking the gauge.
• And... last but not least, you need to be inside a zone.

Chances are we had the issue because we were out of the zone.

[virgo47]

This makes sense! The zone is quite small - if the graphic is precise - because it is quite likely I aligned just in front of the numbers 09!

I'm not sure if the zone can be enlarged without triggering lots of QA on your side, but I'd suggest to cover the wider area - e.g. anything fromt he start of the runway for the most "borderline" pilots.

What could have happened when it did not work with the axis and then worked with the +/- binds is that I moved a bit, just to get to the zone. If it checks the gauge (and not the binding) it is generally the right logic.

Thanks, Flappie, this all makes sense.

EDIT: Why can't I remove/change the "solution" mark? Or is it possible somehow?

Edited October 16, 2023 by virgo47

[Flappie]

You're welcome. I agree, the zone is a tad too small. I'll ask for a fix.

I believe only moderators can change the green "solved" answer, but that's OK.

[Flappie]

Fixed in today's OB update.

[virgo47]

I can confirm it works well and the zone in the mission editor looks great too. Thank you very much!