Pete Dowson

You are using a very old version of FSUIPC (4.853) which has not been supported for a very long time. Please update. The earliest supported version for FSX is 4.947c. If you still have a problem I not only need to see the Windows crash details, but also the FSUIPC4.LOG file from the Modules folder. Pete

The FSUIPC calibration lets you set the "idle" zone anywhere you like. Did you follow the numbered steps to good calibration in the Joystick Calibration section of the FSUIPC User Guide? Assuming you are wanting a reverse zone on the thtottles (which is rarely done on the Saiteks as they have a reverse detente with a button instead) then there are 4 points, minimum (=full reverse), maximum (full thrust), and the two points delineating the central idle zone. Those points are specific to each lever and you set them where you like. That is the point of calibration. Most Saitek throttle users set the NRZ (no reverse zone) option on the Calibration tab, and then the minimum IS the idle. But to make sure you can always set idle you should set that position slightly away from the backstop or detente (as outlined in the numbered steps I mentioned). You set the Reverse by assigning Throttle1 or 2 Decrement controls, repeating, to the button behind the detente. BTW, PMDG advise against using FSUIPC for the 737NGX and 777X aircraft, because they read the throttle inputs in a way which can conflict with FSUIPC calibration. You CAN assign them in FSUIPC, but to the FS controls "Axis throttle ..." controls, and don't calibrate. It's then up to PMDG to sort out where the positions are. Pete

Thomas, to repeat, is there any possibility of me seeing the Log from the "worked flawlessly" run, please? I need to check through that what it is doing is what I think it should be doing. That was the point of you volunteering to test it for me! When I'm confident it is doing all the right things I can make a formal release. Thanks. Pete

I didn't for one minute think it would. The point of using my current version was only to make sure that any crash information was useful against the code as it is now, so I could pinpoint where it was occurring. I cannot explain the lack of Windows crash logs. That makes no sense. But if there are truly no logs at all in the Modules folder then either you've deleted them or FSUIPC4 has never run at all, ever, in that installation. There should at least be an Install log, because the Installer puts one there. The basic files you'd see in any FSUIPC4 installation, after it has run are: FSUIPC4.DLL the module itself FSUIPC4.INI, the settings, either default or your own from the FSUIPC4 Options FSUIPC4.LOG, the log file always created by FSUIPC4 when it runs FSUIPC4 INSTALL.LOG, the complete record of the Installation run FSUIPC4 Documents, a subfolder containing the documentation and other assorted goodies. Additionally, if you registered FSUIPC4 there would be FSUIPC4.KEY If none of these are there then you are looking in the wrong place. If there is no FSUIPC4.INI and FSUIPC4.LOG then FSUIPC4 has never been run. Both files will be updated or created every time FSUIPC runs. In particular, the LOG file will be newly written at the very start of each FSX session, so the date and time on it will be the last time FSUIPC4 actually ran. If there is no log, then SimConnect has never actually managed to load FSUIPC, so there is no way FSUIPC can cause FSX to crash. It will be a serious problem with the FSX installation itself. You might find out more, then, by gettng a SimConnect log file, as explained in the FAQ subforum. One thought -- are you perhaps looking at an Explorer where Windows is hiding the filenames from you, merely describing INI files as "configuration settings" and LOG files as "text files"? If so you should turn off the Folder Options setting which tells Windows to hide filetypes from you, as instructed in the FSUIPC User Guide Pete

You didn't first update to 4.947d as I requested? Does it create a log in the FS Modules folder? If not, then FSUIPC isn't actually being loaded, which indicates a SimConnect problem. If there is a Log created, I need to see it, please, as it will tell me at what stage the problem occurs. To find the crash details you need to use the Windows event viewer. To open that just enter Event Viewer in the edit box after pressing the Windows Start button, and press return. You'll find application crash details in "Windows Logs - Application". Just scroll down the list looking for the red Error (!) line with FSX as the source. You can view the details below, and copy them into a message here. The log from your original "initial crash", the one you showed above, would have been useful if it was for the current version of FSUIPC. With that in mind it would now be better for you to get my current interim update. Use this link please and copy the FSUIPC4.DLL into the FS Modules folder. FSUIPC4947j.zip Pete

Did you have the logging still enabled? If so can I see the log please? And, yes, your friend can test. But is his problem the same? Seems an unlikely coincidence if so. Pete

Ok. No rush anyway, I'm about to have my dinner Back a bit later to see how you got on! Pete

Once you have Joystick IDs assigned which aren't somehow duplicated, as they were, it will be fine. Uninstalling the keyboard from device manager is just to get the registry mess sorted a bit, otherwise you'll always have those three non-joysticks listed. But, sorry, to test the revised FSUIPC which I'm just building now, we'll have to revert to when it didn't work (ie. undo tthe fix made with JoyIDs) then run the updated FSUIPC. Hopefully, FSUIPC will then fix it, instead of having to use JoyIDs. That's my aim, anyhow. I'll have it ready in a few minutes... ... here: FSUIPC4947i_TEST.zip Pete

BTW, it might be a good idea to use Joy Letters in your INI file, e.g P for pedals, Y for yoke. Or just let FSUIPC assign automatically. There's a section about this in the User Guide. I would mean you could go ahead with assignments safe in the knowledge that if the IDs do get changed, the assignments will still be associated, via Name and GUID. Here's your INI changed ready. If you save that it will work no matter what IDs we finish up with. Pete [General] Debug=Please LogExtras=x200000 UpdatedByVersion=4947h History=BN4VZQLKKTYA8RA5H82NH InitDelayDevicesToo=No NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No DeleteVehiclesForAES=Yes AutoScanDevices=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No 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=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=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=No OOMcheck=Yes OOMcheckInterval=10 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=1 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No AssignJoystickIDs=Yes FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.0.3.0 SimConnectUsed=3.0.0.0 [JoyNames] AutoAssignLetters=No 3=Saitek Pro Flight Rudder Pedals 3.GUID={1D58BA90-7763-11E5-8006-444553540000} 4=Saitek Pro Flight Yoke 4.GUID={BFA06680-7A2F-11E5-8001-444553540000} P=Saitek Pro Flight Rudder Pedals P.GUID={1D58BA90-7763-11E5-8006-444553540000} Y=Saitek Pro Flight Yoke Y.GUID={BFA06680-7A2F-11E5-8001-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 0=PX,256,D,7,0,0,0 1=PY,256,D,8,0,0,0 2=PR,256,D,3,0,0,0 3=YX,256,D,1,0,0,0 4=YY,256,D,2,0,0,0 5=YZ,256,D,4,0,0,0 [buttons] PollInterval=25 ButtonRepeat=20,10 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No [GPSout2] GPSoutEnabled=No [WideServer] WideFSenabled=Yes [sounds] Path=J:\P3D\Sound\ Device1=Primary Sound Driver Device2=Speakers / Headphones (IDT High Definition Audio CODEC) Device3=Digital Output (S/PDIF) (IDT High Definition Audio CODEC) Device4=Speakers (3- Raptor HS40) [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 Aileron=-16380,0,0,16380/8 SlopeAileron=6 Elevator=-16380,0,0,16380/8 SlopeElevator=6 Rudder=-16380,0,0,16380/8 Throttle=-16380,16380/8 LeftBrake=-16380,16380/24 RightBrake=-16380,16380/24

Think i've devised a way to fix the original problem in FSUIPC instead of using JoyIDs. Would you mind testing it for me first, because it is very difficult to test without actually having the problem in the first place? If that would be okay I'd need you you undo what you did with JoyIDs -- i.e move the deices back to where they were, i.e Pedals #1, Yoke #2. The run the next update of FSUIPC (which I'm preparing now), and see if that works. Again I'd need the Log and INI. If it does work, well and good. If it doesn't you can always use JoyIDs again. Pete

The INI of course still shows those three wireless keyboard entries. All we've done is added the two real joystick devices. To tidy up you probably ought to unistall the HP Wireless Keyboard Kit from the Windows Device Manager, then re-boot so it adds it back correctly (i'd hope correctly). 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8003-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D581E50-7763-11E5-8002-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D5670A0-7763-11E5-8001-444553540000} 3=Saitek Pro Flight Rudder Pedals 3.GUID={1D58BA90-7763-11E5-8006-444553540000} 4=Saitek Pro Flight Yoke 4.GUID={BFA06680-7A2F-11E5-8001-444553540000} I'm looking at the log now to see whether I could fix this sort of thing automatically. Pete

Hang on. I need to see the results, please. As before. Id like to be able to program my way out of this sort of Registry mess. Pete

Right. What is happening is that of the many entries for that "HP wireless Keyboard Kit", three are currtently recorded in your Registry as having joystick IDs 0, 1 and 2. This is a problem because the Saitek devices also have IDs 0 and 1. The normal Windows joystick interface is returning the first ones it finds, the three HP Wireless Keyboard Kit entries, and so FSUIPC doesn't get the correct devices at all. The extra scan for information, the one showing the Saitek devices, shows this -- the same as the HidScanner does (its mostly the same code). So, two ways to proceed. Just one step at a time ... First, try using JoyIDs to change the joystick IDs for your two devices. Change them to 4 and 5 please (to avoid the 1,2,3 which are falsely taken by the keyboard kit). To do that just click on the name of the device and drag it to the new position. You'll get a popup asking to confirm. Please then try FS, and show me the Logs and INI again. Pete

Okay. That is good. After I check the logs I may ask you to use JoyIDs to change those settings -- i.e. move the two joysticks to new IDs, like 3 and 4 instead of 1 and 2. But let me see the log and INI first, please. Pete

No difference in the Logs? Have you compared the logs? There is MORE logging in the last Test version, that is what I need! That was the point. the correction I included was a correction to what was being logged! There was no way it was going to "fix" things. I'm still trying to work out what is wrong! So, I need to see the Logs and INI again, after using the last FSUIPC update, and I need to know what JoyIDs shows. Pete

You evidently misunderstood. Nothing changes just by running JoyID. It is a tool for you to change things. But not yet. First I need to know what it displayed! Pete

I found how to enable and move the Avatar. But L-M is not using any normal assignable controls for this.It is scanning the joystick (when enabled) itself and using the axis inputs directly. There seem to be no facilities for any other way of controlling it, not even in SimConnect, so I've really got no way of adding support for it through FSUIPC. It's early days for P3Dv3 though. Maybe this will change. Pete

How exactly are the axes assigned in FSUIPC? i.e what mode and control selections? What events are triggered by W, A, S, D? I thought the A and S keys were assigned by default to view selection. You should be able to determine the events used by enabling event logging in FSUIPC. You could also run P3D in Windowed mode (temporarily) and enable the FSUIPC Console Log so you can see the events logged in real time. It would also be useful to know what events are used for the AVATAR when you have the joystick enabled in P3D. I might find time to try the Avatar control this weekend. How is is selected and enabled? Pete

Thank you. Sorry for the delay -- I was later getting back than I had hoped! The information in the logs/INI files is very useful, but I'm afraid it still doesn't tell me what is going wrong in your Registry. I did see one error I made, but correcting it wouldn't fix this entirely. At least I don't think so. However, I've also added some more logging. Could you download this version and try it in exactly the same way as the last test, please -- same INI entries as before and show me the same files. Download link: FSUIPC4947h_TEST.zip Then, could you also please run that JoyIDs program for me and tell me what that shows? If it is what I think it is, you MAY be able to fix it with JoyIDs, but if not I think it will need doing some uninstalling to clear the rubbish from the registry. By "uninstalling" I don't mean any real programs, just telling Windows' Device Manager to remove entries. But we'll need to discuss that after the tests above. Please also see if you can get similar logs/INI's from your friend with the same problem. I must get to the bottom of this. Pete

I woke up eary this morning thinking about this problem! :sad: So I got to work adding more logging. I could do with seeing the INI, LOG and HidScanner results from his system too, then, please. It is puzzling me. The more clues I can get the better at present. But first, please download and copy into the Modules folder this test version; FSUIPC4947g_TEST.zip Before running FS, edit the FSUIPC4.INI file, adding these two lines to the [General] section: Debug=Please LogExtras=x200000 Then load FS. Don't let it run very long. Then show me the LOG and INI fies please. If your friend could do the same it would be useful too, thanks. Also please don't forget to run the JoyIDs program, see what that shows and see if you can fix the Joystick IDs there. Remember that JoyIDs numbers them 1-16 whereas FSUIPC uses the Windows internal IDs which are 0-15. Otherwise they correspond. Thanks. I'm off now. I may be back early enough this evening to take another look today. Pete

No idea why P3Dv3 is doing that. It isn't FSUIPC. I keep meaning to report it to L-M on their forum, but they have too many far more important things to do at present. Pete

It's quite common for the loading process to stick at 6% for some time. I think it gets longer the more scenery layers you have and the more complex they are. No, IPC reads are FSUIPC offsets being read by an FSUIPC client application, and that service isn't available whilst FS is loading. "IPC" stands for "Inter Process Communincation" and is part of the FSUIPC name. Mine takes about that long -- from an SSD on an overclocked PC. I have about 500 scenery layers in my list. I've not sized it all in gigs though. Pete

The current version is 4.947c. Where did you get 4.946? No, sorry. It's nothing at all to do with FSUIPC though unless you have some other add-on trying to use FSUIPC at that time. An unregistered FSUIPC does nothing except act as an interface for other programs. Pete

Please always state the actual version number. Folks have come here saying "latest" and been using a year old version! You have not. Please don't try. Just paste log files into your message. You can use the <> button above the edit area to enclose them neatly. I'll try to help when I have more information. What exactly do you see in the Add-Ons menu? Is there an FSUIPC entry? Is that the one you press and "nothing happens"? What other entries are there? Pete

Thanks. That's very useful. It's going to take me a bit of figuring out though. Your registry for HID type devices appears to be in a real mess. You have 6 entries for that HP Wireless Keyboard kit, including one as a keyboard, one as a mouse, and one as a joystick. Plus three others of completely indeterminate use. There are also corrupt entries for what it says are: a Saitek Mouse, a Saitek Keyboard and Saitek Hotkeys. The only good looking ones appear to be a Corsair Raptor HS40, whatever that is, and your Saitek pedals and yoke. However, that said, FSUIPC should have got just three devices -- the HP Wireless keyboard in its odd joystick guise -- this entry: Device at "\\?\hid#vid_0461&pid_4e25&mi_01&col02#8&b8180dc&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=0461, Product=4E25 (Version 1.50) Manufacturer= Hewlett Packard Product= HP Wireless Keyboard Kit Serial Number= HP Wireless Keyboard Kit Usage Page: 1 though this entry also shows that it is a useless joystick as it has no axes or buttons. Plus the Saitek pedals and yoke, which do actually have good entries. The puzzle I have to resolve is how FSUIPC did manage correctly to derive the three devices, but got them all labelled as HP Wireless Keyboard kits: 0=HP Wireless Keyboard Kit 0.GUID={1D581E50-7763-11E5-8002-444553540000} 1=HP Wireless Keyboard Kit 1.GUID={1D5670A0-7763-11E5-8001-444553540000} 2=HP Wireless Keyboard Kit 2.GUID={1D581E50-7763-11E5-8003-444553540000} This is even odder when you consider that the Log identified them all correctly: 187 Product= HP Wireless Keyboard Kit 187 Manufacturer= Hewlett Packard 187 Vendor=0461, Product=4E25 (Version 1.50) 187 Serial Number= Hewlett Packard 187 Product= Saitek Pro Flight Rudder Pedals 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0763 (Version 1.1) 187 Serial Number= Saitek 187 Using existing joystick id: 0 187 Product= Saitek Pro Flight Yoke 187 Manufacturer= Saitek 187 Vendor=06A3, Product=0BAC (Version 3.4) 187 Serial Number= Saitek 187 Using existing joystick id: 1 I'm afraid I'm out all day tomorrow (Friday), but I'll be seriously investigating this over the weekend. I hope that, should I add more logging to find out what is going on you'll be able to do more tests for me and show me more logs? I am very anxious to get this fixed as it might affect others too. Otherwise I'd be advising you to get your system tidied up by uninstalling as many of those devices, in the Device Manager (only) as possible, and re-booting. in order ot get the Registry tidied up a bit. But I'd rather you didn't do that yet so you can help me resolve the problems. Thanks, Pete