John Dowson

July 16

You need to delete/rename the steam UserCfg.opt file, located at C:\Users\[YOUR USERNAME]\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt

If this file is present, the installer presumes you are installing for Steam and not MS Store.

John

July 16

1 minute ago, cteixeira said:

The folder exist, what I don’t know is, if it existed before FSUIPC install.

I don't think FSUIPC will create this folder, but not 100% sure.

The FSUIPC installer reads the InstalledPackagesPath entry/line, then removes the first 23 characters (i.e. the characters 'InstalledPackagesPath "', then removes the last two characters, which should be the closing quotes and the new line character. Maybe there is no new line after your InstalledPackagesPath entry? If not, then the last character of the path will be removed.
So, check there is a new line after the InstalledPackagesPath entry.

This is obviously not ideal - I will correct the installer for the next release to actually check for the new line and only remove if present.

Let me know what your entry looks like when you get a chance.

Regards,

John

July 16

👍

July 16

The Community folder location is taken from the InstalledPackagesPath entry in your UserCfg.opt file (usually the last line) - what is the value there?

Where was the WASM actually installed? Does the folder C:\Users\Carlos\AppData\Roaming\Microsoft Flight Simulator\Package\ exist as well?

John

July 16

4 hours ago, electricclay2000 said:

where in the general section to add that line

As you quoted, in the FSUIPC7.ini file (which is in your FSUIPC7 installation folder) - did you not look there?

I have moved your post to the FSUIPC7 sub-forum.

John

July 15

Here's the analysis from Microsoft:

Analyst comments:

At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

Thank you for contacting Microsoft.

This was from yesterday. Should be ok with the latest virus definition update.

John

July 15

You can just remove/delete that line. This is the only place that FSUIPC stores that information - if it re-appeared, FSUIPC must still have been running when you removed it - I can't see how else it could have re-appeared.
Only edit the LuaFiles section when FSUIPC is not running.

John

July 14

Here's the analysis from Microsoft:

Quote

Analyst comments:

At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.
1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

Thank you for contacting Microsoft.
Click here for more information

John

July 14

The on-line submission to Microsoft also detected no malware - you probably won't be able to access this but here's the link: https://www.microsoft.com/en-us/wdsi/submission/4df57e58-4a1e-4d81-ac6f-ad28e26e1fdf

Hopefully this will be fixed in a virus definition update shortly.

Cheers,

John

July 14

57 minutes ago, wigmore said:

I’m wondering if it’s tied in to another user reporting in a separate post about Windows Defender identifying something in the package as a threat (I get that too).

It was reported on the exe I believe. And I have had it stopped at run-time and removed from the installation folder by Windows Defender.
As you are using windows defender, you should look at the threat removal/quaranteen and restore it from there.

1 hour ago, wigmore said:

but in the meantime the .exe you posted is a fix.

That exe is the previous version, 7.4.3.

July 14

1 hour ago, wigmore said:

So I think what's happening is that the installer for the new version isn't actually installing FSUIPC.exe at all? Could there be a cause for that?

I think it may be your anti-virus blocking and quarantining the FSUIPC7.exe. I have also experienced this on occasion with this release, but not always. It is very strange - I have reported this as a false-positive to Microsoft so hopefully should be fixed with a virus definition update. Check your anti-virus - if you are using anything other than Windows Defender you should report this o your anti-virus definition provider.

John

July 14

Also, what happens if you manually start FSUIPC7 once MSFS2024 is already running? You don't need to re-install to test this - just double click the FSUIPC7.exe (for your MSFS2020 installation) and it should run ok (although you won't have access to the WASM facilities if this is not installed in MSFS2024).

July 14

Please use the FSUIPC7 sub-forum for all issue/questions on FSUIPC7 / MSFS2020 / MSFS2024. I have moved your post.

4 minutes ago, cehallow said:

Great product.

Thanks,

4 minutes ago, cehallow said:

For some reason, MSFS 2024 started crashing after the installation of FSUIP 2024. It works fine with MSFS 2020. So, I had to uninstall the FSUIP 2024 version and MSFS began working again. Is there anything I need to do to fix this?

There is no fix. This was also reported in the MSFS2024 SU16 beta a while ago, but was later fixed see

If MSFS2024 is crashing, then it is an issue for Asobo and you should check the CTD reports there - there is nothing I can do to investigate crashed in MSFS2020/MSFS2024. And if it is crashing, it will be something that needs to be addressed/fixed by Asobo.

I also just fired up MSFS2024 here to check and everything seems fine here.

John

July 14

I am now getting this again in Windows Defender - I will report to Microsoft....

John

July 14

Such connection issues are usually due to FSUIPC7 running at a different privilege level to APL. If you had previously changed FSUIPC7 to be ran as admin, this will have been lost when you re-install. So maybe try running the latest version with admin privileges, to see if it then connects.

July 14

Can you show me / attach your FSUIPC7.log file please.

The previous version is attached below. Rename your current FSUIPC7.exe (e.g. FSUIPC7.exe.754) and save the attached to your FSUIPC7 installation folder and see if that still works.
Please send me the log for the current version before you do this.

Thanks,

John

FSUIPC7.exe

July 14

That will be a false positive - please report to the ant-virus provider you are using.

I have also had this issue with Windows Defender. I reported this and it seems to be ok now, although I did get one download attempt blocked due to a threat, but subsequent downloads and installs seemed to be ok.

If I get further false=positives from Windows Defender, I will report, but if you are using other anti-virus software you will need to report this yourself, or allow the threat/rstore the file, as there is not much I can do. There is no virus in FSUIPC7.

John

P.S. This is for FSUIPC7 so I have moved your post to the FSUIPC7 sub-forum.

July 14

👍

Thanks for the update.

John

July 13

You will have to do this manually.

First remove all the [LuaFiles] entries that you are no longer using, and move the corresponding lua scripts out of your FSUIPC7 installation folder.

Then, for each lua script remaining, you can renumber it and also change the assignment reference. So, for example, if you changed:
16=Elevator_Trim
to
1=Elevator_Trim
You would need to replace all occurrences of 'CL16:' with 'CL1:', i.e. change the lua reference numbers in the assignments to the new index number of the lua script.

If you are re-organising your luas, you should also consider moving them all to a subdirectory and using the LuaPath ini parameter under the [LuaFiles] section.

John

July 13

No idea. FSUIPC7 does not generate that file on its own - there must be something else running that is generating those files, probably a lua script. Check your assignments and lua files in your FSUIPC7.ini file.

July 13

Better to keep the terminate function - always a good idea to close com connections.

Cheers,

John

July 12

2 hours ago, John Dowson said:

As I said, you should update the sendComFrequencies fumction, e.g.

function sendComFrequencies(offset, value)
    if offset == 0x05C4 then
        local strCom1 = formatComFreq(value)

        if strCom1 ~= lastCom1 then
           com.write(dev, "COM1:" .. strCom1 .. "\n")
           lastCom1 = strCom1
        end
     else if offset == 0x05CC then
        local strCom1sb = formatComFreq(value)

        if strCom1sb ~= lastCom1sb then
            com.write(dev, "COM1SB:" .. strCom1sb .. "\n")
            lastCom1sb = strCom1sb
        end
    end
end

As the offset event handling function is only called when the offsets change, you don't need to store and compare to the old value, so this can be simplified to

function sendComFrequencies(offset, value)
    if offset == 0x05C4 then
        com.write(dev, "COM1:" .. formatComFreq(value) .. "\n")
     else if offset == 0x05CC then
            com.write(dev, "COM1SB:" .. formatComFreq(value) .. "\n")
        end
    end
end

John

July 12

First, can you please attach your lua scripts rather than pasting the contents. It would make this thread far easier to read.

12 hours ago, Isak said:

I tried modifying the Lua script based on your hints and explanation. However, the script no longer runs.

As I said, you should update the sendComFrequencies fumction, e.g.

function sendComFrequencies(offset, value)
    if offset == 0x05C4 then
        local strCom1 = formatComFreq(value)

        if strCom1 ~= lastCom1 then
           com.write(dev, "COM1:" .. strCom1 .. "\n")
           lastCom1 = strCom1
        end
     else if offset == 0x05CC then
        local strCom1sb = formatComFreq(value)

        if strCom1sb ~= lastCom1sb then
            com.write(dev, "COM1SB:" .. strCom1sb .. "\n")
            lastCom1sb = strCom1sb
        end
    end
end

But if its not running, try debugging it. Check the FSUIPC log file for errors, add further ipc.log to determine what is happening, and you can also set Lua Plugin logging to trace what is happening in the lua script.

John

July 12

17 hours ago, jfmitch said:

Why am I getting multiples of the same aircraft?

No idea. Where/what is that image from? What has this got to do with FSUIPC?

You really need to provide more information....

July 11

10 hours ago, Isak said:

I'd now like to clean up the Lua script and refactor it to use the event.com() function for handling serial input.
Could anyone have a look at the script and maybe offer some suggestions on how to best achieve this?

Change

10 hours ago, Isak said:

function processInput()
    local datastring, length = com.read(dev, 256)  -- Read up to 256 bytes from the serial port
        -- Parsing the received string to set COM1 standby frequency
...

to

function processInput(dev, datastring, length)
        -- Parsing the received string to set COM1 standby frequency
...

and wait for the data event using

event.com(dev, 256, "processInput")

For the sendComFrequencies function, you can use event.Offset on offsets 0x05C4 and 0x5CC, and refactor the function to use the value passed in with a conditional on the offset (or use two functions, one for each offset.

John

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information