Pete Dowson

I've moved your post from one of the reference subforums to the main support forum so it can be answered. I think each press changes is from "released to pressed" or "pressed to released", like a latching switch. If so you will simply need to program it in FSUIPC to do the same action on both press and released. Pete

Okay, but you said you'd "upgraded to P3D 4.4", so I assumed you already had a WideFS 7 license from your P3D3 or FSX days. If so the same details would havew been applicable. Pete

FSUIPC5 is for P3D4. Version 4.4 of P3D4 is still P3D4, so FSUIPC5 is still correct. There won't be an FSUIPC6 till P3D5 at least. FSUIPC5 has version numbers, just like P3d4. The current version of FSUIPC5 is 5.15, and that was released simultaneously with P3D4. If you refer to the Announcements subforum here you can see the list of currently supported versions. Pete

I've no idea how ProSim reads the weather if it doesn't have access to an addon weather programs current METAR files. Have you got it set to "SimConnect" mod, or "MSFS" mode (I'm reciting these from memory, but the latter makes it use FSUIPC, as Version 1 did). Whichever you are using, try the other. Really, I think only Humberto miguel will be able to sort this for you. What needs a subscription? Certainly not ASN/AS16/ASP4. (it's ASP4 for P3D4 by the way) I've always used ActiveSky, right from its beginnings and through all versions. Excellent for decent weather simulation. The default stuff is very poor comparatively. Pete

Ah, good! Thanks for letting me know. Pete

Since it really isn't an issue for most folks' systems I think it is some interaction with something else you have also installed. The way i'd try to disabling all othe add-ons, checking FSUIPC, then adding them back one at a time, checking the Shift+E+2 actions every time. THEN it would be worth doing the logging and enabling also the SimConnect logging, because whatever interaction is going on, it will be in there. Pete

Well, with that set off, FSUIPC really doesn't interfere with any of the controls needing a numeric value. Are you only getting the hift E results, nothing from 2, 3 or 4? Do you have other addons which may be sending lots of controls automatically (use FSUIPC Event logging (not axis) to check. That plug key logging should show what is happening with your key presses. With control assignments instead I think you can give the numeric value as a parameter. you could try that? Do you also get the problem with other keys taking a 1, 2, 3 or 4 selection, like Engine selection (just E then the numeric), and pushback (Shift P followed by 1 or 2 for direction). Because all these work fine for me, on two separate systems. Pete

Where does WideClient say that? I think you need to show me the logs, please -- WideServer and Wideclient logs. If you do that you must also state the Protocol to be used, i.e. Protocol=TCP (or UDP). This is normally part of the information it gets from the Broadcasts from the Server, which apparently aren't working through you change in router. Pete

Glad you solved it! Good flying! Pete

Could you explain a little more, please? Confirm that you entered your WideFS registration correctly. And what "Lua" are you talking about? You need to state version numbers please. "Latest" often turns out to mean "the latest I've noticed" and has sometimes been nearly a year old! How do you work that out? WideFS needs to be registered with your WideFS registration details. Pete

This could be significant: You need to edit the INI file before starting P3D, because when you close P3D it will update the file. Editing the value in the Miscellaneous tab should prevent setting 0, or changing it from 0 if set that way, because switching the option off or on has to be done during initialisation. I'll see what I can do about that. I may just remove the option from the Tab altogether. When added it wasn't envisaged that there'd ever be a need to turn it off (and there shouldn't be really). Pete

More likely to be an udate to Windows. FSUIPC 5.15 is no different in joystick treatment to most previous releases since 4.0. Do check, though, that when installing PED4.4 the disabling of controllers there didn't get unset. Also check that the wheel is recognised in Windows games controllers and responds there. If you want me to check anything in FSUIPC I'd need to see the FSUIPC5 Joyscan.csv, the FSUIPC5.INI, and the FSUIPC5.LOG. Pete

Where is your Prepar3D version 4 installed? If you have installed it AND run it at least once then FSUIPC5 will install with no problems. But it seems you either have not even installed it, or it is not installed correctly. You will have to do it again. Also version 5.14 of FSUIPC is out of date. The currently supported version is 5.15. Pete

The FS controls, and FSUIPC ones too, are almost all only applicable to default aircraft and those which abide by the andard system. PMDG and some other addon aircraft makers implement their own aircraft subsystems which are completely separate from those inbuilt to the simulator itself. To operate those with button or keypress you have to find the right control number then assign it via ,custom Control> in FSUIPC. The PMDG 737NGX controls are all listed in the text file of type .h available in the SDK subfolder of your PMDG installation. The list is near the end. You have to work out the control nmber by adding two numbers together. Pete P.S. Please see the thread in the FAQ subforum (which you should have looked through first). It's the one entitled How to program joystick buttons and keys to control PMDG aircraft

No. Is it still in the documentation somewhere? If so, sorry, I shall remove it. Pete

Not if the L:Var was a different one, no. How could it? Pete

Just install. No need to re-enter registration either (choose 'Not now'). It will simply replace the DLL and update the FSUIPC Documents folder. All the settings are retained. This applies to all FSUIPC5 updates (as it did for fSUIPC4 and FSUIPC3). Pete

No, not via the macro file. You can have multiple actions with one L:Var, but because the L:Var name is the name you assign to in FSUIPC's assignments. However, you can assign one to the "Press" and the other to the "Release" (which is okay if you don't want them to repeat). Or you can edit the [Keys] assignment section in the FSUIPC INI file to add more assignments to the same key. That's a little trickier. You certainly need to refer to the Advanced User's manual for more details. You can assign the L:Vars, as already repeated many times, and you can use INC or DEC if you wish, as also stated several times. As I told you a long time ago, you have to experiment to see what works! I can't do any more. You need to start helping yourself! Quite honestly, having all these keys assigned on a keyboard seems much harder to use than simply using the mouse. I could understand if you were using buttons in a cockpit.

Wow! That was a long time ago -- before FSX was released, that was my last visit there: the AVSIM conference and Microsoft tech meetings, when I discussed SimConnect with Dave Denhart. Since then, no, not Seattle. Only a three week holiday in Colorado, concentrating on heritage railways ... and beer! That was in 2017. Pete

I thought you alread stated how -- INC and DEC. What was the problem? As you said: And I said "very probably". i can't be definitive -- you have the aircraft, it is up to you to try it! The parameter for what? There isn't one for INC or DEC. Pete

Your idea "monitor the rate of presses and increase the size of increment or decrement accordingly" can work. An example of doing that sort of thing is provided in the Lua plug-in "tripleuse.lua" in your FSUIPC documents folder, though that's just for a single button of course. GoFlight implement two speed operation in the rotaries in their RP48 units, which FSUIPC supports of course. I also have implemented similar actions in drivers I've made for PFC avionics stacks, and earlier for FlightLink and the GA28R cockpit unit built by Aerosoft Australia. You should note that it is a lot more complicated than sending controls more rapidly, That simply transfers the lag to the queue in Windows and the Sim, for those controls to be obeyed, and if this depends on the Gauge graphics update rate you can see why that could be slow. Instead you have to read and retain the current value in the code, and add to that, only sending the updated value back to the sim when there's a slight pause in the changes. The timing of that has to be adjusted to match the Sim's update speed. You wouldn't get constant continuous feedback on screen unless the frame rate is good, and even then the on-screen gauge can be jerky. It works best when you have a local hardware gauge being updated, the one in the sim not mattering until the adjustment is done or the pause is long enough. Generally, though, for the more simple demands assigning one direction to INC and the other to DEC controls works fine, and it is just the same as for those using the usual two buttons unstead of rotaries. The fact that it's a rotary instead doesn't really make it different unless the number of clicks per roration is really pretty low. I suppose that depends on the make or quality of rotary encoder. Pete

Well, I use PFC throttles (and yoke and pedals and centre console and MIP0 in my 737NG cockpit and never have any such problems. if you only had difficulties with that one aircraft then I thnk it points to the aircraft implementation, but if it's with all aircraft you should really have sought PFC support for a hardware problem. One other point, though. I always had problems when I tried to use Serial to USB adapters. For years now i've been using PCI (or PCI-E) add-in Serial Ports, such as those made by BrainBoxes. Never any trouble with those. Pete

Very probably. But it could be that folks would use a joystick axis or one of the trim wheel controllers you can get. then they'd use 'Set' but leave off the value so that it is provided by the axis value. It is pointless asking me about your particular aircraft, which I don't have, uses in these L:Vars. I did tell you how to find out how they behave. with the "Toggle" action I assume you've already used the Log LVars lua plug-isee how those you've used above behave and have seen that they are either 0 or 1? Pete

There's no such facility as "Toogle". I think you meant "Toggle"? Please do always check your spelling against the documentation. Pete

Really? They are just standard axes but fed directly to FSX rather than as joystick inputs.. Where are you doing your assignment and calibration? With some aircraft you apparently need to select a user quadrant in the PFC driver, and to your calibration in FSUIPC, but this is most rare. So what's changed? Pete