Pete Dowson

The files in question, of course. Pete

Yes, but on the Prop Pitch levers, not the Thrust levers. No. The "prop pitch decr" would operate on all engine props simultaneously. When you use the engine-specific controls they operate specifically on the stated engine's prop. Pete

FSUIPC knows nothing about hardware at all. It only knows about what Windows lists as Joystick type devices in its DirectInput facilities (part of DirectX), and those with up to 32 buttons, two POV Hats, and a maximum of 8 axes (6 normal ones and 2 sliders). I've no idea what a "zero delay USB encoder" is, and nor has FSUIPC, and there's no such thing defined in the DirectInput interface used for Joysticks (by both FS and FSUIPC, incidentally). If a button or axis is recognised by FS, and it therefore isn't outside the list I just mentioned, then FSUIPC should certainly see it just as FS does. Pete

THat shouldn't happen. Many folks, myself included often have several other programs running okay alongside FSX -- with FSX in Windowed mode, of course. Windows gives key and mouse priority always to the process with current focus. In that setup, FSX will be relegated to a lower priority and run slower, of course. If this isn't working maybe your PC isn't up to it. Try minimising FS, or even just pausing it. FSUIPC is PART of FS, it is merely a module running inside FS, not a separate program! Pete

You don't want FSX.EXE for Prepar3D at all! The exe is Prepar3D.exe, and, yes, for 2.4 it should be 2.4.11570.0. If you've changed things and re-run the FSUIPC installer, you'll need to show me the Install log again. I can't see your computer from here and can't determine what the problem is without a log. These migration tools are a pain, because they try to make things look like something they are not. Therefore installers which know what they are doing cannot do the right thing. A proper migration tool would only make the changes temporarily, whilst you install the things that need it, then revert the installation back to its proper form. Pete

you appear to have a version of the Microsoft FSX.EXE renamed as Prepar3D,EXE in your P3D folder. Please right click on the Prepar3D.exe file and check Properties, check the version number and copyright details. FSUIPC4 has actually installed for P2Dv2, but if the EXE actually being run is NOT P3D then things will go wrong, of course. That's why you get the warning. In a normal P3Dv2 install there will only be one EXE, and that is the Prepar3D,exe and it has a version number like 2.4.11570.0, certainly not 10.0.61637.0, which is certainly FSX, not P3D. Pete

Oh, on the Schiratti site you mean? All my packages are available here, too, in the Download Links subforum. Pete

The prop pitch reversing should be on the prop pitch levers, of course, not the thrust levers. The controls are similar -- Prop pitch decr for all engines, or Prop pitchN decr for Engine N. Pete

I've released FSUIPC 4.938c which works with FSX, P3D and FSX-SE. The change from version 4.938b is only that it works with both the original, December 2014, release of FSX-SE, and also the update in January 2015. The update is available here, in the Download Links subforum, and also on the main Schiratti "Dowson" page even though the latter descriptive text may be out of date. [LATER] The current version is now 4.938d, with some additional facilities and corrections. In partucular the wind smoothing option is now fully enabled. Pete

In addition to the logs in Steam\Logs, please include Windows\Logs\CBS\CBS.log Pete

In addition to the logs in Steam\Logs, please include Windows\Logs\CBS\CBS.log Pete

See the (obscurely named?) Installing and Registering FSUIPC4 document actually included in the ZIP file which you downloaded, the one also containing the FSUIPC Installer! There are even pictures provided to help you! Pete

Yes, of course. See the Offsets list document installed into your FSUIPC Documents folder, and included in the FSUIPC SDK which you must surely have downloaded if you are interfacing to FSUIPC! Pete

Sorry, there's not enough information here. You don't even say what version of FSUIPC you are talking about. And your title talks about FSX-SE yet your text refers to FSX. Please find the Installer log in the Modules folder and paste its contents into a message here. The reason the log is made is so that such install problems can be readily diagnosed! Pete

Isn't there any documentation for the device, or stuff on their website, which tells you what it does? As I remember there's no Reverser button in FS but I think we used F2 to accomplish it. Well, yes, F2 as assigned by default in FS -- that's just "Throttle Decr". You'd be better off assigning to the control rather that to a keystroke which may be assigned to a control. And there are Throttle1 decr, Throttle2 decr etc controls too, for separate engines. That looks okay. Pete

If there's no axis inputs into Windows for that area, then you can't assign any action for it. Maybe, like the Saitek throttles, it just pushes a button? Pete

Could you find the log (or logs) in your Steam/Logs folder, zip them up and send them to me (petedowson@btconnect.com), so I can send them to DoveTail? They don't know why this problem is happening. Thanks Pete

Could you find the log (or logs) in your Steam\Logs folder, zip them up and send them to me (petedowson@btconnect.com), so I can send them to DoveTail? They don't know why this problem is happening. Thanks Pete

Yes, it most certainly should do -- but if you've created the file whilst FS is running you'd need to press the "reload" button on the relevant assignments tab. Otherwise the list isn't regenerated. It will appear as "A:Blub" in alphabetic ordering in the normal FS controls assignments, in all lists -- Buttons & Switches, Key Presses, and Axis Assignment. I've just done exactly that with your macro. Where are you looking? Pete

This is the second post showing EXACTLY the same problems with the FSX-SE installer. 1. It is not adding the installation details to the Registry, and 2. It is not installing SimConnect. The first is overcome by you giving the path manually (but not all add-on installers will allow that), but the lack of SimConnect is disastrous for many add-ons, FSUIPC included. Since it looks like these failures in the FSX-SE installer to get SimConnect installed is not an isolated issue I shall report this problem directly to DoveTail today. Meanwhile, please see the following suggestions (copied from another thread on this very subject): Pete

Ah, I know what is going on. The "... SET" commands are all treated as axis inputs, although FSUIPC (not FS) allows you to assign them to anything. FSX and FSUIPC alike only take note of CHANGES in axes. The INC/DEC controls you assign to buttons are different, obviously. The change is not whether the axis is different to what the current value is but whether the axis has been moved. If you want a button to zero trim and you aren't using a trim axis for trimming, then you'd need to send two values, one non-zero and then one zero. You can do that on a button by assigning one to "press" and the other to "release", or editing the INI file and entering more than one assignment. It might be better to have a two line macro instead, then you can assign to button or key easily. Pete

Sounds like you have two different things interacting. First, make sure you are testing with a default aircraft, and that you have nothing also happening in FS. Try using FSUIPC's event logging to see exactly what controls and parameters are being sent. Pete

You definitely need to get SimConnect installed. Most add-ons depend on it. You'll need to ask Steam / DoveTail on the FSX-SE forum on Steam I think. Pete

I would think that unlikely. Are they marked read only? Check in Properties. Pete

Something is wrong, then. It should be quite happy with the 62607 version -- it sounds like it is not finding any version of SimConnect. Did you install FSX-SE free-standing, or is it side-by-side with FSX? Ah! That will be the problem. SimConnect evidently is not installing correctly. Take a look in your Windows\WinSxS folder, search there for SimConnect. If you only have FSX-SE installed, no FSX, it should find one SimConnect.dll entry, with the number 62607 somewhere in the folder name. You could try running its SimConnect installer separately. It's the SimConnect.msi file in your Steam\Steamapps\Common\FSX\SDK\Core Utilities Kit\Simconnect SDK\lib folder. Whilst near there you might also want to install the three legacy Simconnect modules, as you'll no doubt one day encounter other add-ons which are more specific in their needs than FSUIPC (FSUIPC works with any version it knows about, it just prefers the latest one). You'll find SimConnect.msi installers in the Steam\Steamapps\Common\FSX\SDK\Core Utilities Kit\Simconnect SDK\LegacyInterfaces folder. Please remember to report the failure of SimConnect to install to Steam / DoveTail on the FSX-SE forum in the Steam interface. [LATER] I see Wartortle beat me to it with good advice too! Pete