After latest update I noticed my toe breaks on landing do not seem to slow down the aircraft. I.e. no break pressure or not enough pressure to stop the aircraft. You can depress Saitek toe breaks to the floor and no slowing down. All settings and sensitivities have not changed. Break movement in sensitivity settings does appear normal? During taxi breaks seem fine?
Any help will be greatly appreciated
Which aircraft?
Citation Longitude
The aircraft is no longer controllable when landing. Takeoff, flying, etc is all good. Once on apron of runway the rudder and breaks no longer function correctly. Msfs2000 forced an upgrade on Saitek driver before it would start up. Once Saitek driver was upgraded msfs2000 started up ok. From then on the Saitek rudder peddles and breaks do not work correctly on landing! We had a perfectly good aircraft at one time! Well, twice over and now you cannot land it?
Wonder if I can roll driver back? Sim probably will not Start up!
I, like others, are getting frustrated with this. Rudder and breaks seem ok when taxi. Additionally, this is a clean approach to runway and touch down. On runway aircraft is not controllable. breaks seem not to slow aircraft?
Not sure who to point at:
Microsoft or Saitek?
Maybe check that you have nothing selected in the Assistance options that might be putting the AI in control of your aircraft
This has been done.
Thanks
Actually, it’s possibly something to do with the flight model issue, where the flaps are generating too much lift and therefore unweighting your wheels from the runway.
Maybe try raising the flaps straight after you’ve landed, to see if the brakes work any better.
Unfortunately, the Longitude is one of the payware aircraft, so isn’t user patchable. If this is the issue, you’ll need to wait for the next update, Sim Update 3.
Edit: Maybe give the modded CJ4 a go. It’s a blast to fly.
We have actually built the cockpit hardware around the Longitude! All of our hardware and software works well with the sim. Now, we just build a throttle adaptor for the Saitek that brings it more up to the spook, although it is flimsy! We had a combat throttle on this thing to start as a temp and it worked great. When we put the Saitek in the simulator would not start but would just hang on start screen. And of course, it hangs and does not timeout and tell you what’s wrong— no fault banner!
Upgrading the Saitek driver, required for msfs startup, may be the problem. The Saitek throttle and speed break unit we installed may be a cause. I will switch back to the Thrustmaster we have on an A-10 and see what happens. I would think the Saitek throttle is a popular one and we should see this problem more here, but I have not?
Thanks
Hope you or others can bail us out!
Well guys, the Citation Longitude is flying again! We defaulted the peddles and Breaks then reconfigured, for a second time. Can’t say we did much, but we took HawkMoth’s idea and took the CJ4 up and landed to see if breaks worked well with this aircraft. And they did! We then took the Citation Longitude up and landed it and all worked fine as well! We also powered down in between tests. So, what happened? It has to be something we did unknowingly? I am amazed that this sim was running for a week after The latest upgrade and then decided it would not startup because of a Saitek driver that was there before the upgrade? Well, we just guessed On the Saitek driver and got it right. To bad we cannot get a banner from the sim thay gives us a hint As to why it is stalled out waiting for something?
O well,
Thanks for help and I am sure I will be back soon!
Just to keep others informed, today we again tried to startup MSFS2020 and it again stalled out on the splash screen! Now since the software will not timeout on a loading exception, but Will continue to do something, you have to guess at the problem. Windows 10 update will show you a list of drivers that may be causing the startup issue (Win 7 can why not MSFS2020). Again Windows 10 indicated that the Saitek driver was not up to date, as it did 3 days ago. So we updated the driver and again MSFS2020 started up and there were no adverse problems with the Citation this time.
Three times we have had this loading problem where the first was a Windows 10 update that fixed it. The last two times were drivers associated with hardware used with the sim. When you see this busy circle at the lower right of your screen continue, it becomes very Uncomfortable because you do not know if you will recover, meaning many more hours of troubleshooting, again, and again! The developers software should timeout with some exception indicating something like an error code.
Let me just add, this is a great package and I know it will improve over time.
Hey RR, this is slightly off subject but to do with toe brakes.
I have tried numerous times to assign my toe brakes without success. I have Saitek Rudder pedals and when I try to assign under LEFT BRAKE AXIS, and do the motion, nothing happens (same for RB AXIS).
I haven’t been able to find any posts on this, so any suggestions would be appreciated thanks.
Open the Windows USB Game Controller dialogue and open the properties of your rudder pedals. Do you see the associated axes move when you press each of the brake pedals?
If so, then when doing the mapping in MSFS, instead of scanning for input, maybe try selecting the relevant controller axis from the drop down list, for each of the two axes.
HawkMoth is correct. Under devices your peddles should show up if they have been recognized by windows. First step
My set up in on a PC and when you try to assign LEFT BRAKE AXIS and RB AXIS, if you try to scan for input, nothing happens, so the other options is to pick from the list. They include L Y, L Y+, L Y- and the same for the R axis. None of these work, so I have given up and now have my brakes assigned to the E button on the back of my Saitek yoke, which works fine, but loses the reality.
Kubar, did windows device manager recognize your peddles? Do your peddles show up under devices?
I command thee to come out of the rock under which thou hast hid thyself, and behold the light, for, unpatchable though the Asobo Longitude might seem, yet hath one of us, Dakfly0219, a true son of his father, found a way around that (without breaking any rules), and has even updated it to the latest UK up(down)date 
, and those of us who witnessed him solve this puzzle, are so overjoyed that we have vowed within ourselves to never touch the stock Longitude ever again. No, not even with a 20-foot pole. For it does not come close in any way whatsoever to the mod that Dakfly0219 has created. This mod works perfectly with the Working Title Garmin G3000/5000 mod.
Behold some of my most cherished images that I took myself:
Get those two mods, and you will never touch any other aircraft (saving, maybe other modded ones like the A3NX, TBM, etc, of course).
For the Working Title G3000 (in case you don’t know of it):
or:
living under that rock was a little uncomfortable, so many thanks for that. 
