dswo

I have an old Saitek X45 throttle and stick. The throttle has a detente near the top range, which I would like to use in the following way. The plane that I am flying now is the Aerosoft F-16; this is important because the Aerosoft model engages afterburner when throttle >= 80%. I know that FS has an afterburner command, but the model bypasses that (in the same way, I imagine, as the Acceleration Hornet does). What I'd like to do is scale my throttle output to match the physical detente. That is, set the lower range, up to the detente, as 1-79% of output (in setting this up, the percents would be calculated out as absolute values) and the upper range, past the detente, as 80-100% (again, this could be an absolute numerical range). Is this possible with FSUIPC? I've studied both of the manuals and don't see a way of doing it cleanly -- but perhaps I'm missing something?

I understand. Thank you, Pete, for replying so promptly.

Might it be possible one day to assign buttons to adjust the density of ground vehicles in FSX? I already have this set up for airplane traffic, and it's a great aid when moving from town to country and vice versa. (In my case, there are four buttons: one for 0% air traffic, one for 25, one for 50, and one for 100.)

The problem, clearly, is North Carolina. Mark is from Raleigh, Eislinger is from Fayetteville, and I am in Greenville (where, yes, the smoke was pretty bad for three days; I lived in California for 21 years and I've never known anything like it).

Pete, I was on the other thread with assigning multiple controllers per axis. Am still interested in that, and will continue providing feedback there, but I want to add a tiny data point to this thread. On Wednesday, I started having CTDs like the original poster, usually within 15 minutes (again, api.dll listed as culprit). It didn't occur to me to connect the crashes with FSUIPC, since I'd been running the registered version since June 2, and the unregistered version since FSX was released. Last night, I trimmed some background processes that had crept in (e.g., YouTubeLoader.exe) and also installed the 291 beta you provided on the other thread. Since then, I've flown for about an hour and a half (not all one flight, though) with no CTDs. I'm still a little nervous, but so far, so good. Like the original poster, I have a menagerie of USB controllers: CH yoke, CH pedals, Sidewinder joystick, Saitek X45 throttle, Belkin Nostromo keypad. Like the original poster, my CTDs began after I started assigning axes directly (on Tuesday of this week). Post hoc ergo propter hoc? I don't know, but my FSX installation was very stable until recently, and the timing fits: CTDs after direct assignment of axes, no CTDs (yet) after installing beta 291 with your new method of axis processing.

Thank you, Pete, for the fast turnaround. I downloaded and installed 2.91 and flew for 60 mins without a control freeze. Haven't tested dual controls yet, but the latest beta seems to be working.

[JoystickCalibration] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes 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 SteeringTillerControl=0 MaxSteerSpeed=60 ElevatorTrim=-16193,-1341,-298,16192/8 Aileron=-16384,-390,128,16256/8 Elevator=-16380,350,2451,16383/8 SlopeAileron=-4 SlopeElevator=2 SlopeElevatorTrim=2 Throttle=-16253,16256/8 [JoystickCalibration.h1a2] ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes 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 SteeringTillerControl=0 MaxSteerSpeed=60 Aileron=-16383,-507,1002,16383/8 ElevatorTrim=-16193,-1342,-339,16192/8 SlopeElevatorTrim=2 Elevator=-16383,-64,127,16383/8 Throttle=-16383,16256/8 CowlFlaps1=-16384,16383

Here are my assignments: [Axes] 0=0X,256,D,1,0,0,0 1=0Y,256,D,2,0,0,0 2=0Z,256,D,4,0,0,0 [Axes.h1a2] (the same for all specialized planes; just uses HOTAS instead of yoke for ailerons, elevator, and throttle) 0=1X,256,D,1,0,0,0 1=1Y,256,D,2,0,0,0 2=1S,256,D,29,0,0,0 These are my working assignments, before I tried to use the new feature. As you can see, I do NOT have an axis mapped to multiple axes. Most assignments are done through FSX; axes mapped here, though, are direct through FSUIPC (so, for example, FSX is not mapping my ailerons at all).

I reactivated beta and enabled logging; same lockup. The sim doesn't crash, it just stops responding to all input. (Also, any tooltip onscreen at the time of lockup stays on screen.) I'm attaching FSUIPC4.log. Two other things in the mix here which I forgot to mention in describing my system: - I am flying the new Hughes Racer from Aerosoft - Am using ActiveSky X FSUIPC4 log, using beta.zip

I just loaded up with the beta. I didn't get far I'm afraid. Twice after installing, the sim stopped responding to input of any kind after about one minute (including TrackIR). To restart, I had to end FSX in task manager. I deactivated the beta version (by renaming the dll) and reactivated the current public version (with my working fsuipc.ini). Back to normal. Since it happened twice with the beta, and since it didn't happen after I reinstalled the working version, I am wondering if there is something wrong in the beta. If it helps, my system is: Core2Duo E6600 @ 2.4 GHz 4 gigabytes RAM Nvidia 8800 GT (512 Mb) Samsung 20” widescreen LCD (1680 x 1050) Windows XP Pro SP2 TrackIR 3 with Vector Expansion CH pedals, yoke Saitek X45 throttle Sidewinder Precision Pro joystick Belkin Nostromo N52 (another USB controller, no sliders or axes) Buttkicker Gamer Sound Blaster X-Fi XtremeGamer sound card FSX with Acceleration (SP2)

Thank you, Pete; I'm testing now. Is there a way to calibrate the second assignment. In my case, I have yoke already primary for X and Y. Can I also calibrate joystick for X and Y, or will the one calibration be used for both devices?

Thank you, Pete. Your program just gets more and more useful.

Thank you, Pete -- will do.

Thank you, Pete, for the correction (on what I don't need to assign) and for the suggested solution. The only real drawback that I foresee is that it multiplies the number of items that FSX has to work through when choosing aircraft (which, in my case, is already considerable), and the number of items that the user has to sort through when choosing what to fly (again, a considerable number; I wish that FSX would allow bigger thumbnails). On the other hand, it will work with what's available NOW. Reason I'm not assigning two controllers to one axis: delta would diminish the stick's responsiveness.

This morning I spent some time setting up a joystick profile for several of my aircraft. The trick for me was that I wanted to disable my yoke axes completely when I was using the joystick AND have a different calibration for the joystick (rather than create a loose calibration that would work for both yoke and stick). Solution was to (a) delete FSX assignments altogether (b) assign yoke axes in FSUIPC © for joystick aircraft only, reassign yoke ailerons, elevator, and throttle to unused axes (mixture 2, 3, 4) and (d) for joystick aircraft only, assign joystick axes for ailerons, elevator, and throttle. I couldn't get it to work at first, because I still had yoke axes assigned by FSX (hence step a). Once I had this working, I activated substring/short string names in FSUIPC.ini and copied the relevant calibration and axes sections for several aircraft groups. Now, when I load one of my helicopters, it reads from my joystick and uses the joystick calibration automatically, with no interference from my sometimes jittery yoke axes. I realize that, for some FSUIPC veterans, this is very basic stuff, but I'm pleased. Thank you, Peter, for continuing to improve your program, and for making it work with FSX. Now, the question is: what to do with aircraft that I sometimes fly with a yoke (for longer distances) and sometimes with a joystick (for acrobatics). Planes in this category for me: RealAir SF.260, various World War II-era fighters. What I'd like to be able to do is save a generic yoke profile and a generic joystick profile in FSUIPC, both with calibrations, and load one of them manually. Being able to do this automatically, based on aircraft, is fantastic, and I'm sure it was a lot of work to program. However, would it be possible for the user to do this manually as well, for planes that might use more than one profile? Maybe this is possible already, and I have just missed it in the manual (which I have read several times, at intervals); if so, I apologize -- and welcome advice on how to activate different profiles that are not aircraft-specific. - David Wilson-Okamura

That clears it up. As of this writing, there is no publicly released version of SB that takes advantage of this new feature in FSUIPC and WideFS (although it's still possible to make it work the old-fashioned, pass-through way).

New with latest version of FSUIPC: "Support for Squawkbox 3’s private (PVT) message PTT is added for assignment in both the Keys and Buttons controls drop-downs. This also is automatically applied to all WideFS clients. [NOTE]." -- I've got normal PTT with SB3 working handily now. Thank you for making it so easy. Haven't been able to do the same with PVT PTT. Has this SB3 update been released? I'm running build 3.03, and don't see anything more recent on the Squawkbox.ca website. Yours faithfully, David Wilson-Okamura