Pete Dowson

In that case it is defined incorrectly (probably in the registry) as a digital lever instead of an analogue one. That is really one big waste of an axis. I expect the installation of the CH drivers did that. -- I have heard of it happening before, but i am afraid I do not know the fix for it. I recommend you ask Bob Church over in the CH Hangar. http://www.ch-hangar.com/. Bob is an expert in all things CH. Regards Pete

Strange, but I see that your FSUIPC settings are far from the default INI you stated you used. I don't think mere assignment of the button to gear up and down by itself can possibly cause a problem, as nothing will happen till you operate that button. More likely that the button is operating spuriously. you need to look at what is wrong with your CH configuration, and the possibility that you have a badly behaing button. When you descend through 15500 don't you see or feel or hear the gear descending? Or maybe it was lowered (which would explain why you descend at such low speeds) and it got raised then, so increasing your descent to more normal speeds? That in itself may be related to the airspeed as retracting the gear above a certain speed is not possible. Whatever, I'm afraid I'll have to leave you to your own investigations of this. There's really nothing FSUIPC can be doing about it. Regards Pete

Actually those points are covered in the same way for both versions. Actually, printing it is really not so helpful, unless you want to take it into your lounge for full reading. Using it as a PDF on screen may be less conveninent but it has the huge advantage of allowing quick searches. For instance you'd find the Gear solution immediately by searching for "Gear down" or "Gear Up". I'm over 68 now and, yes, my memory is not as good as it was. I put all manuals on my iPad for searching there. That's how I manage to respond here in the forum. Regards Pete

Really? I've no idea why, because that aircraft certainly doesn't use or need FSUIPC. I've never heard of anyone getting FSUIPC automatically with any FSX PMDG asircraft because they simply never use it. Well the latter certainly sounds like a PMDG bug or mis-installation as I'm sure the weather has nothing to do with that. The rest is a function of the buggy FSX weather I'm asfraid. you'd be better off getting a decent weather control program like ASE and using its DWC (global direct weather control) mode. With an unregistered version all that is doing is preventing FSUIPC reading weather. It is certainly never writing any weather. I suggest you check the PMDG support forum or make reports there. Regards Pete

The FSX version, PFCFSX, should work fine with Prepar3D. It does here. The old PFC.DLL was only ever for FS9 and before. Pete

Well, sorry, but there is nothing in FSUIPC itself that touches anything which could do that -- though it does actually seem to me that unless your descent is very slow indeed, the 270 knots speed is the more realistic. most descents, until 10000 feet at least, would be at something like 280 knows. You'll need to look elsewhere to find what it actually happening at 15500 feet. Use FSUIPC logging by all means to see if you can spot it. I think you will need to discuss this with other NGX users. BTW when you "delete the Modules" folder, are you sure you aren't deleting some other modules which are loading? I recall that some of the PMDG modules put themselves there too. Regards Pete

And ... what happened next? Seems your registry is incorrect so that FSUIPC's installer cannot find FS9. There is a utility somewhere which will fix that, but in the meantime just point the installer to the correct FS9.EXE when it asks. Regard sPete

Okay, go to Download Links and get FSUIPC 3.998j, 4.747 and/or WideClient 6.899j, as needed. The Lua "ext" library has been extended quite a bit. You'll need the updated Lua library documentation too. Regards Pete

There are two programs available which may fit the bill: Scenery Config Editor by Andrew & John Thornton, AVSIM file sceneryconfgeditorv1.0.7.zip and one which looks like it could be made to do things properly, except that I can't make it work at all: MH's FS Scenery Configurator V2.0 by Michael Heise, AVSIM file: fsscncfg20.zip I use the former one a lot for renumber layers, to keep everything tidy after adding new stuff. Regards Pete

There are more of those than could be incorporated in the same space as the existing documentation. In fact, as you'll find out if you plough all the way through this Forum, there's probably an unlimited number of things folks want to do or might want to do. FSUIPC is a toolkit. Would you be able to put together a complete list of all the things you can do with a standard workshop toolkit? Of course not. And, after all, the existing documentation does already cover the standard things folks ask about, as in this thread. The documents are searchable, but folks just don't like using documentation, so really adding yet more wouldn't help. Note laso that much of the existing set of documents, helps, FAQs etc have been generated over the years in response to feedback and questions in the first place. BTW I'm the same -- I fiddle around and experiment before looking things up inmanuals. But then if that failed, I'd certainly look things up before posting questions. Pete

You said your FSUIPC INI file is defaulted, though that cannot be if you've disabled turbulence and gusts! So what did you really mean when you said that? The FSX.CFG is really no use to me. It has no effect on anything in FSUIPC. If there's a problem in FSUIPC it will be logged, so check the FSUIPC log file. If I were you I'd post for assistance to the CH Hangar site. Bob is very helpful with CH problems. I really don't know anything about what CH's own programs are doing. most folks I know using CH gear don't use their programs. Regards Pete

Right. The problem is simply that it isn't receiving the Broadcasts from the Server which tell it where it is (name, ipaddress, protocol to use). As fully described in the WideFS user guide (see the "configuring" section), for btroadcasts to work yo MUST have at least WinXP SP1 or later on each PC, and all PCs must be in the same Windows workgroup. If you don't want to rename one or other of your workgroups so that they are the same, or they are the same but something else is using the broadcaster port already (Port2 in your INI files), you can instead add the ServerName and Protocol parameters into the INI. Please do refer to the user guide for more information. Regards Pete

Okay, but why did you paste the WideServer log again? The most important information will be in the WideClient log as I said. Pete

The FSUIPC spoiler calibration can do that. You calibrate the spoilers down as minimum, the arm zone as the centre zone, and the max as the fully extended position. Just follow the FSUIPC calibration instructions in the User Guide. Don't forget to reverse the axis (REV checkbox) before calibrating. There's an example which does exactly that in the User Guide. There are even pictures to help. Please check the section on axis assignments. Didn't you think of looking in the User Guide at all? Sounds like it is also assigned in FS. You sohuld assign buttons and axes in both FS and FSUIPC, only one or the other. Pete

You submitted a support query to the Download Links subforum, which is where I provide links to updates and other goodies. Please use this Support Forum for questions. You are lucky I noticed your post. No, I know no way of doing that. The scenery file is loaded long before anything can be done by FSUIPC. All you can do is run some sort of batch file before FS to rename your assorted SCENERY.CFG files. Note that even having different users doesn't work with scenery, as the SCENERY.CFG is global for all users, unlike the main FS CFG file. There's a good reason for that. Each time there's a change in the SCENERY list, FS has to generate new indices in each scenery library. Regards Pete

If you aren't using FSUIPC for anything, it cannot itself interfere with whatever your NGX is doing. It is possible that with it installed some other program is using it to adjust things like the weather. With autothrottle enabled the usual reason for a sudden increase in thrust is to compensate for a sudden change in wind direction, or gusts, turbulence, or maybe air temperature. You could try checking the options to inhibit turbulence and gusts, in the Winds and Clouds tabs. Regard sPete

If you are not using IPX protocol that doesn't matter. Windows XP and later don't install IPX by default as Win98 used to. The logs you supplied show all is well as far as I can tell, but you've omitted to show the crucial log, the one for WideClient. After all, it is WideClient which cannot connect so that's where the main information will be. BTW if you've changed nothing and it suddenly doesn't work, then a hardware failure seems likely. software doesn't change on its own. Regards Pete

I doubt if anyone could explain that, because in FS and FSUIPC there's no difference in the way the trim works in any default fixed wing aircraft. (Add-ons may do their own thing, although that'd be unusual for trim). Best try the general forum for whatever Flight Simulator you are using, and you'll need to give a bit more information too -- like which FS, which aircraft specifically, etc. Regards Pete

Version 1 was for FS2000, version 2 for FS2002. We were up to version 3 for FS9 and that superseded those. Version 4 was developed separately for FSX. If I contemplated doing a version for MS Flight, which I'm not at present, it would be version 5. We'll never get to a version 9 -- I'll be dust before then! The current versions are 3.998g for FS9 and before, and FSUIPC 4.745 for FSX, ESP and Prepar3D. The earliest supported versions are 3.99 and 4.70 respectively. Also check the Download Links subforum here. Regards Pete

No, just delete it please. Is the RC manual still so out of date? RC's menu window needs are met by provisions in FSUIPC itself. Check the section entitled "Message Window Options" in the earlier part of the FSUIPC user guide. Regards Pete

Well, it's some function operated by one of those, then. It may be an attempt to implerment the anti-skid system. It doesn't make sense in any case to have both high thrust setting and brake the same side at the same time -- opposite side thrust, yes, for tight cornering. Pete

Advdisp is obsolete and not supported in FS9. Since FS9 the same function has been built into FSUIPC. Please read the user guide, and/or visit the Radar Contact Forum for help. Regards Pete

Good. Happens to me too. I think it's often related to other scenery layers, common textures, things like that. It gets very complicated. I've got such a problem at the moment which I cannot resolve -- it isn't consistent, so it is almost impossible to track down. Regards Pete

I've never heard of that. Is this with a specific aircraft? If so it must be specifically programmed like that. It certainly isn't normal. Regards Pete

How did you manage that? The INI file is managed by Windows, not by FSUIPC, and it should be impossible for it to create more than one entry with the same parameter name in the same section. Well they won't do any harm, but I couldn't say whether Windows will pick the first or last of the duplicates, so it makes them ambiguous. If it's only the entries in the General section, as shown, just delete the duplicates lines. Doesn't look that big a job. Here, I've sorted the parameters so you can see which ones to delete: AileronSpikeRemoval=No AutoClearWeather=Yes AutoTaxiWind=No AutoTuneADF=No AxisCalibration=No AxisInterceptIfDirect=No BlankDisplays=No BrakeReleaseThreshold=75 CentredDialogue=No ClearWeatherDynamics=Yes ClockSync=No CloudIcing=No CloudIcing=Yes CloudThinness=100 CloudThinness=1000 CloudThinness=1000 CloudThinness=1000 CloudThinness=1000 CloudThinness=1000 CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CloudTurbulence=Yes CorrectVSsign=No DisconnTrimForAP=No DontResetAxes=No ElevatorSpikeRemoval=No ExtendMetarMaxVis=No ExtendTopWind=No ExternalOptionControl=Yes FixControlAccel=No FixWindows=No GenerateCirrus=Yes GraduatedVisibility=No History=Y4RTTRKM7HV3R0CDVJBVM JoystickTimeout=20 KeepFS98CloudCover=No LimitWindVariance=No LowerVisAltitude=0 MagicBattery=Yes MainMenu=&Modules MaxIce=0 MaxIce=3 MaxSurfaceWind=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 MinIce=0 MinimumVisibility=0 MouseWheelTrim=No MouseWheelTrimSpeed=1 MoveBGLvariables=Yes NavFreq50KHz=No OneCloudLayer=No OwnWeatherChanges=No PollGFTQ6=Yes PressureSmoothness=1 PropTaxiWind=No ReversedElevatorTrim=No RudderSpikeRemoval=No SetVisUpperAlt=No ShortAircraftNameOk=No ShowMultilineWindow=Yes ShowPMcontrols=No SmoothIAS=Yes SmoothPressure=Yes SmoothVisibility=No SpoilerIncrement=512 StopAutoFuel=No SubMenu=&FSUIPC ... SuppressAllGusts=No SuppressCloudTurbulence=No SuppressMultilineFS=No SuppressSingleline=No SuppressWindTurbulence=No TCASid=Flight TCASrange=0 ThinClouds=No ThinThunderClouds=No ThrottleSyncAll=No ThrottleSyncToggle=145,8 ThunderCloudThinness=10000 TimeForSelect=4 TimeSetMode=Partial TrafficControlDirect=Yes TrafficScanPerFrame=10 TrapUserInterrupt=Yes UpdatedByVersion=3980 UpperVisAltitude=10000 UpperVisibility=8000 UpperWindGusts=No UseProfiles=No VisSmoothAirborneOnly=No VisSmoothingDelay=0 VisUpperAltLimit=0 VisibilitySmoothness=5 WeatherReadInterval=4 WeatherReadsFast=No WhiteMessages=No WindAjustAltitude=No WindAjustAltitude=No WindAjustAltitude=No WindAjustAltitude=No WindAjustAltitude=No WindAjustAltitude=No WindAjustAltitudeBy=2000 WindDiscardLevel=0 WindLimitLevel=0 WindShearSharp=No WindSmoothAirborneOnly=No WindSmoothing=No WindSmoothing=Yes WindSmoothing=Yes WindSmoothing=Yes WindSmoothing=Yes WindSmoothing=Yes WindSmoothingDelay=0 WindSmoothness=-5 WindTurbulence=No WindTurbulence=Yes WindTurbulence=Yes WindTurbulence=Yes WindTurbulence=Yes WindTurbulence=Yes WindTurbulence=Yes WindTurbulence=Yes ZapSound=firework ZeroElevForAPAlt=No Assuming the first of each is the one you want (and here I'm not sure), here's the fixed list: AileronSpikeRemoval=No AutoClearWeather=Yes AutoTaxiWind=No AutoTuneADF=No AxisCalibration=No AxisInterceptIfDirect=No BlankDisplays=No BrakeReleaseThreshold=75 CentredDialogue=No ClearWeatherDynamics=Yes ClockSync=No CloudIcing=No CloudThinness=100 CloudTurbulence=Yes CorrectVSsign=No DisconnTrimForAP=No DontResetAxes=No ElevatorSpikeRemoval=No ExtendMetarMaxVis=No ExtendTopWind=No ExternalOptionControl=Yes FixControlAccel=No FixWindows=No GenerateCirrus=Yes GraduatedVisibility=No History=Y4RTTRKM7HV3R0CDVJBVM JoystickTimeout=20 KeepFS98CloudCover=No LimitWindVariance=No LowerVisAltitude=0 MagicBattery=Yes MainMenu=&Modules MaxIce=0 MaxSurfaceWind=0 MaximumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 MinIce=0 MinimumVisibility=0 MouseWheelTrim=No MouseWheelTrimSpeed=1 MoveBGLvariables=Yes NavFreq50KHz=No OneCloudLayer=No OwnWeatherChanges=No PollGFTQ6=Yes PressureSmoothness=1 PropTaxiWind=No ReversedElevatorTrim=No RudderSpikeRemoval=No SetVisUpperAlt=No ShortAircraftNameOk=No ShowMultilineWindow=Yes ShowPMcontrols=No SmoothIAS=Yes SmoothPressure=Yes SmoothVisibility=No SpoilerIncrement=512 StopAutoFuel=No SubMenu=&FSUIPC ... SuppressAllGusts=No SuppressCloudTurbulence=No SuppressMultilineFS=No SuppressSingleline=No SuppressWindTurbulence=No TCASid=Flight TCASrange=0 ThinClouds=No ThinThunderClouds=No ThrottleSyncAll=No ThrottleSyncToggle=145,8 ThunderCloudThinness=10000 TimeForSelect=4 TimeSetMode=Partial TrafficControlDirect=Yes TrafficScanPerFrame=10 TrapUserInterrupt=Yes UpdatedByVersion=3980 UpperVisAltitude=10000 UpperVisibility=8000 UpperWindGusts=No UseProfiles=No VisSmoothAirborneOnly=No VisSmoothingDelay=0 VisUpperAltLimit=0 VisibilitySmoothness=5 WeatherReadInterval=4 WeatherReadsFast=No WhiteMessages=No WindAjustAltitude=No WindAjustAltitudeBy=2000 WindDiscardLevel=0 WindLimitLevel=0 WindShearSharp=No WindSmoothAirborneOnly=No WindSmoothing=No WindSmoothingDelay=0 WindSmoothness=-5 WindTurbulence=No ZapSound=firework ZeroElevForAPAlt=No Incidentally, it looks like you are using an old version of FSUIPC. The current versions are 3.998g and 4.745. I'd advise you to update. No idea, sorry. Some sort of disk access glitch by Windows maybe? As I said, it should be impossible, so something evidently went wrong. But the saving of those parameters is done by Windows profile management, not file access in FSUIPC. Since I've never seen it happen before (and this is over a 12 year history of FSUIPC, I doubt it will happen again -- unless it's a specific bug in your system of course, which seems unlikely. But update your FSUIPC please. Regards Pete