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
snoopy_belgium

problem with Flight Controls

Recommended Posts

Since the arrival of the A320/A321 on my system I have a problem that I never have seen with the A318/A319 Professional (and all the Airbus versions before that).

Before taxi the flight controls are tested by moving the joystick up and down and left and right. Also the rudder is tested.

But sometimes the test fails when I move the joystick to the up position. On the PFD I see that the "cursor" (I don't know the name of the cursor that is moving together with the flight controls) goes up to the highest position, so on the PFD everything is OK.

But on the ECAM the triangle which indicates the position of the flight control doesn't slide completely to the highest position when I push the stick completely forward (it gets stuck somewhere in the middle). When this is happening the checklist is stuck and I have to choose skip this item.

When this is happening the airplane behaves normally during flight. Only during one occasion I hit the joystick during flight by accident. As a result the autopilot was switched off, which is normal. But after that I could not switch it on again because there was always a error immediately after it was set to on. As a result the autopilot was switched off again because of the error and I had to fly the airplane manually.

Does anyone else has the same problem that the flight controls on the ECAM display don't behave as expected?

 

Best regards,

Snoopy

Belgium

 

Moderator's Note: This thread was closed for a while due to unwarranted remarks made by a member. It's reopened with just the original post and suggestions solely related to that issue. The others are hidden except to moderators and staff.  "Me too" posts don't really help. We understand this issue is a big deal with those that have it, but for balance, please try to understand that with literally thousands of users that don't have this issue, our extensive experience has to lead us to the conclusion that there's something unique in the systems of those with the issue that can't be solved with common as well as creative trouble shooting. Despite belief that one's system is 100% not the problem, it almost 99.999% (about) is. For the remaining 0.001% we simply don't know why.

 

Share this post


Link to post

We have not seen this in any test. Have you tried a full calibration? An incorrect reading of the stick could explain all you see.

Share this post


Link to post

Hello Mathijs,

 

Thanks for your reply. No, I didn't try that. But it doesn't happen each time I fly (about 1/3 of the flights or so I see this problem). And the problem was first seen after install of the A320/321. The weeks before I was flying the A318/319 a lot and then the flight controls behaved as expected.

I will try a calibration to see it has some influence.

 

Best regards,

Snoopy

Belgium

 

Share this post


Link to post

When I was reading your topic I was also thinking that these 2 can be related. Is the behavior on your PDF also normal and on your ECAM wrong? But in my case the elevator on the ecam moves when I move the flight control up and down, but it doesn't move completely to the highest position, but somewhere around 50%. The down position is no problem.

 

Best regards,

Snoopy

Share this post


Link to post

I have re-calibrated my stick in P3D and I will test it during the next flights. But it will take some time before I can see the result.

 

Best regards,

Snoopy

Belgium

 

 

Share this post


Link to post
23 hours ago, flying_David said:

Nope. It completely works on one flight but in the next it might be shaky.. I can also rule out a hardware defect 100%!

 

Well as it completely worked on one flight you can also rule out software. It's digital, it either works or it does not, under the same condition it will always behave the same way. 

Share this post


Link to post

Also after re-calibration of the stick the problem is still there (see the attached screenshot).

During flight preparation I was hearing the short beep tone again, a problem that was reported by some other users and that has something to do with the variable winds in AS.

So maybe these 2 problems are corelated. I will investigate this further.

 

Best regards,

Snoopy

Belgium

 

 

Inkedairbus flight controls_LI.jpg

Share this post


Link to post

I did a flight yesterday and paid close attention to controller vs input, and could not find any issues.

 

I help people with many different issues throughout most every day, and I don't remember if I recommended this to you.  Please try reinstalling all 4 versions of SimConnect and check to see if the problem remains.  There is no need to uninstall SimConnect, just run the installers, which you will find in the REDIST folder inside the main P3D folder.  There are 6 different versions if you include the Japanese and Russian versions (if you don't need these then you can skip them).

 

 

 

Share this post


Link to post

I strongly suggest to delete the P3d.cfg, there is a very good chance the axis assignments are mixed up.

Share this post


Link to post

Today I have made a flight with the A319 and the same problem was happening again. And this time there was no short beep because of variable winds, so taht is something that can be ruled out here.

After starting the engines and the GSX pushback the copilot performed the checklist and the flight controls check was failing.

This time the elevator was completely stuck in the ECAM, but in the PFD everything was OK. So I'm sure that there is nothing wrong with the configuration of the axis of my stick, because the movements of the stick are displayed always correctly in the PFD. Also with other airplanes there is no problem at all.

At the outside the elevator was also not moving at all, so I was wondering how I would get this plane into the air...

Then I started to taxi, and suddenly the elevator was working correctly again.

After entering the runway and performing the before departure checklist, the elevator was still moving, but not completely to the up position anymore (only to 50% of it). Anyway the takeoff and flight were succesful.

After landing and taxiing to the gate I checked the elevator again before shutting down the engine and everything was working fine.

 

So there must be something wrong inside the software of the plane. When there was a problem with the configuration of the controls I would expect that also in the PFD the cursor would not follow the movement of the stick.

 

Best regards,

Snoopy

Belgium

 

Share this post


Link to post
44 minutes ago, snoopy_belgium said:

Today I have made a flight with the A319 and the same problem was happening again. And this time there was no short beep because of variable winds, so taht is something that can be ruled out here.

After starting the engines and the GSX pushback the copilot performed the checklist and the flight controls check was failing.

This time the elevator was completely stuck in the ECAM, but in the PFD everything was OK. So I'm sure that there is nothing wrong with the configuration of the axis of my stick, because the movements of the stick are displayed always correctly in the PFD. Also with other airplanes there is no problem at all.

At the outside the elevator was also not moving at all, so I was wondering how I would get this plane into the air...

Then I started to taxi, and suddenly the elevator was working correctly again.

After entering the runway and performing the before departure checklist, the elevator was still moving, but not completely to the up position anymore (only to 50% of it). Anyway the takeoff and flight were succesful.

After landing and taxiing to the gate I checked the elevator again before shutting down the engine and everything was working fine.

 

So there must be something wrong inside the software of the plane. When there was a problem with the configuration of the controls I would expect that also in the PFD the cursor would not follow the movement of the stick.

 

Best regards,

Snoopy

Belgium

 

 

Did you try what Mathijs and I recommended?

 

Share this post


Link to post

I have reinstalled the simconnect packages as suggested by you, but this doesn't solve the problem.

I had a look at the prepar3d.cfg file but I don't see anything that is related to the flight controls.

 

Best regards,

Snoopy

Belgium

 

Share this post


Link to post
On 10/5/2018 at 9:30 PM, snoopy_belgium said:

So there must be something wrong inside the software of the plane. When there was a problem with the configuration of the controls I would expect that also in the PFD the cursor would not follow the movement of the stick.

 

Well then it would be seen by all users and not just you would it not?

Share this post


Link to post

I'm not alone... flying david also has reported the same issue. When a signal produced by movement of the stick is graphically shown on one screen in the plane and not on the other screen, I believe there must be wrong inside the plane. The signal is there and the flightsim is the receiver of this signal. When the airbus is displaying the result of the movement it means that the signal has reached its destination. So inside the plane there must be some code that in some conditions the signal is not shown in the ECAM and the movement of the elevator is locked.

 

I'm using your airbus already many years and the product was mostly very stable. Like every new product there are also some small errors and in the past Aerosoft always could solve them in a short period of time. So many users, including me, have some patience because Aerosoft is doing its job.

With the latest version I have the idea that the product itself is very stable (there are not many CTD's, so congratulations to the developers!), but I remark different small problems (like this problem) that were not there in the previous versions and that are annoying.

But the plane can be flown and it is sometimes difficult to reproduce these small problems, so I think many users are not reporting these kind of problems to you.

The product is also many times used in combination with other products from other companies (GSX, Active Sky, ...) which can have an influence on your product. Depending on which products a user has installed in the flightsim, a problem can be seen or not.

I have tried to reproduce the error, but when I open the flightsim in an Airbus and switch on the engines everything works fine.

When I do the preparing of the flight like in reality with GSX and I'm 45 minutes at the gate before engines are started, the problem is there in most cases. When the problem is time related, some users that don't need so much time for flight preparation (testers maybe belong to this type of user) will not experience it at all.

 

Best regards,

Snoopy

Belgium

Share this post


Link to post

Okay, then I restate my point. if two (or twenty) users have and issue and tens of thousands have not, would it not be logical to look at those systems and not at the code? At this moment we are simply totally unable to recreate this issue on our systems. I am now at the gate for 50 minutes and all still works on all my three test machines. I simply have no idea what causes this.

 

 

  • Like 1

Share this post


Link to post

The controls settings are located at: C:\Users\{YOUR USERNAME]\AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls.  Just move the "Standard" files to your desktop (Backup) and they will be rebuilt the next time you start P3D.  Give that a try.

 

Best wishes.

 

  • Upvote 1

Share this post


Link to post

I have removed the control files as suggested by you. During the first flight everything was OK.

But I have two controls: one X52 stick for the airbus and a yoke for the smaller planes. After configuration of the yoke I have the same problem again.

The yoke is not connected when the problem occurs, only the X52 stick.

Maybe the airbus is confused when multiple devices are configured in P3D?

 

Best regards,

Snoopy

Belgium

Share this post


Link to post
2 hours ago, snoopy_belgium said:

I have removed the control files as suggested by you. During the first flight everything was OK.

But I have two controls: one X52 stick for the airbus and a yoke for the smaller planes. After configuration of the yoke I have the same problem again.

The yoke is not connected when the problem occurs, only the X52 stick.

Maybe the airbus is confused when multiple devices are configured in P3D?

 

Best regards,

Snoopy

Belgium

 

This is certainly perplexing, and I'm sorry you're suffering from this problem.  I have a Saitek Yoke, Dual Thrust Levers, Trim Wheel, Rudder Pedals and a Joystick (Side Stick) plus a Radio Panel, Switch Panel and Multi-Panel and an Xbox controller (for ChasePlane) all connected to P3D with no issues whatsoever.

 

Given everything, I have to believe this is either a Windows or P3D installation/update issue.

 

 

Share this post


Link to post
7 hours ago, Goshob said:

Dave,

May I suggest something, which is unfortunately not part of AS official policy?

I also had lots of problems with axes control hardware Saitec Yoke and Thrustmaster joystick in particular. There is definitely some drivers' interference on Windows or P3D level, which makes them working improper when used in one configuration. My go around method was using FSUIPC with different profiles for big and small planes.

Just a suggestion of course :)

 

Thank you for your suggestion, however I could not possibly disagree more.  I use a single P3D control profile and have for many, many, many years, as do many others.

 

Best wishes.

 

 

Share this post


Link to post

This thread will remain open for an additional 30 days, pending further information or troubleshooting results from the original poster (OP).  To date, it seems to be a problem specific to that installation and of course a genuine issue to the OP.

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