invernyx / md11-bugs

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

[BUG] - SimBrief import failed #1249

Closed wagoozen1 closed 5 months ago

wagoozen1 commented 5 months ago

Describe the bug

Unable to load F-PLN using NAT routes

Steps to reproduce

  1. In simbrief create a flight from EHAM-CYYZ, use the suggested route contain NATX..
  2. Continue create the flight plan and generate the flight.
  3. In the EFB load flightplan and send FLight plan to FMC
  4. The FMC output an error 'Unable to load F-PLN' 5

Expected behaviour

Route importe working including nat tracks

Evidence

image I used reload flight plan in this example as i was testing the steps, and i didnt want to reload MSFS. when starting the plane for the first time and you press load into fmc, you only geet the error message no date

Simulator

Microsoft Flight Simulator 2020 (MSFS)

Crash

No

Phase of flight

Pre-flight

Altitude

0

Departure

EHAM

Arrival

CYYZ

Cruise level

0

ZFW

n.a.

CG

n.a.

Fuel

n.a.

Cost index

n.a.

Route

EHAM/18L N0490F340 BERG4E BERGI L602 SUPUR L60 PENIL M144 BAGSO DCT DOGAL/M084F360 NATE TUDEP/N0491F380 DCT MIILS DCT VILRO DCT SAVEX Q806 TUKIR IMEBA9 CYYZ/15L

Location

EHAM

Agreement

turbofandude commented 5 months ago

NAT tracks is not the problem here. I will need your SimBrief username or the .json of the flight plan from this url: https://www.simbrief.com/api/xml.fetcher.php?username={YOUR USERNAME HERE}&json=1

wagoozen1 commented 5 months ago

Hi Colin,

This one should work: simbrief.com/api/xml.fetcher.php?username=wagoozen&json=1 https://www.simbrief.com/api/xml.fetcher.php?username=wagoozen&json=1

Also, before i report this one are you planning to change the rotate knobs sounds? its very unrealistic and it sounds like one speed of turn while when turning left fast or slow it still is the same ticking sounds. and if you do for example from heading 100 to 095 once done the sounds is still playing.

I know the plane is still in development but wanted to know if i should report it or if this is being polished before going RTM.

Thanks Colin

Andres van Goozen

Op ma 27 mei 2024 om 18:50 schreef Collin Biedenkapp < @.***>:

NAT tracks is not the problem here. I will need your SimBrief username or the .json of the flight plan from this url: https://www.simbrief.com/api/xml.fetcher.php?username={YOUR USERNAME HERE}&json=1

— Reply to this email directly, view it on GitHub https://github.com/invernyx/md11-bugs/issues/1249#issuecomment-2133825958, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JSA3LBIM56B64UFXU22ITZENP6NAVCNFSM6AAAAABIKECS3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZTHAZDKOJVHA . You are receiving this because you authored the thread.Message ID: @.***>

GenericNerd commented 5 months ago

Also, before i report this one are you planning to change the rotate knobs sounds? its very unrealistic and it sounds like one speed of turn while when turning left fast or slow it still is the same ticking sounds. and if you do for example

These are not related to this issue. Please submit new issues for these items.

wagoozen1 commented 5 months ago

I know that was just checking, will report :)

Op ma 27 mei 2024 23:28 schreef GenericNerd @.***>:

Also, before i report this one are you planning to change the rotate knobs sounds? its very unrealistic and it sounds like one speed of turn while when turning left fast or slow it still is the same ticking sounds. and if you do for example

These are not related to this issue. Please submit new issues for these items.

— Reply to this email directly, view it on GitHub https://github.com/invernyx/md11-bugs/issues/1249#issuecomment-2134062794, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3JSA3KSVB3H752TEDQHELLZEOQQLAVCNFSM6AAAAABIKECS3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZUGA3DENZZGQ . You are receiving this because you authored the thread.Message ID: @.***>

turbofandude commented 5 months ago

Resolved in 0.55+. Also, I stand corrected, it was indeed NAT tracks breaking the import. That has since been resolved.