Pete Dowson

The installation you hsave is already more up to date than the version you are now wanting to install. And you do have it installed. That is what the installer is checking. Pete

According to the post you have made, the only L:Vars active are the GSX ones. There are no FSDT ones. It isn't that it isn't changing, it simply doesn't exist in any currently active gauges or DLLs. FSUIPC merely gets the list using the functions provided by P3D/FSX. There's really no way it will miss any. But in the first instance, rather than use the Lua plug-in, you should use the built-in FSUIPC control to list all LVars. Currently, after moving to a new PC, GSX isn't working at all, with various problems starting with a complete failure of the Addon Manager to allow me to enter my serial number. I too am having exchanges with Umberto, but he is slow to respond so i don't know when i will see it fixed. 😞 Pete

Those controls appear to be from a macro file in your Modules folder called "Vasfmc.mcro". it isn't from me. Maybe it was supplied by the VASfmc folks, or you got it from somewhere else? Maybe you can figure out what the macros are doing and thence extend the entries to provide the additions you need? Pete

Why all the way back to 4.0? 4.4 is performing very well for most folks -- have you sought support on L-M's forum? Anyway, even if not for you, surely 4.3 would be a better choice? There's been so many improvements since 4.0. And 4.5 must surely be expected soon. How is P3D going to continue to get better is users retreat? At the minimum you should be on 4.1 surely? I might find one somewhere in my backups, but if you revert you don't get any support. There's no way old versions can be supported. I ask you to think again. Pete

I don't remember VASfmc. Can you remind me what special controls FSUIPC has for this program? Have you checked with VASfmc support about this? BTW I'm not sure why you thought you needed to add a screen image. It doesn't actually show or expalin anything. Pete

Er ... assigning reverse on one PMDG 737NGX gives you problems, but mot doing so on the other makes that okay, yet then undoing that assignment makes no difference? If I'm understanding you correctly, it is therefore definitiely that particular PMDG 737 which is at fault and needs reinstalling! Otherwise, I'm afraid since you've not actually explained what you did to start with nor what the "it" is which didn't solve anything, it isn't possible for me to help. Uninstalling is simply deleting and re-installing is simply putting it back, so what difference could that make? If you have made a mess of your settings, as in making assignments which don't work with thjose aircraft (which is all it sounds like to me), then if you can't unassign those assignments for some reason, you can of course simply delete the INI file and start afresh with no assignments at all. Pete

If you mean configured in FSUIPC, then do you mean you assigned to FSUIPC's Reverser controls, or calibrated your normal throttles with a reverse zone? Just assigning an axis can't really do anything there and then, of course. you do actually have to move the axis to get it to do anything. Is the problem only occurring when actually engaging reverse (or have the throttle parked in the Reverse zone). You really need to ask other PMDG aircraft users (the PMDG forum is best for that), but i don't think you can use "direct to calibration" throttle assignment at all for PMDG aircraft. the only way to assign reversers I think is by using the F2 keypress. This problem is definitely a PMDG implementation difference, not anything FSUIPC can do. You have to find alternative methods of control for such aircraft. Pete

MOVED OUT OF THE "FAQ" REFERENCE SUBFORUM! Please always post support requests to the support forum, not to the reference subforums. FSUIPC doesn't interfere with the mouse, though I do seem to recall an old bug in the PMDG aircraft. Have you made sure they are fully updated? And are you implying that before "configuring the thrustmaster t joystick" this didn't occur? And also that it is okay with other aircraft? I don't understand what this part is intended to mean. Sorry. Pete

There is no "wideserver.INI". Why do you ask? Wideserver is incorporated into FSUIPC in FSUIPC4 (and FSUIPC5), and there would be nothing in it you needed to change in any case. No, they do not request data more than once. The requests are lodged in the server and FSUIPC sends out updates whenever changes occur. PFD, ND and ILC instruments are displays for such information. Even if they were making requests the actual amount of data being passed each way is negligible compared with the capacity of any Ethernet link these days. Or maybe you are using wirelass? If so I'd strongly advise getting them wired instead. One rarely has continuous success with wireless links. It isn't the amount of data, it's the intermittent nature with small packets. I have a Network 9wired of course) of 8 computers supporting my 737NG cockpit. It has served me well with FS9, FSX and these days with P3D, with many years using Project Magenta and, yes, Thomas's modules. These days the same network is used with ProSim737. If you aren't trying to use wireless links then you have something else wrong. Have you not tried with the ServerIPAddr specified instead of the ServerName, as I suggested? Pete

But an unregistered install of FSUIPC doesn't have anything to do with controls, nothing at all! It only serves as an interface for other programs -- so, if it is doing anything at all it is because you have another program asking it to! I think you need to find out what other add-on you have running which is responsible in order to solve this. Start with none but FSUIPC, then add them, one by one. BTW the aircraft you list as tried are all sophisticated add-ons. always test initially with a default aircraft. And check that you haven't disabled controllers in P3D. Pete

The "FSUIPC Lua library" is a collection of ADDED functions relating to its job of interfacing to the simulator. All the standard Lua libraries are also incorporated. Those functions are obviusly not re-documented in the supplied FSUIPC documents because they are better explained in the original texts and freely accessible directly on the Lua website, to which a reference is shown prominently. Look in the Lua Examples ZIP file in your FSUIPC Documents subfolder. Proably the one which springs to mind most obviously is the "record to CSV" example, which both reads offsets and writes to a file. Reading files and writing to offsets is just as easy. Pete

MOVED FROM "FAQ" SUBFORUM TO SUPPORT FORUM, the proper place for SUPPORT! It is little to do with FSUIPC. All the facility does is call the SimConnect facilty to save a flight. It is, in fact, exactly the same as using the menu to do so, or using the Ctrl+; shortcut 9I think that's the one). Any "stuftter" this may cause is directly realted to one or both of two things: 1. The use of sohisticated add-on aircraft such as PMDG ones which also then freeze the sim whilst they collect the data from their assorted subsystems so that they can save that too. 2. A slow or nearly full disk, or one in need of de-fragmenting, plus a lack of sufficient free memory for a decent cache. Both of these applies no matter how you save a flight. There's no way FSUIPC can avoid either. The actual code in FSUIPC is pretty much merely the call to SimConnect. The subject is virtually flogged to death, especially on the AVSIM forums. Go take a look. Pete

I don't kow about that, but it seems a bit odd. Maybe it goes dormant? Is it connected to a proper power supply? Ah, that would explian it! Pete

So, the problem is in the assignment of the buttons to an FSUIPC Offset control? You need to show me what you've done there -- perhaps describe it and show me the FSUIPC INI file? Log button/key presses too in FSUIPC and show me the log after you press buttons. Pete

No, you cannot change a defined offset length. The value documented is the value supplied by the simulator. How will changing the length affect that? The TAT value is degrees Celsius x 256, and, in the two bytes provided, that gives a range of -128.0000 C to +127.9961 C. Why do you need a larger range? Surely that range is easily sufficient? I've no idea what you are talking about regarding "4 needle movements". Sorry. By the way, you posted your question in a reference subforum. Please ALAYS post support questions here, the Support Forum. Else it will not get attention. I've moved it for you. Pete

That's the same for all axis controls, not just trim. I expect the controls you are using to adjust the trims are INC/DEC controls, so the axis input doesn't change -- both FSUIPC and P3D only note changes in axis values. Yes, tha's the usual way around it, whether by two assignments to the press, a macro, or one on the "press" and the other on the "release". Pete

There may well be L:Vars for what you want. I don't know. Did you check? You can list all the L:Vars using an assignable FSUIPC control or monitor them with one of the Lua examples provided. Pete

In what way? Ouch! You are still using one of the first versions of FSUIPC5 and P3D 4.0. Why have you never updated? Sorry. The currently supported version of FSUIPC is 5.15 or later, and you need to be on P3D4.1 or later -- current is 4.4. LVars are totally unrelated. Why confusing? Pete

Okay. Thanks for the quick test. Pete

Could you check the values iwith this one, please. I think I covered all angles. MakeRwys4871.zip Then I'll release it. Pete

Checked. Yes, you are correct. I merely fixed the MagVar entries. The follow through isn't so easy -- I should have had those in True as per spurce dayta. I'll see what I can do. Pete

Ah, are those in Magnetic? They are in True in the sources of course. I'll check ... Does that affect all files, do you know? Pete

Are any of the offsets fulfilled? Did you enable them in the PMDG SDK as described at the beginning of the offsets document( the "PLEASE READ THIS FIRST" section)? BTW there are also parameters in the FSUIPC INI file to switch the action on and off, but they default to "Auto". Check for "PMDG737offsets". you can set it to "Yes", "Auto" or "No". The Auto mode depends on detecting the PMDG aircraft by its original name. I cannot really support PMDG aircraft. I don't even have any installed. The offsets are mapped directly from the data supplied by the code in the PMDG software, so if they don't work even when enabled you may want to ask in their forums. Pete

So what are the "small corrections" for. surely for takeoff you apply max power, or pretty much so. What are you "correcting" for? I don't have access there, and the title talks about "landing". Surely the corrections are to rudder or tiller, not to throttle, which would be at idle on touchdown, or close to. Or do you mean asymmetric thrust? It is quite normal on real aircraft for the same thrust on each engine to requre slightly different positions of the throttle levers -- they are rarely in perfect alignment. But if you wish you can either make one throttle control both, using an FSUIPC hotkey, or sync positions in the calibration tab using the sync option. Pete

Offsets are hexadecimal numbers (hence the 'B' in 64B2). You needs to express it as 0x64B2, or convert it to decimal (= 25778). Pete