Login

This Months Donations

$184.09
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
PowerToNerds
$2.00
Andy
$5.00
Mujtahid Abdulhaq
$2.00
kil
$2.00
DC
$2.00
Number of donations
66
Highest donation
$30.00
Average donation
$3.16
Log in to comment


Wobbles's Avatar
Wobbles replied the topic: #1 3 months 2 weeks ago
Weird, thats just a copy of what i dl'd from the site lol.
c0b4lt's Avatar
c0b4lt replied the topic: #2 3 months 2 weeks ago
Now there's a plugins folder
Wobbles's Avatar
Wobbles replied the topic: #3 3 months 2 weeks ago
Here is an attachment of same file, give it a shot
c0b4lt's Avatar
c0b4lt replied the topic: #4 3 months 2 weeks ago
also listed as the file version if i check the properties of InputMapper1.exe
c0b4lt's Avatar
c0b4lt replied the topic: #5 3 months 2 weeks ago
1.7.6612.19795 displays in the title bar
Wobbles's Avatar
Wobbles replied the topic: #6 3 months 2 weeks ago
when you run the IM, what version does it show?
c0b4lt's Avatar
c0b4lt replied the topic: #7 3 months 2 weeks ago
yes
Wobbles's Avatar
Wobbles replied the topic: #8 3 months 2 weeks ago
Definitely DL'ing the wrong version then, are you getting it from inputmapper.com/downloads/download/13-in...er-1-7-nightly-build
c0b4lt's Avatar
c0b4lt replied the topic: #9 3 months 2 weeks ago
2.96 MB (3,104,768 bytes) I have no AV and windows defender is not running either
Wobbles's Avatar
Wobbles replied the topic: #10 3 months 2 weeks ago
Anti virus may be flagging the folder? Do you show the zip size on disk being 3,895,296 bytes?
c0b4lt's Avatar
c0b4lt replied the topic: #11 3 months 2 weeks ago
Strange I've tried Zipware and Windows Explorer's bultin function for Zip files and both only show the Release folder in the root of the archive
Wobbles's Avatar
Wobbles replied the topic: #12 3 months 2 weeks ago
I just DL'd and it was in there, it's in the root of the zip
c0b4lt's Avatar
c0b4lt replied the topic: #13 3 months 2 weeks ago
I just grabbed InputMapper 1.7 (Nightly Build) 1.7.6612.19795 to try out and noticed theres no Plugins folder in the archive just a Release folder. Was there a change? Or did you just maybe forget to add the Plugins folder lol
Wobbles's Avatar
Wobbles replied the topic: #14 3 months 3 weeks ago
Trigger bug should be resolved in latest nightly build.
Wobbles's Avatar
Wobbles replied the topic: #15 3 months 3 weeks ago
I noticed something weird with the triggers too, looks like some bad match somewhere. Ill look into what the issue could be with USB too
wirenut48's Avatar
wirenut48 replied the topic: #16 3 months 3 weeks ago
Did get it working using the sony dongle, looks promising. One problem I noticed was the trigger axis were inverted.
wirenut48's Avatar
wirenut48 replied the topic: #17 3 months 4 weeks ago
You were right, I had copied over the existing folders. Started with a fresh appdata with only my profile folder in it, but still having issues with mappings. Created a new profile and set it to use the 360 output driver and assigned it to my 2nd gen controller using BT. Using Xinput test the right joystick moves the left stick on the screen and nothing else works. I'll give it another go when you push out a new build.

edit: I did try and run it with the scp bus disabled in the device manager, same results.
Wobbles's Avatar
Wobbles replied the topic: #18 3 months 4 weeks ago
Your log shows you have some extra files in the plugins folder, may need to delete the folder and replace it fresh, could be loading things it shouldent be.
wirenut48's Avatar
wirenut48 replied the topic: #19 3 months 4 weeks ago
Uninstalled the early 1.7 alpha, and ViGEm driver. Reinstalled IM 1.6, HIDGuardian, and ViGEm then ran the nightly build. Still won't recognize any controllers or show any driver options in the profile dropdown list. I'm done fooling with it, but will attach debug log if you want to take a look at it.
Wobbles's Avatar
Wobbles replied the topic: #20 3 months 4 weeks ago
Yea, the ViGEm version change is definitely a change from last couple releases. 1.6 and 1.7 with ViGEm 1.14 should be able to work side by side for testing purposes.
wirenut48's Avatar
wirenut48 replied the topic: #21 3 months 4 weeks ago
I do have that latest version 1.14 installed, I got that ver # above straight from the .sys driver properties. Believe that my problem is trying to run 2 different ver of 1.7 that require different versions of the driver. Anyway I'm primarily sticking to 1.6 until we get macro support for 1.7.

Might uninstall the old version of 1.7 so I can play around with the nightly builds.
Chris's Avatar
Chris replied the topic: #22 3 months 4 weeks ago
seems the nightly don't work for me...yyyyyyy
after deleting old drivers and installing the new one via powershell and starting to run the nightly build i get:

Base: ERROR
Unhandled Exception

attached the debug log
Wobbles's Avatar
Wobbles replied the topic: #23 3 months 4 weeks ago
Also, IM 1.7 has never used anything less than ViGEm 1.8, so you likely have been having issues because of using an old version.
Wobbles's Avatar
Wobbles replied the topic: #24 3 months 4 weeks ago
Nightly builds require vigem 1.14 as of the last couple. Remove the old drivers then use powershell and the commands in nefariouses wiki to install the new ones github.com/nefarius/ViGEm/wiki/Driver-Installation
wirenut48's Avatar
wirenut48 replied the topic: #25 4 months 3 hours ago
Just a bit of more info after playing around some. I have to 2nd gen controllers, only one was detectable with the older 1.7. So I tried that one on the nightly build, didn't work, but now it won't show up on the older build anymore. What a mess, now all I have is 1.6 working.

EDIT: maybe I need to uninstall the older version of 1.7 to get the nightly ones to work.