These are the Support Forums for FSUIPC and related products.
These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.
Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.
Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE
I will also test this with the PMDG 737 and 737 in MSFS2020. Could you also try this in the PMDG 737 on MSFS2024?
If this is needed for all PMDG boings, I could set this automatically and remove the new BrakeRelease ini parameter.
However, I am busy for most of tomorrow so I will check this over the weekend...
Ok excellent news, the new FSUIPC.exe works. Not sure what else you changed besides the brake threshold and the brake release PMDG but we're in business!!
Order of process:
Removed the press and hold command to the keyboard that I was using to bypass the parking brake issue (screenshot attached of how I was doing it, explained in the previous post). Second I rechecked my pedals in joy.cpl through windows. I did a 10%, 40%, 50% and 100% physical press of the pedals, screenshots attached. I have no idea why the values go from -16383 directly to 0 then from 0 to 16384 with all of the values in between in MSFS, DCS and FSUIPC...As you can see windows is correctly reading all of my physical to digital signals correctly.
Then I removed the FSUIPC axis calibration, this had my pedal axis reverse automatically. Then I added a reverse scalar as I no longer had the the FSUIPC calibration which smooths out my pedal movements to follow the actual physical movement. The parking brake came off immediately because my pedals were jumping from 0% to 50% as soon as I went 5% actual on the pedal. So that was back to square 1.
Then I added into my FSUIPC.ini
BrakeReleaseThreshold=90
BrakeRelease=PMDG
Restarted FSUIPC
Re added the axis calibration in FSUIPC to the specs that I had originally 0-16384 with REV checked off. Didn't work. Also tried -16383 instead of 0 to 16384, still didn't work.
Downloaded the .exe that you provided above, loaded in and it works!
So we're back in business now with this new FSUIPC.exe that you provided.
MSFS2024, PMDG 737 & 777 parking brake disengage both work without issues with my FSUIPC calibrations.
Thank you again for your very prompt responses, help and working results!
Jordan
Posted by: @jsheckDownloaded the .exe that you provided above, loaded in and it works!
So we're back in business now with this new FSUIPC.exe that you provided.
MSFS2024, PMDG 737 & 777 parking brake disengage both work without issues with my FSUIPC calibrations.
ok, thats good...
Posted by: @jsheckI have no idea why the values go from -16383 directly to 0 then from 0 to 16384 with all of the values in between in MSFS, DCS and FSUIPC...
Is this still the case? It could be a registry issue - please see the following FAQ entry:
I have removed the images you attached as they don't add anything. I always prefer a description and files rather than images - if I ever need to see an image/screenshot or video, I will ask for one.
Fixed the registry issue with the link provided for the pedals.
Now showing the proper -16383 to 0 then 0 to 16384. Still works to engage and disengage the parking brake. Removed the 2 old lines in my FSUIPC for the original GUID on the pedals, replaced with the new so I could use the same AX and AY lines. Everything works perfect.
Tested the 737 and 777, both function correctly.
Thank you again for your help! I'd call this fixed with the new FSUIPC.exe
I have added automatic detection of the PMDG 737 and 777 and sets the brake parameters accordingly. Could you please try/test the attached version. You can remove the BrakeRelease and BrakeReleaseThreshold ini parameters from your profile JoystickCalibration section with this version.
Regards,
John
@fsuipc I will be back home tomorrow around 2300Z. Will give it a try then.
