Jump to content
The simFlight Network Forums

Andydigital

Members
  • Posts

    1,227
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Andydigital

  1. Linda doesn't really allow you to assign anything that you can't do in FSUIPC directly, LINDA mainly just makes the process far easier for beginners and programmers alike. FSUIPC does have the controls you are looking for though, you just aren't looking the correct name, look in the PDF "list of FSX Controls" located in the FSUIPC documents folder, the items you want have the name "Alternator" in them.

  2. Don't send direct to FSUIPC nor can you calibrate the throttle axis, otherwise you will get that snapping problem and the override AT option set to NEVER won't work either. You must also make sure that you are not using any custom slopes for the throttles. Finally if you are using the script from the user contributions section of this forum that allows you to use the throttle levers as reverser's (after pressing a button) you must remove that too as that will also stop the throttles working correctly in the NGX. All the above is also true with the new 777 from PMDG.

     

    I do not have a set of these Jetmax quads, but the same is true for any throttle and the 777 or NGX.

  3. The snapping back that Arnaldo speaks of probably isn't what it normally looks like i.e. dual assignment, in the case of the 777 its the calibration data in FSUIPC which is causing PMDG's throttle control to not function correctly. This is how it looks, the throttles will start to move forward as you push your hardware throttles then suddenly the throttles in the VC snap back to idle. It will only do this when the engines are running and both AT switches are armed, if either of those conditions is not true then the levers will appear to work perfectly.

     

    This is how I fixed it. Delete the lines mentioned below from the [JoystickCalibration.777] section of your 777 profile (my profile is called "777") and it will work perfectly as long as you have followed Pete's recommendations above and you choose send to FS as normal and choose Axisthrottleset or whatever the correct name is.

     

    Delete any lines like this;

    Throttle1=-16253,-512,512,16128/32
    Throttle2=-16253,-512,512,16128/32

     

    If you only have one throttle assigned it will be similar to this below, simply delete it;

    Throttle=-16253,-512,512,16128/32

     

    And you must remove the slope entries too if you have set any, which will be something like;

    SlopeThrottle1=12

    SlopeThrottle2=12

     

    or this if you just have the one throttle;

    SlopeThrottle=12

     

    Since doing this and setting the PMDG FMC menu option for the AT override to "NEVER" it has worked perfectly for me. PMDG must not like the calibration data or the slope data.

  4. Very true Pete. It also explains why those buttons can sometimes flicker, because if the pot is dirty it will look to the firmware like you have pushed the lever below the detent, when in fact it's just spurious voltage changes because of dirt. The pots once cleaned out with contact cleaner looked like new and work like new, I'm sure I could get at least another 3 years use out of them before they need cleaning again.

  5. Ironically the area below the detent isn't really a button, in reality it's a range on the pot that forces the firmware to press a virtual button. I took one apart a couple of weeks ago to clean the pots and there was no switch at the bottom of the range of movement, there was just a sprung ball and socket for the detent itself. I should have looked while it was open at how easy it would be to create some more detents say at 25%, getting two levers to match exactly would be the hardest part, I'd imagine drilling a divet for the ball would be quite simple. The range of movement below the existing detent is so small it would not be possible to use it as an axis, it's actually below what is output to Direct input, only the board itself can see this range, it's not seen externally by Windows.

  6. I'm sorry but that is completely incomprehensible to me, I think you need to use a better translator or ask a friend who speaks English to help you. All I can understand is that you has some kind of error, but without you copying that error here to your forum post there is no way we can even begin to help you.

  7. I have a problem with this statement;

     

    "order 3 or "R" Check items, advances one step and hangs the PC."

     

    This is not FSUIPC making the simulator hang, it must be whatever this addon Ultimate Checklist is doing when you send that key. I've still never heard of this addon and a quick Google search tells me its an application for Android devices, so I am still non the wiser. Like I've said repeatedly this hang and the app not working as expected can only be resolved by asking for support from the developer of Ultimate Checklist, it's highly unlikely that FSUIPC is hanging the sim.

     

    By the way Shift + 123456789 opens 2d panels in some aircraft, so you don't want to use those either, and CTRL + numbers also has something assigned if I remember correctly.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.