MSFS strange events in console ?

[AndyCYXU]

Hi, I recently run a console while the sim is running and I have come over very strange issue with some of the aircraft here is my recent flight console log.

What I am referring to is this:

    41109  7764 *** EVENT: Cntrl= 66280 (0x000102e8), Param= 0 (0x00000000) RADIO_COMMNAV1_TEST_TOGGLE
    41109  7764 *** EVENT: Cntrl= 66281 (0x000102e9), Param= 0 (0x00000000) RADIO_COMMNAV2_TEST_TOGGLE

... the above event is spamming consistently through the entire flight in this case I am using Cessna 172 SP

NOTE: not all aircraft do that, some do other commands which they spam the console with all the time.. the other was Beechcraft 350i this one was spamming console with these some Starter_fuel_set and Starter_Fuel_set_2 (sorry i deleted this aircraft and the logs, so i don't recall exactly the event, I think it might have started to cause my MSFS to CTD, i tried reinstalling the aircraft same thing, I have (had) no mods for this King 350.

So i tried unhooking all my devices (yokes, throttle even keyboards, yup) also check to see if there are any assignments to these events in FSUIP and/or MSFS, No there are none. so it seems MSFS is sending these by itself... why beats me...?

I do not know if this is FSUIPC issue or MSFS issue, obviously without FSUIP i have no idea if these events being spammed into the console, hence there will be no console LOL

So yeah I was wondering if anyone has any suggestions maybe you would be willing to check on Beechcraft King 350i does it spam these command in your console?

Again NOT ALL AIRCRAFT do that nonsense... most behave normally there is nothing going on in the console unless i actually do something (press button, switch knob etc).

I really think this could be causing sim to crash, maybe worth to report to Microsoft..

NOTE: I had to delete a lot of from this file to make it 20kb... there are as you can see about 3 million events.. out of these 3 million probably 2.8 million was pure spam from the

41109  7764 *** EVENT: Cntrl= 66280 (0x000102e8), Param= 0 (0x00000000) RADIO_COMMNAV1_TEST_TOGGLE
41109  7764 *** EVENT: Cntrl= 66281 (0x000102e9), Param= 0 (0x00000000) RADIO_COMMNAV2_TEST_TOGGLE

Other you may see there they are legit for example press key UP or DOWN that is me moving around the cockpit and if you keep key pressed it will generate these events so these are fine.

It seem like for the problematic ones a key is stuck BUT !!! I have no key assigned to these events (i don't even know what they are really ??COMMNAV2_TEST_TOGGLE???) again i checked all  my key assignments in MSFS and FSUIP nothing like that, disconnected all my yokes, throttles and keyboards to ensure there is nothing that could be sending this event from my hardware.. adn nothing hlped this is still showing like a key that is stuck of sort or something wrong with MSFS.

 

Ok Thanks for any help and suggestions as to why this might happen would be appreciated to put this mystery to bed.

 

Andy

FSUIPC7e.log

[Pete Dowson]

4 hours ago, AndyCYXU said:

Again NOT ALL AIRCRAFT do that nonsense... most behave normally there is nothing going on in the console unless i actually do something (press button, switch knob etc).

The same sort of thing has been happening with (mostly) add-on aircraft in FSX and P3D, especially PMDG aircraft. It seens some parts of the aircraft code handle other parts by using the user controls.

To avoid filling up the log you can add a "DontLogThese" parameter like into the FSUIPC7.INI file. Check the Advanced Users guide.

I don't think they would contribute to MSFS stability. It seems the latest version of MSFS is pretty unstable in any case.

Pete

 

[AndyCYXU]

Ok great! Thank you Pete it's the first time I ever really used the console yet I have been flying with fsuip since FSX lol,

Anyhow great to know that this is common occurrence seen previously and not necessarily affecting stability of somewhat unstable MSFS .... Pun intended, 😄