Login

This Months Donations

$504.85
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund

Number of donations
142
Highest donation
$50.00
Average donation
$3.99

The current build while still incomplete in many areas, seems stable enough for public build so I released a new alpha. This includes the starting foundation for the keyboard and mouse input device as well as the new on screen keyboard. Both are still under development but I would like to hear feedback on them so far. Be sure to follow our new bug and feature request section for upcoming features and to report bugs and request your own features at https://inputmapper.com/support?view=bugs


Dowload IM 1.7.6277.18816a here: https://inputmapper.com/attachments/InputMapper (1.7.6277.18816).exe

Log in to comment


Zwip-Zwap Zapony's Avatar
Zwip-Zwap Zapony replied the topic: #1 1 day 15 hours ago
So... A while back, I posted about me having issues with the lightbar just being blue in InputMapper 1.7, while still working fine in InputMapper 1.6 and 2.0. It turns out that the lightbar profiles were just set for me to be based on a value, but without a set control to monitor the value from, so it had nothing to set the lightbar to. After figuring that out and fixing it to take the value from the battery level, it works just fine again. Just thought I should probably mention that.
zapoqx's Avatar
zapoqx replied the topic: #2 2 weeks 1 day ago
works. Thanks! Trying it out now
Wobbles's Avatar
Wobbles replied the topic: #3 2 weeks 1 day ago
Bug in the installer compile, Try the same DL link again.
zapoqx's Avatar
zapoqx replied the topic: #4 2 weeks 1 day ago
Previous post seemed to not go through. It seems that the installer won't run on my end over here, but the current 1.6.10 download is still fine. It gives the error
"Error Opening installation log file. Verify that the specified log file location exists and that you can write to it."

Something I'm missing?
wirenut48's Avatar
wirenut48 replied the topic: #5 2 weeks 2 days ago
wirenut48's Avatar
wirenut48 replied the topic: #6 2 weeks 2 days ago
OK hold on
Wobbles's Avatar
Wobbles replied the topic: #7 2 weeks 2 days ago
Can you post a SS of what it looks like
wirenut48's Avatar
wirenut48 replied the topic: #8 2 weeks 2 days ago
Virtual keyboard was unuseable as I am running at 2k resolutions on my TV with 175% DPI. Even some of the button text on the mapping screen are cropped with this DPI setting. If I run at 4k, window's sets the DPI to 250%.
Wobbles's Avatar
Wobbles replied the topic: #9 2 weeks 2 days ago
huh?
Maxwellru's Avatar
Maxwellru replied the topic: #10 2 weeks 2 days ago
Hello! Is it me or problem with startup with windows and IM crashing with ds4 direct is still there?
wirenut48's Avatar
wirenut48 replied the topic: #11 2 weeks 4 days ago
OK, that explains a lot, thanks.
Wobbles's Avatar
Wobbles replied the topic: #12 2 weeks 4 days ago

wirenut48 wrote: Guess I don't understand how this global macro thing is suppose to work. How do you plan to be able to do game specific macros as most macros usually are? I wouldn't want to limit Face Button 1 to only one macro to share between all game profiles. I could see having a global list then drag and drop the ones you want to use into that profile. Then you could include game specific macros and keep them sorted since you now have the ability to name them.

Anyway was just sorting through some different scenarios, conflicts, and putting out some ideas.


One of the triggers would be "loaded profile", this would allow macros to be sorted by profile. Im also going to make an "active application" trigger so you can separate by app without needing profiles
wirenut48's Avatar
wirenut48 replied the topic: #13 2 weeks 4 days ago
Guess I don't understand how this global macro thing is suppose to work. How do you plan to be able to do game specific macros as most macros usually are? I wouldn't want to limit Face Button 1 to only one macro to share between all game profiles. I could see having a global list then drag and drop the ones you want to use into that profile. Then you could include game specific macros and keep them sorted since you now have the ability to name them.

Anyway was just sorting through some different scenarios, conflicts, and putting out some ideas.
Wobbles's Avatar
Wobbles replied the topic: #14 2 weeks 5 days ago
1.7 doesn't even have BT disconnect yet
César Navarro's Avatar
César Navarro replied the topic: #15 2 weeks 5 days ago
Any progress with the shutdown function with the dongle?
Wobbles's Avatar
Wobbles replied the topic: #16 2 weeks 5 days ago
This is actually one of the exact issues that are forcing me to rethink my current approach to macros and why the current delay. I have a solution that I think will work its just a matter of shifting everything I have done thus far over to it. I still want to keep macros "global" esentially, but the idea of having to specify a device each time you wanted to create a trigger didn't seem intuitive, so instead I am going to have the macro re-instance itself for each connected controller. The down side to this is since triggers wont be created for specific controllers, users will have to get used to my generic button naming convention to create triggers, IE instead of selecting Cross or "A" it will be "Face Button 1"
wirenut48's Avatar
wirenut48 replied the topic: #17 2 weeks 5 days ago
Where is macro functionality on the development list? Really curious on how this is going to work with the macros independent of the profiles. I know functionality is not complete but was unable to assign a macro to an unbound button. Must have a way to disable controller inputs so it doesn't trigger game commands with macros.

Looking forward to sorting through this.