Sign in to follow this  
MattS

Autobrake and FSUIPC

Recommended Posts

Yesterday I installed P3Dv4 hotfix 1, and FSUIPC update 5.103. Today I flew my first flight in the 747 since the updates and all went well until touchdown. I had autobrake 1 selected for landing on WSSS rwy 2C. The autobrakes engaged properly and everything went well until I initiated manual braking, at which time the manual brakes "stuck" on full with the the red brake text displayed in the lower left. The aircraft stopped abruptly on the runway, and couldn't be moved until I disabled the brake button in FSUIPC (I'm using a side joystick for rudder and the brakes are assigned to the trigger button) and then reassigned it. 

This is the second time I've had an issue with FSUIPC following an update. This time, as well as last time, I deleted my FlSUIPC config file and built a new one which has appeared to fix the issue.  

Has anyone else seen issues like this, and is it SOP to delete your config file following an FSUIPC or other update (P3D or PMDG)? 

I think that I'll be doing this from now on. It only takes be 5 minuted to build a new file and it looks like it could save some headaches. 

Just thought it pass this along.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

9 minutes ago, MattS said:

Yesterday I installed P3Dv4 hotfix 1, and FSUIPC update 5.103. Today I flew my first flight in the 747 since the updates and all went well until touchdown. I had autobrake 1 selected for landing on WSSS rwy 2C. The autobrakes engaged properly and everything went well until I initiated manual braking, at which time the manual brakes "stuck" on full with the the red brake text displayed in the lower left. The aircraft stopped abruptly on the runway, and couldn't be moved until I disabled the brake button in FSUIPC (I'm using a side joystick for rudder and the brakes are assigned to the trigger button) and then reassigned it. 

This is the second time I've had an issue with FSUIPC following an update. This time, as well as last time, I deleted my FlSUIPC config file and built a new one which has appeared to fix the issue.  

Has anyone else seen issues like this, and is it SOP to delete your config file following an FSUIPC or other update (P3D or PMDG)? 

I think that I'll be doing this from now on. It only takes be 5 minuted to build a new file and it looks like it could save some headaches. 

Just thought it pass this along.

Any chance there's an issue with your joystick?

Share this post


Link to post
Share on other sites

The joystick functions normally, never had an issue. No issues since rebuilding my FSUIPC config. Also, controllers are disabled in P3D. 

I should note that manual braking did disengage the autobrake, so I its not a PMDG issue. I have a feeling that it was FSUIPC, especially since I unassigned the button and all was fine. Then rebuilt the config file and couldn't reproduce the problem.

Not bashing FSUIPC, I think it is a fantastic piece of software. But, I find it to be somewhat ornery at times. 

Share this post


Link to post
Share on other sites
10 minutes ago, MattS said:

The joystick functions normally, never had an issue. No issues since rebuilding my FSUIPC config. Also, controllers are disabled in P3D. 

I should note that manual braking did disengage the autobrake, so I its not a PMDG issue. I have a feeling that it was FSUIPC, especially since I unassigned the button and all was fine. Then rebuilt the config file and couldn't reproduce the problem.

Not bashing FSUIPC, I think it is a fantastic piece of software. But, I find it to be somewhat ornery at times. 

Just checking because normally the first problems are either the hardware itself, or the way it's set up. I think since the move to 64 bit, the reliability of FSUIPC has gone down a bit, I think probably because there's had to be significant changes made to the module in order to be compatible.

Share this post


Link to post
Share on other sites

Agreed. I figured I'd put my situation out there in case anyone else experiences something similar. 

We don't need any unnecessary "bug" accusations against PMDG. 

  • Upvote 1

Share this post


Link to post
Share on other sites

Most of the time, this is an issue in FSUIPC, related to how your brake axis is set up and interpreted.

Share this post


Link to post
Share on other sites

I had a similar problem with manual braking after setting up FSUIPC.  When going to manual braking, it was braking so hard I popped all the tires and probably set the wheels on fire!  Stopped on a dime, though!

Problem was I had both fsuipc and default p3d braking mapped to the joystick trigger.  So it's as if it was doubling up on the braking action.  Once I deleted the default p3d mapping, and just set the trigger through fsuipc, now it has been braking fine.

Share this post


Link to post
Share on other sites

I'm not sure if this is related, if not I'll start my own thread, but I've had issues in both the 777 and 747 where the auto brakes are set to RTO and they engage while taxiing.  This is a new issue in p3dv4

dave reage

Share this post


Link to post
Share on other sites
1 hour ago, regis9 said:

but I've had issues in both the 777 and 747 where the auto brakes are set to RTO and they engage while taxiing.

How fast are you taxiing?

Share this post


Link to post
Share on other sites

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
Sign in to follow this