Events log issue

[Doon1]

When I opened the Events log console it displayed 2 constantly occurring events. I've unplugged all of my peripherals in hopes to isolate the issue. This is with the Cessna 172. 

Any ideas?

thanks.

John

FSUIPC7.log

[John Dowson]

6 hours ago, Doon1 said:

When I opened the Events log console it displayed 2 constantly occurring events. I've unplugged all of my peripherals in hopes to isolate the issue. This is with the Cessna 172. 

Any ideas?

All (or most) aircraft in MSFS continually emit certain events, which are different for different aircraft. The more complex the aircraft, the more of these type of events they seem to emit.
These events are just noise - you can ignore them by using the DontLogThese ini parameter. This can go in your [General] section, or, better, in your [Profile.xxx] sections, where you can specify the events to ignore for just the aircraft in that profile.

John

[Doon1]

Hi John,

Thanks for your response. I am perplexed though. I've tried every other aircraft and the steam gauge 172 is the only one to exhibit this concern. These two events run like a high speed ticker tape. From the moment I click "FLY", until I exit the program or select another aircraft in the World Map. It doesn't matter where I go in the program; be it the Marketplace, Profile, wherever. 

I'm assuming the number on the left is a running total of logged events. if so, it's reached over 1.5 million events in the time it's taken me to write this post. I've also noted that if I am logging the issue with the FSUIPC console that the computer will stop responding once the event number reaches about 4.5 million. This can't be right. That's got to be a lot of CPU usage for nothing.

I'm going to try reinstalling the aircraft to see if that helps.

[John Dowson]

5 hours ago, Doon1 said:

I'm assuming the number on the left is a running total of logged events

No, its a timestamp (milliseconds since started).

Just use the DontLogThese ini parameter, as suggested. I haven't noticed that in the logs, but maybe I have them ignored already. I'll check tomorrow,

[VANANTWERPEN]

Hi John, pete and doon1

I was just asking myself the same question as doon1.
after unplugging all my USB devices I noticed the same thing, so it's noise as John rightly says. there are planes without noise ... and others with ... Events are not always the same function of planes.
I will therefore use the function proposed by john.
little question for him: can we launch an event on the action of a Button through an OFFSET? as with WIDECLIENT / IOCARD / SIOC language on another pc without having to use the virtual joystick (3340) and declaration in button & switch assignments?

Thank for your job and this forum.

Gilles near Bordeaux  hips!

 

[VANANTWERPEN]

sorry, in my question to John, instead of reading Events, read Controls.
the events are the consequence of the controls ...
Gilles

[Pete Dowson]

46 minutes ago, VANANTWERPEN said:

sorry, in my question to John, instead of reading Events, read Controls.
the events are the consequence of the controls ...

Really Controls are Events -- the names of the regular controls in the SDK are "KEY_EVENT_ ....". Internally there are additional types like L:Vars and other "letter:Vars", and these can be used as controls, events, or merely data retainers (eg to remember the state of a switch).

Controls are generally speaking the messages sent between parts of the Sim to make things happen. If they were all being sent via windows messages, as most of them used to be in FS9 and before, then we could possibly log them (and in fact before SimConnect that's how it was done) -- but distinguishing between those you are interested in and those you are not would still be the problem.  But now they are all either sent direct to SimConnect, or direct between components. 

You can of course effectively log the controls you instigate via buttons, axis movements or key presses, if they are assigned via FSUIPC, otherwise all FSUIPC can detect is the resulting event(s) if any, courtesy of facilities to be so notified in SimConnect.

Pete

 

[DrDave-]

On 6/27/2021 at 6:00 PM, Pete Dowson said:

Really Controls are Events -- the names of the regular controls in the SDK are "KEY_EVENT_ ....". Internally there are additional types like L:Vars and other "letter:Vars", and these can be used as controls, events, or merely data retainers (eg to remember the state of a switch).

I'm having the same problem.  The controls that are consistently showing for the Mustang C510 are:

    28547 16828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
    28547 16828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
    29078 16828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
    29078 16828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
    29641 16828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
    29641 16828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET
    30172 16828 *** EVENT: Cntrl= 65962 (0x000101aa), Param= 19 (0x00000013) FUEL_SELECTOR_SET
    30172 16828 *** EVENT: Cntrl= 66523 (0x000103db), Param= 20 (0x00000014) FUEL_SELECTOR_2_SET

Fortunately, the log also provided the controls (events) that I needed. It is a shame there is no way to eleiminate controls that one doesn't want to display.

I was able to use Notebook++ to replace unwanted lines with a space and delete duplicates. The result is attached.

 

C510 Switch Press.pdf

[John Dowson]

@DrDave- I am not sure I understand the point of your post, or why you are attaching a pdf (of a log file I presume). Do you actually have an issue that has not already been clarified in this post?

13 hours ago, DrDave- said:

It is a shame there is no way to eleiminate controls that one doesn't want to display.

But there is - have you not even read this topic? My first comment on this issue:

On 6/27/2021 at 12:50 PM, John Dowson said:

All (or most) aircraft in MSFS continually emit certain events, which are different for different aircraft. The more complex the aircraft, the more of these type of events they seem to emit.
These events are just noise - you can ignore them by using the DontLogThese ini parameter. This can go in your [General] section, or, better, in your [Profile.xxx] sections, where you can specify the events to ignore for just the aircraft in that profile.

Is that not clear? 

[DrDave-]

Yes it is and, no, I didn't read your first post. I was searching for "controls" and went to the last entry.

Thanks again