Login

This Months Donations

$244.03
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
CptBrown
$5.00
yamaxe
$2.00
SiesMAN01
$2.00
Glycem
$2.00
jamesnt_408
$5.00
Number of donations
71
Highest donation
$30.00
Average donation
$3.89

InputMapper 1.7.6261 Alpha available for testing

9 months 17 hours ago #1 by Wobbles
InputMapper 1.7.6261 alpha is available for testing. There are some...

InputMapper 1.7.6261 alpha is available for testing. There are some upgrades and some bugs so please read this article.

There are several known issues and shortcommings; Known Issues:

  • Application will NOT update or notify of updates until released live (You must periodically check back in this article or forum for updated copies while in alpha/beta state)
  • Macros not finialized, if macros are important to you perhaps hold off a bit
  • Though all mappings are accessible, the mapping UI is still hackish/incomplete
  • Installer will NOT install 3rd party drivers needed for many features (This will be implemented once the drivers themselves become more stable)
    Do NOT install drivers that you do not NEED.
  • Behavior is untested and could be problematic if installing next to existing copies of IM
  • (Fixed) Icon font will not properly replace old font if you currently have IM 1.6 installed. Delete InputMapperIcons.ttf from your fonts folder prior to install IM 1.7 to fix this
  • (Enhancement) Color wheel, RGB value, HSC, need to be added to lightbar to make color picking easier.
  • (Fixed) Values for sliders in axis tuning
  • (NEW) Arrow keys not properly mappable (fixed just waiting next release)
  • Controller not recignized when connected to Sony adapter if adapter is unplugged then re-inserted while IM is running prior to controller being connected.
  • More to come as discovered...
New features added:

  • Language files updates
  • Bug and stability fixes
  • HidGuardian Support (Window 10 only) (USB & Sony Dongle only)

Download HERE: https://InputMapper.com/attachments/InputMapper (1.7.6261.24470).exe

Read article...

Please Log in to join the conversation.

8 months 4 weeks ago #2 by Thomas
Looks like this on my Windows 10 machine, black all over the window: dl.dropboxusercontent.com/u/518674/inputmapper_alpha.jpg
Have an nvidia 1060 GTX and f.lux running, nothing out of the ordinary as far as I can tell. It also happens with flux closed. InputMapper 1.6.10 UI is fine.

Please Log in to join the conversation.

8 months 4 weeks ago #3 by Wobbles
Can you post logs, I'll look

Please Log in to join the conversation.

8 months 4 weeks ago - 8 months 4 weeks ago #4 by Thomas
Thanks for the quick reply! I've attached some logs for you.

EDIT: Also whenever I select any output driver, InputMapper 1.7.6261 Alpha becomes unresponsive and has to be killed via Taskmanager.

EDIT2: I just went back and checked out Alpha 1.7 and 1.7.6246. They all paint parts of the window black here.
Attachments:

Please Log in to join the conversation.

8 months 4 weeks ago #5 by wirenut48
Try a different desktop theme, one without a black background.

Retired Electrician IBEW Local 48

Please Log in to join the conversation.

8 months 4 weeks ago #6 by Wobbles
Next version will grab your windows defined color for text aswell, should fix that issue.

Please Log in to join the conversation.

8 months 4 weeks ago #7 by Maxwellru
When I tried to emulate DS4 on DS4 it crashes! :)
Plus, start with windows setting not working.

Please Log in to join the conversation.

8 months 4 weeks ago - 8 months 4 weeks ago #8 by wirenut48

Maxwellru wrote: When I tried to emulate DS4 on DS4 it crashes! :)
Plus, start with windows setting not working.


I was having the same problem trying to use the vigemds4 as an output driver and finally gave up. I was thinking you could use it with a DS4 controller so you could use IM's custom mappings for native DS4 supported games. If you can I haven't figured out how, IM becomes unresponsive when trying to assign a profile with that output driver to the controller. The vig system virtual driver was present in the device manager without any errors.

Finally got IM to start with windows, but there has got to be a better way than using a .dll file for startup. When windows boots I got a popup asking to chose a program to open .dll files. After choosing IM and selecting always use this program, it works. But I'm assuming all .dll's are now associated with IM.

Retired Electrician IBEW Local 48

Please Log in to join the conversation.

8 months 4 weeks ago #9 by Maxwellru

wirenut48 wrote: Finally got IM to start with windows, but there has got to be a better way than using a .dll file for startup. When windows boots I got a popup asking to chose a program to open .dll files. After choosing IM and selecting always use this program, it works.

Oh! Now I know what .dll file it tries to start! LOL!

Please Log in to join the conversation.

8 months 4 weeks ago #10 by Wobbles
Wait, what's going on with DLL files o. Startup?

Please Log in to join the conversation.

Powered by Kunena Forum