John Dowson

I will look into this ang get back to you. John

Looks like a registry problem where your device name/guid changed... I have corrected this in the attached file, if you could try with this. There looks to be an issue with your CH Pro pedals as well, but you don't seem to have any assignments to this. Is this working? You may need to clean the registry details for this if you want to assign in FSUIPC. John FSUIPC7.ini

Please DO NOT attach your key file or publish your key details in a public forum. This invalidates your license. I have removed this file and luckily nobody had downloaded it. Can you please explain more clearly what your issue actually is and what this has to do with FSUIPC. FSUIPC will not do anything on its own accord - check your autopilot setup, and also the MSSFS assistance options - maybe coming from there?

You can use the external quickview presets: For other external quickview controls, you would need to either define your own preset, or assign a key combination to the control in MSFS and then assign to this key combination in FSUIPC. John

You should omit the 'B:', and use the input event name EXACTLY as listed by FSUIPC7. Yes, you need to use the input event names as listed by FSUIPC, not in the behaviors window. Not all input events are currently exposed via simconnect API, but Asobo have indicated that more will be available in future releases. Use the Log->List Input Events menu to determine what input events are available, and use the names exactly as specified there. John

FSUIPC numbers buttons from 0, whereas windows (and maybe ProSim) start from 1, so windows buttons 4 & 5 will be buttons 3 & 4. Please see the User guide. The interface in FSUIPC7 is slightly different to that of previous versions. The 'Options and Setting' page of previous versions was the main window of FSUIPC, with all the features available under different tabs. Now, each of these tabs is available from a menu item. Please see the documentation. How was this previously set-up? Have you tried configuring the same way? Sorry, i don't have the ProSim flight model and cannot help with specific assignments for this aircraft. Ty the prosim documentation or the prosim forums. John

You only need to register once - this generates the key file. When you re-install, you can skip registration and FSUIPC will still run as a registered copy. John

Can you please explain what you mean. Key assignments are for a key press, possibly with modifiers, but not for "sequences". You can assign to "Ctrl+L", to "O" and to "Alt+J'. Or do you want to send a sequence of key presses? If so, what is triggering them to be sent?

There is no location tagging in FSUIPC - something else must be going on.... Registration issues are nearly all due to either not having the correct VC++ redistributables installed, or by anti-virus software. You need to install the combined redistributable package, as specified in the documentation, which includes 2015, 2017, 2019 and 2022.

FSUIPC7 has nothing to do with the start-up of MSFS. If you use the desktop icon installed by FSUIPC7, this just displays a splash screen while MSFS is starting, and MSFS will start FSUIPC7 at the appropriate time. The start-up time of MSFS will depend on the number and complexity of the add-ons installed in your Community folder. John

No - only the automatic execution of lua and macro files is supported, as these run in separate threads as part of FSUIPC. For other programs, you can use the [Programs] section to start - see the section Programs: facilities to load and run additional programs on page 43 of the Advanced User guide. John

Sorry, it seems that the license expired earlier than expected.... I have generated and attached a new one (to the existing trial license topic), valid until 1st Feb, so please download and try again. John

The trial license/key file is available to download in the very first comment of this topic. John

Those errors are reported as something is trying to set those variables before the initial request to receive and control them has been completed. It looks like it is taking longer for the initial data requests from being completed on initial start-up, and it works when you restart as these initial data requests are processed a lor faster once MSFS2020 is up and running. You need to determine what is trying to access those variables and delay those requests until all of the initial data requests have been processed. Not sure what you mean by this, but you can delay any initial requests until the offsets have been initially populated, such as checking for when the FS version offset 0x3124 is non-zero. John P.S. Note that I am on holiday until the 2nd or 3rd January.

Why do you need to create a variable? You can just write whatever you want to a (free for general use) offset. You can write to offsets using either the provided offset controls or lua. If you want to create a variable, then create an lvar, but I do not understand why you would want to do this. 0x66C0 is an offset, not a variable. Please do not confuse the two. If you want to write 1 to the offset (or maybe toggle between 0 and 1) when a switch/button is pressed, then assign the switch/button/whatever to an offset control, such as Offset Byte Set or Offset Byte Togglebits. You can overload your assignments if needed, so the button/switch can also send other controls/perform some other function as well as changing an offset value. Please note that I am on holiday now, and will not responding further until January. Please use the provided documentation and these forums - all the information you need is there somewhere, although it can be difficult to find... John

What information? If you want the ADF information, this is already held in offsets - search the Offset status document for ADF. That will never work... The myOffsets.txt file is for adding simvars (or A-type variables) to offsets. Those are FS events/controls and do not have an associated value. John

The trial license (key file) is available to download in the very first post in this topic. However, please note that WideFS has nothing to do with multi-screens, it is for running FSUIPC client applications on a networked client PC (i.e. a different PC to the FS). You are probably thinking of WideView.

You do not have access to the assignments menu as you are using an unregistered version. PLEASE read the provided documentation, namely the INVALID KEY SECTION of the Installation and Registration guide. Just update your VC++ redistributables, as indicated, and as already reported so often that I find it very difficult to answer such questions without being derogatory...

Glad that your issues seem to be resolved. Have a great christmas as well, and best wishes for the new year, John (from Oporto!).

The 'L:' is optional - I like to use it - force of habit. Your code was failing for the other reasons I mentioned, not that. There are various quote signs - if you look at the lua documentation for the ipc.writeLvar function, you will see that the double quotes around name are right and left sloped (i.e. opening and closing double-quotes) - this is what some editors/word processors insert, but for lua code you should just use standard double-quotes. Some folks get in trouble by using the wrong double-quote, which can be difficult to spot. Please note I am now on holiday until January. John

Its normal brackets, not square ones, and you don't need the end, and be careful with the quote symbol, i.e. ipc.writeLvar ("L:C310_LEFT_FUEL_PUMP", 0)

Auto-save is known to cause issues (pauses or stutters) when using complex add-on aircraft, and as anti-virus software is getting more aggressive it seems to be affecting more aircraft. See the following post for possible solutions: Autosave is not active in the unregistered version... John

No. If its not document, you cannot do it. As I have already said, you cannot invent your own syntax and expect it to work. Please consult the documentation for such issues. Or just try it - you will see that you get an error.

Check the MSFS logging console (you need to switch to devmode) - do you see any messages there? Is anything reported in the FSUIPC7.log file (ALWAYS a good idea to attach this for any issue, as well as your FSUIPC7.ini file)? Are you using a registered/licensed copy, or unregistered? If the latter, do you still get this issue when unlicensed/not registered? Unfortunately (for you!), I am now on holiday until the new year. Please try what I have already said and let me know the results, and attach your .log and .ini files and I can take a look in the new year. John

Please don't embed new questions in quoted text - it makes it very difficult to see what you are actually saying. But you obviously do! You are already using the offset controls, which are also added by FSUIPC. There is no distinction in the drop-downs between FS-defined controls and those added by FSUIPC. Use '..+8', as 8 is 'normal', i.e. no shifts. No it is not. Please see the Advanced User manual on the definition of key controls. The 'K...' syntax is for the key you are programming, not what the key is sending. Don't invent your own syntax and expect it to be valid. Yes, that is confusing, and I am not even sure it is even valid, That syntax is for joystick buttons. I will update the manuals and remove. Please note that I am now on holiday until the new year. Any more questions will have to wait until then. John