invernyx / smartcars-3-bugs

The bug tracker for the smartCARS 3 application
3 stars 0 forks source link

[BUG] - Cruise Phase Not Detected #280

Closed citadelskies closed 1 year ago

citadelskies commented 1 year ago

Describe the bug

SmartCARS did not detect cruise phase when you hit cruising altitude within 3-5 minutes and have to descend afterwards. And during descent up to touchdown SmartCARS also did not detect the descent, approach, and final phases.

This has happened twice already in the FlightFX Vision Jet for MSFS.

How do you reproduce this bug?

  1. Set up a flight where you're at cruising altitude for only a few minutes to few miles before you hit TOD (in my case, it was NZRO-NZNP and NZQN-NZDN).
  2. With MSFS and FlightFX Vision Jet, fly to cruise, and descend after cruising for only 1-3 minutes.

Flight 1 is NZRO-NZNP, cruising altitude 26,000 ft.

Flight 2 is NZQN-NZDN, cruising altitude 23,000 ft.

Expected behavior

Cruise, descent, approach, and final phases should be logged.

Screenshots

Flight 1 log NZRO-NZNP (June 17, 2023): [20:27:11] Using Microsoft Flight Simulator [20:27:11] Flying FFX Vision Jet WAT Black Grey [20:27:11] Now boarding [20:34:58] Engine 1 On [20:41:26] Flaps set to 50% [20:43:40] Pushing back [20:47:02] Taxiing out [20:50:09] Taking off with 438 kgs of fuel [20:50:22] Climbing at 97 kts, 7 degrees pitch, 2 degrees bank, with 437 kgs of fuel [20:50:28] Gear lever raised [20:51:15] Flaps set to 0% [21:28:32] Flaps set to 50% [21:29:20] Gear lever lowered [21:29:53] Flaps set to 100% [21:32:11] Touched down at -261 fpm, 1.3g, 83 kts, true heading 072, 1 degrees pitch, -0 degrees bank, wind 120 at 7 kts, fuel remaining 278 kgs [21:32:26] Taxiing to gate, landed in 384 m [21:32:57] Flaps set to 50% [21:37:34] Engine 1 Off [21:37:35] Deboarding

Flight 1 Altitude/Speed Chart (Cruising altitude should be 26,000 ft): Screenshot 2023-06-24 235917

Flight 2 log NZQN-NZDN (today, June 25, 2023): [03:02:36] Using Microsoft Flight Simulator [03:02:36] Flying FFX Vision Jet WAT [03:02:36] Now boarding [03:07:17] Engine 1 On [03:08:25] Flaps set to 50% [03:09:37] Pushing back [03:12:03] Taxiing out [03:12:49] Taking off with 981 lbs of fuel [03:13:00] Climbing at 97 kts, 6 degrees pitch, 0 degrees bank, wind 000 at 1 kts, with 977 lbs of fuel [03:13:04] Gear lever raised [03:13:45] Flaps set to 0% [03:37:26] Flaps set to 50% [03:38:27] Gear lever lowered [03:38:28] Flaps set to 100% [03:45:31] Touched down at -121 fpm, 1.2g, 72 kts, true heading 058, 1 degrees pitch, -0 degrees bank, wind 087 at 3 kts, fuel remaining 688 lbs [03:45:55] Taxiing to gate, landed in 1775 ft [03:46:10] Flaps set to 50% [03:47:47] Engine 1 Off [03:47:48] Deboarding

Flight 2 Altitude/Speed Chart (Cruising altitude should be 23,000 ft): Screenshot 2023-06-24 235930

Flight 2 Screenshots showing descent in-sim with SmartCARS on second monitor Screenshot 2023-06-24 233450 Screenshot 2023-06-24 233241

Operating system

Windows 11 22H2

Community airline

Walker Air Transport

smartCARS Version

0.12.0

Plugins installed

chat, map, flight center, flight tracking, logbook

Additional context

No response

bryan737dfw commented 1 year ago

On a recent flight cruise was detected, but then switched to climb later in flight and never went back to cruise or descend. Since this behavior was somewhat similar to once of the reported issues, wanted to add this scenario as well.

image

bgiorgio0506 commented 1 year ago

On a recent flight cruise was detected, but then switched to climb later in flight and never went back to cruise or descend. Since this behavior was somewhat similar to once of the reported issues, wanted to add this scenario as well.

image

this is a different bug and it as already been fixed for the next update