Axis keep reassigning letter

[Jonald]

Hi John,

Having some issues with the following. It seems like Joyscan is noting that there are some issues with my joysticks for some reason.
If I put 'IgnoreDevice=0x28DE,0x11FF' under the [Joynames] section, the section will run fine but some of my assigned buttons won't work. If I leave the ''IgnoreDevice=0x28DE,0x11FF' out, FSUIPC will move to the next section for assigning a letter to the axis.

For some reason, MSFS is now crashing my PC but when the above happens, I will get the <<MISSING JOYSTICK>> next to two of the entries.

Any help would be great. 
Thanks

 

FSUIPC7.JoyScan.csvFetching info... FSUIPC7.iniFetching info...

[Jonald]

Heres the additionl logs and ini

FSUIPC7_prev.logFetching info... FSUIPC7.logFetching info... FSUIPC7 - With Ignore Axis.iniFetching info...

[John Dowson]

  On 8/28/2024 at 9:50 AM, Jonald said:

If I put 'IgnoreDevice=0x28DE,0x11FF' under the [Joynames] section, the section will run fine but some of my assigned buttons won't work. If I leave the ''IgnoreDevice=0x28DE,0x11FF' out, FSUIPC will move to the next section for assigning a letter to the axis.

Expand  

You need the IgnoreDevice ini parameter, so please leave that, If some of your buttons are not working, please generate a log file (with logging for Buttons & Keys as well as Events activated) and show me/attach that, together with your FSUIPC7.ini and FSUIPC7.JoyScan.csv files and a brief description of what button didn't work.

Also, please exit FSUIPC7 before attaching files.

How many 'RIGHT VPC MongoosT-50CM3' devices do you actually have - 3 or 4? Only 3 are detected in HID scanning but there are 4 registry entries - one may need to be removed.,

[Jonald]

FSUIPC7.JoyScan.csvFetching info... FSUIPC7.logFetching info...

Hi John,
Thanks for your reply. Please find attached the updated files. Seems when I have events logged, I seem to get all of these fuel selectors and spoiler events constantly for some reason.

You can see that the buttons I have for the seat belt signs trigger but don't activate. Like I said, with the IgnoreDevice, these will work.

There should be 3 Mongoose Devices - Where in the Regedit can I delete the other one? The log is finding the device that I am ignoring as :

  2768547 Product= Controller (XBOX 360 For Windows)
  2768547    Vendor=28DE, Product=11FF (Version 0.0)

But I don't know where this controller is coming from?

Thanks,

John

[John Dowson]

  On 8/28/2024 at 11:57 PM, Jonald said:

Seems when I have events logged, I seem to get all of these fuel selectors and spoiler events constantly for some reason.

Expand  

Many MSFS aircraft continually emit some events, and these events are different for each aircraft. You can stop such events being logged by using the DontLogThese ini parameter.

  On 8/28/2024 at 11:57 PM, Jonald said:

There should be 3 Mongoose Devices - Where in the Regedit can I delete the other one?

Expand  

Ok. The 4th registry entry isn't causing any issues so you can ignore this.

  On 8/28/2024 at 11:57 PM, Jonald said:

The log is finding the device that I am ignoring as :

  2768547 Product= Controller (XBOX 360 For Windows)
  2768547    Vendor=28DE, Product=11FF (Version 0.0)

But I don't know where this controller is coming from?

Expand  

This is something that the MSFS steam edition seems to create on start-up. If you exit FSUIPC7 and restart it once MSFS is running, you should not see this device. What that ini parameter does is to ignore this device when detected, so it shouldn't cause issues.

  On 8/28/2024 at 11:57 PM, Jonald said:

Please find attached the updated files.

Expand  

I also need to see your FSUIPC7.ini as this has also been modified...you now seem to be using a profile called 'Fenix A320 - Scoot (2018) 8K' which wasn't present in the ini files you previously attached...

  On 8/28/2024 at 11:57 PM, Jonald said:

You can see that the buttons I have for the seat belt signs trigger but don't activate. Like I said, with the IgnoreDevice, these will work.

Expand  

Did the 'safety no smoking' presets work:

  Quote

  2566734 Button changed: bRef=0, Joy=4 (F), Btn=13, Pressed
  2566734 [Buttons.Fenix A320 - Scoot (2018) 8K] 4=PF,13,CPFNX320_SAFETY_NO_SMOKING_ON,0
  2567031 Button changed: bRef=0, Joy=4 (F), Btn=13, Released
  2567390 Button changed: bRef=0, Joy=4 (F), Btn=13, Pressed
  2567390 [Buttons.Fenix A320 - Scoot (2018) 8K] 4=PF,13,CPFNX320_SAFETY_NO_SMOKING_ON,0
  2567609 Button changed: bRef=0, Joy=4 (F), Btn=13, Released
  2567781 Button changed: bRef=0, Joy=4 (F), Btn=14, Pressed
  2567781 [Buttons.Fenix A320 - Scoot (2018) 8K] 5=PF,14,CPFNX320_SAFETY_NO_SMOKING_OFF_AUTO_ON_TOGGLE,0
  2568140 Button changed: bRef=0, Joy=4 (F), Btn=14, Released
  2568312 Button changed: bRef=0, Joy=4 (F), Btn=13, Pressed
  2568312 [Buttons.Fenix A320 - Scoot (2018) 8K] 4=PF,13,CPFNX320_SAFETY_NO_SMOKING_ON,0
  2568625 Button changed: bRef=0, Joy=4 (F), Btn=13, Released

Expand  

?

Do other presets work after you have determined that the seat-belt preset doesn't? If not, you may be experiencing a WASM crash. Please see the following FAQ entry on how to determine if the WASM has crashed and if so how to prevent this: 

 

If that is not the issue, then I will need to investigate further, but I can't see how this can have anything to do with the use of the IgnoreDevice ini parameter
The seat belt presets you are using just change the value of the lvar L:S_OH_SIGNS between 1 (on) and 0 (off). When you execute the preset, does the lvar value change (you can list the values using Add-ons->WASM0>List Lvars)? If so, then the preset is working as expected. If not, can you manually change the value of this preset using the Add-ons->WASM0>Set Lvar menu item and does that have the desired effect?

For any future logs, please activate logging for Buttons & Switches, Events, Extras and WAPI->Debug level logging. No logging for Input Events necessary. You can also ignore those other events by adding the following to your Fenix [Profile.xxx] section (where xxx is the profile name):
    DontLogThese=66068,65957,66519
Probably also a good idea to set Debug level logging in the WASM (via the FSUIPC_WASM.ini file) - see the Advanced User guide on how to do this / where that file is located.

John

Edited August 29, 2024 by John Dowson
Further info added

[Jonald]

  On 8/29/2024 at 10:44 AM, John Dowson said:

 

Did the 'safety no smoking' presets work:

?

 

Expand  

No, they didn't - same issues

  On 8/29/2024 at 10:44 AM, John Dowson said:

If that is not the issue, then I will need to investigate further, but I can't see how this can have anything to do with the use of the IgnoreDevice ini parameter
The seat belt presets you are using just change the value of the lvar L:S_OH_SIGNS between 1 (on) and 0 (off). When you execute the preset, does the lvar value change (you can list the values using Add-ons->WASM0>List Lvars)? 

Expand  

When I try to do this, FSUIPC hangs and becomes unresponsive - could this be the issue some how? This happened on multiple times. 'IPC Interface and More is not responding' message

All logs and INI files attached for you

FSUIPC7.iniFetching info... FSUIPC7.JoyScan.csvFetching info... FSUIPC7.logFetching info... FSUIPC_WASM.logFetching info... FSUIPC_WASM.iniFetching info...

[John Dowson]

Sounds like your WASM module is crashing - please see the following FAQ entry: