John Dowson

Please keep to this topic for your issue...I have deleted your posts in the other topic I referenced. Do you mean you manually created the key file? If so, what do you mean by 'didn't work'? Have you actually tried to run FSUIPC7 (unregistered)? Does it run? Have you installed the VC++ redistributables?

If you don't have the required VC++ libraries installed, FSUIPC7 won't run, which is why you should try running it, as advised, to see if this is the issue. Anyway, try installing the latest combined VC++ redistributable package, instructions in the README.txt.

Does this mean that you have now successfully registered?

Ok, thanks. Looking at the documentation, both of the EXTERNAL_POWER_AVAILABLE and EXTERNAL_POWER_ON are indexed variables: EXTERNAL POWER AVAILABLE This will be true if the given external power source is available. Use an external power index when referencing. EXTERNAL POWER ON The external power switch position, true if the switch is ON. Use an external power index when referencing. Any idea in what the index refers to? I am currently requesting unindexed, or index 1.

Ok, then you posted in the wrong place - there is a specific sub-forum for FSUIPC7 / MSFS. I will move your post. Did you follow the advice? Can you actually run FSUIPC7? If not, you may need to re-install your VC++ redistributables. I have checked your details and they are validated and working as expected here, so you are either not entering them as specified or something else is going on. If you cannot run FSUIPC7, it will be the VC++ redistributables. If it does run ok, you could try manually creating your FSUIPC7.key file. Instructions can be found in this post (but this really shouldn't be necessary): You only need to buy that if you are going to use WideClient on a 2nd PC (i.e. have FSUIPC clients running on a 2nd PC). Note that you can now run FSUIPC7 on a client PC, so you may not even need it even if you have FSUIPC clients on a 2nd PC. John

Do you know what the difference is between the AUTOPILOT ALTITUDE LOCK VAR:3 and AUTOPILOT ALTITUDE LOCK VAR:1 variables is? Is one the active/set value, and the other the dialed-in value?

It is reported as unavailable when on a runway, but available when at a gate. However, when available and requested, once connected that simvar doesn't change. At least thats what I have found... No time wasted! I will keep those new offsets anyway. John

EXTERNAL_POWER_ON doesn't seem to work as expected for the FBW A320 (haven't checked with any other a/c). EXTERNAL_POWER_AVAILABLE seems to be correct, but when I request ext. power (using the flypad) I can see the truck, the flypad Ext Power button (eventually) goes green, but the simvar doesn't seem to get updated.

Hi Andrew, please try the attached version, v7.2.15b: FSUIPC7.exe In this version, the following new offsets/simvars are/should be available: 0x0798: AUTOPILOT ALTITUDE LOCK VAR:3 [4 bytes] 0x07A8: NEW FUEL SYSTEM [1 byte] 0x07A9: NEW ELECTRICAL SYSTEM [1 byte] 0x07AA: EXTERNAL_POWER_AVAILABLE [1 byte] 0x07AB: EXTERNAL_POWER_ON [1 byte] All are read-only. John

All three components (email, address and key) need to be exactly as specified (in your SimMarket purchase email or account)) - best to copy and paste the details to make sure. Try that, and if you still have an issue please let me know your order number and I will check it here. Do not post your key or other registration details - just the order number. John P.S. Presume you are not using FSUIPC7. If so, you have posted in the wrong place, and you should take a look at the README.txt and Installation and Registration guide (pdf).

Ok, thanks, please do. I have just noticed that you had posted this topic in the User Contributions sub-forum, where it states NOT for support requests. I have moved your post to the main support forum, and also updated the title to clarify that this is for the PMDG 777. John

Hi Tilo, As I don't have the PMDG 777 and do not know how their custom events work, it is difficult for me to advise. However, if they do not provide increment and decrement controls/events, then maybe they use the parameter on the event to determine the increment decrement value? You said: Have you tried assigning to the rotary decrement buttons to the same but with a parameter of -1 (for press) and 0 (for release)? If that doesn't work, then maybe ask about this on the PMDG support forums. John

There are a couple of things you can try: 1. Switch to using the control Set Fuel Valve Eng1 with a parameter of 1 for on or 0 for off 2. If there is an offset that holds the current state of the fuel valve, you can add an offset condition to the assignments based upon that offset (see the Advanced User guide on offset conditions). You can try with offset 0x3590 (GENERAL ENG FUEL VALVE:1) - this seems to work for some aircraft but not all. Alternatively, if there is an lvar that holds the current state of the fuel valve, you can add that lvar to an offset and then add an offset condition to that lvar offset. John

The SimConnect_Text function is broken in MSFS and has been since release. This is documented in the README.txt under Missing Functionality: The only alternative at the moment is to use the lua Wnd library. I will update the offset status document to make it clear that these offsets no longer function correctly in MSFS.

Sure. I will look into adding these on Monday, so if you know of any others that may be useful (e.g. anything similar for airspeed/vertical/rpm/etc) then let me know and I will add them all at the same time. Note I will be unavailable (on holiday) from 12th-17th (inclusive). I am also going to see if I can add a lua functions to return the value of any simvar (i.e. provide access to the get_named_variable_value gauge function via the WASM/WAPI). As mentioned, it is already possible to set any (settable) simvar via calculator code, but I may also add a helper/wrapper function to make this easier.

hvar names don't appear in the assignments drop-down, or do you mean when in a macro file? The same issue should also apply to lvars, no? I understand the issue, but if they are in a macro then they should be ordered by index number (or alphabetical, not sure which without checking) so should be relatively easy to determine which is the correct entry. I can look into allowing more characters/space in the drop-downs and panels, but this will be low priority - I'll do this when I have some other updates to these panels which are in the pipeline. John

The FSUIPC_WAPID.dll is the (dynamic library) interface to the FSUIPC_WASM module - your link software must be using the FSUIPC WASM module via this interface. The version needs to be the same version as compiled in the software and be compatible with the WASM version installed into your Community folder. There should also be a log file in the same folder, maybe called FSUIPC_WAPI.log but could be different (your link software can set this name). If you look in that file it should log the versions and should also log an error if incompatible with the WASM. This is an example of the first few lines: The version compatible with your FSUIPC WASM installation can also be found under the SDK folder of your FSUIPC7 installation folder, in a file called FSUIPC-WASM.zip, or can be downloaded from www.fsuipc.com. John

Hi Andrew, Sure, I can add them. They are only available for aircraft that use the new electrical system - I will also add the simvar NEW ELECTRICAL SYSTEM which will flag when these offsets are/should be available. I will add them as read-only offsets. There are quite a few new simvars for the various new systems (electrical system, fuel system, etc). I still need to go through the MSFS documentation to compile a list of new simvars which I will add to the offset documentation (as available upon request). No, not that I could think of. You can update unknown simvars (those that are settable) using the lua ipc.execCalcCode() function, but there is no way to return the result when executing calculator code to read the current values. I will post a version here for you to test when ready.

Hi Klaus, Its Dowson, not Dawson. John preferred. I so not know why the CDU is not working any more, but for the changes between versions please see either the changes.txt file included in the downloadable zip, or the FSUIPC7 History.pdf, located in your GSIOPC7 Documents folder. Try activating logging for Buttons and Keypresses as well as events, and generate an FSUPC7.log file for the version where it is working and also in the latest version. This should show any differences. You can attach the files here and I can take a look. John

The internal controls do sometimes work differently from those provided by SimConnect. I am not sure what is happening in this instance - I will take a look when I get time, maybe next week... John

Why are you not doing as I asked? What have you actually done? Can you please tell me exactly what you have done, as you don't seem to be following my advice - and why are you running MSFS - I only asked you to run FSUIPC7.... I cannot really help you if you are not willing to follow my advice.... I hope that you at least took a back-up of your registry...

From that page: There are Pause offsets - see 0x0262 and 0x0264. For the Fuel Transfer Pump, there is an indexed variable FUEL TRANSFER PUMP ON:index Returns 1 (TRUE) if the indexed pump is active. Bool Which could be added, if needed/useful, but this is only available in aircraft that use the new MSFS FuelSystem. Note I recently added a similar indexed variable FUELSYSTEM PUMP ACTIVE for up to 16 pumps. There are also several zoom offsets, but I am not sure of their status in MSFS - these have not been checked, but I suspect they are no longer available in MSFS as the view/camera system is very different. Thank you for your contribution. John

I have no access to that file, but it doesn't matter at the moment... Your ini file shows you have 2 button assignments to the Bravo to the same control: The Bravo ALT button is button 4, so you should remove/delete/cancel that other assignment to button 18 (the one in bold). Please see the Advanced User guide P22 for adding offset conditions. If you want to assign as suggested then your button assignments section should look like this: You can also configure in other ways. For example, you could use Ap Alt Hold On Ap Alt Hold Off i.e. again overloaded (more than one assignment on the button) using the same offset conditions as I mentioned before. This would then switch ALT hold on/off. You can then assign your VS button similarly, overloading the assignments with an offset condition on 0x07EC (Autopilot vertical speed hold). My MSFS system is currently updating so haven't tried this, but I can look into this in more detail once I've updated and have time - probably next week. For configuring the Bravo with FSUIPC7, also take a look at this post (covers all Bravo assignments except the AP functions - to be honest I haven't had time to look at these in detail yet): John

Sorry, I was mistaken: -15 IS the most sensitive curve (around the centre position) and 15 the least. Glad it is now working and calibrated to your needs. John

You could also look into using your arduino device with MobiFlight + FSUIPC - plenty of posts out there on this. Also, maybe take a look at the following: http://thegeekforge.com/2017/11/10/arduino-lua-fsuipc-tutorial-001_a/ and Good luck! John