Jump to content

CajunRon

Members
  • Content Count

    91
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

8 Neutral

Profile Information

  • Gender
    Male
  • Location
    Longview, Texas, USA

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

1,550 profile views
  1. How did you program the individual light switches (BCN, LAND, TAXI, NAV, STROBE) directly in P3DV4. I can't find a P3DV4 command for the on/off position of the BCN, TAXI and NAV lights. I think (??) one advantage is to be able to program non-standard switches (like in the PMDG aircraft) IF you know the appropriate codes for them but I'm really telling you more than I know. 😉
  2. Because for some aircraft I don't want to do nothing! For some (general aviation with magneto starter) I want to use Alpha Yoke starter switch. I don't know any other way to use those switches except through the driver since there is a 30 button per device limitation with FSUIPC.
  3. Just go into the YokeInput program and erase ALL assigned commands from ALL switches. Or just erase the switches you want to program with another application (FSUIPC fore example) Remember that each switch has an up position and a down position and represents two buttons. Once you do that SAVE the profile with an appropriate name (I call mine BLANK) and activate that profile. Now the yoke switches are like any other switches on any other yoke/joystick. Program them with what ever you like (FSUIPC, FSX, P3D, etc). There is one caveat. Buttons 31 through 35 (I think) can't be programmed with FSUIPC. In case you didn't know. YokeInput is in the bin directory where it installed it's software. Mine is in F:\Program Files (x86)\aerosoft\Honeycomb\bin\YokeInput.exe"
  4. Thanks for the reply. Yes I understand that. That is why I used the "Create Mouse Macro" method for them. The macro moves the bar above the switches so they all turn on and off together. (In my simple set up that's all I have the switches for anyway) . Could a macro be used for the needed ON/ON/OFF (a different macro for each position)?
  5. For those of you trying to figure out how to assign functions to the Alpha Yoke buttons (for example for using the light flip switches to turn on and off the lights on the PMDG NGX). After a lot of digging into a lot of stuff I didn't fully understand I finally figured out a work around until Honeycomb gets us all of the these templates they promise. First I do NOT guarantee this will work or that my instructions are clear and accurate. USE AT YOUR OWN RISK. All I know is that when I followed these instructions as best as I have been able to document them here, it worked MOST of the time. I am not an expert. I'm sure there are experts out there who know a 1000 times more than I do about all this. I needed a simple step by step guide and by muddling through a lot of expert posts in other forums I've tried to create one here ================================================================================================== How to assign PMDG NGX specific commands to Alpha Yoke (or any other controller) with FSUIPC (purchased version) Two ways to do it. 1. Use "Create Mouse Macro" 1. On Buttons+Switches tab of FSUIPC press Create Mouse Macro button (bottom left) 2. Give Macro a Category Name (for example PMDG73) 2. Close FSUIPC 3. Go into cockpit and mouse click to activate desired control (as you would do in flight) 4. Name the specific macro (For example LandingLightsOn) and hit RETURN 6. Go back into FSUIPC --> Buttons+Switches tab--> Press END MACRO 7. Press button to be assigned and choose the "Control sent when button Pressed" as you normal would. The macro name is in the pull down list. (in example it will be listed as "PMDG73: LandingLightsOn") 2. Pass Commands to P3D 1. Go to the document "Prepar3d V4/PMDG/PMDG 737 NGX/SDK/PMDG_NGX_SDK.h 2. Open with Notepad++ or other plain text reader 3. Find command to be sent (use text reader's search) 4. Find the XXX number (THIRD_PARTY_EVENT_ID_MIN + XXX) 5. Add the THIRD_PARTY_EVENT_ID_MIN number (which is 69632 in this example) to XXX 6. Go into FSUIPC 7. Choose a button to assign 8. In "Control sent when button Pressed" choose Custom Control 9. Enter the calculated Control Number from Step 5 10.Enter any parameters (for example 0 for OFF and 1 for ON) ...I use trial and error to figure this out I hope this helps some of you.
  6. Jose, thanks for the reply. I'm actually trying to set up the reverse thrust for a turboprop. But as is the case many times, right after I post to a forum to seek help, I do a little more investigation and find the solution myself. In this case I MUST use the CH Product Manager but not use the Test/Calibrate tab. Instead I have to use the Throttle Settings tab and set the value that I want the throttle to output when it is in the detent position. Bottom line, I didn't dig deep enough into the documentation for the throttle.
  7. Hi Folks, I've just bought a used CH Throttle Quadrant and have been struggling for days to calibrate (with reverse thrust) with FSUIPC. I got a copy of John Cooks "Configuring FSUIPC with the CH USB Yoke, Rudder Pedals and Throttle Quadrant. version 1.10". He explains that I have to set up an output range for the detent position. Fine and good, makes sense. So I set my full back position value and full forward position value in FSUIPC. But when I go to set the values for the detent position, the input and output values remain at the full back position values until I move past the detent. This occurs with all 6 levers. So in essence the "detent position" is the zero input/output position on the device. This is totally contrary to what John describes should happen in this documentation. I first tried to use the CH Product Manager to first calibrate the throttle before using FSUIPC but then read somewhere that it doesn't work correctly with Windows 10 and is junk anyway so I uninstalled it and tried using FSUIPC as the only calibration processor for the device. But the problem remains. The input and output values don't start changing until after I've moved past the detent. Can anyone offer any insight on this? Thanks.
  8. Slait, that's my take on this as well. They focused so much on the hardware that the software fell through the cracks. And when I tried to get support through their facebook page there was a note that they had all gone to a convention and left no one at home for customer support in the very week that most preorders where delivered. Seems short sighted to me. I'm a little disappointed too.
  9. Anyone know of a support forum for the Honeycomb Yoke. Got mine yesterday...No documentation on button mapping and it isn't intuitive IMHO. I've resorted to FSUIPC offsets to assign functions. Also, what the heck are those 6 tiny rubber caps for. The sparse documentation that comes with the yoke doesn't say and the Honeycomb people are all at a flight sim convention and unavailable for support questions. And why are the last three positions on the starter switch not being recognized as buttons by FSUIPC or the Windows 10 Game Controller Settings (though they are in the Honeycomb settings app)?
  10. I came across an interesting accident re-enactment on the FlightChannel on YouTube. This was the crash of Helios Airways Flight 522. The highly experienced pilots misinterpreted the cabin pressurization alarm with the takeoff configuration alarm which sounded identical. This was on a 737-300 I think. The alarm went off at 10000 ft and they couldn't understand why the takeoff configuration alarm was sounding while in the air when it is only suppose to sound on the ground. Amazingly even after calling maintenance, they never identified that problem was with the pressurization system. It had been place on manual mode and left there by an engineer checking a door seal problem and they failed three times in the preflight and after take off checklist to identify this. Everyone perished on that flight. (One cabin steward remained conscious but didn't know how to fly the aircraft and so died in the crash when it ran out of fuel) What is interesting is that in my own experience with the PMDG 737-800 on some rare occasions I have gotten that alarm myself but didn't know what it was (I've never taken cabin pressurization seriously while sitting in my desk chair at 350 ft ASL while simming). Amazingly, other than the audible alarm there is NOTHING that I could find that identified the problem. On my last encounter I did finally put two and two together and finally diagnosed and found that the bleed air was off (have no idea how it got in that position). I think I corrected the problem at 18000 ft so I and my virtual crew and passengers survived. But more interesting is that, according the the accident re-enactment, in March of 2011 the FAA issued an air worthiness directive requiring all 737s of the 100 to 500 class to have two additional cockpit warning lights, presumably (though it was not clear) to differentiate between a takeoff config and a cabin pressurization alarm. Curiously, the PMDG 737 NGX doesn't model this additional warning light (I frantically searched for one when I got the alarm). Assuming that PMDG modeled the 737-800 correctly and that there is no required additional warning light in that model, it raises the question why would the FAA confine its directive to only the 100 to 500 class and not the 600 to 900 class which by my personal experience suffers from the same deficiency? Here's the link to the YouTube video I think you'll find it really interesting. https://www.youtube.com/watch?v=Go3K0UUt2Us
  11. In the PMDG 737-800, I'm flying the HAWKZ7 Star with a LMT transition to the ILS34L with PONDR transition approach into KSEA. I get an FMC message almost immediately after takeoff that says "NO DES PATH AFTER GOALZ". When I check the Legs pages I don't see a problem. All of the proper way points are there and they all seem to have correct and achievable altitude guidance and restrictions and no discontinuities. Why am I getting this FMC message?
  12. Sorry, I was confused. I interpreted the IMPORT button on the GTN to mean import the flight plan shown above it. I didn't understand that the import button was how you got your list of flight plans to import. Dang I feel pretty dumb now. Guess I should have read the manual.
  13. Thanks. Please consider that some of us "long in the tooth" simmers can't even remember what we had for dinner last night much less what we may have read weeks or months ago. I guess until the government initiates a "Thinning" program, you younger whipper snappers will just have to put up with us. 😉
  14. Thanks to all. Just as an "excuse" to save a little face. I had adjusted the scaling factor on my display to make the text size larger so that these 68 year old eyes could read the desktop text on my curved screen monitor. This caused the right side of the Operations Center window to be truncated so the ADD button wasn't visible. (Yes it did warn me but I just thought it was text that was being truncated...didn't think that some buttons would not show as well)
×
×
  • Create New...