Main > Software Forum

Keyboard2Xinput (Virtual X360 pads from keyboard)

<< < (4/34) > >>

TheManuel:
Hi, there.  I think this was a project for fun by Schwing and he might have lost interest by now, as I don't see any activity on his code page.  Regardless, it is a great tool to have and I'm really glad her shared it.

SpaceNinja:
Schwing thank you so much for this utility! It is exactly what I was looking for and works great with my ipac4. I wonder how we can get this pinned as a sticky others might find this program useful? Schwing I also made a clone of your git hub to add analog support. I have never used github before I hope I did it right. I am not that great of a programmer but if anyone needs axis support check out https://gitlab.com/TheSpaceNinja/Keyboard2Xinput/blob/master/README.md at least until Schwing adds analog support to the master branch.

Schwing:
Hi all,

version 1.1.0 is out, with thumb sticks support (thanks SpaceNinja!).

Something must be wrong with my email notifications (or maybe all notifications were tagged as spam, I must look into this), as I came back here to announce a new version (thanks to a merge request by SpaceNinja!), and found out all the nice comments and requests here. This project is definitely not abandoned, though I don't have as much I time as Id like to :)
Also, since it worked exactly as I needed to, and I didn't receive (or rather thought so) any more feedback, I thought that interest was low. I don't lurk here as often as I did, so that explains a lot too.

By the way, that's exactly why it's open source: so others might improve upon it even if I don't maintain it anymore, I'm so glad that SpaceNinja took the time to do exactly that.
I'll try to answer the questions asked since my last chat with TheManuel in the next hours/days.

Schwing:

--- Quote from: TheManuel on November 25, 2018, 10:46:03 am ---I just wonder if your comment above implies that it is not possible to map one keyboard key to two xinput buttons.  This is not something I was using in my vjoy setup but would be a nice bonus.

--- End quote ---
Unfortunately, it's not possible to map one keyboard key to two xinput buttons at the moment. I do not have any real use-case in mind for now, but I'm open to suggestions. Keep in mind that I'm quite attached to keeping this software simple with very focused goals. Adding this might lead to requests for macros, and this is definitely out of scope. But I'm open to suggestions (or merge requests) about cool use cases for this :)


--- Quote from: TheManuel on November 25, 2018, 10:46:03 am ---Also, very minor but, in your computer, does the tray icon persist after you close the app?  It does in mine.

--- End quote ---
Yes, I have it too, minor but annoying. TBH I had forgotten about it as it's hidden when I use my bartop, but I've created issue #2 to not forget about it. When I find some time, I'll look into it.


--- Quote from: getnbizzy on January 09, 2019, 02:33:47 pm ---Thanks Schwing. This could be the next best thing since demulshooter. I was digging around github last night trying to figure out what was needed and found it a bit confusing. I kept getting an error when running keyboardxinput.exe and found that I didn't have my prerequisites. Any chance you'll be packaging the driver and the keyb2xinput files into a simple installer with instructions? I think it would really increase the number of people that would be willing to help test and debug this program.

--- End quote ---
Thanks for the kind words, really happy that other people find it useful.
Sorry about the confusing error when ViGem is not installed, it's something I had in the back of my mind while coding, but forgot during the polishing phase. I've added a note in my first post about that, and created a bug report. The message in the logs should be explicit as to why the software crashed, and if possible display a message box pointing the user to ViGem's install instructions. I'll try to tackle that in the next few days.

As for the ViGem installer, it's out of my hands: I'm not the developer and lack the knowledge to do that. I suppose if anyone with the knowledge gets in contact with Nefarious, he would welcome an installer. As for now, someone on their forums created a Youtube video on how to install. This is really not my thing, but in case people  prefer videos, I've linked it too.
I'm well aware that's not as easy as using an installer (I wish there was one too), but I also have faith that anyone here can follow these instructions.


--- Quote from: branded on January 13, 2019, 05:40:04 am ---Is there any possibility of your software to support 4 gamepads/players?

--- End quote ---
As pointed out by TheManuel, it does support 4 players (more if you want to! although I THINK there's a limit of 8 XInput devices). Did you manage to make it work?

SpaceNinja, do you use the IPAC4 default configuration? If so, would you mind sharing your configuration file so that I can include it in the documentation?

Schwing:
New version 1.1.1 is out (two releases in 2 days, don't get accustomed to that ;) )! This solves two issues that were reported here:
- Tray icon doesn't disappear when program exits - Issue #2
- Confusing behavior when ViGEm is not installed - Issue #3
download

For the tray icon, it now disappears correctly when exiting the program by right-clicking the icon and selecting 'Exit'. However, this did not solve the case where it's closed by AutoHotKey (that's how I use it), because AHK kills the process (I was using 'Process, Close, Keyboard2XinputGui.exe' as there's no Window), and I can't catch that to make the icon disappear.
So I went about it the other way: you can now configure a key that will exit the program. By using 'SendInput {NumpadMult}' (default configuration) with AHK, the icon disappears as expected.

As always, any feedback is welcome.

Navigation

[0] Message Index

[#] Next page

[*] Previous page