New Updates from PM July,17th 2008

[Jan Pemöller]

found a new bug:

Missing TAI letters over N1 Display when turning Anti Ice on

Can anyone confirm before I will report to pm-support!

Thanks
Jan

[Jan Pemöller]

second bug:

I cant switch to mach 0,78, it goes always back to 0.73!
Using CP Flight MCP ... and had never problems before.

Best regards
Jan

[Peter Dowson]

I cant switch to mach 0,78, it goes always back to 0.73!
Using CP Flight MCP ... and had never problems before.

Same with the PFC MCP (except the Mach value here was 0.76, but I think it depends on the Aircraft txt files or something like that).

Also, I'm not seeing the automatic transition between IAS and Mach which is supposed to occur at the altitude specified in the MCP.INI parameter for this.

Regards

Pete

[michelmvd]

No problems here for the B744 Aerosoft MCP.
Only the transition at FL290 always change to 0.870 instead of 0.860, but this is already a longterm issue.
B. Rgds
Michel

[michelmvd]

Additional to my test flight EBOS-EDDP, I did today also EBOS-LSGG (Geneva)
This time I waited till 80 mls before T/D to add the STAR, as Peter mentioned he had no problem then.
Unfortunately the results were the same : the full UN852 was vanished. (Did the STAR /RWY input just after GTQ)

So my full routing was

EBOS 26 KOK2 KOK UL607 REMBA UM624 RITAX UT27 GTQ UN852 MOROK UZ24 AKITO AKITO 2R RWY 23

It looks that the problem is definitively still there when using the actual NavData.
Very strange that they didn't see that with PM.

Have reported it again to Enrico, with the 2 exemple routes.
The best is to inform them with exemples.
B. Rgds
Michel

[Peter Nielsen]

Did two flights today

NZCH to NZQN, nothing worked at all, and by that i mean that i had had no PFD or ND, but i decided to fly and test, and behold suddenly passing FL150 it all came alive..
This time i entered RNAV for rwy 23 and it actually did work.. then again it was pulling the STAR for my Stardata2file which are the Rnav waypoints i added some 2 years ago for NZQN.

2nd test was a short hop from EDDH to EKCH, again on TOD entered CDA3A and it all went blank again..

I my opinion we ought to all roll back the entire suite some 18 months, then start from there, and above all get the PM team back on communication mode..
Peter

[NicD]

Rolling back is tempting, and I'd say that the PM folks would agree! But then we'd be stuck with navdata that is 18+ months old. And that's what started all this... whene DAFIF finished and Navigraph took over the supply of Navdata, PM had to rewrite there software to handle the new navdata. That's when the bugs started.

I repeated one test flight YMHB-YMML and in the cruise selected the WAREN9 arrival for ILS27. The exec light came on and I left it for a minute before pressing EXEC. The aircraft continued on normal track and didn't deviate. Once I pressed EXEC the STAR entry was fine and the RTE and LEGS pages remained normal. That same route was playing up alot last week, so something is better, however it seems that the problem still surfaces on certain STARs/RWYs ... so it's gotta be a bug in the way some approaches are programmed.

I also noted that the Mach / IAS speed did not switch on descent - causing overspeed.

VNAV and LVL-CHG remain erratic. PM says those are on the list but are not the priority right now. (aren't we all glad Boeing doesn't say that - lol! )

[michelmvd]

Hi Nic,
Thanks for your sharing news about your test routes.
You are right the problem started when DAFIF became restricted to military users and Navigraph took over.
I don't think there is something wrong with the present navdata, as more than another dozen addon's are using it. I checked with PMDG en Level-D users - who have also the complex cdu's to use - and there are no problems at all. The source is all the same, only the addon specific conversion program's are different.

Let's hope that Enrico finally can find the bug with the new exemples we were sending him.
Or I have bad luck or Murphy is around, but I must say that not many of my routes are working normally in my last tests.
Only the very short route EBOS-EGLL is working normally and even the return gives already the same problems.

What I see here basicly is when I enter the route info via the RTE-page (normal procedure, as otherwise you have to enter every waypoint, which can be very frustrating when you fly long haul ) is that SID entering and route entering is ok, but at the moment I select the RWY of destination and/or STAR, the last 2 airways entries are vanished.

Michel

[Michael Carter]

Would it work if you waited until you reached the clearance limit before entering the STAR?

[michelmvd]

No idea, but is certainly not the way you must do it.
A descend and approach planning is done atleast half an hour before t/d, if you fly online, you will come in trouble if you wait so long to prepare your approach.
But will check once during another test.
BRgds
Michel