So I turn back with your app to the fake-wheel adjustment. I assume the dll file wasn't connected with the game. Do alt-tab to go to the editor and change the dz value, save the profile, return to the game and reload the changes on the fly by pressing F4 (or F1, as I dunno in which version I changed the default key, check the readme). Then launch the game and test it with negative dz. Also, set all axis values to their default (right click and click on "reset selected"), and filter only LX ( if that's your steering axis - Axes->Filter->LX check). Launch the editor, before running the game, and uncheck "disable xinput", as well as the rumble options ("On pressing button" & "On pressing trigger" as they will interfere with xinput FFB). So, copy xinput1_3.dll to pcars2 folder and rename it to xinput9_1_0.dll. But it's kind of strange that the you still have the dz bug as it seemed solved for the x360 gamepad.īut in your case if you want to get rid of the dz you only need the xinput dll as you don't need to fake the device. Thx gor answering / Xela1If you have it to force it to use dinput then you won't have FFB as MS doesn't give FFB for their devices under that API.
Is there a solition without the wrapper and then without that f*** deadzone when configure original via "xbox 360 pad" Using now the ACE wrapper, steering and gas/bracke and all buttons work well - but no FFB. Now in pc2 an annoying "deadzone" is still there. Works fine in AC under "xbox pad" adjustment. Hi, I'm using the simple xbox 360 Racing wheel (U-shape). Only bought the game a couple days ago so didn't check if a generic profile save can be included as for pc1. If it's possible I'll also include a save game/profile as for pc1 for quick testing. I'll try to release a corrected version in the next days, so only one xinput dll is needed.
Ps4 to xbox 360 controller xinput test download#
So you may try it and see if it helps (click on my signature to go to the utility download page), but to get it to work with pc2 you'll have to do the same steps as for pc1 but an additional step is needed: do a copy/paste of xinput1_3.dll and rename the copy as xinput9_1_0.dll (and keep both in pc2 folder) Since both versions are virtually the same (from MS documentation xinput9_1_0 is older than xinput1_3.) a simple file renaming will do the job. I checked what was wrong and it seems that pc2 uses the xinput9_1_0.dll file instead of xinput1_3.dll. I then tried my utility, that forced pc1 into "thinking" that I had a wheel instead of a gamepad but. Probably a bug unless I missed something but can't see what.
I tried then to assign the right stick just for testing purposes, and even the triggers but still no wheel movement. I had hope that an option to ditch all filtering would be present, but as you say, even setting all dampening effects to 0 and setting steering sensitivity to 50 doesn't do a real 1:1 input/output.įunny thing is that it's now possible to set a custom wheel under xinput, so I was hoping to get the wheel "treatment" without even using my utility, but after correctly assigning the axes/buttons I couldn't steer the car, brake/accel and everything else was working fine but no steering. Fortunately I can still enjoy the game as long as I stick to slower cars, but it would be great if someone knew of a fix.At least the deadzone bug present since NFS1 is finally fixed. I also messed around with controller damping, but that didn't seem to make any difference either. I've played with the sensitivity and even turned it all the way down to zero but it seems exactly the same. With my 360 controller, the sensitivity seems really high to the point where I can't even drive cars in certain classes because minor steering corrections become overcorrections that turn into over-countercorrections which turn into spinning out.
0 kommentar(er)
