Jump to content
The simFlight Network Forums

xkoote

Members
  • Posts

    22
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Dubai

xkoote's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

0

Reputation

  1. Issue indeed fixed, thanks to all !
  2. Solved !!! You guys rock. Thanks a million .... [Buttons.PMDG DC-6] 1=CP(-B,1)A,0,C66587,40202 -{ROTOR_BRAKE}- 2=CP(-B,1)A,1,C66587,40201 -{ROTOR_BRAKE}- 3=CP(-B,1)A,2,C66587,40302 -{ROTOR_BRAKE}- 4=CP(-B,1)A,3,C66587,40301 -{ROTOR_BRAKE}- 5=PA,5,K87,10 -{Key press: ctl+W}- 6=UB,0,C66587,40401 -{ROTOR_BRAKE}- 7=PB,2,C66587,43401 -{ROTOR_BRAKE}- 8=PB,3,C66587,43601 -{ROTOR_BRAKE}- 9=RB,6,C66278,0 -{RUDDER_TRIM_LEFT}- 10=RB,7,C66279,0 -{RUDDER_TRIM_RIGHT}- 11=RC,0,C65607,0 -{ELEV_TRIM_DN}- 12=RC,1,C65615,0 -{ELEV_TRIM_UP}- 13=CP(-B,1)C,2,C66587,40002 -{ROTOR_BRAKE}- 14=CP(-B,1)C,3,C66587,40001 -{ROTOR_BRAKE}- 15=CP(-B,1)C,4,C66587,40102 -{ROTOR_BRAKE}- 16=CP(-B,1)C,5,C66587,40101 -{ROTOR_BRAKE}- 17=PD,10,C66587,60101 -{ROTOR_BRAKE}- 18=PD,6,C66587,60201 -{ROTOR_BRAKE}- 19=PD,8,C66587,6001 -{ROTOR_BRAKE}- 20=CP(+B,1)C,2,C66587,5202 -{ROTOR_BRAKE}- 21=CP(+B,1)C,3,C66587,5201 -{ROTOR_BRAKE}- 22=CP(+B,1)C,4,C66587,5302 -{ROTOR_BRAKE}- 23=CP(+B,1)C,5,C66587,5301 -{ROTOR_BRAKE}- 24=CP(+B,1)A,0,C66587,5402 -{ROTOR_BRAKE}- 25=CP(+B,1)A,1,C66587,5401 -{ROTOR_BRAKE}- 26=CP(+B,1)A,2,C66587,5502 -{ROTOR_BRAKE}- 27=CP(+B,1)A,3,C66587,5501 -{ROTOR_BRAKE}-
  3. Unfortunately adding this line to my .ini file creates an error. (24=CP(-B,1),C,2,C66587,40002 << ERROR 19! Line ignored >>). I'll have a look at the flagging options.
  4. Indeed, just came back from testing, and it is now dual function. I will try what Pete said. Else I'll see if flags are worth it. Thanks a lot to both.
  5. Cool Pete. I took the example too literally ;-). Cheers !
  6. Hello, I have dual Saitek throttle quadrants. (for a total of 6 toggle) switches. The 4 middle ones are used to control an aftermarket airplane's 4 mixture levers. By using the compound method, I thought it would be an idea to also use these same 4 toggle switches to control the respective magneto's. [Buttons.PMDG DC-6] 6=RC,0,C65607,0 -{ELEV_TRIM_DN}- 7=RC,1,C65615,0 -{ELEV_TRIM_UP}- 8=RB,4,C65607,0 -{ELEV_TRIM_DN}- 9=RB,5,C65615,0 -{ELEV_TRIM_UP}- 10=RB,6,C66278,0 -{RUDDER_TRIM_LEFT}- 11=RB,7,C66279,0 -{RUDDER_TRIM_RIGHT}- 18=PA,0,C66587,40202 -{ROTOR_BRAKE}- 22=PA,3,C66587,40301 -{ROTOR_BRAKE}- 24=PC,2,C66587,40002 -{ROTOR_BRAKE}- 25=PC,3,C66587,40001 -{ROTOR_BRAKE}- 26=PC,4,C66587,40102 -{ROTOR_BRAKE}- 27=PA,2,C66587,40302 -{ROTOR_BRAKE}- 28=PC,5,C66587,40101 -{ROTOR_BRAKE}- 29=PA,1,C66587,40201 -{ROTOR_BRAKE}- 30=PB,2,C66587,43401 -{ROTOR_BRAKE}- 31=PB,3,C66587,43601 -{ROTOR_BRAKE}- 32=PD,10,C66587,60101 -{ROTOR_BRAKE}- 33=PD,6,C66587,60201 -{ROTOR_BRAKE}- 34=PD,8,C66587,6001 -{ROTOR_BRAKE}- 38=UB,0,C66587,40401 -{ROTOR_BRAKE}- 39=PA,5,K87,10 -{Key press: ctl+W}- 40=CP(+JB,B1)JC,B2,C66587,5202 -{ROTOR_BRAKE}- 41=PB,1,C66587,5202 -{ROTOR_BRAKE}- Line 40 represents my effort. Pressing button 1 on the Saitek yoke, before pressing button 2 of the throttle quadrant, I want it be act out Rotor Brake 5202, which turns the magneto rotary selector counter-clock wise. However it does not work. So the next step was to make sure the rotor bake code works. Line 41 represents my effort to make sure Rotor Brake 5202 does indeed control the rotary switch as it should. It does. You notice the same Jostick B (Yoke) button 1 is set to control the rotor brake code. Any ideas why the code does not work?
  7. Just landed in Dallas on a 15+ hour flight. Flying back home on Tuesday. I see a lot of info here. Means I have homework to do as soon as I get back ;-) Thanks !
  8. Thanks for replying. I’ll try it out when I get back home.
  9. Having been a veteran of the FSX/P3D ways for 20 years now I have reached a stumble block. I like to exhaust as many options as possible before posting, but I haven't reached a clear solution, so I have to ask. 😟 I have used FSUIPC for many years now and like it. All my aircraft are all set up through it. So much so that porting over the P3D profile for a single aircraft (DC-6) made "almost" everything work. The throttles and Prop axes are giving me immense headache. So far I have: - Deleted my DC-6 P3D profile and tried a fresh initial setup. - Removed ALL assignments related to power and propeller management via either an MSFS internal axes or keyboard bind in a custom clear profile. - Tried various FSUIPC options related to possible throttle values. (To Calibration, as normal axis and it's various options) None work. The prop control is completely unresponsive, and as I have it now (To FSUIPC Calibration) when you move the physical joystick axis, the engine wants to change setting. However due to the throttle in the DC-6 VC not moving together with the joystick axis, the power jumps back to the current setting. Any ideas? p.s. I am cc-ing this post in the PMDG forums as well. All my other axes (aileron, rudder, individual brake pedals and flaps) work. As well as all buttons (rudder and elevator trim, separate mixture controls) assigned via the same FSUIPC profile. Thanks,
  10. Hello, I tried searching the forums and the net without result. I remember when v4 came out, the old plugin went out the window. Pete's last comment regarding this I remember was that it was not sure if it would come back as Lockheed keep changing the location of the necessary values. My question is, has this changed at all since? Or has the plugin remained elusive? Contrary to popular belief, the friction model is still bad. You still need way more thrust than in real life, and the old plugin was a true Godsend back in it's day. Kind Regards, Xander
  11. Pete, I'm still pretty new (2 days) at FSUIPC calibration and so I have not read up on all the differences. But what did the trick on the 747 and that didn't need to be done on none of the other axes mentioned above was to instead of sending the setting to FS as normal axis I chose to Send Direct To FSUIPC Calibration. It was probably because I don't yet understand the difference between these two. So when I sent it directly to FSUIPC Calibration, selected Rev. and the calibrated the axis it started operating normally. i.e. First inch of travel arms the spoiler, on the ground, full axis travel is full spoiler travel. And when airborne, the axis moves to the FLT DET and stops (at around 60% mark). Further movement of the axis towards fully deployed makes no difference. For those interested, all my throttle, propeller and spoiler axis assignments have been deleted from P3D v4 All is solved, thanks for the input. Xander
  12. Pete, I'm testing airborne. I will try to reset the calibration and set the Rev before assigning Pete. Thanks, Xander
  13. Hey Guys, I am hoping someone can help me on this. I have a Saitek Yoke and Throttle setup. I fly the PMDG 747, 777 and DC-6. As such it has now become a necessity to use FSUIPC to map the throttle quadrant to match my aircraft. I have now managed to: 1. For the DC-6, match the three axes to ENG 1/2, ENG 3/4 and the Master Prop Lever 2. For the 777, match the three axes to ENG1, ENG2 and Spoiler Lever 3. For the 747, match the three axes to ENG 1/2, ENG 3/4 and Spoiler Lever <-- HOWEVER..... The 747 spoiler range has a flight detent tab that seems to throw my spoiler axis completely out of whack. If I just assign the axis it works correctly, but it is not reversed. With the lever to max the spoiler correctly moves down to the Flight Detent. Bring the lever down to min and the spoilers jump from the Flight Detent back up to the Retract position. As you can see, it needs reverse sensing. To do this I have to go to Joystick Calibrations under spoilers, and select "Rev.". This does the trick on the 777 which does not have a Flight Detent setting. On the 747, the spoiler lever suddenly acts completely out of whack, floating about between RET and FLT DET. settings. Anyone have a clue what I can do to solve this? Thanks, Xander
×
×
  • 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.