Jump to content

Speed: 0, Altitude: 0


bluechika

Recommended Posts

Hello.

First of all, thanks for the great product. I am really enjoying it.

I bought the product about 3 weeks ago and have flown the bird about 25-30 times without any problems.

Then suddenly, about 4 days ago, this problem encountered. Today I uninstalled and installed the new service pack (as you outlined), but the problem is still there.

Here is the problem:

From cold and dark cockpit, everything runs perfectly until takeoff.

After takeoff, the CL runs until "gear up" and then "climb thrust" call outs.

But after that when I engage auto pilot, the system acts strange.

As you can see in image #1, the MCDU does not recognise the current speed and altitude (recognises as "0", therefore the CL stops there, shows "climb to crusing altitude" permanantly. This affects all autopilot systems as you can see in the picture).

The MCDU page stays with the "take off" page permanently. Therefore even if I try to ignore this CL and autopilot thing and try to hand-fly, this would not work since I cannot even activate the approach page on MCDU. Basically, the whole aircraft system is STUCK as if it is on the ground with 0 speed and 0 altitude.

The aircraft worked perfectly before but I honestly do not know what is the problem.

I largely appreciate your help.

Thanks!!

regards,

Daniel

post-124203-0-54644000-1429106319_thumb.

post-124203-0-37408900-1429106343_thumb.

post-124203-0-87065000-1429106360_thumb.

Link to comment
Share on other sites

Hi Daniel,

welcome to the the club.

As you can see in this thread

http://forum.aerosoft.com/index.php?/topic/94043-a319-iae-refuses-to-go-into-managed-climb/

I suffer from the same problem.

When you read through it you'll see that I found a probable cause, but no solution (since deinstalling ASN is not an option).

Link to comment
Share on other sites

Thank you very much Farlis.

I went through the thread, but for me the same thing happens when i clean install the fsx and install nothing but this airbus (not even an activesky). So i dont know what the solutions is...

Even the technical guys are silent.. What a waste of money

Link to comment
Share on other sites

  • 2 weeks later...

Scholli04:

Thanks. Finally I get a response from the team. Thank you.

Yes, I did:

1) clean install fsx

2) clean install windows 8.1

The problem still occurs.

Is there a specific log file that you need (or any files), let me know, I am glad to give it to you

regards,

Daniel

Link to comment
Share on other sites

Jonas,

Look, It is not a problem of how I install the product or how i operate the bird. Its got something to do with my pc and the bird.

Look, there are few others having the same problem and no one knows whats the cause of it.

Is there no log file or similar things that you guys can look into and solve the problem? One of my friend is having a same problem, I can send you two at once if needed.

Link to comment
Share on other sites

Experience from other guys in the past shows the brake thing is 99% sure a userproblem by not handling the Airbus correctly.

That's why Jonas asks if you have flown the Step By Step guide. Most likely you simply miss something.

Picture two is defiantly a problem with the vertical mode missing.

Now you could either call that a pilot error, or a softwareproblem, but I rather tend to call it pilot error.

As pilot you have to watch the FMA at all times and if something goes different than expected you have to correct it. Therefore, if there is no vertical mode you have to "create" one. That means either put it in VS/FPA or CLB/OP CLB. If you do that it should fly fine.

That's your responsibility as pilot.

Of course you can also question why the mode vanished in first place and to be honest, this I can't really explain as I can't recreate it.

Link to comment
Share on other sites

Let me chime in here, as I'm, so far , the only other person with the same problem.

I can only speak on my behalf, but it is definately not a pilot error. I know how to handle the bus. Have been flying it since the PSS incarnation in FS9, have flown the Wilco's, and have been on the Aerosoft version since it has gone Extended.

The procedures of how I handle the bird haven't changed.

I suspect it is a simconnect overload and on my system I narrowed the cause down to ASN. But why it only afflicts my FSX installation and not others, I can't answer.

I tested it with P3D and there everything works fine.

And it worked fine with the SP2 of the Bus in FSX. The problem showed up with the new SP3.

I don't go to support for trivial questions like so many others do, who don't even care to read the manuals. So I expect a little more than a "Do the step by step guide"-routine.

Link to comment
Share on other sites

Wow, you guys are blaming on customers again...

THAT'S IT.

I want a refund.

Okay, since you insist on this.

Contact support@aerosoft.com for ANY further request of any kind.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use