Pete Dowson

I'd wait for FSUIPC 4.931 if I were you. Seems you are on P3D version 2.2.0.10438. Version 4.93 is for the main release, 10437. I've only just found the "hotfix" 10437 -- it isn't easy to find even when I was told in another thread that it exists! I'm complaining about this to L-M. I've got hours more work to do now rechecking all the hooks. :-( Pete

Since Monday when I downloaded mine? Oh dear. Back to hacking again. It takes hours each time even if they've not changed much -- I still have to verify each hook by disassembling code and coparing locations etc. Pete

I notice you have a later release of P3D 2.2 that I: Mine is build 10437. Strange. I downloaded mine on moday! If they've updated it aghain I may have a lot more work to do....:-( Pete

Others have now provided the event viewer data I need, so I'm working on it. Odd that you can't find it -- there should ALWAYS be an event logged on any App crash. Pete

I think I've fixed it. I'll upload 4.931 soon. But one thing puzzles me. My Prepar3D 2.2 is build 10437, yours (and others I've seen) are 10438. I don't understand that. Has there been a later update to 2.2 since Monday? Pete

Ah, thanks! That's the info I need! Working on it now. Oddly it runs perfectly here, 100% Pete

i'm writing to 0x07f4 the logging option shows a good write of 1 but no N1 hold Not sure if this is a known issue or not it seems strange to me i have all other autopilot functions working well. All it will be doing is sending your request on to FS. Whether it does anything or not probably dependsupon the aircraft in use. Are you setting 07FA too (the RPM value to be held)? Can you please state the version number of FSUIPC you are using? This FSX option wasn't added till 4.281. Pete

I need more information please. It runs great here, so I can't help in a vacuum. I need to know what the Windows event viewer says about the crash, and also whether there's an FSUIPC4.LOG file produced. If there is please sohw me that too. Pete

What happens? Have you any crash data, eg, from the Windows event viewer? Is an FSUIPC4.LOG file produced in the Modules folder? Is so please show it to me. I notice some oddities on your system but not ones which would affect this: You appear to have removed FSX without properly uninstalling it. Not only that but its install path is pointing to Prepar3D!!! You should really remove the remnants now in the Registry. i.e. the section HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Further, you have installation entries for both Prepar3D v1 and v2 both pointing to the same place! You do really need to do complete uninstalls if you are going to keep installing in one folder. You should remove this section too: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D However, despite all these oddities your P3D should start okay. I really need more data on that. Pete

There appears to be two separate set of installation files for your P3D installation, one listed as Prepar3D and the other as Prepar3D V2, as shown in the Install log: It looks like you installed V2 in the same place as your old V1 either without properly deleting the former or, maybe, their uninstaller doesn't do a decent job? You really need to go into the registry and remove the whole section named HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D The error being reported is for that invalid installation, for V1, and NOT for v2 which was found and updated correctly. It finds the version 2 CFG in the correct place. It can't find the version 1 CFG of course. Look: It isn't that easy. The DLL.XML needs to tell Simconnect to load the module. Pete

Please explain what you mean by "has not worked". The install log shows no problems. So where are you seeing one? It is installing into the Install location of your FSX, look: and: showing installation in in the default place FSX gets into if you dn't select another. The "Andrew" user is where your FSX.CFG and other files, including the vital DLL.XML are residing, thus: and, as you can see, according to Windows, "Andrew" is the current user at the time of installation also. And it is where the FSX files are found. The only odd thing is that you were previous using the FSUIPC4 loader, but now you've removed it. Did you find you needed it before? Pete

You pick between Cessna and Boeing by loading the appropriate aircraft, not by clicking on the profile checkbox! It will be greyed out because once an aircraft is assigned to that profile, it cannot be unassigned (except by editing the INI file, as I said). Yes, of course. You load an unassigned aircraft then select a profile for it, or make a new one. You can even make a new one based on an existing one. Please do peruse the user guide where it is all explained, with pictures to help! No! Joystick calibration does NOT need any assignments whatsoever in FSUIPC. It only needs joysticks assigned somewhere, whether in FSUIPC or in FS. The calibration isn't on the axes directly, it is on the actual FS axis controls just before they are obeyed by FS. Pete

I don't see how FRAPS has anything to do with FSUIPC. It's probably just a matter of timing with assorted FSX threads, some of which will be FSUIPC's. On another system a different module would probably be blamed. Pete

Can you be more specific, please? I assume you mean the calibrations section? Is it responding you your axis movements? Is the checkbox already checked? If so, you have already set a profile for the current aircraft. Button and Key assignments have both specific and non-specific assignments, simultaneously, so the checkbox is used to look at each or change each. But axis assignments and joystick calibrations are only profile-specific or generic. Once you have assigned an aircraft the only way to un-assign it is to remove its name from the [Profile.<profilename>] section in the INI file. If you think there is really a problem which is not now explained, please paste a copy of your INI file in a reply so I can see what you've set. Pete

Ah, by "decimal ADF" you mean frequencies with a .5 fractional part. (In normal English usage, the frequency is all decimal whether or not there's a fractional part). I'm afraid there are aircraft intended for the American market which are fitted with such an ADF (.5 frequencies are not used in North America). You cannot tune to the 0.5 part specifically, but in real life such a close setting as 392.0 will also receive the signal. However, there is a solution provided by a registered install of FSUIPC. It is called AutoTuneADF, and is described on page 9 in the FSUIPC Advanced User's document. You need to add the parameter "AutoTuneADF=Yes" to the [General] section of the FSUIPC4 INI file before running FS. Pete

I am very pleased it is resolved. Pete

Oh dear. It's going to get difficult. Can you check the FAQ subforum. read some of the threads which look likely. Some of these are contributions by others. Ang get a SimConnect log -- there's a FAQ on that too. Pete

So your kit isn't purchased recently, from them? I would have thought they would support it? Pete

Hmm. Very strange. There's no difference software-wise between the aileron (X) axis and elevator (Y) axis on a yoke. I am really at a loss as to why one is seen and the other not. What did PFC say? Pete

The list of controls should be in the FSUIPC Documents subfolder, in Modules, but if not check the Modules folder itself too. Pete

It isn't being loaded for some reason. I think the next step is to see if it's down to one of the other things being loaded. The easiest way to do this is as follows (I think I suggested this before, actually, but here goes: 1. First remove the FSUIPC4 Loader from the Modules folder, as I think this might give misleading results. 2. Rename the DLL.XML so you don't lose its contents. 3. Re-run the FSUIPC4 Installer yet again. 4. Run FSX and see if the FSUIPC4.LOG and INI files are there then. Pete

Sorry, that's a bit confusing. The yoke has two axes -- elevator and aileron. The aileron should certainly show in FSUIC if it shows in FS. So the elevator can be seen moving in the PFC test program, but not in Windows "game controllers" control panel item, and not in FSUIPC or FSX? I really don't know then -- it sounds like a Windows joystick driver or registry problem. What about the other PFC devices I see listed? 1=PFC USB Pedals 2 2=PFC Remote Instrument Console 3=PFC Avionics Adaptor They all appear to categorised by Windows as Joystick type devices. My driver handles the latter two, or used to on the Cirrus Pro I had. Maybe PFC have changed things -- it was years ago I was last involved in PFC equipment. You do really need PFC help I think. Pete

So, you resolved the PFCFSX.DLL driver issue and removed it as being unneeded? The Cirrus yoke is a normal joystick device and not handled by my software. The only axes my software have to deal with on the Cirrus are those on the Throttle Quadrant - those 6 assignedhere: [Axes] 0=17X,256,D,4,9,0,0 1=17Y,256,D,10,0,0,0 2=17Z,256,D,5,17,0,0 3=17R,256,D,18,0,0,0 4=17U,256,D,6,13,0,0 5=17V,256,D,14,0,0,0 So, I suspect you have a fault. Have you asked PFC about all this? It is really their job to support their hardware. I can only help with my drivers. Incidentally, the elevator appears to be the ONLY one you've actually calibrated in FSUIPC, or at least operated the "SET" button for it. You've not actually calibrated the numbers at all. You should really calibrate the throttle quadrant axes. Pete

Is that AFTER you've run FSX since installing FSUIPC4, or before? Unfortunately you have omitted the filetype part of each filename. Here is what I ASSUME those files are: FSUIPC Documents = subfolder containing the FSUIPC documentation and plug-ins FSWidgets = no idea, not related to FSUIPC FSUIPC4 Install.log I assume, the log you showed above FSUIPC4.DLL = the FSUIPC4 program FSUIPC4_loader = Optional loader, not normally needed *** GPS Module = no idea, no related to FSUIPC List of FSX controls.pdf = Document providing assignable controls list *** Why did you install the Loader? It is optional and generally not advised. I assume you read the Installation note about this? If you have run FSX before this list then FSUIPC4 is definitely not being loaded. If you had not run FSUIPC4, then please do so and see if there is now two extra files: FSUIPC4.LOG and FSUIPC4.INI We'll then have to decide what to do after that is clarified! Pete

Good news! Thanks for getting back. Hmm. There must be some odd interaction with other things accessing SimConnect. Very strange. But glad there was a work-around. Regards Pete