Pete Dowson

All of the mouse macro log entries which trap a call show that the function being called when you use the mouse are in FS's generic screen utilities module, "window.dll", not in a specific GAU (gasuge) file. I'm afraid those functions, in those panels, aren't susceptible to mouse macros. Your attempts with the C172 all use normal FS controls, as you can see. For example: 815761 Mouse Event=66379 815761 *** EVENT: Cntrl= 66379 (0x0001034b), Param= 0 (0x00000000) TOGGLE_NAV No need for Mouse Macros for functions you can simply assign to a control! Pete

Show me the log messages please. Pete

Mouse macros only work on gauges specifically written using the FS C/C++ gauge SDK. Even most of Microsoft's own gauges don't do this, and more and more modern gauges are written differently, often using XML instead. If the window doesn't appear when you click the mouse on a spot then that gauge isn't amenable to mouse macros. Reinstalling FSUIPC never achieves anything, because all you are doing is replacing the DLL with the same DLL (unless you are updating ... that's different). Pete

You call that rambling? Wait to you get to my age! (71+) ;-) Pete

4.926 is way out of date and not supported. Please update if you want support -- current is 4.937. And please use the Support Forum for support questions. Pan View is correct for panning views using a hat. There is no other. It is exactly the same as in FS assignments. The right hand side is not for basic assignments, but for complex setting of different actions on different ranges in different directions with a continuous analogue axis! Please do read some of the documentation! Never use anything you don't understand! Pete

It isn't so much how it "looks" but how it behaves. I can't tell you what is "right", all I can do it point out that some of the axes haven't really been calibrated, only left to default actions. You still have some like that. For example: Aileron=-16380,-512,512,16380/8 Elevator=-16380,-512,512,16380 Rudder=-16380,-512,512,16380 Throttle=-16384,16383/8 LeftBrake=-16384,16383/24 RightBrake=-16380,16380/24 ElevatorTrim=-16380,-512,512,16380 Those values are pretty much all defaults. For brakes, in particular, you should always have a large enough dead zone with "feet off" so that you never get brakes stuck on simply because the pedals haven't full returned to their stops. Without a dead zone there's only one possible position for "no brakes" and it is unlikely to always be there -- especially with toe brakes whilst steering with the rudder It can be quite difficult not to see a little bit of toe brake movement, and you don't want any unintended braking. But in the end it is all your choice. You set it as you like it. Try it all out. Pete

Fine, but for my records I need the name of the App and your real name. If it is confidential please just send me an email, petedowson@btconnect.com. And please confirm that you actually do need 64 bytes. Okay? Pete

No. It is logical to work left to right, low to high, but it doesn't matter PROVIDED that at no time you try to enter a higher number lower than a lower number. They increase left to right. Any reversal is rejected with a beep. The only think wrong with your max calibration is that you are not actually reaching a high enough input value to reach the max. This is probably simply that you've never pressed the max Set button. When I looked at your calibrations in the file, very many of them just showed default values, showing little or no actual calibration. Follow the numbered steps in the calibration chapter of the manual. Just by way of illustration, all these are just default values, not ones set by you: Elevator=-16380,-512,512,16380 Throttle=-16384,16383/8 Throttle1=-16384,-512,512,16383 LeftBrake=-16384,16383/24 ElevatorTrim=-16380,-512,512,16380 Aileron=-16380,-512,512,16380/8 Rudder=-16380,-512,512,16380 Mixture1=-16384,8192,8192,16383/8 Real values will tend to be rather more haphazard, and certainly, when you allow for little dead zones at the extremes and in the centre, as suggested in the manual, they will inevitably fall withing the -16380 to +16380 region, not match it or exceed it. Pete

There's no difference between the treatment of engines 1 and 2. Have you tested with the default FSX 737? That's the first step, to make sure it is not a problem with the PMDG add-on. Next step is to try the PMDG 737 using keyboard and mouse, to make sure you can engage the reversers even when you cannot using the PFC device. After that you need to do some logging -- axis logging in FSUIPC will show you what is happening. If you temporarily run FS in Windowed mode you can enable the Console Log and see it all in real time on screen. Pete

That's correct, though you need to calibrate the top end (your +16128 should give +16383), and the idle zone. +16383 is max full thrust, -4096 is max reverse thrust for most aircraft due to the setting of 0.25 (25% of full thrust) for max reverse set in their Aircraft.CFG file. For no reverse zone you simply need to check the "No Reverse Zone" option. Idle output is 0. I did actually notice that most axes were not calibrated at all -- the values in the file were mostly the default values, which really very rarely apply to actual controls. If you only what to stop reverse zone for the one profile (TwinProp), don't forget to set Profile Specific before setting the option. Regards Pete

It shouldn't have, unless some of it occurred BEFORE you changed to using Joystick Letters. The letter system enabled FSUIPC to keep track when you unplug and re-plug devices, even in different USB sockets. I have just noticed something odd, though. In the JoyNames section the details for C and D (the Saitek Quadrants) seem complete, but the CH pedals and yoke are not. Look, here's the settings with them sorted: A=CH PRO PEDALS USB 3=CH PRO PEDALS USB 3.GUID={EB210F40-4AE7-11E3-8003-444553540000} B=CH FLIGHT SIM YOKE USB 0=CH FLIGHT SIM YOKE USB 0.GUID={29F7FC00-4AE9-11E3-8001-444553540000} C=Saitek Pro Flight Quadrant C.GUID={EB235930-4AE7-11E3-8004-444553540000} 1=Saitek Pro Flight Quadrant 1.GUID={EB235930-4AE7-11E3-8004-444553540000} D=Saitek Pro Flight Quadrant D.GUID={EB235930-4AE7-11E3-8005-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={EB235930-4AE7-11E3-8005-444553540000} There should be lines A.GUID={EB210F40-4AE7-11E3-8003-444553540000} B.GUID={29F7FC00-4AE9-11E3-8001-444553540000} to complete the section. .Not that it should matter in this case because the devices names are unique, unlike those for the Quadrants. FSUIPC only actually uses the GUIDs when the names are the same, so it can distinguish between them and not get the assignments mixed up. Regards Pete

You had 3 assignments for both Mixture 1 and Mixture 2 -- you had them assigned on the Pedals (!!!) A, and on the Yoke B, and on the quadrant C. Naturally i assumed the assignments you realy used would be on the quadrant. After all you have two quadrants listed, why not use them for their intended purposes? Sorry, I don't know what is 1st, 2nd etc. the INI uses the letters supplied by their drivers, not the positions. Of course! None of the buttons or keypresses were assigned as "Aircraft Specific", so I didn't need to change any. I didn't even look at them. There were only these two odd ones: [buttons.Maule M7 260C paint1] 0=PB,38,C66416,0 [buttons.Tiger Moth GBMPY] 0=PB,34,C66416,0 but those were where you tried to assign the hat to "Pan View" as a button instead of as an axis. So those are not wanted in any case Wouldn't it all become clearer faster and more easily if you simply installed it and tried it? It can't do any harm! And you would still have your older copy!! Pete

I've taken the mixtures off the pedals AND the yoke -- I left the one's assigned to your first quadrant, joystick C. If you prefer to use the yoke then you'd need to change those assignments, but now you only need to do that in the SingleProp and TwinProp profiles. Don't forget to clear the quadrant assignments for Mixture if you do. FSUIPC can handle multiple assignments to the same control, but it takes the one with the biggest deviation, so they can give odd results unless you are sure the unused levers are dormant / parked. The Pan View action on the hat is now on all the settings. When you want to create a new Profile you can base it on an existing Profile, or on the defaults, as you wish. You don't need to start from scratch. However, if you ever decide to try helicopters I would advise starting from scratch as they have very different needs! ;-) Pete

Here's a much simplified (and corrected) version of your INI file, converted to Profiles. I found that almost all of the different aircraft had only one of two different axis assignment arrangements, and ALL of them had almost exactly the same calibration settings. And many of the sections for specific aircraft obviously hadn't been used for a long time since they still used the original joystick numbers, not the letters you currtently have. There were errors which would certainly have affected some of your operations. in particular you had, in many cases 3 different axes on three different devices all competing to control the Mixture 1 and Mixture 2 settings. In one case the mixtures were assigned to the pedals! The default axis assignments are those suiting the 737 and 747, which didn't seem to have anything very sophisticated assigned, so at present I have not made a "Jet" profile. You may wish to do this if you get more into jets. Most of your use seems to be with single and twin props, so there are two profiles -- SingleProp and TwinProp. I've added short names for your main aircraft in each of the Profile lists, thus: [Profile.Twinprop] 1=Baron 2=Twin Otter [Profile.SingleProp] 1=DHC-2 2=Beaver 3=Grand Caravan 4=Maule 5=Skyhawk 6=Bravo 7=Tiger Moth 8=Arrow 9=Kodiak You may want to add to these, or make some a little more specific. The only requirement is that the text you put here must be an exact part, any part, of the aircraft name. Here's the new file. Obviously keep a copy of your current one just in case. [General] UpdatedByVersion=4937 History=JRIXLNSXM0S00802WNH2J MouseWheelTrim=No MouseWheelTrimSpeed=1 FixControlAccel=Yes FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=Yes SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=Yes MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=Yes ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=Yes RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=Yes ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No SaveDataWithFlights=Auto ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 Console=No BrakeReleaseThreshold=75 DontResetAxes=No SetSimSpeedX1=75,8 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No GetNearestAirports=Yes LuaRerunDelay=66 MouseWheelMove=No DeleteVehiclesForAES=Yes EnableMouseLook=No AxesWrongRange=No InitDelay=0 InitDelayDevicesToo=No AutoScanDevices=Yes OOMcheck=Yes UseMidMouseBtn=Yes NewInterceptTextMenu=No UseSystemTime=No DelayedMouseLookZoom=No FSVersionUsed="Microsoft Flight Simulator X",10.0.61637.0 SimConnectUsed=10.0.61259.0 [JoyNames] AutoAssignLetters=Yes A=CH PRO PEDALS USB B=CH FLIGHT SIM YOKE USB C=Saitek Pro Flight Quadrant D=Saitek Pro Flight Quadrant 3=CH PRO PEDALS USB 3.GUID={EB210F40-4AE7-11E3-8003-444553540000} C.GUID={EB235930-4AE7-11E3-8004-444553540000} D.GUID={EB235930-4AE7-11E3-8005-444553540000} 1=Saitek Pro Flight Quadrant 1.GUID={EB235930-4AE7-11E3-8004-444553540000} 0=CH FLIGHT SIM YOKE USB 0.GUID={29F7FC00-4AE9-11E3-8001-444553540000} 2=Saitek Pro Flight Quadrant 2.GUID={EB235930-4AE7-11E3-8005-444553540000} [AutoSave] AutoSaveEnabled=Yes Interval=180 Files=2 SaveOnGround=Yes Next=1 1=Sat 233804 2=Sat 234103 [GPSout] GPSoutEnabled=No Port=COM1 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [WideServer] WideFSenabled=Yes [Buttons] ButtonRepeat=20,10 6=PC,7,K113,8 11=PD,5,C66240,0 13=PC,1,C66379,0 14=PD,1,C65751,0 15=PB,6,C65860,0 16=PB,7,C66112,0 17=PB,4,C65853,0 18=PB,5,C65589,0 20=HC,6,K113,8 21=HC,4,K78,8 22=HD,0,K65,8 24=HC,2,K72,8 25=PD,3,K67,8 26=PC,3,C65560,0 27=PC,5,C65750,0 29=PD,2,C65799,0 30=PC,0,K90,8 PollInterval=25 32=PD,4,K74,8 33=RB,3,C65607,0 34=RB,2,C65615,0 44=PB,9,K78,9 45=PB,1,K83,9 46=PB,10,K74,9 47=PB,11,K65,9 54=PB,34,C66416,0 [Keys] 2=38,8,65892,0 3=40,8,65893,0 4=38,9,65894,0 5=40,9,65895,0 6=39,8,65879,0 7=37,8,65880,0 8=39,9,65663,0 9=37,9,65662,0 10=33,9,65665,0 11=36,9,65664,0 12=39,10,66446,0 13=37,10,66445,0 14=33,10,66450,0 15=36,10,66449,0 16=35,10,65648,0 17=40,10,65649,0 18=34,10,65650,0 19=33,8,65896,0 20=34,8,65897,0 21=72,8,65798,0 22=87,8,65809,0 23=83,8,66093,0 24=73,8,1126,0 25=75,8,65876,0 28=81,8,66448,0 30=81,9,66452,0 31=37,12,66776,0 33=35,12,66434,0 36=N85,8,66204,0 40=34,12,66435,0 41=35,9,66434,0 42=34,9,66435,0 43=189,8,65755,0 44=187,8,65754,0 46=189,8,65655,0 47=187,8,65656,0 [Axes] RangeRepeatRate=10 PollInterval=10 0=AX,256,D,7,0,0,0 1=AY,256,D,8,0,0,0 2=AZ,256,D,3,0,0,0 3=BX,256,D,1,0,0,0 4=BY,256,D,2,0,0,0 5=BZ,256,D,29,30,31,32 6=BP,0,F,66416,0,0,0 7=CX,256,D,9,0,0,0 8=CY,256,D,10,0,0,0 9=CZ,256,D,17,0,0,0 10=CU,256,D,14,0,0,0 11=CV,256,D,13,0,0,0 12=DX,256,D,18,0,0,0 13=DX,B,0,16383,66079,0 14=DY,256,D,23,0,0,0 15=DZ,256 16=DZ,UR,129,15738,66079,0 17=DZ,DR,-16384,-258,66080,0 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=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 Elevator=-16380,-512,512,16380 Throttle=-16384,16383/8 Throttle2=-16384,-512,512,16265 PropPitch=-13700,14484/8 Throttle1=-16384,-512,512,16383 PropPitch1=-16384,0,512,16383/32 PropPitch2=-16256,0,512,16383/32 LeftBrake=-16384,16383/24 RightBrake=-16380,16380/24 SyncSlopePropPitch2=113/110 Mixture=-16254,16125/8 Mixture3=0,8192,8192,16380 ElevatorTrim=-16380,-512,512,16380 Mixture2=-16384,8192,8192,13056/8 SlopeRightBrake=10 SlopeElevatorTrim=-7 Flaps=-16384,16383/40 SyncSlopeThrottle2=114/121 Aileron=-16380,-512,512,16380/8 Rudder=-16380,-512,512,16380 SlopePropPitch=-4 SlopeAileron=5 Mixture1=-16384,8192,8192,16383/8 SlopeRudder=3 [Profile.Twinprop] 1=Baron 2=Twin Otter [Profile.SingleProp] 1=DHC-2 2=Beaver 3=Grand Caravan 4=Maule 5=Skyhawk 6=Bravo 7=Tiger Moth 8=Arrow 9=Kodiak [Axes.SingleProp] 0=AX,256,D,7,0,0,0 1=AY,256,D,8,0,0,0 2=AZ,256,D,3,0,0,0 3=BX,256,D,1,0,0,0 4=BY,256,D,2,0,0,0 5=BZ,256,D,29,30,31,32 6=BP,0,F,66416,0,0,0 7=CX,256,D,4,0,0,0 8=CY,256,D,5,0,0,0 9=CZ,256,D,6,0,0,0 10=CU,256,D,14,0,0,0 11=CV,256,D,13,0,0,0 12=DX,256,D,18,0,0,0 13=DX,B,0,16383,66079,0 14=DY,256,D,23,0,0,0 15=DZ,256 16=DZ,UR,129,15738,66079,0 17=DZ,DR,-16384,-258,66080,0 [Axes.TwinProp] RangeRepeatRate=10 0=AX,256,D,7,0,0,0 1=AY,256,D,8,0,0,0 2=AZ,256,D,3,0,0,0 3=BX,384,D,1,0,0,0 4=BY,256,D,2,0,0,0 5=BZ,256,D,29,30,31,32 6=BP,0,F,66416,0,0,0 7=CX,256,D,9,0,0,0 8=CY,256,D,10,0,0,0 9=CZ,256,D,17,0,0,0 10=CU,256,D,14,0,0,0 11=CV,256,D,13,0,0,0 12=DX,256,D,18,0,0,0 13=DX,B,0,16383,66079,0 14=DY,256,D,23,0,0,0 15=DZ,256 16=DZ,UR,129,15738,66079,0 17=DZ,DR,-16384,-258,66080,0 [Window.Radar Contact] Docked=393, 13288, 1717, 2674 [Sounds] Path=E:\Microsoft Flightsimulator X\Sound\ Device1=Primary Sound Driver Device2=IDT Audio1 Device3=IDT Audio2 Have fun! Pete

There's no way to tell FS not to redraw scenery when you change position. If it doesn't redraw scenery, what would you expect to see? A void? Why on Earth is it taking as long as 3 minutes though? Pete

What if I make the current DHC-2 settings the default, so they apply to all other aircraft which don't have an assigned Profile, then add the ones which are rather different in a few Profiles? Pete

All those PFC offsets appear in the Axis assignments as joystick numbers over 15. They have to actually change in value to be recognised, so you can only do the assignment once you have the mechanism in place to change them. I don't know how you propose to do that, but of course you could always do it easily with a Lua plug-in or using FSinterrogate to write values. You can have as many assignments as you like to any button or keypress. In fact you can try writing different values to the same offset with one press, but be aware they may all happen within one poll period, so not be seen as changing. Pete

Sorry, what exactly is this about? Why on Earth are you reproducing documentation here? Is the question merely "won't this save my settings"? YOU can AND SHOULD always save your settings. Just make a safe copy of the INI file somewhere else, on a DVD if you wish. I'm surprised your file has lasted so long intact without any safeguards. The data will of course be saved by any automatic conversion. But it may not be any clearer afterwards because it's such a messy jumble already. you know the saying "garbage in, garbage out"? Your settings won't be lost and can be reinserted if necessary afterwards in any case. Really, I suspect it would be much quicker, tidier and easier to start again from a blank canvas, creating carefully considered profiles, THEN paste in the settings you really want from the original INI. This is basically what I was suggesting I'd help with in my previous reply, just above. Anyway, it is late here now and I'm off to bed. Pete

Questions on your settings. These sections: [Axes.Beech Baron 58 N12F] 0=2Y,256,F,65820,0,0,0 1=2Z,256,F,65821,0,0,0 [Axes.Boeing 737-800 HB-FUN] 0=2X,256,F,65821,0,0,0 1=2Y,256,F,65820,0,0,0 [Axes.Bombardier CRJ 700 Tyrolean] 0=2Y,256,D,9,0,0,0 show only one or two axes usable on those specific aircraft. How do you fly them, using keyboard? There are other liveries of the same aircraft with fuller sets of assignments -- maybe you just never use the above named? Anyway, I've had a good look through your settings and I'm afraid I cannot make head nor tail of them, or at least I am totally confused as to how you have so many different assignments for similar aircraft. I started trying ot sort it out, but gave up when I realised I might be choosing the setups you don't use and losing the ones you do. So: If you could actually list the aircraft you actually use, just one "paint job" for each, your favourite, then I'll make all the similar aircraft use the same settings as those. Then at least the conversion to Profiles will be tidier. however, that said ... Ideally you want Profiles for jets, props, turboprops, stunt planes / fighters and helicopters, separately, plus maybe really separate special categories for those complex add-on aircraft which need special treatment because of the way they are implemented (PMDG stuff comes to mind). Usually there's no need to have separate profiles for 1, 2, 3, 4 engines as the mappings will work accordingly -- unless of course you have 4 throttle evers and like to use three of them for other things when flying a single engine plane, and so on. Best to map out what you really would like to do before embarking on any changes. Let me know what you think and how you'd like to proceed. Pete

Wow! That has just got to be the largest INI file with the most duplication I've ever seen!!! I did offer to help tidy it, but it might take me a while. Better give me your email address and I'll send you the result, but I cannot promise when I'll finish it! Because you have "UseProfiles=No" set. The default for that has been "Yes" for several years now, but you were using Aircraft Specific before this, so it stuck. Also, and the worse thing, is that you have: ShortAircraftNameOk=No whereas the default became ShortAircraftNameOk=substring a much longer time ago, and even when you first started the recommendation was to set this, then shorten the names in the INI so, for instance, "737" matched all 737's. As it is you have complete sections for every single aircraft even if its only a lick of paint different. You should always back up your INI file in any case. With all that work involved you wouldn't want to lose it, surely! Have a go, by all means. But the direct conversion which FSUIPC can do for you won't be any shorter because it cannot tell which aircraft to collect together to make sensible profiles. I'll try to do something for you. Pete

Well of course those offsets are the actual Axis input values, after calibration, NOT the brake pressures at all! You need to have assigned brake axes to get them set. You can write to offsets 3BB4 and 3BBC, and assign and calibrate these to the left and right toe brake axes. These are used by my PFC driver for that purpose. It wouldn't matter if there were methods to do this (and there are) because you say ProSim reads offsets 3416 and 3418, which are NOT brake pressures but axis input values, as documented. Those axes may even be disconnected (using another offset) but they'd still reflect the axis input. That's the whole point of those offsets. If ProSim wanted brake pressure it would read different offsets. Pete

Ah, aircraft specific is the ancient facility which was effectively replaced by Profiles years ago. You must have set your system up with those a long time ago. Aircraft specific settings are still valid, and everything I said still applies except it's a little more complicated deleting them in the INI file -- but as I explained, you don't have to. I assume you don't have every single aircraft, in every possible livery, all individually "specific"? I hope you took advantage of the facility to make them more generic, by using only part of the name so that one entry applied to all? eg 737 for all 737's, etc? If you change the profiles option to Yes then FSUIPC will automatically convert your Specific settings to Profiles, but all it can do really is make a separate profile for every different specific setting so it would still really need tidying up. If you'd like to paste in your FSUIPC4.INI file here, in a message (enclose it using the <> button above the Edit area), I'll try to sort it out for you. Meanwhile it might be a good idea if you perused the current edition of the FSUIPC User Guide. Maybe there's a lot more you've been missing? ;-) Pete

No. Battery life isn't relevant in flight in any case -- you have generators. You aren't flying an electric aircraft, are you? And if there was no electric power you'd have no instrumentation anyway. Why would the COM radios survive? FSUIPC doesn't operate radios itself. It has offsets which can be used by application to directly set and read the frequencies, of course, and it can pass on radio commands just like when they are assigned in FS directly. But it has no manipulations of anything itself. Ask Sim-Avionics support more about what they do. They surely must be able to help if their software is managing the radios. However, most such packages leave radios to the normal FS facilities, as in general there is nothing wrong with them and no reason for even sophisticated cockpit software to interfere -- unless they want to simulate faults of course. I use Project Magenta and also Prosim737 and in both cases the radios are normal FS radios, interfaced to my hardware through FSUIPC using normal FS controls. They'd be the same without either package. Pete

Once you've assigned an aircraft to a Profile you can only unassign it by deleting it from the Profile's list of aircraft -- in the [Profile.<name of profile>] section of the FSUIPC4.INI file. However, it is not necessary (which is why there's no option for it) -- just load an aircraft which has not been assigned to a Profile and assign there. That assignment will then apply to all other unassigned aircraft. However, for each different existing profiles you will still need to repeat the assignment. But only once per profile, of which it is unlikely you have many. Just load once aircraft of each profile. Pete

Well obviously something has changed. Are you sure FSX hasn't re-enabled its controller assignments and it interacting with your FSUIPC assignments? That's the most usual cause. It tends to do this sometimes when it thinks the controller is newly attached. Otherwise I can only think you have a bad connection or a faulty yoke, which gives occasional disconnections -- that would result is such a bad reading and no doubt it would be intermittent. Have you tried just watching the values in the assignments or calibration tabs, or in Windows own calibration applet (game controllers or whatever)? You can use FSUIPC's axis event logging, in the logging tab, to see what is going on. If you (temporarily) run FS in Windowed mode you can enable also the Console Log, and see the changes in real time on screen. Pete