I was using an x-box one controller with all same previous controller button setup. I decided to change the button configuration some when I installed 1.5.4 going from 1.5.3 on a windows 11 laptop. The button I chose ( A ) to “start job” wouldn’t start the job. I knew the button works, as I was using it to select “precise” jog before. So I chose a different button to “start job” . Then that button wouldn’t start job. So I chose a different button (that was previously worked), that button would not “start job” either. Confused, I mouse clicked “start”. The job started, and with the controller I could “pause” the job. but could not continue the job by pressing the button which i had set as the “start job” button. so then I removed all other button actions except ( A ) for starting job, nothing. Chose a different button, nothing. Gsender 1.5.4 would not start a job with any controller button that I would bind it to. I could mouse click “start” on the screen, and the job would start. I reverted back to 1.5.3. I’m just posting this because I thought someone else might have the same issue.
I can confirm this is a bug in v1.5.4. I’ve added it to our backlog, it should be fixed in one of the next patch updates we release 
I just updated to version 1.5.5 I am still having the problem of no ( Bluetooth connected x-box) controller button (any button I bind as “Start job “ button) being able to “start job” . I am able to mouse click “start” on Gsender, and the job will start. Also , if I “start” by mouse click, I can pause job (with the controller) then continue the job with my “start job” button on the controller. Just in case anyone is still looking into this for the next patch.
So, I tried Gsender version 1.5.6, and it does the same thing (at least for me) as 1.5.5. I can’t initially “start job” from Xbox controller, but I can mouse click “start job”, it will start then “pause” with the controller, then resume the job with the controller. so, for me anyway, versions 1.5.4- 1.5.6 all do the same thing. Version 1.5.3 will allow starting from the controller. I had started wondering if something may be going on with the Xbox controller, that (somehow) version 1.5.3 was not having a problem with. (just documenting here) So far, I have ….
updated windows 11, restarted Gsender and windows several times, removed/disconnected the controller from Bluetooth, deleted the controlled profile, reconnected the controller via Bluetooth , set up a new profile with the controller, tested all the buttons that I’m using,
Hey Dmaden,
I have no joypad or update my gsender anymore so have no direct hand on knowledge but I’ve read a lot of problems with updating being solved deleting/renaming this file talked about here, and reinstall.
Found here:
Maybe try this going foreward to the latest version or downgrade to the version that worked for you?
thanks, Spamming_Eddie I had been able to revert to a prior version of Gsender ok, as I had saw on the facebook group before “How to revert back to a previous version that worked”.
A bit of an update for anyone that may be watching: in Gsender 1.5.6 under the automations section (file start, pause, resume, stop/end) it is possible to have gcode that will run at the beginning, pause etc. of a program run before it will actually run. I inserted into the file “start” section this character “!” , Now when I mouse click “start” the program will pause waiting for me to use the Xbox controller to actually “start/resume” ( which is acting like a pause) . So that works fine, as the clicking on “start” is like a “Prepare to run” , arming the program, then start-able from the controller.
@Dmaden thanks for the heads up, we’ll look back into it @walid_kayhan and it should be fixed for 1.5.7