Pm Cdu 394

[NicD]

Ok, thanks Jonathon. I haven't had time to do much testing yet but wil do later this week, and will report back.

[michelmvd]

I did this week some test with the latest pm builds, available on the site (MCP423a and CDU 394 full -released version ).
Route building on the displays looks more smoother and also the CDU gives me a general feeling of smoother operation. Still some overshoots of waypoint with high crosswinds.

The MCP didn't give me any problems but also no addional functionally for B744.

First I did some test with short routes EBOS/EGLL/EBOS and operation was ok.

I furthermore tested a route EBOS/LSZH (Zurich), still a very short route for a B744

EBOS RWY 26 KOK2M - UL607 REMBA UM624 DIK UN852 LIMGO R7 SUTAL UN852 LASAT UL851 TRA TRA 1Z RWY16

Airac cycle 0802

Big was my surprice, when I saw all the same major bugs as reported here and to PM already for more than a year, were still there. When selecting the STAR (TRA1Z), a major part of the routing disappeared again! The part between DIK and TRA simply vanished from the LEGS page. (UN852 R7 UN852 UL851.) I selected the STAR during preflight, but also at the end of the route , it gave the same result (plus returning).

After waiting so long for an patch or update to the CDU394 this is extermely frustrating. Maybe Jonathan can inform us what was fixed then and what not.

Would be good I think if some forum members are checking this route and see if the same behavior can be reproduced.

I send mail with routing the usual support adresses aswell.

This is really a very unpleasant situation.

B. Rgds

Michel

[Trevor Hale]

Hi Michel,

I am hoping to get back into the pit this weekend. I am looking to upgrade the builds and have a slash.

First on my Addenda is to get my Epic unit installed and replace my existing interface.

Following that, I will see what happens to the route during a couple vatsim flights.

Best regards,

Trev

[JWS]

I'll do some testing as well.

Strange that the bugs are still there while PM claims that it has been fixed earlier (although that claim may not have been acknowledged by the users here). And how the h%## can it "come back"? Makes you wonder why it did not pop up during the tests PM will surely have performed before they released this version.

JWS

[Ray Proudfoot]

Hi

Actually this was fixed prior to release, if it is coming back as a problem now it is because several other major changes were made to accomidate other things - somehow that old one has crept back in it seems. It will be looked at of course.

Regards
Jonathan Richardson

Hi Jonathan,

It would be useful if the notes that accompany each release (beta or full) gave details of what has been fixed. Nowhere in Enrico's release notes here does it mention this particular problem has been fixed. http://www.projectmagenta.com/downlo...MCPchanges.txt

We would all appreciate an early fix to this annoying problem - thanks.

[Trevor Hale]

Guys..

I must reiterate the fact that PM does not regularly monitor these forums.

Please send your comments and support requests via email to: PMSUPPORT


Best regards,

Trevor Hale
Mycockpit.org - Admin

[David Withers]

well trevor, tell johnathan to stop peeping then!!!...these issues are our secret!!...not.

[JonathanRichardson]

>

well trevor, tell johnathan to stop peeping then!!!...these issues are our secret!!...not.

Hi

You want me to stop - .... LOL

The status is simple, we do not monitor the forum "all the time" it could be that you post something here and we do not see it at all, or only after several days or weeks. So, as Trevor says - issues like this that you post are just for yourselves, which is fine - if you post to support you can be sure that they are seen. Do not expect a reply all the time though, the more you send to support the more the issue is logged in our brains - here you can post as much as you like but Enrico will never see it of course...

Regards
Jonathan Richardson

[michelmvd]

Hi Jonathan,
I have send the complete detailed report of course to support too. I hope you received it and can at least confirm you are able to reproduce the problem. By posting the routing here I hope others will be able to reproduce this well know bug also, which maybe will give finally some clues to resolve the problem after a year.

I normally enter the route, as its done according the ops manuals, when entering manually.
- RTE page EBOS - LSZH + RWY of origin (B744 procedure)
- DEP/ARR sid (KOK2M)
- RTE page routing (UL607 REMBA UM624 DIK UN852 LIMGO R7 SUTAL UN852 LASAT UL851 TRA )
- DEP/ARR expected RWY and STAR
- Activate
- EXEC

Already immediately after entering the STAR, the route between NIK and TRA was vanisched.

Many thanks
Michel

[JonathanRichardson]

Hi

As I already stated before - you probably need to enter all routes via the legs page, even if this means a lot of data entry, this is not something we omitted - it is the current status. The current update has been an entire re-write of the lower level code and many things have been improved that perhaps are not obvious on the first level. Your post to support was received (as others) and has been seen. In the course of time the RTE page entry is being looked at - but it was not promised by us re this update.

Regards
Jonathan Richardson