Pete Dowson

I find it very difficult to work out what your question really is from trying to view gigantic images which don't even fit on my screen in their entirely. Could you try to describe whatever problem you have in words, please? Pete

Check with a default aircraft. PMDG tend to do their own things for lots of stuff. FS itself has only one Landing Lights control -- on or off. There are no individual ones. Pete

Thanks for the files, now received. I've not got time to do a simulation today, but one thing has now occurred to me. Originally you had the path incorrect because of the double .. in the filename. Before we recognised this as a problem, It was suggested that you enclose the whole path in "", because of the spaces it contains. I now think that advice was wrong, and in fact the "" are not needed and in fact stop the AlsoManage working. So, could you please try it WITHOUT the ""? If this is it, I will change the program for the next release to allow "" to be there or not, so there's no confusion over this. At present some parameters need them some don't. Incidentally, there was also a file called "AutoSave Tue 001104..FLT" in the package you sent. Where did that come from? Prepar3D does not save FLT files, only fxml files. And this FLT file has that double dot .. error too. So I assume it must also be produced by your Majestic add-on? If so, shouldn't you manage those files too? Pete

Users don't need to purchase FSUIPC in order to run applications which interface to it. But publishers of software which makes money out of interfacing to FSUIPC are expected to come to an agreement with me for commercial rights to use it. Freeware is free, shareware and payware normally subject to a fee unless the amount being charged to users is trivial and only made to cover costs. There used to be a lock on application access, opened only by an application registration key which was obtained on from myself, with payment if appropriate. The administration of this got more tiresome than it was worth, as 99% of all software publishers proved reliably trustworthy and would volunteer appropriate payment in any case. So the checking was removed. If you are planning to release a payware program which needs FSUIPC to operate, you should write to me at petedowson@btconnect.com to agree a fee or royalty arrangement, or a waiver is deemed appropriate. Pete

I do all my development for FS on a system with 2 monitors, and have done so for a long time (though I'm about to change over to one of those beautiful 34" ultra-wide Dell curved screens, more space than my current two monitors!). Unless you have something very odd going on with the video driver that really should not be an issue either. And the affinity mask business shouldn't really matter in any case. When any application is in the background (i.e. not the process with the keyboard and mouse focus) then it has a lower priority in any case. Your IDE should run fine. And with a machine as powerful as yours you should be able to run several other processes at the same time with no problems. If the second monitor makes a difference, I'd first look into the video driver. Make sure it's up to date and that the multi-screen options are set correctly. Pete

No sure what SFX is -- typo for FSX? But in Windowed mode the resolution isn't relevant. Pete

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