Pete Dowson

Ah, I see. I've never heard about that program, till now! Pete

Sorry, I don't know these devices. Does it accept AV400? Is the speed correct? Have you selected the correct serial device in the FSUIPC GPSout tab? It cannot choose it by itself you have to tell it the COM port or name. Pete

Not sure what you mean by "v4". FSUIPC 4.938c IS v4, there are no other current "v4's". Just use the 4.938c installer. The original version 4.000 has not existed or been supported for years! What sort of "entries"? All there is of FSUIPC is in the FS Modules folder, no where else at all. It does NOT spread itself about! The Modules folder contains the DLL plus your registration KEY, plue your settings (INI file) and any Macro and Lua files you might be using. There's also an FSUIPC Documents folder containing all the documentation and Lua examples. Pete

Thanks for getting back with the answer. It's a relief to know it isn't The Steam installer! Pete

I'm afraid I can't really support third party offsets. I've no record of any offsets at all being requested for Wilco aircraft, and 560E is within the range of offsets assigned to Project Magenta. What program is using those other than PM? Do the FS-related offsets seem to freeze? Is FSUIPC still connected to SimConnect, or frozen? Have you checked the FSUIPC log file to see if there are any errors? Try using something like FSInterrogate on more regular FSUIPC offsets, for FS items that should be changing. If they are still changing, then it must be Wilco's code, or whatever program it is that you are using to map Wilco data to Project Magenta FSUIPC offsets. Pete

Can you give me a very specific detailed example to follow please. There was a long-standing bug, fixed in version 4.937d back last October, and listed as item 19 in the Changes document, thus: 19. When creating a new profile in the Axis assignments tab, existing assignments are now kept for the Profile if this is requested. In error previously these were lost even if you did request they be carried over. Is your another one, related to this? I need to be able to reproduce it to fix it. Pete

Doesn't the PMDG.h file you mentioned list the controls to be used to send keys to its CDU? If PMDG provide no mechanism I don't know how it would be done. Emulate mouse and keyboard? Ugh. Messy. Programming in Lua is just programming as you are doing in C#, so I don't know why that's an alternative you would be interested in. And doing it with "just FSUIPC itself" doesn't make sense to me ... do you mean program one button to send loads of data to the CDU? It would be a mighty big macro -- maybe that's why Lua was suggested, if you wanted to keep it all in FSUIPC and not use your C# program. Pete

No. FSUIPC3 only supports 6 axes, as I said. That will never change, though you might be able to program around it using the Lua plug-in libraries. The restriction is simply due to the older version of the Windows interface used by FSUIPC. I re-wrote that for FSUIPC4, but I'm no longer developing FSUIPC3. After all it is for FS9 and before, now an 11 year old version! Pete

FSUIPC3 recognises 6 (SIX) axes -- XYZRUV. It doesn't recognise sliders (ST) or POVs (PQ) as axes. Those were added in FSUIPC4, which uses a more modern DirectX API. Incidentally, 3.7 is out of date. You should be on 3.999z8 or 3.999z9, the last and final version. Pete

Just use offsets 3114, 3110, as described in the Offsets list supplied in the FSUIPC Documents folder. You need the Event numbers, which are listed in the List of FSX Controls document, also supplied. Pete

Yes of course. Pete

Does it read the version number and check it? I don't know either Delphi or VB, but the sources of the interface are provided in the package, so you can debug the code yourself using a Debugger. (I assume those languages have debuggers?). You should also try using FSUIPC's ipc Read and Write logging, and of course FSInterrogate2, supplied in the ZIP, to check what is happening. Perhaps you'd better show me the FSUIPC.LOG file. You'll find it in the FS Modules folder. Close FS down first so that the Log is complete. You can use the <> button above this edit area to enclose the text when you copy and paste it into a message. There should be no need to do that. They just both need to be at the same privilege level. Pete

There's no certificate in use any more, not for a while! You are referring to a 2-year old problem. Just make sure you are using an up-to-date version of FSUIPC, not one which is over two years old! Pete

Assign the Hat as an Axis to "Pan view". That's the same control FS uses for the hat by default. The use of the hat as 4 or 8 different buttons is for other purposes, such as fixed view selection (which I prefer since I don't use a virtual cockpit). Pete

If you don't know, it doesn't really matter. It's always best if you keep up to date. Installing a new version only updates the program, fixing bugs and adding facilities. It won't change your settings and you don't need to re-register. If you ever need support I would always first check to see that you were up to date as I cannot support old versions. You don't need to re-register unless you reinstalled Windows or moved to another PC. You paid for FSUIPC4, not a specific release of FSUIPC4. You can apply all updates to it for no extra. Pete many thanks

You are just looking at the definition of the READ ONLY data which is mapped into FSUIPC offsets! The part you quote is mapped at offsets 65D5 to 65F0 -- surely you looked in the "Offset Mapping for PMDG 737NGX" document I supply? Else what did you try before? The only part of that header file relevant ot inputs TO the 737NGX is the list of control numbers which appears AFTER all of the data output definitions. Pete

The PMDG 737NGX data mapped into FSUIPC offsets is just that. Data supplied by an interface provided by the 737NGX, which initially gets read en bloc and dumped into fSUIPC memory space for reading (only) by applications. Updates are then notified via a SimConnect mechanism. It's a type of memory sharing system. PMDG have not provided any means to write to any of those data items. It's purely data provided for reading. The only concession there is to control, and maybe setting data, is the list of additional FS-type control numbers. You'll need to refer to the header (.h) file supplied in the 737NGX SDK for that. I no longer have any PMDG aircraft so I can't check, but I doubt that there will be controls to set fuel levels. BUT you never know, it would be worth checking. If you need to send controls through FSUIPC offsets you use offsets 3110 (control number) and 3114 (data), setting the data first. The only other way I know of setting fuel levels (and payload for that matter) is to edit the Aircraft.CFG file directly, in situ, then send the FS control to reload the aircraft. However, I'm rather doubtful even that would work properly with PMDG aircraft. Regards Pete

Okay, good. I'll be changing the code to accept with or without "", to prevent future confusion! I guessed that from the double dots! So, you'll need another AlsoManage line for those files. Pete

There have been lots of reports of Saitek throttles (also made by Mad Catz) operating with only half the range. It's usually caused by bad Registry entries, and i think the fix is documented somewhere on the Saitek support forum. Probably installing the regular Windows drivers fixed those entries, or put better new ones in. Pete

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