Pete Dowson

No idea. What's ADEX? Seems there's a good link there, both to FSUIPC itself and to the SDK (the SDK is for developers). Pete

Okay. Try this. [General] UpdatedByVersion=4880 History=G6H2CO1TR9UX5U0REPI3X TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No GetNearestAirports=Yes WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 LuaRerunDelay=66 Console=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=3 MinIce=-1 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No 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=No 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 BrakeReleaseThreshold=75 SaveDataWithFlights=Yes ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes MouseWheelMove=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes EnableMouseLook=No AxesWrongRange=No InitDelay=0 InitDelayDevicesToo=No OOMcheck=Yes LogExtras=x4 LogButtonsKeys=Yes LogLua=Yes PollInterval=15 UseMidMouseBtn=Yes LogWeather=Yes FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0 SimConnectUsed=10.0.61259.0 LogWrites=Yes LogReads=Yes LogEvents=Yes [JoyNames] AutoAssignLetters=Yes A=BU0836 Interface B=Virtual Joystick 0=BU0836 Interface 0.GUID={486EF670-8BD6-11E2-8001-444553540000} 1=Virtual Joystick 1.GUID={7BA4DE70-8BDA-11E2-8002-444553540000} A.GUID={486EF670-8BD6-11E2-8001-444553540000} B.GUID={7BA4DE70-8BDA-11E2-8002-444553540000} [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [Sounds] Path=E:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Sound\ Device1=Primary Sound Driver Device2=SAMSUNG-1 (NVIDIA High Definition Audio) Device3=Digital Audio (S/PDIF) (High Definition Audio Device) Device4=Digital Audio (S/PDIF) (High Definition Audio Device) [AutoSave] AutoSaveEnabled=No Next=1 Interval=60 Files=10 SaveOnGround=No [GPSout] GPSoutEnabled=No Port=COM0 Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No Sentences= [Programs] [ClientNames] 1=AVIONICS [Monitor] Display=1 [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=Yes 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=-16068,-512,512,16096 SlopeAileron=-7 Elevator=-16209,-512,512,16131 SlopeElevator=-6 Rudder=-13926,-492,512,16274 LeftBrake=-16384,16383 RightBrake=-16384,15798 !1=T PropPitch=-16380,16380 Throttle1=-16182,-104,-104,22/56 Throttle2=16383,16383,16383,16384/40 SlopeThrottle1=12 FlapStarts=-16384,-2461,9451,15968 FlapEnds=-15968,2923,12663,16384 Flaps=0,16380 Spoilers=3674,3674,10823,16185 Reverser=-16380,16380 SlopeThrottle2=7 [Axes] 0=AX,256,D,3,0,0,0 1=AU,256,D,7,0,0,0 2=AV,256,D,8,0,0,0 3=BX,256,D,9,0,0,0 4=BY,256,D,10,0,0,0 5=BU,256,D,22,0,0,0 6=BV,256,D,23,0,0,0 [Buttons] 0=P1001,0,Cx0D0073F8,x01 2=P1001,5,Cx050073F8,x20 4=P1001,1,Cx050073F8,x02 5=P1001,14,C66040,16211 6=U1001,1,Cx090073F8,x02 7=U1001,0,Cx090073F8,x01 8=P1001,2,Cx050073F8,x04 9=U1001,2,Cx090073F8,x04 10=P1001,3,Cx050073F8,x08 11=U1001,3,Cx090073F8,x08 12=P1001,4,Cx050073F8,x10 13=U1001,4,Cx090073F8,x10 14=U1001,5,Cx090073F8,x20 15=P1001,13,Cx050073D5,x40 18=U1001,13,Cx090073D5,x40 19=P1001,7,Cx050073F9,x01 20=U1001,7,Cx090073F9,x01 21=P1001,8,Cx050073F9,x02 22=U1001,8,Cx090073F9,x02 23=P1001,9,Cx050073F9,x04 24=U1001,9,Cx090073F9,x04 25=P1001,10,Cx050073F9,x08 26=U1001,10,Cx090073F9,x08 27=P1001,11,Cx050073F9,x10 28=U1001,11,Cx09000049,x10 29=P1001,12,Cx050073F9,x20 30=U1001,12,Cx090073F9,x20 31=R1001,19,Cx110073FD,x00FF0001 32=R1001,18,Cx210073FD,x00FF0001 33=R1001,23,Cx110073FC,x00FF0001 34=R1001,22,Cx210073FC,x00FF0001 35=R1001,21,Cx210073D2,x00FF0001 36=R1001,20,Cx110073D2,x00FF0001 37=R1001,25,Cx110073D7,x00FF0001 38=R1001,24,Cx210073D7,x00FF0001 39=R1001,27,Cx210073D8,x00FF0001 40=R1001,26,Cx11000049,x00FF0001 41=R1001,29,C65883,10 42=R1001,28,C65884,10 50=PB,0,C3,0 51=PB,1,C65552,0 54=RB,2,C65604,0 55=PB,3,C65972,0 56=RB,5,C66635,0 60=PB,4,C65588,0 66=UB,4,C65752,0 67=UB,5,C65967,0 [MacroFiles] 1=iFly737 2=leveld767 [Buttons] Buttonrepeat=20,10 [LuaFiles] 1=ipcReady [/CODE] Regards Pete

It looks like you've made another complete mess. It seems you do not know how to edit files at all! You now have one Profile only, called LEAR45, and it only works with an aircraft with exactly "Learjet 45" in its name. That profile has a large Buttons assignment section, but with an error: 0=PB,4,Cx02000BC8,x0000 1=UB,4,Cx02000BC8,x7FFF 0=P1001,0,Cx0D0073F8,x01 Two lines 0's won't work, only the second one will have any effect (I think -- it rather depends on how windows processes it -- Windows is "in charge" of FSUIPC's INI file)! You've now only got one Axis assigned: [Axes.LEAR45] 0=BS,R0,D,23,0,0,0 and no Joystick Calibrations in that Profile -- the default ones in your default section will apply. It seems that every time you mess about with the file you make it worse. Why not delete the **** thing and start again? Or simply avoid using Profiles, because it seems obvious you don't know what you are doing with them. Since you've only got one and only ever fly the one aiircraft, why on Earth are you messing with Profiles in any case? I hope you've saved your proper complete INI because it appears you've lost some stuff. If you'd like to post the most complete one I'll edit it for you to make it only have the one set of things, no profiles. Maybe then you won't get so confused? :sad: Pete

Yes, the TA's (and, where they are fixed irrespective of QNH, the TLs) are in the Airports.dat file (a text file) in the Aivlasoft\NavData folder in your FS folder. Regards Pete

So, that's an old copy of WideSever.Log? WideServer log is actually created only if it enabled, so it seems you did have it enabled earlier today and have disabled it since then! BTW, I was wrong when I said that the WideFSenabled parameter in the INI was only changed on FS exit --it is actually changed when you OK from the FSUIPC Options. If you 'Cancel' or Escape' out then nothing is changed. With that in your INI file the "About" tab in FSUIPC will show whether your WideFS is registered or not (if so it will give your name and email in that bottom right quarter), and the button will show "Enable WideFS". If you press that it will change to "Disable WideFS" and when you press OK, the INI file is updated. WideFS is enabled when FSUIPC shows your are registered and the button shows that you can Disable it. It sounds like you are rather mixed up on the function of the button. It does what it says on the label! Regards Pete

The value is a 16-bit binary number. It is neither a decimal integer or an hexadecimal one, it is simply a row of 16 bits, each of which is 0 or 1. It is the way you interpret it, the way you display it, which changes, never the value itself which is still always a row of bits. In the case of BCD, the hexadecimal way of showing it shows the correct Transponder code. It isn't the conversion of one type of value to another, only the way of showing it in printable/displayable form. Pete

What does that mean? I don't understand you. Are you saying there is no WideServer log file at all, or you can't read it, or what? That might mean WideServer isn't running, but it might also mean that there is a Firewall preventing access. Let me clarify one thing: the "WideFSEnabled" parameter in the INI always defaults to "Yes". The only thing that will ever turn it to "No", other than editing the INI, is clicking on the button in the FSUIPC options to disable it. That facility is intended simply to allow WideServer to be temporarily disabled for any reason. The only thing which stops WideServer running otherwise is a lack of Registration. Perhaps you need to check the FSUIPC log itself to make sure it shows that you are Registered for WideFS! Please, rather than trying to interpret Log files yourself, you should just paste them into your messages here. They won't be too long and I will be able to see more clearly what you are doing. Regards Pete

Oh dear. I already told you, it is HEXADECIMAL!. I am sure Delphi has some way of converting a decimal number into a hexadecimal string!! Don't you have any reference books or "Delphi for Dummies" books to refer to? If not you will have to resort to VERY simple arithmetic -- Take the Remainder when dividing by 16 = 4th digit Take the Quotient from that and divide by 16, remainder = 3rd digit Take the Quotient from that and divide by 16, remainder = 2nd digit Take the Quotient from that = 1st digit Try it! Pete

Except for buttons, switches, axis settings, parameters in the INI only get updated on a normal close of FS. No. WideFS is independent of SimConnect. But FSUIPC must have the full interface to SimConnect working, of course. WideServer has its own log file. That's where you look -- WideServer.LOG in the Modules folder. WideClient also makes a log. If you have WideFS problems those are the places to look. You don't need any experience to use WideFS. I don't know why you are studying INI files and wrong LOG files instead of just saying why you think it isn't working! You've not even said if you have a problem, yet! Regards Pete

Don't edit the INI, click the button in the FSUIPC options to enable or disable it! Pete

It sounds exactly like you have multiple assignments to the same buttons, probably in FS and in FSUIPC. You must use one or the other for buttons. Pete

FSUIPC doesn't load the aircraft. BTW I see you use a differnt aircraft too! You have two buttons assigned to a Profile called LEARJET45. [Buttons.LEARJET45] 0=PB,4,Cx02000BC8,x0000 1=UB,4,Cx02000BC8,x7FFF [/CODE] Also all of your axes and calibrations are for LEARJET54, not LEAR45. Are you sure you didn't just make a mistake when you edited the INI file? You say you only have one, the LEAR45, but if so why is everythnig else in the name of LEARJET45? Either that or you are really loading the wrong aircraft despite your belief. The LEARJET45 has been assigned to an aircraft with the title Learjet 45 and the LEAR45 to an aircraft named LEAR45, so there are certainly two different Profiles for differently named aircraft. Pete

When using FS offsets fpr the gear LEDs, (0BEC, 0BF0 and 0BF4), you simply set Green when they are >=16383, Off when they are =0, and red otherwise. How do I know? Originally by trying every number I think. Or maybe I looked it up in the Goflight SDK. It was a long time ago. Trgards Pete

It's all still there. It simply sounds like you didn't load the aircraft known as LEARJET45. None of your settings apply to any others. BTW is that the full name of the aircraft? You have: ShortAircraftNameOk=No set, for more flexibility that would be better as "ShortAircraftNameOk=Substring" so that it recognises "LEARJET45" anywhere in the aircraft title. Pete

I seem to recall that there are actually 6 lights for the Gear indications in the LGT: 1 = not used 2 = right gear moving (red) 3 = right gear down (green) 4 = left gear moving (red) 5 = left gear down (green) 6 = nose gear moving (red) 7 = nose gear down (gren) So every setting you'd need two "clearlights", eitherr both off, or one on the other off. I don't know ProSim offsets though, so I can't help with that side. Pete

If its installed then it will run when FS is running. You don't "start it". It is a collection of tools for you to use as you wish. i assume you bought it for a reason? The User Manual is quite comprehensive, so it sounds like you've not even looked at it! And there are lots of other bits installed for you to help you do whatever it is you want to do with it! You could have installed it and read the user manual BEFORE you paid for it. If you don't know what to use it for or even whether you want it, surely that would have been the sensble course? Buying it then asking what it is for seems an odd way round to go!? Pete

That looks fine. FSUIPC is working well. No, not exactly. All I am saying is that nothing FSUIPC does has anything whatsoever with any certificates at all. It simply is not any part of anything it does. Not even anything remotely related to that area. Therefore if the problem occurs when FSUIPC is running but not if it isn't then what is happening is some interaction either in SimConnect or in another add-on, which is corrupting something in memory only in those circumstances. It may be because there's a bug in FS (but in that case I'd expect others to corroborate your findings), or because of some fluke in the timing of different events in SimConnect (or elsewhere), or simply because the memory arrangement is different when FSUIPC is loading. There are so many variables here that it is not possible to say, especially without any process of elimination being carried out too. It would also help somewhat if you could find at least one other person with the same problem and compare notes -- add-ons, etc. Whatever it does turn out to be, without Microsoft's assistance in debugging the cause (which they won't) there's zero chance of it being fixed I'm afraid. The best you might be able to do is find some slightly different arrangement which works. For example, changing the order in which the different add-in DLL modules load might well fix it. The entries in the DLL.XML file govern this. [LATER] I just had another look at your AVSIM thread. There are two things which concern me a little: Since you are using Windows 8, which came out much later than FSX, it might be a good idea to see if you could run it in the compatibility mode for the Windows version it was originally designed for -- XP, or maybe try Vista or Win7. Ugh! That is definitely NOT a good idea. Why do that? It should never be necessary! Regards Pete

There are only buttons for Joystick B. Just one joystick? I thought you said there were two on the Client PC you needed re-programmed? It's always best to paste in any case. Else i'd have to download into a folder on my PC and analyse separately. Doing it here is easier and quicker. And are all these now on Joystick 1001? You've not told me which is which. The joystick entries from before don't tell me anything about joysticks on the Client PC -- obviously, because they are the results of scanning on the FSX PC. You need to actually press a button on each of your Client PC devices to determine the Joystick numbers! If they are 1001 then all you needed to do was change all the B's into 1001, thus: [Buttons.LEAR45] 0=P1001,0,Cx0D0073F8,x01 2=P1001,5,Cx050073F8,x20 4=P1001,1,Cx050073F8,x02 5=P1001,14,C66040,16211 6=U1001,1,Cx090073F8,x02 7=U1001,0,Cx090073F8,x01 8=P1001,2,Cx050073F8,x04 9=U1001,2,Cx090073F8,x04 10=P1001,3,Cx050073F8,x08 11=U1001,3,Cx090073F8,x08 12=P1001,4,Cx050073F8,x10 13=U1001,4,Cx090073F8,x10 14=U1001,5,Cx090073F8,x20 15=P1001,13,Cx050073D5,x40 18=U1001,13,Cx090073D5,x40 19=P1001,7,Cx050073F9,x01 20=U1001,7,Cx090073F9,x01 21=P1001,8,Cx050073F9,x02 22=U1001,8,Cx090073F9,x02 23=P1001,9,Cx050073F9,x04 24=U1001,9,Cx090073F9,x04 25=P1001,10,Cx050073F9,x08 26=U1001,10,Cx090073F9,x08 27=P1001,11,Cx050073F9,x10 28=U1001,11,Cx09000049,x10 29=P1001,12,Cx050073F9,x20 30=U1001,12,Cx090073F9,x20 31=R1001,19,Cx110073FD,x00FF0001 32=R1001,18,Cx210073FD,x00FF0001 33=R1001,23,Cx110073FC,x00FF0001 34=R1001,22,Cx210073FC,x00FF0001 35=R1001,21,Cx210073D2,x00FF0001 36=R1001,20,Cx110073D2,x00FF0001 37=R1001,25,Cx110073D7,x00FF0001 38=R1001,24,Cx210073D7,x00FF0001 39=R1001,27,Cx210073D8,x00FF0001 40=R1001,26,Cx11000049,x00FF0001 41=R1001,29,C65883,10 42=R1001,28,C65884,10 [/CODE] So those work with a Joystick on the FSX PC? Is that this one, which used to be Joystick A? If then they are all okay, as you have them? BTW, you have a "LEARJET" and a "LEARJET45". Are the really distinct aircraft Profiles or specific selections? Or do you need the above merged into one section? If so the line numbers in the smaller section should be changed to 43-50 so there's no duplicates. Regards Pete

So how did he get this? 1001 is Joystick #1 on the 1st listed Client on WideFS. Okay. In that case, for those two, the joystick letterng isn't relevant. They will be joysticks 1001 and 1002 now, assuming that PC is your first or only Client (the clients are listed in the WideServer section of the FSUIPC4.INI file). That's okay, providing they are only buttons, no axes, and it is for those i offered to edit your [buttons] section for you. I've not seen that yet. No, it cannot do that. To start with there is no guarantee that the GUIDs on two separate PCs are the same and/or not duplicated. The only way FSUIPC can identify devices on a WideFS client is by WideFS assigning joystick numbers 1xxx for the 1st client, 2xxx for the second, and so on. Only for the joysticks connected to the new FSX PC. For the WideFs ones we need to convert the letters to the client joystick numbers.. Look, I explained all this already, and even volunteered to do the work for you. What else do you want? :sad: BTW, is your client PC a long way from your FS PC? Or have you run out of USB ports on the FS PC? If neither, why not simply plug those two into the FSX PC and use the same INI as beflore? Aren't you making this rather more complicated than you need to? Pete

Er, there's some misunderstanding here! You said: which means that joystick is connercted on your Client PC, not on the FS PC! But there are only two "virtual Joysticks" listed on you "Old PC" -- #0 which is A and #1 which is B. Evidently you didn't copy the [Joysticks] section as well as the Buttons section!!! Why didn't you simply use the whole existing INI file? Why pick out sections? That's why the new assignments are different -- FSUIPC had to remake them all! Throw away the INI and use your old one. There's no point in having letters assigned to unique GUDs as you had and then just discarding the correspondence! That destroys the whole point. Can't you see that? Meanwhile i've no idea where WideFS and your Client joystick connections come into this. You appear to have completely changed subjects since the first post! :sad: :sad: Pete

Yes, but you must surely realise that each joystick on each Client PC needs to have a unique number -- otherwise how can FSUIPC handle joysticks on both the local PC and all of up to, what, 99 clients? The whole point, surrely, of being able to have joysticks on clients is to enable as many separate assignments as you need, where you want them. How would assignments work if all PC joysticks were numbered from 1, or 'A'? I'm afraid the lettering of joysticks only applies on the FS PC. it won't help with clients. You'd need to simply replace the joystick numbers in the INI file with the new ones. If you know, for example, that joystick 1001 now is the same one as 'A' or maybe 1 on the original, then search and replace all instances or =PA or =P1, with =P1001, and the same for =U and =R. If you don't have an editor which can do this easily, or you are not sure, just paste your complete original FSUIPC.INI in a message here (r at least the [buttons] section(s) ), and tell me all the correspondences, and i'll do it for you. It's no trouble -- I have an editor with a good search/replace facility. BTW you do realise that Axis assignments aren't transmitted through WideFS? At least, not without a Lua plug-in to do this. Regards Pete

I said it must be related to Simconnect because the nterface FSUIPC has into FSX is almost entirely through the SimConnect facilities. The only extra bits not through SimConnect are the user facilities for assigning things, and some facilities used by applications or specific controls like changing the traffic levels and the patching to prevent some G3D crashes and provide better ground friction coefficients. Incidentally, I've got one PC which has a broken SimConnect interface which only a complete Windows reinstall might fix. The SimConnect installation .msi's won't fix most SimConnect problems, especially those caused by attempts to uninstall and reinstall which almost always make a pigs-ear of the Windows side-by-side registration. The Win vista/7/8 side-by-side system is one of the most diabolically convoluted designs I've ever encountered and one which the FSX uninstall and repair routines obviously have little knowledge of or power over.. I also note from your AVISM post that you have a number of other add-ins, any one of which might interact poorly with any other, including FSUIIPC. You probably blame FSUIPC because it is no doubt the biggest user of SimConnect of them all, the most active, and so most likely to be involved in any interactions. To really narrow things down you need to stop all the others running and just test with FSUIPC alone. If that gives no problem then add the others one at a time, testing in between. You also need to consider whether anything you are using is an FSUIPC application -- i.e. interfaces into FSX internals through FSUIPC. Because they can do many drastic things which FSUIPC wouldn't do of its own volition. In fact if you are not using any such programs, and are not using its user facilities, FSUIPC is simply passively reading data to populate its offsets and nothing else. Test also without Registration (i.e. temporarily remove the FSUIPC4.KEY file from the Modules folder) as that ensures it is doing even less.. The only relevant log file is FSUIPC4.LOG and you need do nothing at all to obtain it. It is always produced, in the Modules folder. Close FSX down first, then paste it into a message here. I doubt it will tell me much, but that's the only thing I can check. Anything better will be a process of elimnination at your end. Regards Pete

FSUIPC itself cannot possibly have anything directly to do with this. It sounds very much like you may have some SimConnect problem. And without further information (log file and version number of FSUIPC) i can't support you in any case. The currently supported version of FSUIPC for FSX is 4.88 by the way. Maybe you are out of date? Provide proper information, and use the current version, and i can look, but i cannot work miracles. You don't even say if you are using a registered install or not -- it makes a lot of difference because unregistered FSUIPC4 is doing virtually nothing but responding to application requests, should you actually have any FSUIPC applications. Oh, please close FSX down before retrieving the run-time log file. Regards Pete

It's been uploaded to YouTube now, for those who find it more convenient: Pete