Jump to content
The simFlight Network Forums

chumley

Members
  • Posts

    25
  • Joined

  • Last visited

About chumley

  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Not Telling
  • Location
    Australia

chumley's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. The Twin Otter is the biggest load of rubbish ever produced. For the life of me I cannot get the throttles synchronised when in every other add-on aircraft they work as expected. Visually they flick and dance around more than Gary Gilmore did when he met his fate and he had 2,500 volts going through him.
  2. Just a small further question. I have just noticed that the toggle doesn't respond to the first button press but then activates on each press thereafter. Is this a normal situation?
  3. I used the GUI as you suggested to select the byte togglebits and in the Offset box I entered 66C0. After manually changing the .ini to correct the offset and returning to the GUI I now realise I should have entered an x before the 66C0. Working as expected now. I now feel a bit more confident and motivated to move forward. Once again many thanks for the help.
  4. Thanks again Pete. I have put your code in the FSUIPC.ini and it works just fine. I will work through it in detail to get across the structure using the various manuals as you suggest as i can see quite a bit to gain particularly if I progress to putting together a few switch panels with the help of a friend. I also delved a little further into your original suggestion and have come up with the following coding in the FSUIPC.ini which has a problem in that it toggles the taxi light on but doesn't toggle it off. 4=P1,0,Cx0D000042,x01 -{offset byte togglebits, offset 0042}- 5=B66C0=0 P1,0,C69749,1 -{Custom control: <69749>}- 6=B66C0=1 P1,0,C69749,0 -{Custom control: <69749>}- I'm obviously missing the point somewhere. I appreciate your help in this matter. Thanks
  5. Hi Pete After a period of reflection I really do want to be able to control more of my Sim using a combination of keys and buttons so am asking of how the FSUIPC.ini file can be amended to make the example below work. Once I have a framework to work with I will be able to make similar functions happen. So my example is I want to use the Joystick 1 Button 1 to action the taxi Light switch on the PMDG NGX panel which according to PMDG is 69749 (69632+117). After using the GUI to create the first action I have: 4=P1,1,C69749,1 Note: (0-3 inc in the numbering sequence are taken up with viewing option using the hat switch on the yoke) I have had a look at the various documents but cannot quite come to grips with the process. I know from previous comments by you that two more lines will allow a conditional test to be applied and presumably from that a second press of the P1,1 will switch the lights off. How would those two conditional lines be coded? I have tried this but it doesn't work: 5=B66CO=0 P1,1,C69749,1 6=B66CO=0 P1,1,C69749,0 Thanks
  6. Thanks Pete. I have had a look at the FSUIPC Advanced User Documentation and it is all gobbledygook to me. I think I will stick to flying the simulator 'as is' and pretend the mouse pointer is actually my finger.
  7. I am doing some work on assigning PMDG NGX functions to keystrokes using the information PMDG has provided in the SDK. I have been able to assign the 'Ground Power' to a key and it switches on when I press the key. I would like to be able to have a second press of the same key to switch it off. I have spent some time trying to achieve this goal but thus far to no avail. Is it possible to do this and if so can someone point me in the direction of the way to achieve it. I would consider using a button if that is the only alternative but buttons are scarce whereas keys are many. Thanks
  8. Thanks for the advice. The reason I thought about the 'gear up' link was that the icing event and subsequent power loss happens at varying altitudes depending on the temperatures and ca be a problem when traversing mountains as I do in NZ given the aircraft loses power and descends eventually until it reaches a point at which icing stops then the engine roars to life and climbs again sadly too late sometimes. I figured that if I turn on Carb Heat when the gear goes up and off when it comes down that would stop me forgetting.
  9. I read somewhere (can't for the life of me remember where) that to ensure Carb Heat is always switched on to circumvent the P3D fault it can be linked to the raising of the undercarriage. I currently have a lever (axis) on my TQ6 controller set to raise and lower the gear. Is it possible to link the Carb Heat function to this action on my controller and if so could you point me in the direction of how it is set up Thanks
  10. Thanks again Pete The only reason for the alignment was that I thought I may have been missing something in the setup but if it's just the vagaries of hardware then I'm not that bothered. At the end of the day I have managed for quite a while with the different values and it hasn't stopped me enjoying what I'm doing. Having said all that I'll get back to what I enjoy doing. Thanks for your time (and of course FSUIPC)
  11. Thanks Pete I had a crack at Syncing the throttle levers following the information referred to above. After doing this I had the following values showing in the .INI file: SyncSlopeThrottle2=7/9,19/19,30/30,44/41,53/51,64/63,75/71,87/86,97/96,108/106,120/121,127/128 When testing this the N1 values in the PMDG NGX are still up to a couple of units in variation when the levers are visually at least correctly aligned. I should add that I have, using a spirit level, drawn a line on the throttle unit and moved each lever to the line - the N1 values are L - 75.3 and R - 77.6 I'm pretty sure I followed the instructions carefully. The question I have is - does the data from the .INI file look reasonable and should it still show the kind of differences in N1 values I am seeing? Thanks
  12. I have a GF-TQ6 Throttle Unit connected to P3D and two throttles mapped in FSUIPC for the PMDG NGX and using direct mode with no reverse zone. With the throttle levers in the same position I am getting different thrust settings on the PMDG guage on the display. I have checked the settings in the Joystick Calibration page and have the following settings for the two controller levers: Approx setting Throttle 1 Lever Throttle 2 Lever Max 16383 16383 Min -16384 -16384 75% 11430/13907 11543/13963 50% 4000/10192 4282/10333 25% -4572/5906 -3724/6330 I accept that the internals on the throttle levers are most likely prone to giving different readings for the same position but I am wondering if there is some feature in FSUIPC that will remove this discrepancy. Thanks
  13. I have a Goflight GF-TQ6. This unit has been calibrated and all the levers assigned as Axes in FSUIPC to functions. The issue I have is that after assigning the levers the settings for the throttle levers to Throttle 1 and Throttle 2, using the 'direct' option, no reverse zone and having the filter box checked. When I advance the levers together (aligned) the following results are shown in the PMDG gauge: Setting Left Right Full 98.0 98.0 80% 80.0 82.2 70% 70.7 73.2 60% 60.7 63.1 50% 50.3 50.5 40% 39.8 41.6 30% 29.4 32.1 Idle 20.5 20.6 To get near identical thrust on each engine the levers are not aligned. Is this a situation where I should use the Syn Pos option or is there an alternative way. Makes taxiing a little problematic. Thanks
  14. I got the same pop up but only in the load immediately after uninstalling FS Passengers X. I am having the same issues as the OP (with FS passengers X) so I expect his apparent FSUIPC problem is for the same reason. I'vr given up on FS passengers. No support. An expensive waste of time - many better things to do. As always, FSUIPC, is delivering the goods. Thanks for that. Regards Andy b
×
×
  • 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.