Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Vnav cuts corner on approach

Featured Replies

When using VNAV to fly a  STAR(then ILS) or RNAV approach the FMS turns onto the next waypoint well before it has reached the first one sometimes up to 5nm, because it does this the VNAV path has gone, as a result the aircraft is too high for landing on finals. I have not selected approach mode prior to this so the FMS is still in Nav mode. Anyone else having this problem or know of the cause.

I'll check this out when i get home from my japan trip- it could be when the FMS "smart turns" it affects the VNAV path calculation. 

Brendan R, KDXR PHNL KJFK

Type rated: SF34 / DH8 (Q400) / DC9 717 MD-88/ B767 (CFI/II/MEI/ATP)

Majestic Software Q400 Beta Team / Pilot Consultant / Twitter @violinvelocity

I'll check this out when i get home from my japan trip- it could be when the FMS "smart turns" it affects the VNAV path calculation. 

This is the same issue i have. I've just the topic in the official forum:

http://majesticsoftware.com/mjc8q400/support.html

("2 issues i hope to be improved in the Pro Version")

 

Btw, Brendan, i just noticed that you live in EDTF - me too, so if you want you can just come over and i show you the "issue" live.... :lol:

Regards,
Chris Volle

i7700k @ 4,7, 32gb ram, Win10, MSI GTX1070.

This is the same issue i have. I've just the topic in the official forum:

http://majesticsoftware.com/mjc8q400/support.html

("2 issues i hope to be improved in the Pro Version")

 

Btw, Brendan, i just noticed that you live in EDTF - me too, so if you want you can just come over and i show you the "issue" live.... :lol:

 

Ah yes! I've since moved to PHNL however, but I go back to Germany a few times a year to visit University friends/family. We should go ins Aspekt, fals es noch da iss! GEL?

Brendan R, KDXR PHNL KJFK

Type rated: SF34 / DH8 (Q400) / DC9 717 MD-88/ B767 (CFI/II/MEI/ATP)

Majestic Software Q400 Beta Team / Pilot Consultant / Twitter @violinvelocity

Thanks for the reply. I prefer to post problems in this forum it seems to get more responses.

  • Commercial Member

We prefer that "technical issues" for which you require Majestic Support however be addressed on the Majestic forum...there is nothing wrong with posting here as you mentioned you can get great user feedback here as well, but we do not have a chance to browse through both forums everyday, so it may take longer to be addressed here.

 

Thanks 

KROSWYND    a.k.a KILO_WHISKEY
Majestic Software Development/Support
Banner_MJC8.png

Sys 1:  AMD 7950X3D, NOCTUA D15S, Gigabyte Elite B650, MSI 4090, 64Gb Ram, Corsair 850 Power Supply, 2x2TB M.2 Samsung 980s, 1x4TB WDD M.2, 6xNoctua 120mm case fans, LG C2 55" OLED running at 120Hz for the monitor, Win11. Sys 2:  i7 8700k, MSI GAMING MBoard, 32Gigs RAM, MSI 4070Ti & EVGA 1080Ti. Hardware:  Brunner CLS-E-NG Yoke, Fulcrum One yoke, TM TPR Rudder Pedals, Yoko TQ6+ NEO, StreamDeck, Tobii Eye Tracker, Virpil VPC MongoosT-50CM3 Base with a TM grip
SIMULATORS: MSFS2020/XP12/P3D v5.4 & v6:  YouTube Videos

Okay got that - do you want me to copy it over?

  • Commercial Member

It is not a must....since one of our technical advisors is already looking into the situation that you mentioned.  But for the future....issues that you need technical assistane with should be posted at the Majestic site.  The Avsim site is a great place for general infomation as well, and you can post hear as well, as someone may have experienced the same issue/over-sight that you may have.

KROSWYND    a.k.a KILO_WHISKEY
Majestic Software Development/Support
Banner_MJC8.png

Sys 1:  AMD 7950X3D, NOCTUA D15S, Gigabyte Elite B650, MSI 4090, 64Gb Ram, Corsair 850 Power Supply, 2x2TB M.2 Samsung 980s, 1x4TB WDD M.2, 6xNoctua 120mm case fans, LG C2 55" OLED running at 120Hz for the monitor, Win11. Sys 2:  i7 8700k, MSI GAMING MBoard, 32Gigs RAM, MSI 4070Ti & EVGA 1080Ti. Hardware:  Brunner CLS-E-NG Yoke, Fulcrum One yoke, TM TPR Rudder Pedals, Yoko TQ6+ NEO, StreamDeck, Tobii Eye Tracker, Virpil VPC MongoosT-50CM3 Base with a TM grip
SIMULATORS: MSFS2020/XP12/P3D v5.4 & v6:  YouTube Videos

Thanks crosswind, having lot of problems grasping the FMS and VNAV setup and flying, (as opposed to AXE and NGX) read all your manuals, flown the trial flight, watched all the youtube vids...BUT...an in depth manual/tutorial from you guys might help out. The more I read other sources the more I get confused.

  • 2 weeks later...

When using VNAV to fly a  STAR(then ILS) or RNAV approach the FMS turns onto the next waypoint well before it has reached the first one sometimes up to 5nm, because it does this the VNAV path has gone, as a result the aircraft is too high for landing on finals. I have not selected approach mode prior to this so the FMS is still in Nav mode. Anyone else having this problem or know of the cause.

Any word on this i,m having the same issue. I looked on Majestic forum and could not find help on this issue.

It is not a must....since one of our technical advisors is already looking into the situation that you mentioned.

 

Thanks,

Tom

Tom Davis

 

I7 6700k 4.7 ghz, gtx 1080ti , 16gb 3400 ram, 32’’ 2k monitor, 1TB ssd, 500gb ssd, 250gb ssd, h115 water cooler

UAL440.png

  • Commercial Member

My apologies for the delyed response.  This problem is something that we have been looking into and have added to the "to fix list" which has been sent out to the Beta team for testing.

KROSWYND    a.k.a KILO_WHISKEY
Majestic Software Development/Support
Banner_MJC8.png

Sys 1:  AMD 7950X3D, NOCTUA D15S, Gigabyte Elite B650, MSI 4090, 64Gb Ram, Corsair 850 Power Supply, 2x2TB M.2 Samsung 980s, 1x4TB WDD M.2, 6xNoctua 120mm case fans, LG C2 55" OLED running at 120Hz for the monitor, Win11. Sys 2:  i7 8700k, MSI GAMING MBoard, 32Gigs RAM, MSI 4070Ti & EVGA 1080Ti. Hardware:  Brunner CLS-E-NG Yoke, Fulcrum One yoke, TM TPR Rudder Pedals, Yoko TQ6+ NEO, StreamDeck, Tobii Eye Tracker, Virpil VPC MongoosT-50CM3 Base with a TM grip
SIMULATORS: MSFS2020/XP12/P3D v5.4 & v6:  YouTube Videos

Can any explain this problem with more clarity? Sorry I haven't a perfect English...

 

Mean that if I fly a STAR in VNAV, the aircraft won't be at the correct altitude to intercept the ILS?

 

 

Enviado desde mi iPhone 5S con Tapatalk

José Fco. Ibáñez /// i7 6700k (Delid) @ 4,6 Ghz /// Asrock Z170 OC Formula /// 16GB RAM G.Skill Ripjaws V 3200 /// GTX 1070 Founders Edition 8GB /// LG 27UD58 4K 27' // OCZ Vertex 4 SSD (X-Plane 10) & SAMSUNG 850 EVO SSD (P3D V3) /// Windows 10 Pro x64

 

sig_FSL-By-Wire.jpg

  • 2 weeks later...

When using VNAV to fly a  STAR(then ILS) or RNAV approach the FMS turns onto the next waypoint well before it has reached the first one sometimes up to 5nm, because it does this the VNAV path has gone, as a result the aircraft is too high for landing on finals. I have not selected approach mode prior to this so the FMS is still in Nav mode. Anyone else having this problem or know of the cause.

 

This problem (early waypoint sequencing) has been mentioned several times both on the Majestic forum and here. It will activate the ILS approach at a specific point  at which time you have to switch back to NAV1 and hit APP to capture the loc and GS. However, especially on RNAV approaches the early waypoint sequencing can make RNAV's unflyable. I'll fly a few flights that will work well, but on my last flight on an RNAV approach it sequenced a waypoint turning final way way too early. LNAV remained engaged but the plane turned way off course and headed for the mountains. I was hoping this early waypoint sequencing issue would be addressed in version 1.008 but it remains a problem. As I stated on the Majestic forum long ago, this plane would not meet RNP specifications the way it works now. I'm tired of the FMC inconsistency with this model and it's benched until this long running issue is addressed.

No plans to fix it?

 

 

Enviado desde mi iPhone 5S con Tapatalk

José Fco. Ibáñez /// i7 6700k (Delid) @ 4,6 Ghz /// Asrock Z170 OC Formula /// 16GB RAM G.Skill Ripjaws V 3200 /// GTX 1070 Founders Edition 8GB /// LG 27UD58 4K 27' // OCZ Vertex 4 SSD (X-Plane 10) & SAMSUNG 850 EVO SSD (P3D V3) /// Windows 10 Pro x64

 

sig_FSL-By-Wire.jpg

No plans to fix it?

 

 

Enviado desde mi iPhone 5S con Tapatalk

José Fco. Ibáñez /// i7 6700k (Delid) @ 4,6 Ghz /// Asrock Z170 OC Formula /// 16GB RAM G.Skill Ripjaws V 3200 /// GTX 1070 Founders Edition 8GB /// LG 27UD58 4K 27' // OCZ Vertex 4 SSD (X-Plane 10) & SAMSUNG 850 EVO SSD (P3D V3) /// Windows 10 Pro x64

 

sig_FSL-By-Wire.jpg

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.