invernyx / md11-bugs

The official bug tracker for the TFDi Design MD-11
https://tfdidesign.com/md11.php
25 stars 2 forks source link

[BUG] - Stepclimbs not working #1491

Closed wagoozen1 closed 2 months ago

wagoozen1 commented 3 months ago

Describe the bug

Not possible to perform stepclimb

Steps to reproduce

Flying on cruise 310. FMC CRZ levels set to 310/330/350/370/390 OPT/MAXFL 330/379 image

When pressing prof nothing happens, when pressing autoflight it descned a few 100ft feet.

Expected behaviour

  1. when on cruise lets say FL310 and estableshed, you can predial 33000
  2. This should make sure that 31000 is magenty and 33000 in withe image

Maybe i am missing some instruction how to step climb but when pressing PROF it should start climb to selected level.

Evidence

https://github.com/invernyx/md11-bugs/assets/114499693/361c4457-f999-49ac-9982-2a9f7e798eac

Simulator

Microsoft Flight Simulator 2020 (MSFS)

Crash

No

Phase of flight

Cruise

Pitch

5.5

Bank

leveled

Heading

055

Altitude

30850

Departure

kphl

Arrival

kmem

Cruise level

310

ZFW

165.4 KG

CG

28.1

Fuel

55.1KG

Cost index

15

Route

MKK5 CODDY DCT FITES R578 FLITY/N0474F370 R578 FICKY C1177 SXC DCT PKE DCT DRK DCT KA30Q DCT KA33U/N0474F390 DCT KA33W DCT NOSEW DCT IRW DCT LIT HOBRK3

Location

In cruis from KPHL to KMEM

Agreement

wagoozen1 commented 3 months ago

I have an update to report, once i change crz levels to 330/350 it was able to climb. Its not climbing to 330 with is optimum as well. Still not able to predial 350.

image image

wagoozen1 commented 3 months ago

I was checking father time his viideo with version 66.02, and i see that he as the step climb in his pfd image

I am starting to think to do a new install of the md11 as the rotary switch for auto brake is also working in his stream. (i have an issue open for that).

Will report back once done

github-actions[bot] commented 2 months ago

This issue has been marked as stale! This means that we're waiting for your response and we haven't heard anything in 12 days. If you'd like to keep this issue open, please leave a comment with the information previously requested. If we don't receive a comment within 48 hours, this issue will be closed, and you will be required to re-submit.

wagoozen1 commented 2 months ago

The 12 days open mark has to do that TDFI didnt look at this yet, i will check if this issue persist in the RTM build.

wagoozen1 commented 2 months ago

By the help of the video of father time i understand hat went wrong issues is resolved.