Error 2 bad number format when probing from xbox controler

Community Support ❓ Something's Up
1

Hi, so I manage to connect my xbox controller.

I map begin probing on the A button. I’m using the autoprobe. Longmill 2.5, gSender1.5.6

When I start the probe from the gSender interface, it works perfect but when I use the controller, the tool goes down and I get a message Error 2 bad number format.

Any advice?

2

@JMenard Welcome to the group!

Did you look at the console to see what input the controller produced? It’s just a shot in the dark but I’m wondering if maybe the controller button ‘fired’ more than once or something along those lines.

Comparing the console output from both ways of starting a probe might provide some insight into the issue.

EDIT: There might be a problem with shortcuts. Basing this on:

and

Those both mention Alarm 2. Did you get Alarm 2 or Error 2?

3

Thanks @_Michael I will check the console output this weekend and compare them. The message says Error 2

4

The fix for this will be part of 1.5.7, thanks for the report.

5

Thank you will wait for it then

6

@JMenard it came out today and should be fixed. My related issues have been.

7

Will update and test this weekend then

8

Just tested it works well thank you. However ran into a new problem. Will open another thread