Login

This Months Donations

$167.73
of $500.00 goal
Server, CDN, Network, Licensing
Development Budget
Developers Beer Fund
Recent:
Buzzy92
$5.00
Dennis Westphal
$4.00
krisen
$2.00
Billy Lee
$2.00
username: leeb427
Michael Li
$2.00
Number of donations
56
Highest donation
$20.00
Average donation
$3.43

Does Windows 10's Creators Update really break InputMapper?

Log in to comment


Wobbles's Avatar
Wobbles replied the topic: #1 7 months 2 days ago

Mustafa wrote: Hi, the problem was never with Input Mapper or with the Creator's Update. And there was no problem with the ISO's that came out early, they're exactly the same as what got released today. They're official from Microsoft.

Sorry I didn't post this earlier, but I came back to post and I noticed you locked my thread when I first reported the issue. So I didn't create a new one. But you can post what's below in the INPUT Mapper news feed so everyone can see it:

The problem is with MSI Afterburner and RTSS. More specifically RTSS (RivaTunerStatisticsServer). A lot of people use it for their videocards. Here's how to fix the issue:

Run RTSS... Click the big + button at the bottom-left corner to add a new program. Go to the InputMapper directory:

C:\Program Files (x86)\DSDCS\InputMapper

Add InputMapper.exe

Now that you see it in the left panel. Click on it, and on the right menu of RTSS, under where it says "Application Detection Level", choose "NONE".

That's it, problem solved. Hope that helps anyone who is having an issue.

Regards, Blackfyre.


To clarify the issue with getting updates early, regardless if they are final versions or not, is that you are getting them before me and it means that I cannot do anything but throw my hands in the air when things are reported because I dont install updates early.
Mustafa's Avatar
Mustafa replied the topic: #2 7 months 6 days ago
Hi, the problem was never with Input Mapper or with the Creator's Update. And there was no problem with the ISO's that came out early, they're exactly the same as what got released today. They're official from Microsoft.

Sorry I didn't post this earlier, but I came back to post and I noticed you locked my thread when I first reported the issue. So I didn't create a new one. But you can post what's below in the INPUT Mapper news feed so everyone can see it:

The problem is with MSI Afterburner and RTSS. More specifically RTSS (RivaTunerStatisticsServer). A lot of people use it for their videocards. Here's how to fix the issue:

Run RTSS... Click the big + button at the bottom-left corner to add a new program. Go to the InputMapper directory:

C:\Program Files (x86)\DSDCS\InputMapper

Add InputMapper.exe

Now that you see it in the left panel. Click on it, and on the right menu of RTSS, under where it says "Application Detection Level", choose "NONE".

That's it, problem solved. Hope that helps anyone who is having an issue.

Regards, Blackfyre.
zapoqx's Avatar
zapoqx replied the topic: #3 7 months 6 days ago
heh as I said, I had to update for work reasons. In fact, it already paid off for me with my job. Also, the iso downloader wasn't a reinstall. It functions the same way as back with the Windows 7 and Windows 8.1 to 10 upgrade back in the day. In this case, it just rerouted everything from looking on the computer for the updates over to the iso... unless you just told the updater to just upgrade the system, then it just dumped it all locally as if the update was there already. The only known issue that I can deal with for a while that is more prevalent, but not a detriment is the Sound over Optical breaking for anything more than stereo.

That said, I don't know the issues per say. I just know if I do a fresh start, it seems I have to run the Exclusive mode tool and disable Logitech HID hidden device with 1.7 to get the exclusive access, but I'm eagerly waiting for the newer version of the InputMapper as was talked about in support. I just didn't deal with 1.6 after the update because of seeing people's issues about it since Insider version and recalling the attempt at 1.7 as well that I just might as well jump in to it.
matwiej's Avatar
matwiej replied the topic: #4 7 months 6 days ago
Hello,
first, I want to say thank you for writing and supporting this superb application.
There is indeed a problem with InputMapper after installing Windows 10 Creators Update.
InputMapper seems to crash at start. I think this is due to some conflict with RivaTuner Statistics Server.
After I’ve added InputMapper.exe in Rivatuner and set Application detection level to ‘none’ problem disappeared.

InputMapper 1.6.10.19991
Rivatuner Statistics Server 6.6.0