John Dowson

April 4

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

April 4

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.

The new installer is available here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe.

Note that the default auto-start method in the new installer is to use the MSFS.bat file to start FSUIPC7, not the EXE.xml, although this is still available as an option (bit not recommended).

Regards,

John

April 4

If you look at your log files, the error is obvious:

Quote

1040344 *** LUA Error: C:\FSUIPC6\My789functions.lua:66: attempt to call global 'DspShow' (a nil value)

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

April 4

15 hours ago, Ian Dale said:

Might this also be the explanation as to why require(“LUACOM”) works in FSX but not in P3D?

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

April 4

7 hours ago, Song said:

I did Register and it works well.

Ok.

7 hours ago, Song said:

But, i have a big problem.

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

April 4

8 hours ago, dragunov2020 said:

iam new to msfs2020 and FSUIPC 7 and i noticed that there is no mouse macro in FSUIPC 7 like FSUIPC 6 in P3D

is there any plans for FSUIPC 7 to have mouse macro ?

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).

8 hours ago, dragunov2020 said:

because if its not it will be a big problem for me

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

April 4

8 hours ago, ark1320 said:

Above worked for me, tried it 3 or 4 times.

Ok, thanks for checking.

8 hours ago, ark1320 said:

Question: If at some point auto-tuning doesn't work and values are set manually for the startup parameters, the next time FSUJIPC7 starts will those manually set parameter values be over written by the auto-tuning, or does the auto-tuning code check the FSUIPC7.ini file for those parameters?

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

April 3

15 hours ago, raptor84 said:

I also have the event log checked within the FSUIPC but no log file was created.

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

April 3

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:

April 3

7 hours ago, JakedarlingYT said:

i am having the same issue

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

April 3

13 hours ago, raptor84 said:

I'm a bit confuse with this one. Are you saying that in the AUTO section, it should look like this:

[AUTO.A320]
1=Lua My320functions

[AUTO.B789]
1=Lua My789functions

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.

13 hours ago, raptor84 said:

So, I need to include the above functions as well in order to use the QW_OH_LT_Both_RWYTF_toggle function??? I thought the above function was to be use individually, that's why I left it out because I wasn't trying to turn them on individually, which is the case that is happening. Meaning, when I went back and included the missing functions and assigned Ctrl+F2 to the function you saw in my lua file, what ended up happening, it turned on/off the only Left Runway Turnoff light instead of turning on/off Both Runway Turnoff light as how I want it. The function name is copied correctly from the action file, so I don't know why the QW_OH_LT_Both_RWYTF_toggle function isn't working as its intended to do?

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

April 3

13 hours ago, ark1320 said:

When and how are offsets 0x0B47 and 0x0B48 updated in order to indicate the current com frequency spacing?

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

April 2

6 minutes ago, fennelda said:

I spoke too soon - all three ghost controllers are now showing up again, without any change on my part! And my [JoyNames] section is corrupted again.

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

April 2

4 minutes ago, jonas_llubi said:

How can I read the offset values in the logging?

As I said, using the facilities provided (Log->Offsets).

Please read the user manual!

John

April 2

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

April 2

36 minutes ago, jonas_llubi said:

I have the plug-and-play version of the A320-Radio from OpenCockpits and i am using the "IOCModules" software to use it with MSFS2020. I have the problem that when i change the frequency there for example to 122.805, the frequency on the A320 is 122.800. For a reason the last "5" digit is ignored. I contacted OpenCockpits regarding this and they think, that this is a communication error with FSUIPC.

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

5 minutes ago, jonas_llubi said:

I think it is related to:

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

April 2

52 minutes ago, fennelda said:

As well as your suggestions, I also right-clicked on MSFS in the games list, clicked Properties, Controller and then selected "Disable Steam Input". I really felt this was going to work, however I still have the ghost controllers - but I now only have two, not three!

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.

54 minutes ago, fennelda said:

I believe the problem is that in the latest versions of Steam client, Steam Controller support can not be disabled completely. Indeed, in the Controller menu mentioned above, it states that Steam Controller and Remote Play are "Enabled, always required", and from a brief search online it seems impossible to change this setting.

I also think this is caused by Steam - I will raise a support request with them.

55 minutes ago, fennelda said:

Interestingly, the positions of the "virtual" controllers in the FSUIPC7.JoyScan.csv file seem to determine whether these controllers cause an issue or not. I still now have two phantom controllers in my list, however since they are the top two entries in the list, they do not mess up my FSUIPC7.ini [JoyNames] section.

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

April 2

2 hours ago, raptor84 said:

For example, when I assign the key Ctrl+F2 to toggle on/off the Runway turnoff lights and press it, nothing happens.

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

Quote

[Profile.B789]
1=QualityWings 787-9 United Airlines -SATCOM

to

Quote

[Profile.B789]
1=QualityWings 787-9

which will then match the aircraft when using a different livery.

John

April 2

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

April 2

9 hours ago, fennelda said:

Thanks for your help - I have done as you have suggested but it doesn't help. It would appear that the detection of the controllers is done before the attempts to connect via simconnect, at the moment when FSUIPC is launched by the sim, so delaying the simconnect request makes no difference.

Yes of course - I should have realized that, sorry.

9 hours ago, fennelda said:

I might create a batch file which launches FSUIPC and then MSFS instead of the exe.xml method, but it's not really an ideal solution!

You can use the MSFS.bat file for this. This was the old way that FSUIPC7 was started, and there shou;d still be lines in that file to start FSUIPC7 although they will be commented-out. You can uncomment them and move them to before the start of MSFS.

Maybe this is a Steam issue... Could you check your Steam Controller settings - what does that look like? All my settings are off, except for Guide button focuses Steam, and I do not have the Xbox Extended feature Support Driver installed.

Please check that, and I will review your files and check the other posts on this issue to refresh my memory. Quite busy at the moment so it may take a few days before I get a chance to look into this again.

John

April 2

9 hours ago, JJ547 said:

Run the connecting program as admin.

You only need to do this if running FSUIPC7 as admin - all clients must be ran at the same privilege level as FSUIPC7.

John

April 1

17 hours ago, Francisco Sanchez said:

I´m just wondering how long take now the simulator to start. It´s about 10 minutes to get the main menu. Is there any workaround to do?

The log file attached stops after 3 seconds and was attached when FSUIPC7 was still running - MSFS was detected but FSUIPC7 hadn't even tried to connect yet.

Please see this post:

And please hijack unrelated posts - this post is about virus protection blocking the installer. There are several posts on start-up issues but not this one - and this one is badly named - I will update.

John

Later: sorry, look like you have already adjusted that. Please create a new post and attach a fill log, where you get to the main menu, wait a short time and then exit FSUIPC. FSUIPC should not affect the start-up time much though. Try disabling FSUIPC7 (just rename the FSUIPC7.exe) and see what start-up times you get then.

April 1

1 hour ago, John Dowson said:

Note that LIGHTING_PANEL_1 is also available as an lvar, so it would be easier to use this. Just add that to a free/spare FSUIPC offset (using the facilities provided), and then you can just assign your rotary buttons assigned to the offset inc/dec controls.

This lvar holds the correct value, but if you manually change the value of this lvar it does not change the lighting. Therefore you cannot use this to control the lighting, but you can use it to get the current value of the lighting, then increment/decrement this and send the new value via an Input Event. You would need to write a lua script to do this. The script should wait for a button press on your rotary buttons (event.button), and in the button press handling function it can read the current lvar value (ipc.readLvar), inc/dec the value to the new value and then send this on using ipc.execInputEvent.

April 1

1 hour ago, Wray2400 said:

It worked!

Does it also validate?
If it works, then why didn't the one you created manually work (it should be exactly the same)?
If it validates, why doesn't it validate when you entered the key (the details will be the same)?

I would like to know what your issue was...

John

April 1

33 minutes ago, Wray2400 said:

3412140

The key details for that order work fine here. I have PM'ed you a key file - please save that to your FSUIPC7 installation folder and run FSUIPC7 and see if you have access to the Assignments menu to confirm it works. If so, then re-run the installer and see if that validates.

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information