jahman

Hello, Pete! I´ll let Microsoft know at the email you mention. Let´s hope it gets fixed for FSXI! All the best for you in 2008, Cheers, Andrew.

I´ve encountered these last(!) :D "Flight Replay" Mode problems in my quest to replace all hardware configration in FSX with FSUIPC: A. POV Hat The POV Hat pans around the aircraft nicely when in the "Flight Replay" mode and when assigned in FSX Config to "View (Panoramic)" <-- Translation from Spanish. Logging via FSUIPC v. 4.208 reveals FSX SP1 assigned the POV Hat to the "PAN-VIEW" control with parameters of 0, 45, 90, 135, 180, 225, 270, and 315 when the hat is ,and always a "PAN-VIEW" of -1 when it is released. LOG Example of FSX Using the POV Hat: 6838924 *** EVENT: Cntrl= 66416 (0x00010370), Param= 270 (0x0000010e) PAN_VIEW Now I de-assign the POV Hat in FSX and replicate the exact same assignment in FSUIPC via the "Buttons and Switches" tab (Buttons 32-39), but... Now the POV Hat no longer works!! (but works just fine when not in "Flight Replay" mode!) :shock: (BTW, the POV hat is NOT assigned in the FSUIPC "Axis Assignments" tab.) B. Camera Selection Ditto for switching camera views: The "VIEW_CAMERA_SELECT_(n)" works for the "Flight Replay" mode when assigned in FSX but not when assigned from within FSUIPC! Both camera selection LOG entries are identical: Via FSX Config: 1245687 *** EVENT: Cntrl= 66852 (0x00010524), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_2 Via FSUIPC: 1265344 *** EVENT: Cntrl= 66852 (0x00010524), Param= 0 (0x00000000) VIEW_CAMERA_SELECT_2 How can one work and not the other??? :shock: Again with cameras assigned via FSUIPC switching cameras works fine, provided I´m not in "Flight Replay" mode!) Any tips most appreciated! Cheers, jahman.

Thanks, Peter! :D Indeed, Windows also uses the CH calibration software!Cheers, jahman.

Setting Thrust Reverse, Prop Feather and Mixture Idle-Cutoff with CH Hardware For USB Yoke Pad, USB Rudder Pedals, USB Throttle Quadrant, with FSUIPC 4.207 (or later) and the Microsoft FSX Beechcraft Baron and Super King Air aircraft (will likely also work for other standard FSX a/c). A Beguinners Guide FIRST, get FSUIPC - Flight Simulator Universal Inter-Process Communication (make sure you purchase so you can register and get the full features.) 1. Purchase: http://secure.simmarket.com/product_infts_id=2068 2. Download: http://www.schiratti.com/files/dowson/Famp=250707 3. Update: viewtopic.php?f=54&t=55488 This is the latest update (v. 4.208) with a fix regarding the mixture levers. SECOND, Read: 1. FSUIPC Users Guide for CH Products Hardware at viewtopic.php?f=54&t=59729 (Kindly posted by "flyboy2002"). 2. FSUIPC User Guide (Basic), and 3. FSUIPC User Guide (Advanced) Reference Manuals provided in the FSUIPC zip you downloaded. Additional Info (in case you landed here direct via a Search Engine): FSUIPC Web: http://www.schiratti.com/dowson.html FSUIPC Support: viewforum.php?f=54 This forum! (Promptly provided by Pete Dowson, FSUIPC Developer, with advice and suggestions offered by other users.) THIRD, the Beginner´s Configuration Notes! Here are some "Notes to Flatten the FSX/FSUIPC/CH Products Thrust Reverse Learning Curve" and save you time so you can keep flying! Note 1: Buy and Register FSUIPC You may already have FSUIPC installed if you have Go-Flight or PFC hardware or fly PMDG aircraft or other hardware and software, as most all use FSUIPC to communicate with FSX. Remember, the "U" in FSUIPC stands for "Universal" :-). Still do install the latest version and also register to unlock features not available in the unregistered version, such as the joystick calibration you need to do to apply these Notes! Note 2: Set Throttle Lever "DetentValue" in CH Control Manager Before starting lever calibrations, make sure you go into the / CH Control Manager v. 4.2 / Calibrate / CH Throttle Quadrant USB / "Throttle Settings" Tab and / set all to: MinValue ...... = 0 MaxValue ...... = 255 DetentValue= 240 &lt;-- Forget this and no "Reverse" on your throttle levers! DeadZone ...... = 4 Then calibrate all (CH Yoke, Pedals and Throttle Quadrant) in CH Control Manager BEFORE going into FSUIPC. Note 3: Set "DirectMode" in CH Control Manager Make sure you set your CH Device Drivers to "Direct Mode" (NOT "Mapped"!) in CH Control Manager (middle button, see mouse hover tool-tip). Note 4: Keep FSX From Re-Assigning the Axes you Already Assigned in FSUIPC Go into FSX Device Configuration and de-assign all the levers you want to assign from within FSUIPC to avoid double assignments. Also make sure you do not disconnect and reconnect your hardware to different ports, or else FSX will dream-up its own automatic assignments and you will again have to manually de-assign all the relevant levers. Additionally, disable joystick processing in FSX via the Menu / Options / Disable Joysticks. Note 5: FSUIPC Axis Assignment Tips Now go to the FSUIPC Configuration Dialog Box via the FSX Main Menu "Add-Ons" option. To assign a lever (axis) to a certain function in the FSUIPC "Axis Assignment" tab, you must first move that lever for FSUIPC to set its focus to that axis. However, you might find certain other axes "twittering" (axis "noise") and thus hiding the movement of the axis you are moving for FSUIPC to detect. If so, click repeatedly on the "Rescan" button repeatedly until FSUIPC selects the axis you want. (Clicking on the more intuitive"Ignore Axis" did not seem to work for me.) The "Delta" refers to the minimum axis input change that will be detected by FSUIPC and forwarded to FSX for processing: For a given joystick movement, a lower Delta means FSUIPC will sense joystick movements with greater precision, but at the cost of more work for FSX (more joystick movement messages are sent by FSUIPC to FSX.) But since CH Control Manager in the "Direct" mode only reports 256 possible positions for its joysticks while FSUIPC works with 32K possible positions, this means a minimum joystick movement of "1" in CH-World translates to a minimum movement of 32768 / 256 = 128 in FSUIPC. Thus the minimum "Delta" you can set in FSUIPC is 128. If you set the Delta to 256 (the equivalent of a joystick minimum movement of 2 in CH-World) then FSUIPC will only sense 128 possible joystick positions. For a Delta of 512 (a joystick minimum movement of 4), FSUIPC will only sense 64 possible joystick positions, and so on. While elevator and trim axes will benefit from the smallest Delta possible, the idea is to set higher deltas for other axes requiring lower precision (e.g. spoilers, cowl flaps) to avoid flooding FSX with meaningless joystick messages. Note 6: More FSUIPC Axis Assignment Tips When assigning levers, do *NOT* check "Raw", as this is for virtual (software only) levers. All your axes should be assigned in "Direct" mode in FSUIPC (as well as in CH Control Manager). Note 7: My Axis Assignments in FSUIPC (For CH Products Controllers) I´m not sure if each particular CH Joystick is always assigned the same Device numbers (0, 1, 2), or whether the assigned number is dependent on the order the operating system detects that joystick at boot-time. (Refer to your own joystick numbers if they show-up different in FSUIPC). Now go to the "Axis Assignments" tab in FSUIPC and make the following assignments: 0 = CH Products USB Pro Pedals Actions -------------------------------------+------------------------- X: ToeBrakeLeft .................... LeftBrake Y: ToeBrakeRight ....................RightBrake Z: Rudder .......................... Rudder, SlewHeading 1 = CH Products USB Yoke Actions -------------------------------------+------------------------- X: Ailerons ........................ Aileron, SlewSide Y: Elevator ........................ Elevator, SlewAhead Z: SpoilersLever1fromLeft .......... Spooilers, SlewAlt R: CowlFlapsLever2fromLeft ......... CowlFlaps1 U: ElevatorTrimLever3fromLeft ...... ElevatorTrim P: POV Hat Switch .................. Do NOT assign as an axis! (Assign as buttons instead.) 2 = CH Products USB Throttle Quadrant Actions -------------------------------------+------------------------- X: Throttle1Lever1fromLeft ......... Throttle1 Y: Throttle 2Lever2fromLeft ........ Throttle2 Z: Prop Pitch 1Lever3fromLeft ...... PropPitch1 R: Prop Pitch2Lever4from Left ...... PropPitch2 U: Condition1Lever5from Left ....... Mixture1 V: Condition 2Lever6fromLeft ....... Mixture2 While these assignments might seem obvious in retrospect, there are many more "Actions" available that perform similar tasks but may implement techniques relating to previous versions of FS and SimConnect, so this list will save you some trial-and-error. Note 8: Calibrating Axes in FSUIPC Once the axes are assigned to Actions as above, they need to be calibrated: Go to the "Joystick Calibration" tab in FSUIPC. Since calibrating reverse-enabled levers may be a daunting task for the uninitiated (it was for me!) as a *GUIDE* here are the values I use that serve me well for the FSX Beech Baron and King Air: +----------------------+--------+--------+--------+--------+--------+ | Control: | M | C I | C I | M | R A D | | | i | e d | e d | a | e x i | | | n | n l | n l | x | v i r | | | i | t e | t e | i | e s e | | | m | e | e | m | r c | | | u | r L | r H | u | s t | | | m | o | i | m | e i | | | | o w | o g | | o | | | | r | r h | | n | +----------------------+--------+--------+--------+--------+--------+ | Ailerons: .......... | -16384 | 0 | 0 | +16256 | No | | Elevator: ...........| -16384 | 0 | 0 | +16256 | No | | Rudder: .............| -16384 | 0 | 0 | +16256 | No | | BrakeLeft: ..........| -16256 | n.a. | n.a. | +16384 | Yes | | BrakeRight: .........| -16256 | n.a. | n.a. | +16384 | Yes | | Throttle1: ..........| -16384 | -15083 | -14433 | +16383 | No | | Throttle2: ..........| -16384 | -15083 | -14433 | +16383 | No | | Mixture1: ...........| -16384 | 0 | 0 | +16383 | No | | Mixture2: ...........| -16384 | 0 | 0 | +16383 | No | | PropPitch1: .........| -16384 | -15083 | -14433 | +16383 | No | | PropPitch1: .........| -16384 | -15083 | -14433 | +16383 | No | | ElevatorTrim: .......| -16384 | 512 | 0 | +16383 | No | | Spoilers: ...........| -16384 | -512 | -512 | +16383 | Yes | | CowlFlaps1: .........| -16383 | n.a. | n.a. | +16384 | Yes | | CowlFlaps2: .........| Map 1 |-&gt; 1234 | = Yes | -- | -- | | SlewAltitude:........| -16384 | 0 | 0 | +16383 | No | | SlewSideways: .......| -16384 | 0 | 0 | +16256 | No | | SlewForward/Back: ...| -16384 | 0 | 0 | +16383 | No | | Slew Heading: .......| -16384 | 0 | 0 | +16383 | No | +----------------------+--------+--------+--------+--------+--------+ IMPORTANT NOTE: The axis values in this table are the values FSUIPC sends to FSX and are mapped to their proper numerical ranges according to what FSX expects to receive. The axis values FSUIPC receives from the CH Products drivers are all in the (-16384, 16383) range (although in the CH Control Manager calibration dialog boxes they ALL show a range of (0, 255).) If your FSUIPC Joystick Calibration "IN" values are in the (0, 65536) range, you are reading all the axes of that particular joystick in the "Raw" mode, i.e. bypassing the CH Products drivers. See Note 6 again! Reading axes in the raw mode is incorrect and you will not be able to properly calibrate the axes of that joystick. (For a given joystick, axes are read either all "Direct" or all "Raw".) Also note that on the Joystick Calibration tab, "IN" refers to the joystick values FSUIPC receives from the CH Products drivers, while "OUT" refers to the values FSUIPC sends to FSX. Note 9: Assigning Buttons in FSUIPC No buttons need to be assigned for Throttle Reverse, Prop Feather and Mixture Idle-Cutoff to work for the FSX Beachraft Baron and Super King Air! Should you want to assign the POV Hat in FSUIPC instead of FSX, then go to the FSUIPC "Buttons + Switches" tab and make the following assignments: +---+----+--------------+---+----+------+------+ | J | B | B P P R | B R P | | o | u | u r a e | u e a | | y | t | t e r p | t l r | | s | t | t s a e | t e a | | t | o | o s m a | o a m | | i | n | n e e t | n s e | | c | | d t | e t | | k | | e | d e | | | | r | r | +---+----+--------------+---+----+------+------+ | 1 | 32 | PanUp 0 No | Null Null | | 1 | 33 | PanRightUp 0 No | Null Null | | 1 | 34 | PanRight 0 No | Null Null | | 1 | 35 | PanRightDown 0 No | Null Null | | 1 | 36 | PanDown 0 No | Null Null | | 1 | 37 | PanLeftDown 0 No | Null Null | | 1 | 38 | PanLeft 0 No | Null Null | | 1 | 39 | PanPanLeftUp 0 No | Null Null | +---+----+--------------+---+----+------+------+ Set other buttons to your heart´s content! (See the FSUIPC User Guide (Advanced) for configuring conditional buttons!) Note 10: Other Useful FSUIPC Settings In the FSUIPC "Miscellaneous" Tab: - Disconnect Elevator Trim Axis for AutoPilot: Avoids trim axis "twitters" from constantly changing trim and throwing-off the auto-pilot. - Pause After Crash: Does what it says! - Control Spike Elimination (Rudder/Elevator/Aileron): Filters unintended (spurious) large control movements. - Extend Battery Life: Worth its weight in gold, especially if you like to obtain clearances before engine start. In the FSUIPC "Winds" Tab: - Allow Gusts in Upper Winds - Allow random Turbulence In the "AutoSave/GPS Out" Tab: - Set AutoSave interval and how many files to keep. The "FSUIPC.ini" Configuration File: - FSUIPC keeps all its configuration settings in the FSUIPC.ini file. This is a standard text file and can be edited as described in the FSUIPC manuals. The FSUIPC.dll file (software) and the FSUIPC.ini configuration file are kept in your "Microsoft Flight Simulator X\Modules" directory. Well, that´s basically it. Now go fly! And "Welcome to the Wide World of Flight Simming with FSUIPC!" :D Many thanks to all who have helped me with their wisdom and patience to get my own configuration up-and-running. Please post-back your suggestions to improve these Notes! Happy Simming and Seasons Greetings 2007 to all, jahman.

Good news, Pete! You rock! :D Cheers, Andrew.

Indeed! Except my Holy Grail is not dealing with FSX at all for control configuration and keep all centralized in FSUIPC with it´s wonderful "per aircraft" configuration and 2 --> 4 engine mappings. Heck, I can really live with the jump in the mixture (at least as the Baron is concerned) especially now that I now what´s invovled (and while FSX doesn´t track engine wear due to excessive CHT...). Kind regards, Andrew.

Pete, Although many mixture settings are possible, only three have meaning for turboprops: Idle Cutoff, Low Idle, and High Idle. The situation is similar to assigning an axis to control flap extensions: Although continuous settings would be possible, only 3 would be significant (for the King Air). Kind regards, Andrew.

Indeed, but only three values are significant, as Frank mentioned. Consider also you seem to not have received any complaints about "jumpy mixtures" for Microsoft turboprops. So perhaps an adequate compromise causing the least disturbance might be to preserve "jumpy mixtures" for turboprops and jets, while allowing smooth mixtures for pistons and gliders (might sport engines). Kind regards, Andrew.

Indeed, it is important not to mess-up other user instalations: There could be hell to pay, and rightly so! This said, may I suggest a couple alternatives? 1. Automatic Setting Optimally (and I am leaping way ahead of my knowledge of FSX/FSUIPC4), from within FSUIPC4 perhaps it is possible to read the current aircraft engine type and then: IF (ENGINE_TYPE (TURBOPROP | JET) ) - TRUE, then use "standard" FSUIPC4 Mixture output (Default); /* TURBOPROP | JET */ - FALSE, then use Linear Mixture output (no jump); /* PISTON | GLIDERS */ ENDIF; 2. Manual Setting With a "Continuous Output" checkbox added to the Mixtures Tab, IF NOT (CHECKBOX (Continuous_Output) ) - TRUE, then use "standard" FSUIPC4 Mixture output (Default); /* TURBOPROP | JET */ - FALSE, then use Linear Mixture output (no jump); /* PISTON | GLIDERS */ ENDIF; Kind regards, Andrew.

Hi again, Peter! :D Direct Mode - I have removed ALL assignments (joystick, buttons) from FSX. - Joysticks ARE enabled in FSX - Sensitivities are set to ZERO by FSX (but all axes work fine anyway, except for Mixture) No, but I have calibrated all in CHCM with (Min, Detent, Max) = (0, 240, 255). I have read them all now (and would have saved me quite some time...) and after reading FSXCTLS2 I´m even more convinced in my quest for banning FSX from having any say in configuring my sim hardware! :twisted: The Mixture axes work OK for TurboProps because the missing 50% to 75% mixture range doesn´t matter. But with Pistons where I gradually have to lean-out the mixture (100% down to 20%) that missing 50% to 75% mixture range is a big problem (especially when ATC clears me to climb and maintain FL220... in a Beech Baron! :shock: ). FSUIPC4 "IN" values (post CHCM, I suppose) move smoothly along the range (-16384, 16383), while the corresponding FSUIPC "OUT" values move smoothly in the range (0, 8192) and then again in the range (12320, 16384). The missing/unreachable OUT values are in the range (8192, 12320) (exclusive). My guess is maybe I´ve done something for FSUIPC to think I´m flying a TurboProp as the OUT value of 8192 is "Idle" in the TurboProp context. Yet for Pistons 8192 is not a magic number: Speaking of "Idle" in the context of Mixture doesn´t seem quite right. Only "Rich" and "Lean" are relevant to a Mixture lever, while "Low Idle" and "High Idle" would be appropriate for a "Condition" lever. Finally, for both Pistons and TurboProps the Mixture levers move along 100% of their range, with the FSX ToolTip showing 0% and 100% at either extreme (in Flriendly Panels´ friendly tooltips with parameter values). It´s just that the 50% to 75% (exclusive) are not reachable: You can actually see the on-Screen Mixture levers jump! In the FSUIPC4 documentation set I see that the control MIXTUREn_SET has these key values: - Cut-Off: 0 - Idle: +8192 - Rich: +16384 ... and 8192 is exactly where my "jump" happens. A coincidence? Kind regards, Andrew. PS: What is "F9XBPD"?

Howdy! Newby here, with documentation read (and mostly understood), but likely dealing with some conceptual difficulties. Problem: FSUIPC4 "4 of 11: Separate Micture Controls" OUT values (for "Mixture(n)" control) jump from 8192 to 12320. This is OK for TurboProps, but for Piston Engines means I can not set mixture values between 50% and 75%! Argh! :x This "50% to 75% jump" occurs regardless of: 1. Detent Value calibrated in CH Control Manager 2. Type of Aircraft (TurboProp vs. Piston) 3. Maker of Aircraft (Microsoft FSX or Friendly Panels) 4. "Idle" Settings in FSUIPC4 Joystick Calibration ("4 of 11: Separate Micture Controls" Tab). Environment: Running: FSX and FSUIPC v. 4.205, reading all axes in "Direct" (not Raw!) mode. With: CH Products Yoke, Pro Pedals, Throttle Quadrant and Control Manager. Also: GoFlight MCP-PRO and EFIS Modules FSX: Joysticks disabled, no axes assigned, no buttons assigned (all assigned in FSUIPC4). Likely this has been encountered by others... Looking forward to your wisdom and insights :-) Cheers, Andrew.

Yes! Yes! Yes! And as I checked the CH Control manager - Throttle Quadrant - Throttle Setting Tab, I find that my Max Value = Detent Value = 255, which is why my throttle axis FSUIPC "IN" values would remain pegged at 65536 (Raw) (Now 255 "non-Raw") as I moved the lever along the IdleDetent-to-Reverse range. The additional info from CH-Hangar is also of the invaluable kind! Likely saved me a zillion hours of debug. Thanks a million, Peter! (Any relation to Wallace ("Wally") D. Hayes?) Cheers, Andrew.

Alas, not in the users mind! In FSUIPC4 you can program the POV Hat as 8 buttons or as an axis ("P" on the CH Yoke) so as a newbie user I unwittingly did both! :oops: Thing is the "P" Axis overrides (acts "after") the button programming, and a particular feature of the FSUIPC POV Hat implementation as an Axis is that when mapped to the pan view, the view will always revert to the forward view when the hat is released. With the "P" axis de-assigned, the POV buttons now all work as advertised! So thread viewtopic.php?f=54&t=66828 (many thanks also to Andydigital!) that also helped with the proper POV settings. Kind regards, Andrew.

Done! As a newbie I was not aware from reading the manual that the Direct mode is not advised for aircraft control joysticks. Also, I was not aware that the "Joystick Calibration" FSPUIPC Tab is not the same as the hardaware device calibration offered by FSX. Perhaps this is not explained in the documentation. Now upon further inspection (See: posting.php?mode=reply&f=54&t=66778 ) I gather by "Why direct"? you mean "Why raw?" (since "Direct" is needed for FSUIPC Joystick Calibration for the thrust reversers.) So I set my joysticks back to "Direct" and removed the "Raw" part. Now "A" in my initial post no longer occurs! Hooray! But "B" gets the best of me: As soon as the throttle levers fall into the detent, I get the -4096 thrust setting for reverse, regardless of how I calibrate the throttles. I´ve already spent several days on this... And I thought this was going to be easy... :-( Kind regards, Andrew. My FSUIPC.ini: [General] History=D6NCUKQKZYQ47Y9PM2VG4 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No WeatherReadFactor=2 SimConnectStallTime=1 GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=10000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 SetVisUpperAlt=No VisUpperAltLimit=0 ExtendMetarMaxVis=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=Yes SuppressWindTurbulence=No WindTurbulence=Yes SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 DisconnTrimForAP=Yes ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No MagicBattery=10 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No FixWindows=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=Yes PauseAfterCrash=Yes ShortAircraftNameOk=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes SpoilerIncrement=512 ZapSound=firework AxisIntercepts=No WeatherRewriteDelay=10 ProcessGlobalWeather=No [WideServer] WideFSenabled=No AdvertiseService=1 Port=8002 Port2=9002 [GPSout] Port= Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= GPSoutEnabled=No [AutoSave] AutoSaveEnabled=Yes Interval=120 Files=1 SaveOnGround=No Next=1 1=Fri 234623 2=Mon 202741 3=Mon 204137 4=Mon 201942 5=Mon 202142 6=Thu 053815 7=Thu 053915 8=Thu 054014 9=Thu 054114 10=Thu 054213 [JoystickCalibration] ExclThrottleSet=No SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 MaxSteerSpeed=60 SteeringTillerControl=0 Elevator=-16384,0,0,16256 Aileron=-16384,0,0,16256 Spoilers=0,65535 ElevatorTrim=-16380,-512,512,16380/16 PanHeading=-1,-1,0,31500 Rudder=-16384,0,0,16256 LeftBrake=-16256,16384/16 RightBrake=-16256,16384/16 MapThr12to34=Yes MapThr12to123=Yes Throttle1=-16384,-10922,-10662,16383 Throttle2=-16384,-10922,-10922,16383 MapCowl1to1234=Yes MapCowl12to123=Yes MapCowl12to34=Yes Mixture1=-16384,-10662,-10662,16383 Mixture2=-16384,-10662,-10662,16383 PropPitch1=-16384,-10792,-10792,16383 PropPitch2=-16384,-10532,-10532,16383 SlewAlt=-16380,-512,512,16380/16 SlewSide=-16380,-512,512,16380/16 SlewAhead=-16380,-512,512,16380/16 SlewHeading=-16380,-512,512,16380/16 CowlFlaps1=0,16380/16 [buttons] 1=P2,16,C66537,1 2=P2,18,C66538,1 3=P2,17,C66537,0 4=P2,19,C66538,0 5=P2,20,C66494,0 6=P2,21,C66494,1 7=P2,22,C66495,0 8=P2,23,C66495,1 9=P1,4,C66079,0 10=P1,5,C66080,0 11=P1,6,C65759,0 12=P1,7,C65758,0 29=P1,2,C66172,0 30=P1,3,C66173,0 31=P1,1,C66514,0 33=P1,0,C66513,0 34=R1,10,C65607,0 35=R1,11,C65615,0 38=P2,0,C66609,0 39=P2,1,C66612,0 40=P2,2,C66616,0 41=P2,3,C66615,0 42=P2,4,C66624,0 43=P2,5,C66617,0 44=P2,6,C66626,0 45=P2,7,C66625,0 46=P2,8,C66628,0 47=P2,9,C66627,0 48=P2,10,C66618,0 49=P2,11,C66623,0 50=P1,9,C66852,0 51=P1,8,C66853,0 52=R1,32,C65735,0 53=R1,33,C65857,0 54=R1,34,C65672,0 55=R1,35,C65856,0 56=R1,36,C65734,0 57=R1,37,C65854,0 58=R1,38,C65671,0 59=R1,39,C65855,0 [Keys] 5=189,8,66700,0 6=187,8,66699,0 7=32,9,65752,0 8=69,10,66224,0 9=69,9,66389,0 10=13,12,65553,0 14=89,11,66807,0 16=80,10,65561,0 17=81,10,65552,0 18=89,10,65557,0 19=86,10,66722,0 [Axes] 0=0X,3,D,7,0,0,0 1=0Y,3,D,8,0,0,0 2=0Z,3,D,3,0,0,0 3=1X,3,D,1,0,0,0 4=1Y,3,D,2,0,0,0 5=1Z,3,D,22,0,0,0 6=1R,3,D,29,0,0,0 7=1V,3,D,21,0,0,0 8=1P,3,D,33,0,0,0 9=2X,3,D,9,0,0,0 10=2Y,3,D,10,0,0,0 11=2Z,3,D,17,0,0,0 12=2R,3,D,18,0,0,0 13=2U,3,D,14,0,0,0 14=2V,3,D,13,0,0,0 [Monitor] Display=9

Apologies for the multiple posts... With "Direct" switched to "F" I of course couldn´t use FSUIPC joystick calibration to set the thrust reversers. I gather therefore when you said "Why Direct?" you actrually meant Why "Raw"? So I switched all my joysticks back to "Direct" from "F" and then eliminated the "Raw" part. Guess what? The PAN command behaviour changed! Now I can no longer get the POV hat to work properly, because on Button Release there pan action reverts to the previous state (even though all eight POV Hat buttons have NULL entries for button release). So there definitely seems to be some connection between axis modes (Raw, Direc, FS) and PAN command behaviour. Any chance you can verify this? Cheers, Andrew. My FSUIPC.ini: [General] History=D6NCUKQKZYQ47Y9PM2VG4 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No WeatherReadFactor=2 SimConnectStallTime=1 GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=10000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 SetVisUpperAlt=No VisUpperAltLimit=0 ExtendMetarMaxVis=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=Yes SuppressWindTurbulence=No WindTurbulence=Yes SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 DisconnTrimForAP=Yes ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No MagicBattery=10 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No FixWindows=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=Yes PauseAfterCrash=Yes ShortAircraftNameOk=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes SpoilerIncrement=512 ZapSound=firework AxisIntercepts=No WeatherRewriteDelay=10 ProcessGlobalWeather=No [WideServer] WideFSenabled=No AdvertiseService=1 Port=8002 Port2=9002 [GPSout] Port= Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= GPSoutEnabled=No [AutoSave] AutoSaveEnabled=Yes Interval=120 Files=1 SaveOnGround=No Next=1 1=Fri 234623 2=Mon 202741 3=Mon 204137 4=Mon 201942 5=Mon 202142 6=Thu 053815 7=Thu 053915 8=Thu 054014 9=Thu 054114 10=Thu 054213 [JoystickCalibration] ExclThrottleSet=No SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 MaxSteerSpeed=60 SteeringTillerControl=0 Elevator=-16384,0,0,16256 Aileron=-16384,0,0,16256 Spoilers=0,65535 ElevatorTrim=-16380,-512,512,16380/16 PanHeading=-1,-1,0,31500 Rudder=-16384,0,0,16256 LeftBrake=-16256,16384/16 RightBrake=-16256,16384/16 MapThr12to34=Yes MapThr12to123=Yes Throttle1=-16384,-10922,-10662,16383 Throttle2=-16384,-10922,-10922,16383 MapCowl1to1234=Yes MapCowl12to123=Yes MapCowl12to34=Yes Mixture1=-16384,-10662,-10662,16383 Mixture2=-16384,-10662,-10662,16383 PropPitch1=-16384,-10792,-10792,16383 PropPitch2=-16384,-10532,-10532,16383 SlewAlt=-16380,-512,512,16380/16 SlewSide=-16380,-512,512,16380/16 SlewAhead=-16380,-512,512,16380/16 SlewHeading=-16380,-512,512,16380/16 CowlFlaps1=0,16380/16 [buttons] 1=P2,16,C66537,1 2=P2,18,C66538,1 3=P2,17,C66537,0 4=P2,19,C66538,0 5=P2,20,C66494,0 6=P2,21,C66494,1 7=P2,22,C66495,0 8=P2,23,C66495,1 9=P1,4,C66079,0 10=P1,5,C66080,0 11=P1,6,C65759,0 12=P1,7,C65758,0 29=P1,2,C66172,0 30=P1,3,C66173,0 31=P1,1,C66514,0 33=P1,0,C66513,0 34=R1,10,C65607,0 35=R1,11,C65615,0 38=P2,0,C66609,0 39=P2,1,C66612,0 40=P2,2,C66616,0 41=P2,3,C66615,0 42=P2,4,C66624,0 43=P2,5,C66617,0 44=P2,6,C66626,0 45=P2,7,C66625,0 46=P2,8,C66628,0 47=P2,9,C66627,0 48=P2,10,C66618,0 49=P2,11,C66623,0 50=P1,9,C66852,0 51=P1,8,C66853,0 52=R1,32,C65735,0 53=R1,33,C65857,0 54=R1,34,C65672,0 55=R1,35,C65856,0 56=R1,36,C65734,0 57=R1,37,C65854,0 58=R1,38,C65671,0 59=R1,39,C65855,0 [Keys] 5=189,8,66700,0 6=187,8,66699,0 7=32,9,65752,0 8=69,10,66224,0 9=69,9,66389,0 10=13,12,65553,0 14=89,11,66807,0 16=80,10,65561,0 17=81,10,65552,0 18=89,10,65557,0 19=86,10,66722,0 [Axes] 0=0X,3,D,7,0,0,0 1=0Y,3,D,8,0,0,0 2=0Z,3,D,3,0,0,0 3=1X,3,D,1,0,0,0 4=1Y,3,D,2,0,0,0 5=1Z,3,D,22,0,0,0 6=1R,3,D,29,0,0,0 7=1V,3,D,21,0,0,0 8=1P,3,D,33,0,0,0 9=2X,3,D,9,0,0,0 10=2Y,3,D,10,0,0,0 11=2Z,3,D,17,0,0,0 12=2R,3,D,18,0,0,0 13=2U,3,D,14,0,0,0 14=2V,3,D,13,0,0,0 [Monitor] Display=9

Pete, While working on posting.php?mode=reply&f=54&t=66778 I changed all my joystick "ForD" settings from "D" to "F", as you suggested. Now the PAN commands work as expected! Perhaps the joysticks in "D" mode were causing some interferece? Note that to exactly replicate FSX POV Hat behaviour, a "Repeat" must be added to each hat position while the corresponding "Button Up" command must remain NULL. This is a slight difference from the POV Hat seetings on p. 30 of the FSUIPC4 User Guide (Basic). Kind regards, Andrew.

Pete, Many thanks for your kind reply. Unfortunately the difference between the settings you suggested and mine is only the PAN_RESET_COCKPIT command on POV button release. In any case I added that command but I still get the unexpected behaviour I mentioned in my initial post. Are the PAN commands not reliable via FSUIPC4? Cheers, Andrew. (Let me know next time you´re near SABE, I´ll show you around! :-)

Howdy! I´m re-programming the CH Products USB Yoke POV-Hat switch in my quest to forever banish joystick, button and keyboard configuration in FSX (to run all configuration centrally from FSUIPC to avoid conflicting configurations and generally speaking, to keep my sanity). My environment: Running: FSX and FSUIPC v. 4.205, reading all axes in "Direct" mode. With: CH Products Yoke, Pro Pedals and Throttle Quadrant. Without: CH Control Center Also: GoFlight MCP-PRO and EFIS Modules Aicraft: FSX stock Beech Super King Air 350 FSX: Joysticks and POV-Hat switch disabled What I´ve Done: I´ve programmed my POV-Hat switch with the 8 PAN commands (UP, DOWN, LEFT, RIGHT, etc.) all on "Key Pressed" with no repeat and no commands for "Key Released". The Problem: In the External Fixed View... - PAN_DOWN works fine, with about 6.5º down for every click. - PAN_UP does pan up again with about 6.5º down for every click, but strangely, a PAN_LEFT appears in-between for the duration while the hat is kept back. - PAN_LEFT does pan left, but by a whopping 165º and only while the hat is held left. Once the hat is released, the view reverts to the view before the PAN_LEFT. Recall, no command is programmed for button release. - PAN_RIGHT is actually a 45º pan to the left (or 315º to the right)! Once the hat is released, the view reverts to the view before the PAN_LEFT. Recall, no command is programmed for button release. - The compound pans (left-up, left-down, right-up and right-down) also seem to all have a mind of their own. My FSUIPC.log: [Continuation log requested by user] Running inside FSX (SimConnect SP1 May07) Module base=61000000 10978531 System time = 04:05:35, FSX time = 15:38:02 (19:38Z) 10987187 [buttons] 52=P1,32,C65735,0 10987187 FS Control Sent: Ctrl=65735, Param=0 10987187 *** EVENT: Cntrl= 65735 (0x000100c7), Param= 0 (0x00000000) PAN_DOWN 10987828 [buttons] 52=P1,32,C65735,0 10987828 FS Control Sent: Ctrl=65735, Param=0 10987828 *** EVENT: Cntrl= 65735 (0x000100c7), Param= 0 (0x00000000) PAN_DOWN 10989047 [buttons] 56=P1,36,C65734,0 10989047 FS Control Sent: Ctrl=65734, Param=0 10989047 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP 10989844 [buttons] 56=P1,36,C65734,0 10989844 FS Control Sent: Ctrl=65734, Param=0 10989844 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP 10990484 [buttons] 56=P1,36,C65734,0 10990484 FS Control Sent: Ctrl=65734, Param=0 10990484 *** EVENT: Cntrl= 65734 (0x000100c6), Param= 0 (0x00000000) PAN_UP 10992297 [buttons] 54=P1,34,C65672,0 10992297 FS Control Sent: Ctrl=65672, Param=0 10992297 *** EVENT: Cntrl= 65672 (0x00010088), Param= 0 (0x00000000) PAN_RIGHT 10992937 [buttons] 54=P1,34,C65672,0 10992937 FS Control Sent: Ctrl=65672, Param=0 10992937 *** EVENT: Cntrl= 65672 (0x00010088), Param= 0 (0x00000000) PAN_RIGHT 10993765 [buttons] 58=P1,38,C65671,0 10993765 FS Control Sent: Ctrl=65671, Param=0 10993765 *** EVENT: Cntrl= 65671 (0x00010087), Param= 0 (0x00000000) PAN_LEFT 10994422 [buttons] 58=P1,38,C65671,0 10994422 FS Control Sent: Ctrl=65671, Param=0 10994422 *** EVENT: Cntrl= 65671 (0x00010087), Param= 0 (0x00000000) PAN_LEFT 10998500 Sim stopped: average frame rate for last 20 secs = 11.3 fps Any pointers most appreciated! Cheers, jahman (SABE)

Howdy! Newby here, with documentation read (and mostly understood), but likely dealing with some conceptual difficulties. Environment: Running: FSX and FSUIPC v. 4.205, reading all axes in "Direct" mode. With: CH Products Yoke, Pro Pedals and Throttle Quadrant. Without: CH Control Center Also: GoFlight MCP-PRO and EFIS Modules Aicraft: FSX stock Beech Super King Air 350 FSX: Joysticks disabled Lofty Goal: Replacing *all* FSX control and keyboard configuration with FSUIPC. Will post results :-) A. Direct-Joystick Wrong Input Range Read Sporadically at start-up, FSUIPC will read all my joystick input values in the (0, 255) range(*), but then revert to the regular, normal and expected (0, 65536) range after I exit the FSUIPC Dialog Box with "Accept" (sometimes I need to repeat this procedure). (*) NOTE: Range numbers are actually negative as I have the "Rev" box checked in most cases. B. Throttle Quadrant Lever Low Detent Range not Read When calibrating the Throttle Quadrant levers (with joystick ranges operating properly), FSUIPC sees the lever direct input remain pegged at -65536 (reverse is checked!) while the lever is moved along the range below the detent (the "thrust reverse" range.) The output is correct at -4096, but remains fixed throught the reverse thrust detent range. Above the detent the range is (0, 65536). This makes setting a zero thrust range at the detent difficult. All six levers are affected. But perhaps this is how it´s supposed to be? C. Minor Bug: Yoke Axis Mislabelled The yoke rightmost lever is labelled "U" by CH Control Center and "V" by FSUIPC. No idea if this difference is important, just passing it on. D. Info Needed: FS Command Parameters I have checked the FSUIPC and FSX SDK documentation but can´t seem to find info on the parameters for those FS Commands that take parameters. Many are obiously 0 or 1, but others are not so obvious. Any pointers to this info will be much appreciated. PS: My FSUIPC.ini is attached (I believe) but somehow it´s not showing...? Thanks! -jahman (SABE) Can´t seem to figure how to upload my FSUIPC.ini file (and he wants to fly them heavies, he says!) so here it is: [General] History=RI2X7W2ZKAQAMKQ40G9U3 TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No WeatherReadFactor=2 SimConnectStallTime=1 GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=10000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 SetVisUpperAlt=No VisUpperAltLimit=0 ExtendMetarMaxVis=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=Yes SuppressWindTurbulence=No WindTurbulence=Yes SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 DisconnTrimForAP=Yes ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No MagicBattery=10 RudderSpikeRemoval=Yes ElevatorSpikeRemoval=Yes AileronSpikeRemoval=Yes ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No FixWindows=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=Yes LoadPlanMenu=Yes PauseAfterCrash=Yes ShortAircraftNameOk=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes SpoilerIncrement=512 ZapSound=firework AxisIntercepts=No WeatherRewriteDelay=10 ProcessGlobalWeather=No [WideServer] WideFSenabled=No AdvertiseService=1 Port=8002 Port2=9002 [GPSout] Port= Speed=4800 Interval=1000 PosTo6Decimal=Yes Sentences= GPSoutEnabled=No [AutoSave] AutoSaveEnabled=Yes Interval=120 Files=1 SaveOnGround=No Next=1 1=Fri 234623 2=Mon 202741 3=Mon 204137 4=Mon 201942 5=Mon 202142 6=Thu 053815 7=Thu 053915 8=Thu 054014 9=Thu 054114 10=Thu 054213 [JoystickCalibration] ExclThrottleSet=No SepRevsJetsOnly=No ApplyHeloTrim=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=66731 RudderTrimControl=66732 CowlFlaps1Control=66162 CowlFlaps2Control=66163 CowlFlaps3Control=66164 CowlFlaps4Control=66165 MaxSteerSpeed=60 SteeringTillerControl=0 Elevator=-65535,-33548,-33548,-255/16 Aileron=-65535,-32768,-32768,-255/16 Spoilers=0,65535 ElevatorTrim=-16380,-512,512,16380/16 PanHeading=-1,-1,0,31500 Rudder=-65535,-31999,-31999,-255/16 LeftBrake=-65535,-255/16 RightBrake=-65535,-255/16 MapThr12to34=Yes MapThr12to123=Yes Throttle1=-65535,-64234,-64234,0/16 Throttle2=-65535,-65274,-65274,0/16 MapCowl1to1234=Yes MapCowl12to123=Yes MapCowl12to34=Yes Mixture1=-65535,-58513,-56173,0/16 Mixture2=-65535,-59813,-58513,0/16 PropPitch1=-65535,-59033,-58513,0/16 PropPitch2=-65535,-58513,-58513,0/16 SlewAlt=-16380,-512,512,16380/16 SlewSide=-16380,-512,512,16380/16 SlewAhead=-16380,-512,512,16380/16 SlewHeading=-16380,-512,512,16380/16 CowlFlaps1=0,16380/16 [buttons] 1=P2,16,C66537,1 2=P2,18,C66538,1 3=P2,17,C66537,0 4=P2,19,C66538,0 5=P2,20,C66494,0 6=P2,21,C66494,1 7=P2,22,C66495,0 8=P2,23,C66495,1 9=P1,4,C66079,0 10=P1,5,C66080,0 11=P1,6,C65759,0 12=P1,7,C65758,0 29=P1,2,C66172,0 30=P1,3,C66173,0 31=P1,1,C66514,0 33=P1,0,C66513,0 34=R1,10,C65607,0 35=R1,11,C65615,0 38=P2,0,C66609,0 39=P2,1,C66612,0 40=P2,2,C66616,0 41=P2,3,C66615,0 42=P2,4,C66624,0 43=P2,5,C66617,0 44=P2,6,C66626,0 45=P2,7,C66625,0 46=P2,8,C66628,0 47=P2,9,C66627,0 48=P2,10,C66618,0 49=P2,11,C66623,0 [Keys] 3=86,8,66722,0 4=32,10,66852,0 5=189,8,66700,0 6=187,8,66699,0 7=32,9,65752,0 8=69,10,66224,0 9=69,9,66389,0 10=13,12,65553,0 11=80,8,65561,0 12=81,8,65552,0 13=83,8,65589,0 14=89,11,66807,0 15=89,8,65557,0 [Axes] 0=0X,R3,D,7,0,0,0 1=0Y,R3,D,8,0,0,0 2=0Z,R3,D,3,0,0,0 3=1X,R3,D,1,0,0,0 4=1Y,R3,D,2,0,0,0 5=1Z,R3,D,22,0,0,0 6=1R,R3,D,29,0,0,0 7=1V,R3,D,21,0,0,0 8=1P,R3,D,33,0,0,0 9=2X,R3,D,9,0,0,0 10=2Y,R3,D,10,0,0,0 11=2Z,R3,D,17,0,0,0 12=2R,R3,D,18,0,0,0 13=2U,R3,D,14,0,0,0 14=2V,R3,D,13,0,0,0 [Monitor] Display=9 Cheers, jahman.

Many thanks, PeterC! I ended-up going the Notepad route, i.e. directly writing the appropriate entries into the the INI file as mt controllers just wouldn´t stop twitching. The reason I want to "do all" in FSUIPC is to avoid a myriad of config files (FSX, FSUIPC, GoFlight, etc.) and so be able to benefit the most from FSUIPC´s ability to automatically select configs for different aircraft (and especially map 2 engine controls to 4 engine aircraft...) I´ll post my FSUIPC "FSX Replacement" config file when I´m done... Cheers, jahman.

Howdy! Newby going through replacing CH Manager and FSX joystick handlers with FSUIPC 4.20. In the "Axis Assignment" tab several axis (mostly controller 1: CH Yoke) keep popping-up. Having duly read the included manual (and the setup doc for CH Products gear) I click the "Ignore Axis" button, then "Rescan" while moxing the controller axis that Im looking to select. After a while I click "Clr Ignores" and start again, or even quit FSX and re-start, but all to no avail. But still I get the same ole axes showing-up! The hours pass and Im still clicking "Ignore Axis" and "Rescan" while moving the axis I want to select. I see a paddywagon on the way with serious-looking folk in white lab coats. Am I doing something wrong here? Many TIAs... jahman.