If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Treat everyone else in the forum with respect even when you disagree. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.Ģ) BE NICE. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. This is one of the few rigid rules that we enforce regularly. You took the time to be here, we want to get to know you. We do this in order to keep conversations personal and familiar. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. If I want to cause a keypress, how do I configure that? "GAUGE_KEYSTROKE" seems likely, but the value must be ASCII or string?1) SIGN YOUR POSTS. The other pair seems to have a similar issue, but that is complicated by "NEXT_VIEW" and "PREV_VIEW" not doing anything, which is probably not your problem. On the yoke the aileron trim is now on the top button, and the sub-view switch on the bottom one. My current profile, when loaded in the configurator, has:īutton "Elev Trim A UP" set to "K:NEXT_VIEW"īutton "Elev Trim A DN" set to "K:PREV_VIEW"īutton "Elev Trim B UP" set to "K:ELEV_TRIM_UP"īutton "Elev Trim B DN" set to "K:ELEV_TRIM_DN"īutton "Aileron Trim Left" set to "K:PREV_SUB_VIEW"īutton "Aileron Trim right" set to "K:NEXT_SUB_VIEW"īutton "Rudder Trim Left" set to "K:AILERON_TRIM_LEFT"īutton "Rudder Trim Right" set to "K:AILERON_TRIM_RIGHT" The only mystery I have left is that I made my own version of the PMDG NGXu profile for the Alpha, where I added bindings for switching views, only to find that after I activate them, buttons appear switched. I even removed FSUIPC as it isn't doing anything.īetter still, the axes now work both with and without FSUIPC. I tried calibrating, changing sensitivity, but nothing helps. Configuring them in Prepar3D itself had as effect that, with the physical levers on zero, the PMDG throttles were somewhere at 10%. But for a flight this evening I needed the 737, So I enabled all the profiles and translators, and found the throttles still don't work. Wasn't able to get all lights to work, but between the Configurator and LINDA I'll get it to work eventually. All configurations wiped.Ĭonfiguring the Bravo to work with a pretty basic dual-engine prop aircraft (Alabeo Cessna 404 Titan) went well.
Fsuipc 5 upgrade#
Needed to upgrade LINDA to 3.2.x as well, so in the end everything was shiny and clean. Searching the FSUIPC support site I found that I was lagging a major version behind, so I spent the 12 euros on FSUIPC version 6 and tried again. No matter how I change the settings in FSUIPC, they will not behave.
Fsuipc 5 full#
Moving them from zero to full power will make the reversers behave weirdly, but do nothing to the actual 737's throttles. Then the problems started: For some reason the throttles will not work with the PMDG NGXu. Now with the Bravo you need the new software, because of the lights, and you can simply load empty profiles for the buttons. Since then the Configurator has grown, but I never noticed.
When the Alpha came I simply did not install the associated software, because it was too much focused on mapping buttons to keystrokes, which is kind of doubling the effort, because you then still have to map that key in Prepar3D. My setup used to be Prepar3D 4.5, with FSUIPC 5 for the axes, and LINDA 3.1.x for the buttons. I spent a partly happy, partly frustrating day with my Bravo.
0 kommentar(er)
