Iām using an Xbox One wireless controller with the latest version of gSender. On both Windows and PI OS, moving along X and Y sends repeated move commands rather than a continuous move. Shift+R/L/U/D Arrow works as expected. The major difference Iām seeing is the Joystick Options section of the gamepad settings. That wasnāt there in the 1.2.X version where the gamepad worked. Otherwise, all settings appear to be the same. Maybe itās an issue with the xbox driver?
The same controller worked just fine in gSender 1.2.X. Ever since I upgraded, Iāve had this problem. I tried installing gSender on a fresh install of Windows 11 and also on 64bit PI OS on an rPI 4B but saw no change.
I can post the output log and a screen capture of whatās going on later. My longmill is in a shop with no internet or cell service nearby, so that will take awhile. Any ideas in the meantime?
I had similar problems when upgrading the gSender version. I have gone back to V1.2.2 and everything works great (including the XBox wireless controller) so Iāll be staying there.
There were some drastic changes to gamepad jogging within gSender on version 1.4.x, I went into great detail in this post a while back with some other users experiencing issues with the new jogging functionality.
You would need to tune the movement distance override setting to a value that causes the least amount of lagging for jogging on your gamepad, this varies depending on everyoneās computer setup. Some users reported that 120% was a good value for them.
Please play around with the setting and let me know if you still canāt find an optimal value for jogging
Who asked for this? How many user requests did you get around this feature? Was this something the community asked for or was it a neat idea that someone had? A dynamic jog is something that I personally donāt care about. Itās one more thing to work around. I like knowing that I can set my distance to 1mm and a single push is 1mm of travel, regardless of how hard I push the joystick. If I want to move faster, Iāll change the speed to rapid and move.
Make this optional, or an advanced feature, but also bring back the same kind of movement that was in 1.2.2. Iāll decide if itās worthwhile to use in my workflow. It might not seem like a big deal to you, but as the end user, it matters.
Downgrading to have a fundamental function restored is lazy programming. For context, Iāve been in the software industry as an IC and EM for 20 years. Code is complex, and youāve probably done a complete overhaul for this, but this should be an optional feature to enable.
If a joystick is held down, I expect whatever itās controlling to move until I let go, not roughly when I let go. This is especially true for a CNC or laser that is being used by a lot of us to make some extra money in one way or another. Fine-tuning this to make it work is annoying and a waste of my time.
Iāll put it in the backlog to make this feature optional.
For the record, many users did request this feature, even if it doesnāt seem so.
gSender at the end of the day is an open-source project, where anyone can contribute to its development. If anyone would like the non-dynamic jogging feature an option sooner, feel free to open up a pull request on GitHub, otherwise, we will get to it when we can.
@walid_kayhan Iām sorry for jumping all over you like that. Dealing with similar situations at work that bled over to this. I forgot it was open source Iāve got a local change in place to test out, so no need to have it on your backlog.
Iām assuming I should branch off of dev, but your dev branch is ahead of and behind master. I thought that was a bit odd. If I shouldnāt use dev, which branch should I use? I didnāt see any docs about that is preferred, but I did find out that the wiki is wide open and can be edited by anyone.
We donāt have any support docs on how to set up gSender for development at the moment but that is something weāre looking at for the future.
We are currently utilizing the dev branch for the new UI update we are working hard on. All bug fixes and maintenance work we do for the regular releases of gSender are done on the master branch, so you would need to branch off from that. I hope that makes sense.
Yeah, that makes sense. Normally my workflows are dev branch ā master/main ā dev|stage|prod environments. All good. Iāll branch off master. Also happy to help test the local setup when you get to that, or if you do bug bounties.
The post was in reference to not finding any supporting docs for the āmany users requesting this featureā (change to jogging function) which you referred to on #Post 8/14
@walid_kayhan has presented Sienciās solution to the original question.
The topic has veared off subject into questions concerning who asked for the changes that have been instituted and why their requests have not been made public, neither of which are relevant to the issue.
Iāve got a local change in place to test out, so no need to have it on your backlog.