Closed GoogleCodeExporter closed 9 years ago
the issue is reduced considerably if you use type 2 rumble.
Original comment by danialho...@gmail.com
on 23 Jan 2013 at 2:51
what i assume could be implemented to reduce the cases of this issue is a 10ms
thread loop.
Original comment by danialho...@gmail.com
on 23 Jan 2013 at 2:54
Do you mean motor peroid ? Mine is currently set to the default 500ms
Original comment by miguelmu...@gmail.com
on 23 Jan 2013 at 3:04
in no version of x360ce has 500ms ever been the default motor period.
Original comment by danialho...@gmail.com
on 23 Jan 2013 at 4:13
well thats weird. Anyway, i set it to 10ms and set type to 2, and now i've lost
all vibration completely. If i change the settings back, still no vibration :/
Original comment by miguelmu...@gmail.com
on 23 Jan 2013 at 4:41
left should be 120 and right 60 (or reverse it if the left motor isn't the
large motor)
Original comment by danialho...@gmail.com
on 23 Jan 2013 at 4:42
Original comment by tapcio
on 23 Jan 2013 at 4:51
Thanks for being patient. Vibration works perfectly in x360ce. however
vibration does not work in games :/
Original comment by miguelmu...@gmail.com
on 23 Jan 2013 at 6:57
which games would that be.
Original comment by danialho...@gmail.com
on 29 Jan 2013 at 7:09
Protoype 1 and 2, SW Force Unleashed 2 and Assassin's Creed (all of em). Though
strangely enough, on Skyrim it works
Original comment by miguelmu...@gmail.com
on 29 Jan 2013 at 11:37
Rumble only works on AC if you set x360ce to compatibility
might be the same for Prototype 1, i haven't played 2.
Force unleashed never had rumble on the pc afaik
Original comment by danialho...@gmail.com
on 29 Jan 2013 at 11:08
Original comment by tapcio
on 11 Feb 2013 at 10:21
going to have to add a gdb entry for AC so it gets the correct pad info.
Original comment by danialho...@gmail.com
on 15 Feb 2013 at 6:10
Original comment by danialho...@gmail.com
on 28 May 2013 at 12:08
Original issue reported on code.google.com by
miguelmu...@gmail.com
on 23 Jan 2013 at 1:56