lewismorrison22

How did you solve it Willy? I also have thi

How did you solve it Willy? I also have this problem it is very annoying

Ok i'll give it a try

Hi, I currently have a Saitek x52pro, and P3D v3.2. My problem: My rudder and pitch axis work flawlessly. However when I try to roll, for the first 80% of joystick movement the yoke moves a minuscule amount, and for the remaining 20%, the yoke leaps to full left and right. I have this problem on ALL carenado and Alabeo products and I have found no solution yet, it is quite frustrating. I think the problem only started when I got my X52, this does not make sense as all other aircraft work fine with it (PMDG, A2A, aerosoft.) I have tried re calibrating it is P3D, but this does nothing. I have null zones and sensitivity set to min, and max, respectively. Any help is appreciated, Lewis.

Hi, I currently have a Saitek x52pro, and P3D v3.2. My problem: My rudder and pitch axis work flawlessly. However when I try to roll, for the first 80% of joystick movement the yoke moves a minuscule amount, and for the remaining 20%, the yoke leaps to full left and right. I have this problem on ALL carenado and Alabeo products and I have found no solution yet, it is quite frustrating. I think the problem only started when I got my X52, this does not make sense as all other aircraft work fine with it (PMDG, A2A, aerosoft.) I have tried re calibrating it is P3D, but this does nothing. I have null zones and sensitivity set to min, and max, respectively. Any help is appreciated, Lewis.

I have installed 20+ other add-ons that are not compatible with P3D with the migration tool, all have worked flawlessly. Thanks for your helpful advice though. :wink:

OK so I installed Wilco Airbus Vol 2 with the FSX migration tool, then installed the A380 mega-merge, this works perfectly in fsx, but the clickspots in P3d do not work? Any Ideas? Im lost If you're interested, here is the merge: https://www.dropbox.com/s/pja55rjrachs0c2/A380%20Super%20Pack%20FSX%20V1.zip?dl=0

Thanks for all the responses guys, It was because I put 0 in step climb

Never heard of anything like this... might be time for a reformat ^_^

Ok, I've tried to figure this out but I can't so I'm hoping someone on here will be able to help... So, when I'm programming the FMC for a long flight and there are planned step climbs, I go to the way point in which I must climb and put in the new altitude followed by an 'S' for example, I may put '/370S' and this works as it should, i.e. it will change all the following way point to 37000FT. The problem I face is with the auto step climb feature. It simply does not work when I turn the feature on. So here is a quick example. Im flying LAX - DXB. My initial altitude is 370, with a step to 390 - I programme the FMC appropriately and will have 370 set in the MCP. However, when I reach the SC point, nothing happens. The MCP does not change and the aircraft does not climb. I've also tried putting 390 in the FMC before the SC point, but the aircraft still does not climb automatically. I am at a loss. Any help is greatly appreciated. Lewis