DaveCT2003

It may look like this to you because of the calibration, but I never experience this with my thrust levers nor have I provided support to anyone who has had this issue. Thus at this point I have to assume it's a calibration issue or bad pot, so I believe CH is the one to help you sort this out. To be blunt, I do not believe nor do I see any indication this is caused by our software and nobody else has this issue my friend. Please let us know how you make out with CH Products? Best wishes.

The thrust levet3and modes wirk withmy Saitek, Thrustmaster, and are known to work with many other thrust levers so I really have no idea why they aren't working for you, though something like like this is usually calibration. Perhaps asking CH Products?

Ray, I sincerely apologize for my being in hit and run mode for the next several weeks but it's unavoidable as real world concerns have piled up. I believe most of us have suffered the issue in question, and the guys who write the code are looking at this. At this point I believe we just need to give them time to research and address this issue. Best wishes!

That will work! Sorry I didn't get back to sooner Ray, I'm not going to be around much in the next few weeks. Thanks, and best wishes!

It's the same thing you did for us a while back ago. the Data folder.... the folder itself, just Zip it and upload it here to this thread.

Ray, Unless things change, I won't be around very much for the next few weeks, but I wanted to get you to zip and post your A330 data folder as that has the information we need to see to understand what occurred. It's even more helpful if you have all three loggings selected in the A330 Configurator. I have experienced this myself, almost always when transitioning from land to water in Europe. Best wishes.

Thanks my ftiend, I was starting to think he gad severe resolution issues if ours looked like that.

Have you selected the Checklist in the MCDU settings? Also, are you using the regular or steam version of the A320?

This usually occurs because one or both parties have not forwarded both ports 6881 and 6882, usually 6882.

When you ran the updater, did you first disable your computer security and run the updater as Administrator?

Okay, well I would have much preferred you do what I suggested, but we can work around that too. What I'll need you to do is delete the following files: 1. The Prepar3d.cfg file, located in the C:\Users\[YOUR USERNAME]\AppData\Roaming\Lockheed Martin\Prepar3D v4 folder. 2. The "Standard" files located in the C:\Users\[YOUR USERNAME]\AppData\Roaming\Lockheed Martin\Prepar3D v4\Controls folder. 3. If you have ever used FSUIPC to set any control bind for any aircraft, please delete the FSUIPC.cfg file, which would be located in the Modules inside your main P3D folder. The deleted files will all be rebuilt when you start P3D up, but you'll have to adjust your P3D settings and control binds when you start P3D back up. This is the least intrusive way to troubleshoot this issue your having, which is a system issue as reverse thrust worst fine for me and others whether it's triggered by a key or a switch. The next possibility is that one of your C++ redistributables got whacked, or maybe even DirectX. But looking at those things is a more intrusive, so let's stick to the more simple stuff for now.

Yeah, I know it's disappointing. I have a project that has been tremendously negatively effected by the development and update schedule so I too am disappointed, but not with the team. They are dealing with some issues (not of their making), but doing excellent work. Plus, yours truly found a handful of new issues which came out of nowhere, and you didn't want the 1.0.0.8 version that we were testing for release, people would have gone ballistic over that and rightfully so. These were completely new, to my knowledge never seen before issues and one of them that we're still tracking down may well have been created by another developer that most flight sim airline drivers use. Right now all of them have been fixes except one (the worst of the bunch) and we're working very hard to track down the cause and effect (well, we darned sure know the effect and it wasn't good). On the good side... there are many more fixes that can be added to the upcoming update that wouldn't have made it into the release, and that's a great thing! Anyway, it's not like our team is sitting on their hands and holding the update. We want it out as badly as you guys do!

Okay, I think I see the problem.... it's what I suspected it might be. Remove your thrust lever binds, close P3D, restart P3D, and set up the thrust level behind again, but this time leave the calibration to default. What I believe is/was happening is that the thrust lever signal was still being sent (add thrust, no matter how small) and that overrides the reverse thrust command.

I apologize my friend. A thrust lever, which you might have seen or referred go as a throttle lever, is a hardware axis on a controller which can be set up to ckntrol the Airbuses thrust lever(s). I was asking if you used one or more of these. Understand the issue you're having. I also understand why you jump to what looks to be a common denominator, but its not really case as thete are a few reasons why something might work with one addon and not another. So anyway, are you using a thrust lever or throttle quadrant? If so which one? If so, are you using P3D control bindings or FSUIPC? Would you please po rovide screen shots of the control setup/bindings and calibrations? Looking forward to hearing back from you.