Force feedback on DirectInput devices doesn't work

[GoogleCodeExporter]

Force feedback on DirectInput devices doesn't work

[GoogleCodeExporter]

I've added DirectInput force feedback C++ source code example from Microsoft:
x360ce\x360ce\Support\FFConst.zip
Force feedback works on my device when using this example. Maybe it will help 
since
example code is very similar to x360ce\x360ce\x360ce\directinput.cpp.

Original comment by ejocys on 24 Apr 2010 at 10:04

[GoogleCodeExporter]

i respect you for this application!keep up the good love im in love"" with my 
rumblepad2 for quite some years now and wanted to be able to play games that 
require 
xbox 360 controller .i used until now the toca edit xbox emulator but your 
version 
is much more awesome!

Original comment by [email protected] on 24 Apr 2010 at 12:46

[GoogleCodeExporter]

ok with the 2.0.2.47 i dont have vibration in assassijns creed 2 anymore in 
2.0.2.46 
it worked

Original comment by [email protected] on 24 Apr 2010 at 12:57

[GoogleCodeExporter]

ok with the 2.0.2.47 i dont have vibration in assassijns creed 2 anymore in 
2.0.2.46 
it worked

Original comment by [email protected] on 24 Apr 2010 at 12:57

[GoogleCodeExporter]

Please test r106

Original comment by tapcio on 24 Apr 2010 at 1:09

[GoogleCodeExporter]

Seems setting direction to 0,0 not works on every gamepad (works on my 
Trustmaster)

Original comment by tapcio on 24 Apr 2010 at 1:12

[GoogleCodeExporter]

i cant test it since i dont compile versions,i only download them from download 
section:(

Original comment by [email protected] on 24 Apr 2010 at 1:14

[GoogleCodeExporter]

Here

Original comment by tapcio on 24 Apr 2010 at 1:27

Attachments:

• xinput1_3.7z

[GoogleCodeExporter]

10x.testing...btw i tested soome more and it seems that vibration does not work 
everytime you enter the game is it a game problem or x360ce bug?

Original comment by [email protected] on 24 Apr 2010 at 1:33

[GoogleCodeExporter]

i tested xinput1_3.7 and its the same thing

Original comment by [email protected] on 24 Apr 2010 at 1:48

[GoogleCodeExporter]

ok i found the problem.you have to enable all fake ids to get vibration to work 
everytime you enter the game,now the problem is after you do that you cant 
enter 
x360ce again because it starts and exits instantly

Original comment by [email protected] on 24 Apr 2010 at 2:32

[GoogleCodeExporter]

Strange because for me it work in any configuration.

Original comment by tapcio on 24 Apr 2010 at 2:33

[GoogleCodeExporter]

Vibration is not working i nthe latest setup app.

it worked fine in the previous version i used which was .35

Original comment by [email protected] on 24 Apr 2010 at 2:39

[GoogleCodeExporter]

Bleh, ejocys break force with it changes, reverted this changes and build. 
Please test.

Original comment by tapcio on 24 Apr 2010 at 3:22

Attachments:

• xinput1_3.dll

[GoogleCodeExporter]

FF doesn't work for me. Tried different versions with different options. Maybe 
its
windows (I am using Windows 7 64-bit OS + DirectX February 2010).

Original comment by ejocys on 24 Apr 2010 at 8:23

[GoogleCodeExporter]

... or Logitech wheel or gremlins. Do we have anyone here with 64-bit OS and 
working
Force Feedback?

Original comment by ejocys on 24 Apr 2010 at 8:32

[GoogleCodeExporter]

I have Win 7 x64, Thrustmaster Dual Trigger 3-in-1 and working ...
I cannot debug this issue because works for me ...

Original comment by tapcio on 24 Apr 2010 at 8:58

[GoogleCodeExporter]

Original comment by tapcio on 24 Apr 2010 at 11:34

• Added labels: Priority-High, x360ce-Core
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by tapcio on 24 Apr 2010 at 11:34

[GoogleCodeExporter]

As I've mentioned before, force feedback works only with "TocaEdit XInput 3.0 
Vista"
version:
http://www.tocaedit.com/IB/index.php?automodule=downloads&req=download&id=30
included XInput DLL supports extra FF options:

UseForceFeedback=1
ForceLargeGain=8500
ForceLargePeriod=120000
ForceLargeFadeTime=10
ForceLargeFadeIn=0
ForceLargeFadeOut=0
ForceLargeStartMag=3750
ForceSmallGain=8500
ForceSmallPeriod=30000
ForceSmallFadeTime=10
ForceSmallFadeIn=0
ForceSmallFadeOut=0
ForceSmallStartMag=3750
WheelInertiaGain=2500
WheelSpringGain=5000

Source code is unavailable and I can't find decompiler which could disassemble 
it in
readable format.

Original comment by ejocys on 25 Apr 2010 at 9:21

[GoogleCodeExporter]

TocaEdit XInput 3.0 Vista by Kalessian ?
Kalessian only fix NULL pointer in original 3.0 (possible by commenting out 
some 
code).
Original  3.0 code is one big mess.
My DLL is far better. I tested it on my Thrustmaster and Logitech Rumblepad 2 
(wired) 
on different computer in AC2, works fine with FF.
I really don't know why is not working for you... 
Even in app help, is about not working FF in GTA IV on newer dll. Thats not 
true, on 
my system all works fine.
All these old setting modify fade thats are NOT needed because games in xinput 
modify 
motor speed self. Wheel option add spring inertia to effect. Seems 3.0 uses 
periodic 
force, not constant force.

You gamepad has support for constant force effect ?

Original comment by tapcio on 25 Apr 2010 at 9:42

[GoogleCodeExporter]

Sorry for double comment. In DirectInput is not possible to doing LeftMotor = 
only left 
motor in gamepad or RightMotor = only right motor ! This is DirectInput 
limitation and 
cannot be done. Maybe some FF Driver allows set effect to work in similar way, 
but 
Logitech & Thrustmaster not.

Original comment by tapcio on 25 Apr 2010 at 9:45

[GoogleCodeExporter]

> Even in app help, is about not working FF in GTA IV on newer dll

I've updated App help, now it relates to FF and Logitech Wheel

> You gamepad has support for constant force effect ?

Yes it supports "Constant" force. Microsoft 'FFConst' VC++ example use constant 
force
and it works on my wheel. PrepareForce(...) inside DirectInput.cpp is nearly
identical to code inside Microsoft's FFConst.cpp which means that code fails not
because effect parameters are missing. Maybe wheel device is not ready or 
something.

Original comment by ejocys on 25 Apr 2010 at 10:33

[GoogleCodeExporter]

PrepareForce(...) should be called twice. Both calls fails ? Log or something ?

Original comment by tapcio on 25 Apr 2010 at 10:35

[GoogleCodeExporter]

//fix Summary

Original comment by tapcio on 25 Apr 2010 at 10:49

• Changed title: Force feedback on DirectInput devices doesn't work
• Changed state: Started

[GoogleCodeExporter]

Yes, PrepareForce(...) is called twice and both fails.

11:57:16.967065:: [DINPUT] [PAD1] CreateEffect (0) failed with code HR =
DIERR_INVALIDPARAM 
11:57:16.967065:: [DINPUT] [PAD1] CreateEffect (1) failed with code HR =
DIERR_INVALIDPARAM 

I will try to get Logitech Rumble Pad II and see if this is Logitech Wheel 
specific
issue or something else.

Original comment by ejocys on 25 Apr 2010 at 11:02

[GoogleCodeExporter]

Maybe it have only one FF axis ?

Original comment by tapcio on 25 Apr 2010 at 11:16

[GoogleCodeExporter]

Please try r115.

Original comment by tapcio on 25 Apr 2010 at 11:35

[GoogleCodeExporter]

> Maybe it have only one FF axis ?

Yes, FFConst reports one axis (g_dwNumForceFeedbackAxis = 1).

 // Enumerate and count the axes of the joystick 
    if( FAILED( hr = g_pDevice->EnumObjects( EnumAxesCallback,
        ( VOID* )&g_dwNumForceFeedbackAxis, DIDFT_AXIS ) ) ){
   ...   
   }

Original comment by ejocys on 25 Apr 2010 at 11:51

[GoogleCodeExporter]

If it's a single FF axis r115 should work. Please test.

Original comment by tapcio on 25 Apr 2010 at 11:53

[GoogleCodeExporter]

Nope, doesn't work. Same:
[DINPUT] [PAD1] CreateEffect (0) failed with code HR = DIERR_INVALIDPARAM 
[DINPUT] [PAD1] CreateEffect (1) failed with code HR = DIERR_INVALIDPARAM 

AS, I've said, maybe its not the parameters (since FFConst have same "prepare 
effect"
code and works) maybe device or something is locked, not ready (some line which 
runs
before preparing FF effect function), maybe parameter type is wrong. I will try 
to
investigate differences between FFConst and c360ce since I am only one who can
replicate it, maybe I will come up with something one day :).

Original comment by ejocys on 25 Apr 2010 at 12:34

[GoogleCodeExporter]

Please test Force Editor, it can create, and test any DirectInput effect. It's 
from 
very old SDK (summer 2004).

Original comment by tapcio on 30 Apr 2010 at 4:32

Attachments:

• fedit.zip

[GoogleCodeExporter]

Greetings. At me too problems with FF, sometimes it very weak, but in most 
cases is 
absent completely. Has tested fedit, I do not have effects SPRING, FRICTION, 
DAMPER, 
INERTIA

Original comment by [email protected] on 25 May 2010 at 12:07

[GoogleCodeExporter]

x360ce at the moment use only Constant Force effects.

Original comment by tapcio on 25 May 2010 at 12:29

[GoogleCodeExporter]

what to do with the r115?

Original comment by [email protected] on 25 May 2010 at 12:37

[GoogleCodeExporter]

Verified with version 3.2.0.120 of the dll and 2.0.2.62 of the exe.  Running 
Vista
using a wired Logitech RumblePad 2.

The error is caused when using either left or right motor.

Original comment by [email protected] on 28 May 2010 at 12:42

[GoogleCodeExporter]

Dunno, I tested rev 91 on my pal wired Logitech RumblePad 2 on Windows 7 with 
newest 
drivers and FF works.

Original comment by tapcio on 28 May 2010 at 10:30

[GoogleCodeExporter]

Windows 7 x64, Saitek p580

FF working in Control Panel, but in games and such tools as XInputTest.exe and 
x360ce.exe - isnt, and the last one crashes when I trying to move "Test Left 
Motor" 
slider or "Test Right Motor"

I was trying: x360ce vibmod 3.1.4.1 and XBOX 360 Controller Emulator 2.0.2.62 
Beta 2 
(XInput 3.2.0.120) with x360ce Core (xinput1_3.dll) 3.2.0.120.

Anyway the gamepad works great in Blur, but no FF ((

Original comment by [email protected] on 31 May 2010 at 8:22

[GoogleCodeExporter]

I got one of those PS2 usb generic gamepads, and FF works great!
Tested on Batman:AA.

Original comment by [email protected] on 23 Jun 2010 at 1:43

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

@ejocys

Please test attached debug build.

Original comment by tapcio on 6 Aug 2010 at 12:03

• Added labels: x360ce-Lib
• Removed labels: x360ce-Core

Attachments:

• xinput1_3.dll

[GoogleCodeExporter]

I've got latest version. Force feedback works on Logitech RumblePad 2. It works 
on Xbox 360 Controller when in Native mode too.

I think I need to update App because sometimes DirectInput and xinput1_3 device 
order doesn't match until I re-load preset. I will check it more thoroughly 
this weekend.

@tapcio

Original comment by ejocys on 6 Aug 2010 at 7:36

[GoogleCodeExporter]

This issue was resoled in r145

Original comment by tapcio on 10 Aug 2010 at 11:20

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by [email protected] on 16 Feb 2013 at 7:12

• Changed state: Verified