Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content
DrShadow

MCDU routing problem after update to 1.2.4.0

Recommended Posts

Hi all

 

I have updated just rightnow my busses to 1.2.4.0.

 

Now i cant connect routes in the mcdu propperly anymore.

As soon is i want to connect a short flight from LSZH to LSGG or LSZH to LOWW my whole routing dissapear.

 

I try to explain, as an example LSZH to LSGG in A319

Take off via RW28, WIL3V departure and in LSGG ILS22, as soon as i want to connect WIL with PETAL WP my routing in LSZH dissapears. 

Example in the picture. The same with LOWW.

image.thumb.png.e71778c47a87151d8c30afc539281d58.png

 

Here is my routing..

 

image.thumb.png.4e81c37ddcaaf8b3f1a6cd2c52ae1425.png

and now i'd like to connect WIL with PETAL, as a simple routing..

 

image.thumb.png.0fc6063ae88f94bf2ee41ea64f8ec501.png

 

And now this happens. :(

 

Does anyone have an idea? (btw, new NDP is updated)

Thank you for your help :)

 

Cheers Pascal

 

 

 

 

 

 

Share this post


Link to post

yes, did new start.

 

And set fisr the buss to turn around.

 

And now i checked the A320, and it is the same.

This morning, with the experimental version, it was no problem.

 

I deinstalled the old version with the aerosoft deinstaller, installed the new one, did reboot and now it isnt working anymore.

Share this post


Link to post

And now i noticed that the mcdu is constantly doing calculations altough i havn't inserted or changed anything

Share this post


Link to post
1 hour ago, DrShadow said:

yes, did new start.

 

And set fisr the buss to turn around.

 

And now i checked the A320, and it is the same.

This morning, with the experimental version, it was no problem.

 

I deinstalled the old version with the aerosoft deinstaller, installed the new one, did reboot and now it isnt working anymore.

 

Remember to allow an aircraft state to fully complete loading before you switch to a different aircraft state.  Failing to do so can leave you with questionable results.

 

1 hour ago, DrShadow said:

And now i noticed that the mcdu is constantly doing calculations altough i havn't inserted or changed anything

 

That is normal.  Remember, you're not looking at altitude restrictions in the FLT PLN page, what you see there are altitudes the aircraft will actually hit and are calculated based on many different dynamic variables.  The crossing restriction data is located in the Vertical Def sub-page.  It's far different than Boeings.

 

Best wishes.

 

Share this post


Link to post

Good morning Dave 

 

thank you for your help. 

 

Well i gave the bus several minutes to load, then did the checklist and then went to mcdu procedure. 

 

I try the whole thing today again.

If that doesnt help, i ll do a complete deinstallation, reinstallation. 

 

Share this post


Link to post

Ok, did the whole procedure again. 

Is not working, exactly the same mcdu situation as in the pictures. 

 

Then deinstalled the whole busses, installed them again as admin, reboot, loaded the newest airac, and nothing gas changed. 

 

I cant fly over easter:( 

 

(is there a possibility to download the earlier version from rhe busses?) 

Share this post


Link to post
7 hours ago, DrShadow said:

Ok, did the whole procedure again. 

Is not working, exactly the same mcdu situation as in the pictures. 

 

Then deinstalled the whole busses, installed them again as admin, reboot, loaded the newest airac, and nothing gas changed. 

 

I cant fly over easter:( 

 

(is there a possibility to download the earlier version from rhe busses?) 

 

I'll be back online in about 4 hours from now, if you're available, i can provide desktop support for you.

In the meantime, would you try using the earlier NAVDATA cycle and see if that helps?

 

Given its the weekend. I don't think I xan get the earlier version for you.

 

Let me see what I can do to help you on our system. My family will kill me, but I'd like you to be able to fly!

 

 

Share this post


Link to post

Hi Dave

 

Thats awsome! very kind of you. Yes i am here in 4 hours.

Ok i try to get the old cycle 1902, hope i can find it.

Share this post


Link to post
1 hour ago, DrShadow said:

Hi Dave

 

Thats awsome! very kind of you. Yes i am here in 4 hours.

Ok i try to get the old cycle 1902, hope i can find it.

 

Also, please provide the complete route so I can check that?  In the meantime, please see if the folllwing route works for you.

 

By the way, we have discovered a bug that MIGHT be affecting this issue.  Please take a look at the following thread and see if there are any similarities to what you are experiencing?

 

 

Share this post


Link to post

Ok, i try

 

For try it is a very simple route actually just from departure point or SID to SID arrival point.

My exact route is:

LSZH28, WIL3V departure (LSZH28, KLO23, BREGO, ZH555, ZH551, WIL)   , to LSGG22( ILS) (PETAL, GG808, ISW40, LSG22)

 

This is the arrival:

image.thumb.png.7586fc9db819912cba43b110864a51c8.png

 

As soon as i want to connect WIL with PETAL this happens:

image.thumb.png.19448c47a56402795f926a8984535292.png

 

 

The funy thing is, when i incert direct to (PETAL) it works!

image.thumb.png.ab1bfc7cfc27940f081ad89a45082efb.png

 

 

 

 

With the route in the already mentioned problem , it is exactly the same! I am not able to incert FERDI, and if i do, it is not connected with the WP before.

image.thumb.png.3ccc98ead2b3ee6be3aef123a52a7697.png

Share this post


Link to post

Dave, it was so nice from you to help me with that issue.

 

It was a great help, and i learned a lot.

@DaveCT2003 thank you for your time.

Share this post


Link to post

If that issue was solved, please post the solution.  I am seeing the same routing issue with 1.2.4.0, took pictures too, but the show the same thing as above.

Share this post


Link to post
On 4/21/2019 at 2:36 PM, Mark Crabtree said:

If that issue was solved, please post the solution.  I am seeing the same routing issue with 1.2.4.0, took pictures too, but the show the same thing as above.

 

Our customer (and now my very good friend, he's a great guy!) just needed a little information on flight planning, navigation aides and the like.

 

There has been a confirmed bug (though I've never experienced it) for SOME waypoint designators that are the same in different parts of the world that caused a problem and our programmers (aka guys who don't know what a shovel is, drink far too much caffeine, and talk to computer screens all day every day as if expecting an answer back... lol) are looking at this.  Should you experience the same thing, just remove the offending waypoint from the flight plan and carry on.  I don't believe this was the same issue our DrShadow was having, though it might have impacted it indirectly.

 

I'm going to close this thread, but if you have a similar issue which isn't resolved by removing the offending waypoint, which has happened in real life as well, then please open another thread with the flight plan and what the issue is.

 

My very best wishes!

 

Share this post


Link to post

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...