Pete Dowson

It might help if you actually mentioned the aircraft, then maybe others with the same one might be able to contribute. In fact it would be best mentioned in the title. There's actually no difference in what the "Tab" test keypress s doing compared with whatever key or button you assign does. Does the "TAB" test work both with and without the Window title? It may be that it needs a parameter value, too, as also discussed in the documentation. But I've never heard of a case where it works with the TAB test but not with any other key or button assigned. Nonetheless it might be worth experimenting. Very few add-on aircraft are these days written in such a way that the mouse macro facilitiy operates. It's a shame. When I first implemented it, for FS9, most did -- oddly enough, except for default FS aircraft. Microsoft didn't follow their own gauge making "rules" in the SDK. BTW please always post support questions to the Support Forum, not to one of the reference subforums. You are lucky I came across it. Pete

The Lua language is well documented on their website and in books. All FSUIPC adds are a set of libraries of functions to handle FS matters. There are lots of examples in your FSUIPC Documents folder as well on in the User Contributions subforum, and I think those are really the best way to learn. The Lua reference documentation for FSUIPC is also provided in your FSUIPC Documents folder. Pete

An easy solution would be for the calling program to provide you with an offset number which you could change to signal the event. Then, if in a loop, the plug-in could simply test the offset value from time to time, and/or use event.offset. If you need to feed back more information then I could instead allocate your DLL some offset memory space for fixed use. But I'm not sure if the DLL needs to be capable of multiple simultaneous use. Pete

That's exactly what the FAQ subforum if for. There's also the User Contributions subforum which is less for problem solving than additions made by users. Well, depending on how you want them displayed you could either simply use the FSUIPC Logging facilities. On the right-hand side of the Tab there's a "Monitor" section and there you can monitor up to 4 different offsets, to screen or title bar (or both) optionally. You'd need to find the correct offsets in the Offset List (one of your FSUIPC Documents). The other, more sophisticated way is to write a small Lua plug in to act on COM1 and COM2 offset changes (via event.offset) and format and display the results in any desired fashion for display using the ipc.display function. Pete

If you are assigning that axis to a surface control with a "middle" (centre), such as Aileron, Elevator or, Rudder, then you just define the zone around that area to be unused (all values set centre). Look at the calibration sections in the FSUIPC options screen. See values you can set for "Minimum", and "Maximum", and TWO Centre values. They delineate the area you want all to be centre. The numbered step-by-step guide in the User Guide does cover this quite clearly You must have missed a whole chapter, then? The process is the same. For any control which has a centre, there are 4 values to calibrate, not just the 2 you seem to have understood! You just set them in order, left to right. If your faulty axis is not being assigned to a control with a centre, you are stuck -- such control surfaces need a continuous change as you move the lever. I suggest you try to get the joystick repaired -- but try cleaning first. I always found electrical switch cleaner very effective on pots. Pete

Hmm, I don't think you can. You'd need to open a new account with the new email. That shouldn't be a problem. You could still log into the old account to get updated products and keys. I think the only way to talk to SimMarket admin is to raise a problem ticket on your account. Pete

Sorry, there are conflicting statements there. You seem to say in one paragraph that you program keystrokes in FSUIPC, but in another that you do this in KeyMapper. If you mean you use keymapper to send keys to FSUIPC and then program those to send FS controls, then I need to ask whether the keypresses from KeyMapper are seen in FS itself. Have you checked? For keypress programming FSUIPC can only interpret what it sees, and if what it sees is not recognised as an assigned keypress, it lets it through to FS. Try using the same keypresses on your keyboard. Maybe your "KeyMapper" is not Win10 compatible? You can of course also use FSUIPC's key/button logging to check into this further yourself. Pete

Well, I use Google Chrome all the time and it certainly is not so signalled here! Pete

There is only ONE MakeyRunways, irrespective of the FS version. It is not version dependent. Your link works perfectly well! Pete

If the virtual joystick entries are still recognised even after disusing "vJoy", then the DirectInput system in Windows still believes these are there. it seems you need to do more than not run the driver. Pete

You post seems to say two different things: First, if you have areas on your levers where the INput values do not change, then (obviously?) FSUIPC can't do anything with them. Second, if you really mean you want to eliminate parts of your joystick axis range, then you can easily do at both lower and upper ends, and of course in the centre (where there is a centre -- as in Aileron, Elevator and Rudder cases), by simply calibrating after moving the levers to the positions involved. Please do refer to the Calibration chapter in the User Guide, where you will find numbered steps to proper calibration. It it important NOT to mess with "slopes" till you have calibrated properly. Pete

The button/keypress throttle controls are all called "throttle_xxx" or "throttleN_xxx" where N is the throttle number, and "xxx" is Decr, Incr, Cut, or Full. The default assignments for the F1 - F4 keys are Throttle Cut, Decr, Incr and Full respectively. So F2 actually invokes Throttle Decr. There is no specific reverser control supported by any version of FS. F2 just decreases the throttle setting a tad, no matter where it is. FSUIPC not only supports all those controls, but also dedicated reverser axes in the axis assignment section. This is actually more support for reversers than offered by FS itself. If FS default keyboard shortcuts do something you want to program on a button, just enable Event logging in FSUIPC, use the keyboard short cut, and view the resulting event in the FSUIPC Log. It'll give you the correct name there. With FSX in windowed mode you can even use the FSUIPC console log option so you can see the results in real time, whilst you press the keys. Pete

Well, you have 4 X-55 devices listed -- two X55 throttles and two X55 sticks. Does any button on any of them cause the crash? You only have two buttons assigned on one of the Throttles, and you have axes assigned on that same throttle and on one of the sticks. Do you have controllers disabled altogether in P3D? You should do if you are assigning in FSUIPC. From what you say it seems to me as if it must be a problem of P3D, but just try an experiment first -- rename the FSUIPC4.KEY file in your P3D Modules folder. That will make FSUIPC temporarily unregistered so it won't even scan any joysticks, let alone respond to any buttons. See if P3D crashes then. Try enabling controllers in P3D, see if it then crashes. Apart from scanning for changes on any joysticks you have assignments for (only the 2 of them out of the 4), FSUIPC only takes action on assigned buttons, of which you only have the two. Also, I noted from the L-M forums that Saitek released new Win10 drivers for the X55 back in September. Have you checked that you are up to date? ftp://ftp.saitek.com/pub/software/beta/Windows10/ I think you might need to report the problem on the L-M forum. Pete

FSUIPC recognises up to 8 axes and 32 buttons per device. This is for normal easy user assignments. Using the user plug-in facilities,with Lua program scripts you could handle any number of either, using the COM/HID library built in, but that requires some programming in Lua. Pete

All of the FSUIPC applications interface is available whether the installation is registered or not, and that includes program access to all of the offsets. Pete

No need to SHOUT. Of course you can map views to buttons, but I assume you don't want them all on one button? I use a hat and assign its 8 directions to the 8 views, View Forward, View Forward Right, ... and so on. I do this in FSUIPC's button assignments NOT in the axis assignments which is where you'd assign it as a POV for panning. That's the FS mouse look. You don't need to use that. FSUIPC has the same facility, a check box in the Miscellaneous tab. Are you another who never reads documentation? The FSUIPC one also supports the centre mouse button, like EZCA and unlike FS. Pete

I can't be sure without checking the FSUIPC4.LOG file (which is a text file you will find in the P3D Modules folder), but this sounds like something is causing SimConnect to stall -- it is taking longer that 1 second to supply data which should actually be supplied on every frame. In that event FSUIPC decides something is wrong with the connection and does a full re-connection, which is probably what is causing the pauses. If you paste the contents of the log here, or at least part of it till the first stall (it will be obvious in the log), I'll check. Generally this could simply mean that you are overloading P3D and SimConnect cannot keep up. If this were the case, and the stall is merely occasional but then unrecoverable because the reconnection takes too long with other applications also running, then you could try increasing the "SimConnectStallTime" from the default of 1 (second). That's a parameter in the [General] section of the FSUIPC4.INI file. Try 10, and if that appears to fix it, reduce it till it just starts happening again, then increase it by 1. It isn't good having to do this, though, as it means anything dependent on FSUIPC data is getting irregular or infrequent service. Really you should seek to solve the underlying problem, that P3D's SimConnect simply isn't getting enough time, or is getting held up from time to time by excessive demands. Take a look also at your average frame rate. If that is quite high, put a lower limit on it so that P3D allows more time for other things. If it is rather low then it is a matter of reducing the load -- sliders down, less AI, simpler weather from ASN (and less frequent updates), and so on. Pete

Access hasn't needed registration for years now, so, no, I don't. I you are writing something with the intention of selling it for profit, then we need to come to an agreement over payment. But if it will be for your own personal use, is freeware, or you only want it to pay you the cost of developing it, then it is free to use. There's no one license for commercial application, it is decided individually. User registration provides user facilities, including the Lua plug-in option. The application interface is all an unregistered installation provides. Details are provided in the documentation. Pete

Sorry, you have come to the wrong place. None of the products you mention are supported here. This is my Support Forum for my software -- primarily FSUIPC and WideFS. I don't know FSBUILD at all. Pete

The "direct" method does exactly what it says. The axis value doesn't get to FS at all until after calibration, when it is effectively injected directly to control that aspect of FS. The FS control method is exactly the same as assigning to the same axis control in FS itself. The control is sent directly to FS for processing. If, and only if, you also calibrate that axis, then FSUIPC intercepts it afterwards and then calibrates as before. So, assignment to FS control and calibration are two independent actions. Calibration can be used no matter where you do the assignment. The direct method is more efficient and is generally the best way, being simpler and more directly effective. However, some add-on aircraft don't like this. The PMDG NGX and 777X, to take prime examples, also intercept the FS axis for some things, like throttles, and assigning direct in FSUIPC bypasses this. I think the more sophisticated Airbus models from Aerosoft are similarly adversely affected. So, you use direct where it works, and FS control otherwise. In fact the PMDG examples probably don't take kindly to FSUIPC calibration either, because they would then be trying to use two throttle values -- the original the model intercepts and the post calibration value from FSUIPC. This might not notice too much if the calibration is basically linear and the input values from the joystick already cover the entire range. Using different profiles for different aircraft allows you to choose whatever works best for each, without having to constantly change assignments etc. Pete

I'm afraid the way SimConnect operates that process can often do more harm than good. I've known cases where the only answer was to re-install Windows. Does the log show the SimConnect's installed? If the log is identical to the last one then they are not! FSUIPC does'n even need a fully correct install of SimConnect, unlike most other SimConnect add-ons. All it needs is to find the actual SimConnect.dll file. It connects by direct linking, not going through the very frail WinSxS system. So, check folders named like this in your Windows WinSxS folder (you will have to make sure you have Windows explorer to show all files including system ones): C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect .... without ".cat" or ".manifest" at the end. There should be one such folder for each installed version of SimConnect. As an example, my latest FSX-SE SimConnect is installed (as "simconnect.dll") here: C:\Windows\winsxs\x86_microsoft.flightsimulator.simconnect_1ed9da73c880e429_10.0.62615.0_none_69960aa860d87067 The parts in blue may be different on your system. FSUIPC ignores those in any case. The important part is the bit in red. That's the version number -- this example is for FSX-SE build 62615. Just the existence of a simconnect.dll in such a folder is enough for FSUIPC, but it might not be for any other programs you try to use. In the end unless you can get DTG support to help I think you may face a reinstall of Windows. I had to bite that bullet once after experimenting with uninstalling stuff in order to see how a user got into a similar mess. Pete

Yes: your SimConnect installation is corrupted: But you should have the Steam edition of SimConnect installed, or at very least the FSX SP2/ACC version: 281 NOTE: SimConnect Steam is supported, but it isn't installed. 313 NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed. 344 Trying to connect to SimConnect SP1 May07 ... I think your Steam edition has been improperly installed. Have you altered anything yourself, like trying to move it or uninstall and re-install it? You probably need to contact DTG support, or at least try running the check and repair options in the Steam (right click on it on the left of the main Steam window, select Properties -- Local Files -- Verify integrity of game cache). Also try repairing the Steam SimConnect. First go to Windows Control Panel and select Programs & Features. Find each SimConnect entry ("Microsoft Flight Simulator SimConnect Client ...") and select it and uninstall it. Then find the FSX folder inside Steam\SteamApps\Common, and install at least: FSX\SDK\Core Utilities Kit\SimConnect SDK\lib\SimConnect.msi and SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi Some applications may also want the FSX-SP1 version installing too. Pete

Yes, and the reason for the problem is clear: It seems you missed the pinned thread at the top of this Forum stating: P3D Version 3: FSUIPC menu entry not appearing You will see there exactly what action to take! Pete

The log you supplied is the Installer log file, NOT the FSUIPC run-time log file. I need to see the FSUIPC4.LOG as originally stated, please. And please include ALL of the lines in the Log -- you omitted the first line in the earlier post with the wrong log file. It should begin with something like: Installer for FSUIPC4.DLL version 4.949f Also please remove the FSUIPC4_Loader.DLL and re-run the installer to return the installation to normal. Pete

Any "clues" will be found in the FSUIPC4.LOG file, from the FSX Modules folder. It's plain text. Paste the whole thing into a message here. Pete