Airbus A320 Controls

[Adah]

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

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The same experience in Aerosoft A320. No response of the rudder during taxiing, even the plane starts to move backwards, brakes don't have effect. I tried other FSX planes such as the Bombardier X45 and with this plane it doesn't occur. Several steps tried, reset of FSX, complete restart FSX. The only what help is a complete pc restart. I have a Saitek X52 and especially for this occasion re-installed the latest W10 driver. Hower, no joy! Assistance is appreciated.

3a8082e126