Hi,I do have a quesiton regarding the altitude restrictions on the FMC. I am trying to enter a restriction for "at or above 3500ft". While I can enter "3500A", which should do what I want, the FMC doesn't seem to care about the "or above" after the 3500. The 737NG always tries to hit the waypoint at excactly 3500ft, even though the MCP is set to 8000 and there was plenty of distance to climb to at least 5000 with normal climb rates.The same problem seem to exist for a "at or below" restriction. The plane also tries to meet the restriction exactly, which doesn't always make sense.Therefore, I'd like to know whether this is simply not modelled and will be implemented later, whether I am doing something wrong or whether this should work but for some reason doesn't work for me.Thanks you for your support and a great product,Thomas Boehme

Hi guysThis is something I missed in the FMC SID/STAR file syntax as well. Any chance it could be implemented there as well?Great pice of machinery guys! Did a VNAV flight without the DoD!!Regards

Hello,Soft constraints will be implemented in the 800-900 release.Yes, when vnav does not dive it is actually nice ;-)Anthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com

Nice to hear (and I mean about the soft constraints!) ;-)Without the DoD she's a beauty!Regards

That is a disappointing response. For a product that is touted to be "standard setting" (PMDG press release words) to not have this makes it rather not standard setting. People will have to buy a future product that has not even started development to get functionality that 767PIC, DF737, PSS A320 had from day one.Lee Hetherington (KBED)

Hmmm.... I hadn't tried this yet... I'm a little disappointed as well that this feature is not modeled in the initial release.