mbucholski

I have found the culprit of PMDG brake issues in my FSUIPC.ini: [JoystickCalibration] LeftBrake=-16380,16380/16 RightBrake=-16380,16380/16

Well, I've experienced this on several rare occasions in my MD11 (200+ hrs) and I'm very sad to see the same issue in the 777 - it goes as follows: 1) Autobrakes kick in on touchdown, 2) Reversers deployed, 3) Upon roll out and deceleration manual trials to deactivate the autobrakes are ineffective (either keyboard, Saitek Yoke, Saitek Aviator, Saitek Rudder, in different combos), 4) I deactivate the autobrakes using the parking brakes, 5) Brakes stop working. Pressing the dot key or FSUIPC-assigned joy keys give zero response. Red FSX info bar doesn't appear. 6) I'm left only with the parking brakes for taxiing. 3 landings so far in the T7 and this happened every single time. I noticed this occurs more frequently after I've assigned all my buttons and axes via FSUIPC, but this is the only reasonable solution for a Win8 user. I deleted the brakes assignment altogether from FSUIPC - no luck. Going to delete FSUIPC.ini now. PS. What's interesting, is that glitches occur also on takeoff: red FS info bar (BRAKES) appears on lift-off and can only be deleted by cycling the parking brakes (T7, never MD). EDIT: Deleting the .ini seems to help. So much workload in this hobby... :rolleyes:

Approx. 800 MB. I will not state exactly, I don't know whether this is permitted by the EULA (sorry if not!, no harm intended).

The disagreement here is that some are talking normative and others positive. And I'm with the normatives - how can managements sleep at night knowing their employees are on food stamps? It's simply unjust. Want to see the law of supply and demand go mad? Look at the casus of PA Child Care.

You can assign the hat switch via FSUIPC. It doesn't work as smooth though. Space bar will have to be INOP. Side note, I run with controls enabled in FSX, as it doesn't really matter with FSUIPC assignments and doesn't give you above hiccups. I have my hat switch assigned both in FSX and FSUIPC - you can easily see when the input dropout occurs.

BOX512 EDDP-LIME.

His tribal forum games remarks are spot on though.

Marginal, but your mileage may vary.

Honestly, with 8.1 on the horizon it's a pretty risky business.

No issues with FSX and Vista, been running this config for 1,5 year.

Normal. Depends on your Cost Index and/or Policy Descent speed if active.

Gulfstream is unhappy with the idea, so I heard.

It's for the hours.

Varies. It takes years to jump to the left seat, so that's quite irrelevant. Regional entry F/Os circa $20,000/year. You're better off in Taco Bell.

After all this time, I'm pretty convinced the problem is in the kernel and there isn't much we can do. We're destined to either use FSUIPC or loose input unless MS shows some effort and interest.