John Dowson

@naizo I have looked at this again and it seems that lua scripts run a lot slower when FSUIPC7 is auto-started by MSFS. if it is started manually, it runs a lot faster. Are you auto-starting FSUIPC7 via the EXE.xml (i.e. using the auto-start component)? If so, can you try manually starting FSUIPC7 - just exit it when it starts and then restart it manually., Do you see a performance improvement? I noticed this when running the example record to csv.lua script. If I run this when FSUIPC7 is auto-started, the data is logged at roughly 800ms intervals, but if I exit and start FSUIPC7 manually, the rate goes up to around 63ms intervals, more than 10 times faster. I will update the documentation with this information, and report this to Asobo to see what, if anything, can be done. John

LINDA is quite a complex system - you cannot just extract one lua file an expect it to work asit may have many dependencies. If you want to do this, then you need to have some knowledge of lua to be able to modify the files so they work stand-alone. You cannot assume that. You need to extract all dependencies, and then all functions that those depend on, etc etc. No. That lua script will work withing the LINDA environment, where all dependencies will be available. The use of a string rather than a number is minor - that will still work (due to lua's lax type specification - the string will be converted to a number), but it is always a good idea to correct such mistakes as they can cause issues - especially if blindly copied. This error: 1040344 *** LUA Error: C:\FSUIPC6\My789functions.lua:66: attempt to call global 'DspShow' (a nil value) is telling you that he function DspShow, called on line 66 of the My789functions.lua script, does not exist. Just remove that line (and also remove it if it appears elsewhere in your script) and then try again. When you try again, look at the log file to see if any errors, correct them, and repeat. However, I think if you remove those calls to DspShow, the script should work. If you want to use lua, you should really at least learn the basics of the lua language, If you don't want to do this, then you should use LINDA. But if you want to use lua, you need to at least understand the basics, And the log files are there for a reason - to help you. If you get any issues, at least try looking at the logs. If there are basic errors, e.g. syntax errors or missing dependencies/functions, then this should be pretty obvious, as in this example. I don't mind helping people with these sorts of issues, but I prefer to help people understand what the issue is and to help them diagnose and fix these type of issues for themselves. This then reduces the support I have to provide and gives me more time to develop and improve FSUIPC. I have a huge backlog at the moment but have hardly any time to work on improving my products as nearly all my time is spent on support. John

Please see the following announcement: Please post all issues with this version to that announcement topic, I will release this version officially when SU15 is released. John

@DaveSCUSA Have you managed to set this up yet (and I can consider this closed) or are you still having issues? If so, please let me know and I can provide further details on how to configure assignments for the C510. I will soon be looking into updating the Input Event functionality to store the current values of the Input Events, and this will make incrementing/decrementing these far easier. But until then, work-arounds are necessary for this. John

The next release of FSUIPC7 (which will be 7.4.12) will auto-tune these connection parameters. This release is currently available as a beta release here: John

The next release of FSUIPC7 (7.4.12) will auto-tune these connection parameters. A beta version of this functionality is currently available here: John

I have now released this version as a beta release, available here: Please download and use that version, which has a few minor updates compared to the version posted above, which I will now remove. For any issues with key presses or hot keys, please post here. For any other issues, especially with auto-tune, please use that announcement page. John

Please find attached below (at the bottom of this post) the latest beta release of FSUIPC7, which has a new feature to auto-tune the start-up connection parameters. Please note that this feature is only activated when using the auto-start facility, i.e. when MSFS is starting FSUIPC7, which is the default and recommended configuration. If manually starting FSUIPC7, tuning (manual) is only required if you start FSUIPC7 before MSFS is started, or if you start FSUIPC7 before MSFS is fully initialized and has not yet arrived to the main menu state. Quick Start If you have not already tuned your auto-start parameters, just run this version and it will automatically tune these parameters - there is nothing you need to do. If you have already set the DetectToConnectDelayAuto ini parameter in your FSUIPC7.ini file (in the [General] section), there are two methods to try out this new feature: 1. Remove/delete the DetectToConnectDelayAuto ini parameter from the [General] section of your FSUIPC7.ini file (before you start FSUIPC7 / MSFS). This will then tune starting from the default value of this parameter, 2. Add the following to the [General] section of your FSUIPC7.ini file (before you start FSUIPC7 / MSFS): StartUpTuningActive=Yes This will then tune starting from the current value of the DetectToConnectDelayAuto parameter, When is auto-tuning performed? Auto-tuning will be activated in the following circumstances, and only ever when auto-started by MSFS: 1. When the default value of the DetectToConnectDelayAuto parameter is being used and auto-tuning has not already been performed 2. When explicitly instructed to do so, by adding the following ini parameter to the [General] section of your FSUIPC7.ini file: StartUpTuningActive=Yes 3. If I detect a major difference in start-up times with a new MSFS release (either increase or decrease), then I can force an auto-tuning in a new FSUIPC7 release. 4. If some re-connection attempts are detected during start-up, then auto-tuning will be set to run on the next auto-start of FSUIPC7. Can I disable auto-tuning? Yes. To completely disable auto-tuning, update or add the ini parameter StartUpTuningDoneVersion to your FSUIPC7.ini file with a value of -1, i.e. StartUpTuningDoneVersion=-1 To re-enable at any point, simply remove this ini parameter. What does auto-tuning actually do? The new auto-tuning feature will tune two of the parameters used by FSUIPC7 to determine how and when to connect to MSFS: DetectToConnectDelayAuto : this is the delay (in seconds) between when MSFS is detected and when FSUIPC7 will try to connect InitialStallTime : this is the time (in seconds) that FSUIPC7 will wait for a response from the connection request until it decides that the connection is dead and tries to reconnect How does auto-tuning work? When auto-tuning is active, it will count the number of times that FSUIPC7 tries to connect to MSFS. It it takes multiple attempts to connect to MSFS, then it will adjust the DetectToConnectDelayAuto time by adding the InitialStallTime for each failed connection attempt, i.e. new DetectToConnectDelayAuto = old DetectToConnectDelayAuto + InitialStallTime * number of reconnection attempts Provided the new DetectToConnectDelayAuto parameter is not greater than 500 (seconds), the InitialStallTime parameter will also be set to 5 (seconds). If the maximum limit of 500 (seconds) is reached for the DetectToConnectDelayAuto parameter, the InitialStallTime parameter will be increased by 5 seconds (to a maximum of 100) and auto-tuning will run again on the next auto-start. If auto-tuning detects no reconnection attempts, the DetectToConnectDelayAuto will be reduced by 10 seconds (to a minimum of 30 seconds), the InitialStallTime set to 5 seconds, and auto-tuning will be set to run on the next auto-start. So auto-tuning will reduce this parameter until either the minimum is reached (30 seconds) or re-connection attempts are reported, in which case it will increase the parameter and stop running. Maximum values reached If, after auto-tuning you see this message in your FSUIPC7.log file: **** Start-up tuning complete: maximum values set. Please contact FSUIPC7 support (and attach your log file). then the maximum value for these parameters has been set. If you are still having issues, please post a support request, attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. There is not much I can do about this, except maybe increase the maximum values allowed. However, if you are still having issues then you have a start-up time of over 10 minutes, and I think you should be considering alternative solutions, such as using the MSFS Add-on linker program to reduce the number of Community add-ons you are using for each flight. But if you post your files I can advise. Manually starting FSUIPC7 (i.e. no auto-start with MSFS) Auto-tuning is only ever performed when FSUIPC7 is auto-started by MSFS. If you start FSUIPC7 manually, then the auto-tuning details do not apply. If you start FSUIPC7 when MSFS is fully loaded, and either in the menu system or with an aircraft already loaded and ready-to-fly, then there is no tuning necessary. However, if you start FSUIPC7 before MSFS is started, or when FSUIPC7 is starting, then it is recommended to tune the DetectToConnectDelay ini parameter. Please see this FAQ entry on how to do this: For any issues or comments with this beta release, please comment below, in this topic. To use this version, just download this FSUIPC7.exe file and use it to replace the current one in your FSUIPC7 installation folder (you can also temporarily rename your current FSUIPC7.exe if you prefer): FSUIPC7.exe Regards, John

If you look at your log files, the error is obvious: This is happening after the left light has been set (i.e. turned on or off) and will stop the processing, so the function to control the right light will not be called. The error is because you are using the function DspShow which is not defined anywhere. Note also that your lua scripts are writing numeric lvars as strings, e.g. ipc.writeLvar(lvar, '0') This should be ipc.writeLvar(lvar, 0) This happens in various places. Can you please try looking at the log files yourself and at least attempt to diagnose the issue before asking for support. I don't mind helping, but such obcious errors should be detected by the user really and not require support. Always at least look at your own log files before posting and the error may be obvious. John

No. This is quite an old post. The lua COM library is working in all versions of FSUIPC. The 'LUACOM' library that you are using is different - it is a library to support the windows COM object library, not to read data from COM ports/sockets, which is what this thread is about. As I said in the other thread, I have no idea why/how WideClient can load this library but not FSUIPC. As I said (in the other thread), I will take another look at this when time permits. John

Ok. But this topic is about 'No ASSIGNMENT button shown FSUIPC7', which you have now solved (by registering). You cannot use the same topic for all your issues, If you have another issue, please create another topic. I am closing/locking this topic now as it is solved. John

No, it is not possible to have mouse macros with MSF2020, and there are no plans to add this as the functionality is not provided by the MSFS SDK. There are alternative methods that replace the need for mouse macros - hvars (HTML variables), Input Events (also known as B vars) and calculator code (usually executed via presets). It really shouldn't be an issue. For example, check the presets availalble for each aircraft here: https://hubhop.mobiflight.com/presets/. All MobiFlight presets are available for assignment in FSUIPC7. John

Ok, thanks for checking. I will provide full details later today, but auto-tuning will only kick in if the default value of the DetectToConnectDelayAuto ini parameter hasn't been changed, or if it is forced. To test the auto-tuning, just remove the DetectToConnectDelayAuto parameter from your ini. If auto-tuning increases the DetectToConnectDelayAuto parameter, it will not run again. If it decreases this parameter, it will run again on the next auto-start unless the parameter has been decreased to 30 (minimum value for this parameter). I also noticed a minor issue in the above attachment - this has been corrected and the attachment replaced (no change in version number though). So please download this again if you want to try the auto-tuning. John

Events are logged to the FSUIPC6.log file. You also activated Log Lua Separately. Please do not set this - I prefer to see the lua log embedded in the FSUIPC6.log file. Only activate the logging I request please, no other logging needed. And no-need to rename your lua files with a txt extension. Also never start a new log file when generating logs for support, and always exit FSUIPC/P3D before attaching logs. I will look at your files tomorrow - just finishing for the day... John

Sorry to have to revisit this, but I need to make further changes to the way FSUIPC7 starts, and I would like users who have this issue with key presses not being received to try this before I release publicly. Therefore could all people with this issue, especially @Cuantreau please test this version. Please attach logs if you have issues. This version contains an auto-tune feature for the connection issues, but I will publish details on this once I have verified that this version doesn't re-introduce the problem with keys/hot keys reported by so many of you. Thanks, John Attachment removed, now available from here:

What issue is that? If it is the same as reported. follow the advise I have already posted. Otherwise please explain your issue and attach the relevant files - the InstallFSUIPC7.log file if having issues with installation, otherwise your FSUIPC7.log file. If unsure, attach both. As a new user to these forums you will have a restricted upload limit - zip/compress the files if too large. John

With your current [Auto] section, both lua scripts will be ran for every aircraft that you use. If you replace this with the above, only the relevant script will be ran in each profile. I can't help if you don't show me/attach your updated script. You can also try logging (for Lua Plugins and maybe also Events) and work out what the script is doing and why it isn't working as intended. John

They do not indicate the current com frequency setting, they indicate if the avionics in the current aircraft support 8.33 or 25 KHz, and will be set when the aircraft is loaded. John

Ok, so probably related to the timing, i.e. what Steam/MSFS is doing when FSUIPC is scanning the registry. I will report this to both Steam and MSFS and see what they say... Thanks for the files. Cheers, John

As I said, using the facilities provided (Log->Offsets). Please read the user manual! John

I have responded in the other topic you created on this same issue: In summary, FSUIPC7 is holding the correct 8.33KHz frequency, so the problem must be elsewhere. Maybe @sdlc can comment if he has resolved this issue? John

What offset are you using for the COM frequency? For COM1, there are two offsets (for the active frequency): 0x034E: COM1 frequency, 4 digits in BCD format. A frequency of 123.45 is represented by 0x2345. The leading 1 is assumed. 0x05C4: Active COM1 frequency in Hz (32 bit int) For 8.33KHz frequencies, you need to use offset 0x05C4, not 0x034E (as that does not support 8.33KHz spacing). Check which offset you are using. You can also use FSUIPC's offset logging facilities to check what these offsets hold. You can also check offset 0x0B47 which will tell you which frequency spacing mode is being used (25KHz or 8.33KHz). There are similar offsets for COM2 and standby - see the Offset Status document for details Yes, the same issue - but that user was already using offset 0x05C4. What A320 model are you using? Check what frequency spacing mode is supported. In the Asobo A320, I see this: 5469 Monitor IPC:034E (U16) = 0x1870 5469 Monitor IPC:05C4 (U32) = 118705000 5469 Monitor IPC:0B47 (U8) = 1 and in the FBW A320 (Development branch) this: 185610 Monitor IPC:034E (U16) = 0x1870 185625 Monitor IPC:05C4 (U32) = 118705000 And when I change to 122.805, this: 450344 Monitor IPC:034E (U16) = 0x2280 450344 Monitor IPC:05C4 (U32) = 122805000 So FSUIPC is holding the correct values for these aircraft. Please check those offsets for your aircraft model. If they are holding the correct values, then you need to go back to OpenCockpits. If they are not holding the correct values, then maybe the aircraft isn't setting the COM ACTIVE FREQUENCY simvar correctly. You can either report this to the aircraft developer, or check to see if they use an lvar to hold the correct 8.33KHz spacing - if so, you can add this lvar to an offset and use that. Cheers, John

Mine is set to Use default settings and I don't have this issue. I have experienced this issue before, but I can't remember what I did, if anything, to stop this. I also think this is caused by Steam - I will raise a support request with them. Ok, that's good as at least your controllers are recognised and acquired correctly. Could you attach a joyscan.csv file for this please. It would also be useful to see a joyscan.csv file from when you start FSUIPC7 without MSFS running, when these phantom entries do not appear. I can then use this to show the difference to Steam support. Thanks, John

Ctrl+F2 is assigned to LuaToggle My789functions with flag 2. Flag 2 calls the QW_OH_LT_Both_RWYTF_toggle function: event.flag(2,"QW_OH_LT_Both_RWYTF_toggle") This is the function called: function QW_OH_LT_Both_RWYTF_toggle () QW_OH_LT_L_RWYTF_toggle () QW_OH_LT_R_RWYTF_toggle () end The functions QW_OH_LT_L_RWYTF_toggle and QW_OH_LT_R_RWYTF_toggle do not exist (and neither QW_OH_LT_L_RWYTF_on, QW_OH_LT_R_RWYTF_on, QW_OH_LT_L_RWYTF_off, QW_OH_LT_R_RWYTF_off and QW_OH_LT_R_RWYTF_offQW_OH_LT_R_RWYTF_off). So looks like your lua is missing some functions, although I don't know why this error isn't logged. Note that you arer starting two lua dunctions in your [Auto] section, one for each profile. Better to use profile Auto sections (e.g. [Auto.B789]) to only start the luas needed for that profile. Also, consider using substrings for your aircraft profile names. i.e. change to which will then match the aircraft when using a different livery. John

But there is no need to do this - the email address is never used. And once you have generated the FSUIPC key file you don't need to use it again, and the registration details are always available in your SimMarket account. It is just not necessary. John