Force Feedback issues

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use the right motor test slider

What is the expected output? What do you see instead?
for the left slider to rumble the big motor and the right slider to rumble the 
small motor

What version of the product are you using? On what operating system?
latest

What gamepad are you using? On what version of drivers?
XBOX Stype via XBCD (rumble directions are implemented in the driver)

Please attach a log file created with Log=1 setting in x360ce.ini file.

Original issue reported on code.google.com by danialho...@gmail.com on 13 Aug 2010 at 2:13

[GoogleCodeExporter]

Original comment by tapcio on 30 Jan 2013 at 6:12

• Changed title: Force Feedback issues

[GoogleCodeExporter]

Issue 227 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:13

[GoogleCodeExporter]

Issue 228 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:14

[GoogleCodeExporter]

Issue 233 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:14

[GoogleCodeExporter]

Issue 235 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:14

[GoogleCodeExporter]

Issue 237 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:15

[GoogleCodeExporter]

Issue 246 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:33

[GoogleCodeExporter]

Issue 254 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:34

[GoogleCodeExporter]

Issue 269 has been merged into this issue.

Original comment by tapcio on 30 Jan 2013 at 6:41

[GoogleCodeExporter]

Implementation of the Type 2 rumble did go towards adding both motors properly, 
though there are still a few issues here and there.

1. The applications test sliders only rumble as long as the they are being 
dragged back and forth - this seems to just be a limitation of how the duration 
is set in the current app code.

2. sometimes at random, the vibration can get stuck on until the player does 
something that triggers vibration again - This might be a bug in bad rumble 
drivers, I know in particular that xbcd's isn't the best but others have 
reported it on Logitech drivers as well.

Original comment by danialho...@gmail.com on 31 Jan 2013 at 1:14

[GoogleCodeExporter]

I have a prefect ffb driver for tests : 
http://lavendy.net/special/driver/xi/index.html
It is a DInput ffb driver implemented on HID level but compatible to all XInput 
devices.

Original comment by tapcio on 31 Jan 2013 at 1:22

[GoogleCodeExporter]

lol, I looked at source code ... this uses xinput for force feedback, not HID 
after all ...

Original comment by tapcio on 31 Jan 2013 at 1:35

[GoogleCodeExporter]

I'm aware of Mori's FFB driver :), but since i use xbcd drivers its not 
compatible -  360 pads use a serial number so its not easy to just switch 
between xbcd and common class by  changing ports like you could with the old 
xbox controls.

I prefer XBCD, since lots of games still use Dinput and the microsoft driver 
doesn't really handle the triggers too well.

Original comment by danialho...@gmail.com on 31 Jan 2013 at 1:37

[GoogleCodeExporter]

I just wanted to let you know that I'm tracking this thread very closely and 
ready to jump on any testing needes as you guys work toward a solution for the 
vibration problem. 

I too love XBCD and hope we continue support for it. It's probably not perfect, 
but a solid driver none the less. No other driver out there gives you both 
dinput and xinput(with x360ce) and allow you to customize every stick, trigger 
and button however you wish. I've used it for years and I don't see that 
changing for many more!

Original comment by wespipe...@gmail.com on 31 Jan 2013 at 10:11

[GoogleCodeExporter]

Thanks wespipes :)

Once i get some motivation going, i'll try and get 0.2.8 pushed out - I might 
need to add a switcher tool to switch between the old rumble driver and the new 
one, Since some emulators work better with the old tool - X360CE works best 
with the new version as Motor intensity scaling works properly in it.

Original comment by danialho...@gmail.com on 31 Jan 2013 at 11:53

[GoogleCodeExporter]

Glad to hear! Squall? Sounds like a setting would be needed unless you can get 
EVERYTHING working well on the new code - hate to lose my N64 rumble or 
something. Looking forward to Win8 support also - I have the disc just sitting 
in my drawer waiting for the 0.2.8 release so I can finally install it. :)

Original comment by wespipe...@gmail.com on 1 Feb 2013 at 3:03

[GoogleCodeExporter]

N64 rumble is fine in both the old and new rumble driver

basically the new one just has a couple of lines that were unfortunately 
overlooked (due to being written in asm at the time) that fixed up the ramp and 
periodic intensity scaling.

The fixed binaries seem lose periodic effects in psxemupro plugins like 
Harakiri for some reason - but continue to work in FEDIT... so its really odd

Original comment by danialho...@gmail.com on 1 Feb 2013 at 3:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

vibration does not work correctly on - Genius MaxFire Blaze 3 (( only one 
engine is running.. please correct if not very difficult. thanks.
I tested different drivers gamepad and x360ce. on different versions of the 
drivers is also not working properly vibration. Gamepad Working 100%

Windows 7 x64 and xp x32

Original comment by Irri...@gmail.com on 4 Feb 2013 at 12:30

[GoogleCodeExporter]

test Constant, Sine and Sawtooth up and down modes in Fedit

Theres not alot we can do with gamepad drivers that fail these modes.

Original comment by danialho...@gmail.com on 4 Feb 2013 at 12:34

[GoogleCodeExporter]

Issue 444 has been merged into this issue.

Original comment by danialho...@gmail.com on 8 Feb 2013 at 6:34

[GoogleCodeExporter]

Issue 423 has been merged into this issue.

Original comment by tapcio on 11 Feb 2013 at 10:22

[GoogleCodeExporter]

Trine 2 has very little rumble with Type 2 unless the motor duration is maxed.

Even then it isn't as long as the official drivers, may have to extend the 
maximum possible duration to 1000ms

Original comment by danialho...@gmail.com on 11 Mar 2013 at 3:26

[GoogleCodeExporter]

ah, i see that its actually the app that puts a limit on it, it accepts values 
much higher than 500.

Original comment by danialho...@gmail.com on 11 Mar 2013 at 3:32

[GoogleCodeExporter]

I have the same problem: both gamepad's motors work at the same time.
Gamepad "Gembird - PC TWIN SHOCK".
Tried almost every version of x360ce - no changes.
In windows control panel gamepad's motors work properly.

Original comment by spyfox.h...@gmail.com on 28 Jun 2013 at 11:51

[GoogleCodeExporter]

rumble test in joy.cpl does not utilise the FFB library, it interfaces the 
driver directly

Original comment by danialho...@gmail.com on 28 Jun 2013 at 12:34

[GoogleCodeExporter]

Emm... so, what exactly do I need to do to fix this? Maybe some kind of special 
driver? Or is it issue of this application?

Original comment by spyfox.h...@gmail.com on 28 Jun 2013 at 4:56

[GoogleCodeExporter]

For EA games like need for speed and specially FIFA, the vibration of the 
controller is not working. Everything else is fine. Please help.

Original comment by lakshay...@gmail.com on 22 Feb 2015 at 4:18

[GoogleCodeExporter]

USB Vibration Joystick (BM)
I have this controller, in controller settings in windows the rumble works 
perfectly, but in x360ce does not detect the vibration, I've tried everything 
you said but still not working.
I'd tested with a xbox 360 wireless controller and the x360ce detects perfectly 
the rumble. 
So I don't know how to fix, help!

Original comment by jorchf...@gmail.com on 25 Feb 2015 at 4:54