Pete Dowson

You can more easily send keypresses using one of the added FSUIPC controls: 1070 keypress and release 1071 key press and hold 1072 key release These are documented in the Advanced User's manual (page 24 or so) and can be sent via offset 3110/4/ Pete

If you have no Modules folder, where on Earth are those files? Certainly FSUIPC's installer only ever puts files into the Modules folder, which it will create for you. It doesn't care about files in other folders. Pete

Did you not see the text shown on the Garmin unit? "receives flight plan data ..."? It looks like the Aviation In mode you are using is there just to provide waypoint information,, exactly as I said originally: "I think the USB connection may only usable for transferring waypoint type information." You need to refer to Garmin documentation I think. Maybe what you want to do is not possible with that unit. BTW why do you select AV400? Is there something in the Garmin manual which states this can be received? Pete

By "fuel levers" do you mean the idle/cutoff start levers? Or the fuel pump switches. If the former, then aren't they controlled by the MixtureN lean and MixcxtureN rich controls 9N=engine number), as in most aircraft? Have you tried? Otherwise, you should know that PMDG implement their own controls. Have you looked in the 737NGX SDK? There's a list of "custom controls" at the end of the PMDG.h file. Pete

Are you using Profile files (ie "UseProfiles=Files"), with the profiles being in the separate Profiles folder? If so, I think I've found it. The "Based On" facility looks messed up when the profile details are separated because it is still only looking through the main INI file. I've also found a long-standing bug in Profiles, and that is that, although the "Based On" facility is supposed to reproduce the settings from Axes, Buttons, Calibrations and Keys, no matter in which Tab in which you used "Based on", it only does this IF the category you are currently within already has entries for the "based on" aircraft. In other words, if you did this without any Based On axis assignments, then it wouldn't copy over the Buttons, Keys and Calibrations either. :-( I'm working on this now, but it isn't a trivial fix so it might take a couple of days or so. Please confirm what Profiles mode you are using. If NOT "UseProfiles=Files" then I don't know what the problem is because it doesn't occur here. I'll need to see your FSUIPC4.INI file. Pete

But do you KNOW the device wants AV400 at 4800? The AV400 check box is not "on top". What about the unique port name? You still don't mention that at all. Unless you are sending it to a different PC using WideFS, you MUST tell it which port to use. As I said, it cannot guess! If you don't tell it where to send the data , it cannot send any! Pete

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