Jump to content

Recommended Posts

Posted (edited)

Example: EDDV27R NDB
MAP is 0.6 before runway threshold.

So the AnchorPoint has to be labeled EP27R

The AnchorPoint is missing at the ND.

Also the AnchorPoint height need to be checked. It has to be 50ft or the TCH above the threshold. The FLS was guiding me to low.

image.png.d9f17d98cda31ea88bac74ffab5ab936.pngimage.png.146308c577ffbe4918b5ec77cf3ad737.png

image.png.de6b20d1a91570107634f4682c62c7b1.png

image.png.d853d7952c8632b9594c7d454552e2fe.png

image.png.33ffce84df1f371e1c0fec4e2e8f207e.png

image.png.99eaae96a1b616ca44f3d5a1c71f0fc4.png

 

And just for clarification the rules for other MAP placements:

 

image.png.c3428a25a1eae7142facfd032005dcea.png

image.png.03c32fa7815f1b2ff02cc5ab0a449de9.png

image.png.a0a97636995f6c2e64c52b21601f8fdc.png

Edited by Der Michel
  • Like 2

Specs:
CPU-13900K, RAM-64GB-6800, GPU-4090

  • 2 weeks later...
  • 1 month later...
Posted (edited)

still not fixed in 1.1.0

- naming of Anchor Point is still wrong
- the achor point (it's avirtual one) has to be displayed on ND
- during descent the FLS glidepath was going up and down during last few hundred meters. (magenta double diamond)

 

image.png

Edited by Der Michel

Specs:
CPU-13900K, RAM-64GB-6800, GPU-4090

Posted

Correct me if I am wrong, but its up to developers how deep they want to go and how deep system will be…..so this is not the bug….also others are not.

This plane is totally perfect after last update. Looking forward for some more immersion update in the future.

Cheers

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...