Page 1 of 2

Bad inputs in Unity input debugger

Posted: Thu Jun 30, 2022 22:20
by radranic
I've been trying to figure out a bug in a game written in Unity that seemed to be tripping up the default input binding library for my Gladiator NXT L & R.

It would always report extra input from the stick, hat, and axis in the first event sent when pressing the binding button. The next event would be normal and have the correct button information in it.

It's using: HID::© Alex Oz 2012-2019 VKB-Sim Gladiator NXT L

This:
ButtonNoise.png

is what happens in the event before I pressed Button 11.

I've included a dump from of the log from the unity debugger.

Is this a know issue/something that can be fixed? Old HID driver or firmware?

It doesn't seem to affect gameplay if you can force the binding because of the correct event after, but it causes the Hat Up button to always be detected instead of anything else.

We've found what appears to be a work around for the binding issue, but it would be nice to figure out what's going on with the events so we can remove a bit of weird code that is there only to ignore the weird events.

Re: Bad inputs in Unity input debugger

Posted: Thu Jun 30, 2022 23:31
by fallout9
Post 2 screenshots with VKBDevCfg showing 1. Global/External panel and 2. Profile/Axes/Physical Axes.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 0:02
by radranic
Global:
LeftProfileAxes.png


Profile Axes:
LeftGlobalExternal.png

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 3:29
by fallout9
Try reflashing to the latest firmware.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 16:22
by radranic
I've now got them both running on v2.090 and it still happens sadly.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 16:58
by Ron61
See this post, do accordingly.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 18:19
by radranic
Ah! Stuff newer than the downloads page. Thanks. Will try as soon as I can.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 18:53
by radranic
I ran the config software and flashed the left one and it started throwing errors.

This is what I get in the config now:
LeftFlashed.png



I can't reflash it to something older. Did I just brick my left stick?

Nevermind, closed everything and disconnected it and reconnected and it seems to be acting normal again. Scared me.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 19:03
by radranic
Weird inputs still happening.

Currenting being reported as: "HID::VKB-Sim © Alex Oz 2021 VKBsim Gladiator NXT L "

So at least that's updated now. Oddly it's now using that HID descriptor for both sticks despite only reflashing the left for now.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 20:03
by fallout9
Screenshot of Global/External please.

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 20:08
by radranic
Here you go:
LeftGlobalExternal92.33.png



Is there any kind of logging/debugging I can enable to get you more information?

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 21:10
by Ron61
Update the right as well as the left. Is the problem gone?

Re: Bad inputs in Unity input debugger

Posted: Fri Jul 01, 2022 21:20
by radranic
Just updated the right and it's the same.

Both2.111.png

Re: Bad inputs in Unity input debugger

Posted: Sat Jul 02, 2022 9:48
by fallout9
Just to make sure - you did pressed the Default button after flashing, right?

Re: Bad inputs in Unity input debugger

Posted: Sat Jul 02, 2022 15:03
by radranic
Default then recalibrate each time yes.