FSUIPC crashed (7.5.5a - beta version)

[John Dowson]

11 minutes ago, kaha said:

I understand. But I'm not pressing any buttons before the flight is loaded. Maybe some USB devices send some button states anyway?

Maybe - could be due to the initial button state scan...

12 minutes ago, kaha said:

This never happened before 7.5.5d September 7th.

Then I think this is because of the change I made to allow repeated LuaValue calls with the same parameter - but I'm not sure how this change could cause this error!
I have disabled Button actions before everything is initialized in the attached version.

John

FSUIPC7.exe

[kaha]

Thank you John, I'll test.

[kaha]

Seems to work. Let's see if it returns.

[kaha]

It "crashed" yesterday when I listed LVars. I was checking some things and hadn't switched on Buttons and Keas log at that time.

I got the window you see in the screen shot and had to kill it, there was no crash dump.

Karl

FSUIPC.zip

[kaha]

This might be helpful?

FSUIPC_evtx.zip

[kaha]

Today it crashed. I was about to show input events in the FSUIPC GUI. Same aircraft as with the incident yesterday. Same .ini file. 

Karl

 

FSUIPC7_crash_20250912.zip

[John Dowson]

These crashes were related to the logging of the parameter type for input events. According to the documentation, this can be either Float64 or String, but, as far as I know, only Float64 types have currently been implemented/are available. I request the parameter types for all input events received, but it looks like I am only getting a response for some of these, leaving the other unitialised. It is these uninitialised ones thar are causing a memory error/exception due to a buffer overrun.

I have corrected this in the attached (by setting the default parameter type to 'Unknown'). As the parameter type is also not really useful for end users (it is always a number!), I have removed the logging for this, unless you have set logging for Extras or Input Events.

Please find the updated version attached.

Regards,

John

FSUIPC7.exe

[kaha]

Thank you, I'll test and get back to you.

[kaha]

John, this one gets deleted by Defender.

Karl

[John Dowson]

47 minutes ago, kaha said:

John, this one gets deleted by Defender.

This happens due to a Windows virus definition update causing a false positive, and its continually happening. It happened in an update a few days ago, but another definition update the same day fixed the issue. If they don't update to fix  this in a day or two, I report it and it tends to get fixed in a subsequent update a day or 2 later.

I have just checked and I also now get that here - and there have been 2 updates today. You can use the attached, which isn't compressed (its the compression of the exe that seems to trigger this): FSUIPC7.exe

If this isn't fixed by Microsoft in a day or two I will report (again).

John

 

[kaha]

Works. And doesn't crash anymore.