Pete Dowson

Sorry, the last part confuses me. When you write fuel and payloads directly, is the balance changed accordingly? i.e. the CofG %MAC value?

Latest version? Unfortunately that's often meaningless. It does actually have a version number. Is it 4.938c? You do actually need to describe what you mean by "despite several installations". Why several? Have you entered your registration details at all? Did you read the instructions? All the details of what happens when you install FSUIPC4 are saved in the FSUIPC4 Install log. I would need to see that. But only if you are using the current version, 4.938c. Pete

Are you REALLY wanting to use such an old and unsupported version of P3D? You do know the current version is 2.4 don't you? Are you also using a very old version of FSUIPC4? The currently supported version is 4.938c. In order to diagnose installation problems I need to see your FSUIPC4 Install log, either from the P3D modules folder, or if it isn't being saved, from a copy you save using the File .. Save menu entry on the log screen. Paste the log into a message here. Pete

Just log the L:Vars (local panel variables) to see if you can find one you can use. You can list them using the add-on FSUIPC contorl provided, or you can use the supplied Lua plug-in for logging them live as they change, on screen. Pete

Both of those are set when the SimConnect variable "PARTIAL PANEL TRANSPONDER" is true (non-zero). The "partial panel" Simconnect variables sometimes only indicate when the DISPLAY is disabled or covered -- eg for training purposes. I'm not sure if that also includes actual unit failures, though the description in the SimConnect documentation does mention 'fail', thus: PARTIAL PANEL TRANSPONDER Gauge fail flag (0 = ok, 1 = fail, 2 = blank) You'll see in the Offsets Status list that most of those failure flags have question marks against the Read/Write columns. That means that they've not (yet) been verified as working. You can log the actual value read for that variable by simply adding either offset to the Monitor table in the FSUIPC Logging Tab -- select Normal log in the options below after entering the offset and data type (U8). Maybe this is a specific problem only in P3D? I don't know if it was the same in FSX. Nevertheless it might be worth reporting this problem to Lockheed Martin, on their support forum. Unfortunately there's no other SimConnect variable that would help. Pete

Yes, and that's why I abondoned that method. Yes, a LIB file. Rather than building it into FSUIPC I built my own SimConnect DLL with the lib built in. "Hacky" or not, it is easy enough to just find the relevant folder names (which do include the build number) in WinSxS. And this method works even when the SxS system is in a mess (I never managed to unravel some of the possible Registry messes folks get into, especially in Win Vista/7/8. It was easier in XP. Pete

Not sure what "is because of ..."? FSUIPC has to be modified each time there's a new release because the position of the places it hooks, inside FS code, changes. The SimConnect version is trivial by comparison. Surely most SimConnect apps aim at a particular version of SimConnect. like the SP1 or SP2 build. I'm still using some apps which only work with the original, 60905, version. This isn't a problem as long as the end user knows he needs to run the relevant SimConnect.msi. They are still all included with the FSX-SE install, in the SDK folder's "LegacyInterface". In facyt a third party installer could rely on that and run the relevant installer ready. FSUIPC can use any version of SimConnect it knows about. For P3D I had to build my own SimConnect DLL ("SimConnectP3Dv2.dll") and install it in the Modules folder with FSUIPC, as Lockheed-Martin decided not to install any SimConnect DLLs at all and just expect developers to build the library into their code. If you have a dedicated P3D-only program that works fine, of course, but I wanted the one build of FSUIPC to work with all. I don't use Manifests, or the automatic side-by-side mechanism. I just determine what versions are installed (by looking in the WinSxS folder), and choose the one I want to interface to -- normally the latest one which is compatible with the version of FS I find I'm running with. I link dynamically to all of the SimConnect functions, not statically. Pete

Well, nothing of mine EVER puts anything anywhere but the FS Modules folder. I don't know where you got those files, but they are nothing whatsoever to do with anything of mine! Look further for what? What on Earth are you looking for? Pete

What's the "rg" version? There are only two versions -- FSUIPC3 for FS9 and before, and FSUIPC4 for FSX and later. If FSUIPC doesn't see them then they are not part of the basic 32 buttons and 8 axes which FS supports. Are they seen by FS? FSUIPC uses the same system as FS to read the settings. Don't edit the INI, use the in-program dialogues and assign in the buttons drop-down. The controls you mention are listed by name, i.e. "Rudder left" and "rudder right" respectively, and will appear as such in the list. Pete

Sorry but I have no idea what is wrong with Win8. Pete

I thought there was already a program linking FS to Google Earth? Does Google Earth accept NMEA sentences via a serial port? If so then, yes, GPSout may work with it. Pete

You'd need to write a program which referred to a database of airports and worked out how far away you are from your chosen one. Pete

That doesn't help at all. That INI shows you using FSUIPC version 4,934. Please update. The current version is 4.938c. Pete

I don't have the PMDG aircraft or else I maybe could help. I can only suggest you ask in the PMDG support forum. It is there SDK and their set of custom controls. It may well be simply that you need to have the proper parameter value. Maybe there's one parameter for "press" and another for "release". I know many of their commands are more based on mousae operations than keyboard, so maybe the mouse-type parameters are needed, the "click" and "unclick" flags. Pete

There have been many solutions found, usually via local panel variables (L:Vars) or "mouse macros". I believe the latter method was quite successful on the PMDG 737 and the only way before they published their SDK. Browse through the User Contributions subforum here and see what folks have managed. Also I think generally most cockpit builders who might be so serious they'd set up extra monitors for displays they are not looking at would more likely opt for one of the more fexible cockpit packages such as ProSim737, Sim-Avionics, or Project Magenta (and there are others), which actually emulate the full systems much more accurately and allow use of a much more VAS and frame-rate friendly cockpit-less aircraft. Quite honestly, graphics and screens is not a subject I'm at all familiar with, and even if I had time I wouldn't know where to start. If you yourself are not a programmer I think you need to find someone who is and who is willing to take this up. Regards Pete

Do you mean using the GPSout facility in FSUIPC? If so, you can route it through WidefS on a network, as shown in the documentation. At the client end you'd need to use a program to simulate two linked serial ports, one for the GPSout data going out from WideClient, and the other for the input to FliteMap. I have only ever used Flitemap. I've no idea about Flitedeck and Jeppview. I don't know that they even support NMEA input. And I haven't used Flitermap for many years-- it became too expensive. These days I use PFPX as my planner and Aivlasoft's EFB as my moving map. Much more FS friendly! ;-) Pete

Sorry, I have no idea why Saitek installations go wrong like this. Apart from the answer supplied in the first message in this thread, thanks to another user, I can only suggest you visit the Saitek support forum. Pete

Yes. Ctrl+Shift+F4 = Mixture Rich for all engines, and Ctrl+Shift+F1 = Mixture Lean for all engines. But you want separate levers, so use the controls I already told you about, the separate ones for each engine! Pete

These are custom controls. Just work out the numerical value assigned to each name (a simple addition) and send it via offset 3110. Pete

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