Pete Dowson

Please also see the other thread on this subject, rightr next to this one. It appears that a bug in one of the Win10 updates may be responsible for Installer problems. See my last post there. Pete

Which "era" is that? I am 74. Are you of an earlier generation? All I need is data to look at. Files mostly. Yes, thank you. This error: Exception code: 0xc0000409 is, according to this web page http://winwiki.org/exception-code-0xc0000409/ caused by Windows system file corruption. It appears to be something to do with the Locale setting (CRT) in Win10. I just found this report: This was a bug in the TH1 build (10.0.10240) of the Universal CRT. The bug was fixed in the Windows 10 November Update (TH2) build (10.0.10586). So please check that your Windows is properly updated and that you are on build 10.0.10586 or later. Pete

No, it looks fine, and it shows that a brand new DLL.XML file was created in C:\Users\nico\AppData\Roaming\Lockheed Martin\Prepar3D v4\ Please find the DLL.XML file and attach it or show it (not a screenshot though, please). Pete

A screenshot is no use at all, especially in an editor which doesn't understand that type of file! Please just attach the file itself! Also I will need to see the Installer log file. NOT a screenshot! Pete

What file? What is your question? Pete

Oh dear. I told you exactly what parameter to change!! Look, I'll repeat part of it, with the important bits for you in RED: If you set the [JoystickCalibration] INI parameter UseAxisControlsForNRZ to "Yes", then the NRZ (no reverse zone) option for all three axis types will use the AXIS_????n_SET controls (e.g. AXIS_THROTTLE1_SET) instead, with a range of -16363 (idle) to +1 6383 (Max). This will be Aircraft or Profile-specific if you set it in the appropriate calibration section of the INI file. In your INI file it's the 7th line in the section headed [JoystickCalibration]. All you needed to do, as it says, is change the two letters "No" into "Yes" on that one parameter! You may need to re-calibrate afterwards, and reset the Sync points. So, best delete the two Throttle lines at the end, and the SyncSlope line. so you get fresh numbers from scratch. Pete

Sorry, i don't understand what this means. Pete

Sorry, but a picture is of no use whatsoever. I *know* what they look like! Please find the DETAILS of what it thinks went wrong! Use the Windows Event Viewer! Crash data is needed! Pete

Well, assuming that the aircraft responded properly to the forward thrust range of 0 to 16384, obviously your -16200 to +16200 "resolution" is still being spread over the whole range of 16384 units. So not less, more if anything. However, in any case i think you'll find that the true resolution of the axis is well below the 15 bits used for 0-16383. Most throttle units hve 8 or 10 bit chips, giving a true resolution of either 256 or 1024 different values. Possibly. It is a pity you didn't show me your INI file as I requested, as I could advise more accurately. But here is an excerpt from the FSUIPC Advanced User guide (on one of the first few pages in fact). this may help: UseAxisControlsForNRZ=No: This is a facility for the [JoystickCalibration] section(s) of the INI file, not [General]. It is a special option provided to try to cope with some different add-on practices (notably, in this case, the Wilco A320). Normally, the 4-Throttles, 4-mixtures and 4-Prop pitch calibrations result in an output with either a range which includes the reverse zone, or, if the "no reverse zone" option is checked, a range from 0 (idle) to 16383 (max). These are sent to FS using the older "????n_SET" controls (THROTTLE1_SET, etc), since these are the ones providing the reverse zone below zero. If you set the [JoystickCalibration] INI parameter UseAxisControlsForNRZ to "Yes", then the NRZ (no reverse zone) option for all three axis types will use the AXIS_????n_SET controls (e.g. AXIS_THROTTLE1_SET) instead, with a range of -16363 (idle) to +1 6383 (Max). This will be Aircraft or Profile-specific if you set it in the appropriate calibration section of the INI file. Pete

What aircraft is this with? I could really do with seeing your FSUIPC INI file, where the settings are saved. Proper calibration should give you either 0 to 16383, or -16384 to +16383 (depending on what is needed by the particular add-on aircraft and thus on the options you have selected in FSUIPC). Normal "direct calibration' gets you 0 to 16383, because the values are written directly into the simulators engine values using Sim Vars as follows KEY_THROTTLE_SET THROTTLE_SET Set throttles exactly (0- 16383) Shared Cockpit KEY_AXIS_THROTTLE_SET AXIS_THROTTLE_SET Set throttles (0- 16383) Shared Cockpit (Pilot only, transmitted to Co-pilot if in a helicopter, not-transmitted otherwise). KEY_THROTTLE1_SET THROTTLE1_SET Set throttle 1 exactly (0 to 16383) Shared Cockpit KEY_THROTTLE2_SET THROTTLE2_SET Set throttle 2 exactly (0 to 16383) Shared Cockpit KEY_THROTTLE3_SET THROTTLE3_SET Set throttle 3 exactly (0 to 16383) Shared Cockpit KEY_THROTTLE4_SET THROTTLE4_SET Set throttle 4 exactly (0 to 16383) Shared Cockpit That is an extract from the P3D SimConnect SDK. Note the range for the values, 0 to 16383. Your 16200 values are just the limits provided by your input levers. Full thrust is +16383, not 16200. Just using 'sync' shouldn't affect the range from min to max. If it is doing that I shall have to investigate as it would be an error. Please confirm that without sync you get what you want for the range. Pete

The AppData\Roaming\Lockheed Martin\Prepar3D v4 folder IS the correct directory! I think you maybe a bit confused? (Easy to get confused with L-M's new rather over complex add-on control system). The ProgramData DLL.XML file is where higher priority loads are enabled. FSUIPC5 should be the last loaded except for the Active Sky DLL, it is best in the AppData\Roaming version. Pete

There's no way to download 5.121b, it was replaced by 5.122. Where do you see 5.121b? Just on the Schiratti website? I'll have to remind Enrico, whose site it is, to update the description there. But the link there ALWAYS points to the latest full install version. Interim updates, when available, are posted to the Download Links subforum here. Pete Pete

What "supplement"? Just this? a note added there to say "but if you want to process all of the inputs piled up, loop using com.read, do not use com.readlast". Why not read it now? Pete

There must be a DLL.XML file. The FSUIPC installer log confirms it was written. I've no idea where you are seeing "Launch dll.xml False False FSUIPC 5 False" Is that a filename? So, FSUIPC5 is not being loaded. Which confirms either a bad DLL.XML file, or a corrupted SimConnect part of P3D4. So, FSUIPC5 is not being loaded. Which confirms either a bad DLL.XML file, or a corrupted SimConnect part of P3D4. Sorry, you installed it ands then ran P3D4, then got the message? What is displaying that message? If it's Windows then there will be more details, a crash report.Look for it in Windows' Event Viewer. Before it said "FSUIPC stopped working", now "installer stopped working"? ds like you have some really serious problems with your Windows installation. i need more details, the actual crash reports and the Logs. There's no way i can help with zero information. I see you managed to find a DLL.XML at last, but the copy you posted is badly corrupted, with 259 zeroes stuffed into it. I don't know how that can arise, apart from a disk problem, or maybe subsequent corruption. Best to delete it altogether to re-run the Installer. Or save the following as DLL.XML in the correct AppData folder. This is exactly what the FSUIPC Installer writes in any case: <?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>as_connect</Name> <Disabled>False</Disabled> <Path>as_srv\as_connect_64.dll</Path> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>P:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL</Path> </Launch.Addon> </SimBase.Document> Your most recent message: What's "Attached". If not in AddOns then as I said, either your DLL.XML is bad so FSUIPC isn't being loaded, OR there's another problem and I'd need to see the FSUIPC5.LOG, as I said. That's the P3D CFG file. I don't need to see that -- there's nothing relevant to any of this in the P3D settings. I need to see the FSUIPC5.LOG, as I have said several times. Pete

Ah, so the Mode switch IS set to send button presses. I didn't realise that. Good to know - thanks! Pete

Not 'lost'. Zero throttle = idle. Negative throttle is reverse thrust. You have 'No reverse zone' set so you get the whole of the IN range, -16200 to +16200 for forward thrust, 0 (idle) to 16383 (full thrust). Pete

Well, part of it. What exactly is this supposed to be: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Launch dll.xml False False FSUIPC 5 False ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ??? I really need to see the actual DLL.XML file, the one here: "C:\Users\Roger\AppData\Roaming\Lockheed Martin\Prepar3D v4\" Also, please see if there is an FSUIPC5.LOG file in the Modules folder. i.e. in "P:\Lockheed Martin\Prepar3D v4\Modules\" If there is a Log, I need to see that, because the Installer log shows things are okay. If there is no log then FSUIPC is not being loaded, so it's a DLL.XML problem. if there is a log then something else is wrong and the log will help. Pete

PLEASE POST SUPPORT QUESTIONS TO THE SUPPORT FORUM! I've moved it for you, but you are lucky I saw it! The SubForums are for contributions and reference material. Support is carried out in the SUPPORT forum, which is here! Just assign that button to the same thing you'd assign to on the keyboard or any other button (Throttle Decr), or just the keypress F2 which is the same thing by default. You'd probably want it to repeat whilst held on, too And maybe throttle cut when released to stop reverse, but that's up to your method of use. Pete

3 Dots? No! Three types of assignment, the things you call "dots" are little circles which you click (they are just the standard type of Windows mutually exclusive alternative check boxes). Click one to select the type of assignment you want. I'm looking a page 32 (in the FSUIPC5 User Guide) and there are no "dots". The check boxes gain a "dot" inside them when you click one! It's a standard Windows type of selection mechanism! If you mean the circles aren't appearing either, then I think there's something wrong with your Windows installation, or maybe the video driver. FSUIPC doesn't have any control at all over the display of those, the whole dialogue system is pre-defined in a standard Windows format and displayed through Windows interfaces. Try a different (later or earlier) video driver, or maybe a repair of Windows. Pete

I don't think you've bothered to look at the user guide at all! :-( Just select the method you want to use for assignment then you can select which of that type of assignment you want, up to 4 simultaneously. Not sure what you think you ought to see "ticked". Please PLEASE user the documents provided! Pete

There's a REV checkbox in the calibration. You need to check that before ANY attempt to calibrate. I don't think the Mode switch is seen by FSUIPC. I think it is used by Saitek's own software. You may be able to use it with a Lua plug-in program, but it isn't easy. Pete

Previous version of what? FSUIPC? The difference between 5.121 and 5.121b is negligible except in the two small option areas it addressed, and a problem with one of those was fixed in 5.121c. Are you using P3D version 4.1? If not, please update. then download FSUIPC 5.122. Pete

I was just about to make this change, for inclusion in the now-released version 5.122 package, when I noticed that the value after the "BRAKES_BrakePressNeedle" is a 1 BYTE at 65EE. So the offsets were 1 out already in any case if BrakePressNeedle is a 2-byte WORD. Making it a 4-byte INT will move everything 3 bytes, not 2! So, I think something else is wrong. There are no other values, described as integers or otherwise, which are 4 BYTE INTs, so I reckon either BrakePressNeedle is only 1 byte and there's another 2 byte discrepancy somewhere. After all, the values it can take are only 0-100. OR ... ... it gets more complicated! I've just found another arithmetic error! 65FB is only a one byte value, yet the next value is 4 bytes further on, at 65FF. So, if 65ED is a 4 byter, as you think, but I've only allowed 1 byte, the offsets thereafter are 3 further on, not 2, except from 65FF, where they are correct again! I've assumed the latter is the case for now, and attach and amended PDF for you or your contacts to check again, please. (Sorry about the mess). Pete Offset Mapping for PMDG 747QOTSII.pdf

You can't have 2 "RunIf1" lines. Number them 2, 3, 4 etc, so RunIf2=READY,CLOSE,c:\P3D 4\FS-FlightControl\FS-FlightControl.exe But because you have a space in the pathname you should enclose it is quotes, thus: RunIf2=READY,CLOSE,"c:\P3D 4\FS-FlightControl\FS-FlightControl.exe" The CLOSE option you already have should do it. It does for me with AS P3D4. You'd probably want to have the option in AS to turn off the "are you sure" prompt. CLOSE should work with most programs, but some are obstinate and need KILL instead. Please entitle your threads here with something more descriptive. If I'm here I look at all outstanding ones, but most folks who could help would decide that based on your subject title. "Need a little help" is really not enough. Pete

With PMDG's 737 there are "custom controls" for everything. It doesn't use normal FS controls. These are documented in the file ending in ".h" in the SDK folder, in the aircraft folder. The controls are listed towards the end. You have to calculate the custom control number then assign it to <custom control> in FSUIPC. There are no mouse macros in FSUIPC5. For LINDA you need LINDA support. I cannot really help with that. For PMDG aircraft you can also check the PMDG support forum and the User Contributions subforum above. Pete