cfoley Posted March 1, 2014 Report Share Posted March 1, 2014 Hi, I just recently started having problems with my Level-D 767 Vertical speed. It will not hold on auto pilot and the plane just shoots upward at a very steep climb. I tried all kinds of trouble shooting and sumbitted a post in Level D and they suggested I re-install Level D 767 and FSUIPC. I did reinstall Level D 767, but not FSUIPC and when I did 3 test take offs, it seemed to work ,but on a planned flight, the V/S stopped working again on descent and on another, it did not work on take off. It just keeps shooting upward and there is no control unless I push the nose down. All my other add on aircraft work fine. I have purchased FSUIPC last fall and have used the 767 since then without this problem. In your opion, should I reinstall FSUIPC and if it may help with this problem? My only concern is other problems crop up if I re-install FSUIPC. Link to comment Share on other sites More sharing options...
Graham Pollitt Posted March 2, 2014 Report Share Posted March 2, 2014 I did reinstall Level D 767, but not FSUIPC and when I did 3 test take offs, it seemed to work ,but on a planned flight, the V/S stopped working again on descent and on another, it did not work on take off. Did you have FSUIPIC reinstalled again when V/S stopped working? Above you don't mention reinstalling it. If you didn't its not a problem with FSUIPC If you did have you checked buttons and axis assignments in case there has been a control assigned that shouldn't be and is overriding the AP? Link to comment Share on other sites More sharing options...
cfoley Posted March 2, 2014 Author Report Share Posted March 2, 2014 Thanks for the reply! No, I did not reinstall FSUIPC. I kind of figured FSUIPC was not the cause but just wanted to find out if reinstalling it might help. But since it is likely it is not the cause, I will not reinstall it. I checked the FSUIPC Axis assignments and nothing is selected for Level D 767. Link to comment Share on other sites More sharing options...
flibinite Posted March 3, 2014 Report Share Posted March 3, 2014 Suggest save your FSUIPC4.ini file somewhere safe. Then delete it, and start FSX - try a flight and see if the problem persists, that should answer whether or not it's an FSUIPC issue Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now