#58 Force Feedback issues

[Anonymous]

Originally created by: danialho... (code.google.com)@gmail.com

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.

[Anonymous]

Originally posted by: tapcio

Latest version??, please specify.

Status: Accepted

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

http://code.google.com/p/x360ce/downloads/detail?name=x360ce.App-2.0.2.76.zip&can=2&q=

[Anonymous]

Originally posted by: tapcio

Please send a screenshot of third tab inside (named as you gamepad, with its parameter) Controller 1 tab.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

Its not a controller issue, all rumble types scale and work properly in FEDit. this is new to the DLL in this version. the previous version was large rumble on both.

[Anonymous]

Originally posted by: tapcio

But is to you FFB drivers. Older build uses constant force, newer use periodic, to better simulate xinput behavior.
Take a look at my gamepad, it supports ALL effect types.
You must wait for fix in x360ce (this is low priority because this affect only XBCD) or better XBCD ffb driver.

Labels: -Priority-Medium Priority-Low

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

No, it is not my force feedback drivers.

It supports all the valid Periodic effects
See here http://gamingdeveloper.immersion.com/downloads/IStudio/HTML/ISTUDIO/Periodic_effect.html

Sine, Sawtooth and Wave effects are periodic. As per the DirectInput/Forcefeedback driver and implementation these effects work in the MS supplied testing tool.

All Params does not exist and usually introduces flaws in directinput applications that expect explicit rumble parametres.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

unless you're interested in further improving the FFB driver in xbcd :P

it effects logitech and morii drivers too.

[Anonymous]

Originally posted by: tapcio

ejocys have logitech gamepad and FFB works alright.
Also I tested x360ce on my friends Rumblepad2 and it works right.

[Anonymous]

Originally posted by: tapcio

seems ejocys also have Rumble Pad 2 :p

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

Than they are exploiting flaws or hacks in the logitech drivers for their devices.

As far as DirectX is concerned, my Periodic effects are implemented correctly.

[Anonymous]

Originally posted by: tapcio

So I cannot reproduce this problem on my gamepad, new FFB code write ejocys because I fail to do so (DI is f***** up in effect creation).
You a developer of XBCD? Or something ;)? Maybe you want help ;P?

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

I have taken up some of the work on xbcd, and ensured it is compatible with x64, the rumble driver is a bit above me but since switching to VC2010 all the rumble effects have been present and work in FEDit, emulators and games.

I did come across an issue with the lilypad pcsx2 plugin, i expect the developer of that is using a controller where the devs have been lazy and just applied all parametres to the rumble dll.

I've attached the source of the rumble driver, Its possible theres something i can add to improve compatibility, but as far as i've tested in my various rumble capable apps, games and tools, the effect types are valid.

[Anonymous]

Originally posted by: tapcio

You may also check x360ce code in svn, if you find some bug or solution of problem, please write :)

Labels: -Priority-Low Priority-Medium

[Anonymous]

Originally posted by: tapcio

I attached xinput1_3.dll from SVN, it support changing effect period from ini file:

LeftMotorPeriod=60
RightMotorPeriod=120

Values are in milliseconds, please test if changing theres values fix you problem (that is only difference between right/left motor).

Included my ini file.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

that dll isn't loading in the tester, or any of my xinput apps with the required changes to the ini.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

that dll isn't loading in the tester, or any of my xinput apps with the required changes to the ini.

it seems to be the ini itself though in this case.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

errr dll i mean.

[Anonymous]

Originally posted by: tapcio

Is work for me, Product/Instance has changed to ProductGUID/InstanceGUID, so if you have old, it will NOT load.
Please copy name, and GUIDs from you old ini to my new ini file.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

both seem to use the small motor.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

http://ptgmedia.pearsoncmg.com/images/art_fogie_xbox360/elementLinks/fogie_fig15.jpg

You can manipulate The ranges for Sawtooth up(Small motor) and for sawtooth down(large rumble) to simulate left and right periodic rumble.  Thats how i assume the Harakiri plugin for psxemu pro does it.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

by ranges, i mean wavelength.

Minimum wave length for sawtooth up vibrates the small motor only, while minimum wave length for sawtooth down vibrates the large motor only.

[Anonymous]

Originally posted by: tapcio

I don't know what is doing Harakiri plugin, but even PCX2 LiliPad does not allow my gamepad to vibrate ONLY one motor, it always use both.
I cannot write this correct because, if I write this ideally correct using MS docs, my pad does NOT vibrate at all (FFB driver?). It may be my FFB driver, so I retired from writing FFB in x360ce (I do not have any other gamepad right now).
ejocys writhed that FFB method we now using. But ejocys is not good in C++ code (is C# programmer).
For me Dinput is really not nice api, even worse is hard to make FFB effect and make it work on all gamepads, xinput in this is far superior.

[Anonymous]

Originally posted by: danialho... (code.google.com)@gmail.com

When testing with FF Rumble or Xinput rumble?

with FF Rumble, i get both left and right to work with lilypad (though the author refuses to fix up the broken periodic settings, since his control is using poorly made drivers)

with xinput rumble, i only get the right motor vibrating.

[Anonymous]

Originally posted by: tapcio

I want to make this work on as many gamepads as possible, if writhed correctly, most cheep ffb drivers will cause problems, so it must be compatible, not correct/nice.

[Anonymous]

Originally posted by: tapcio

BTW, now FFB is not main concern, but game compatibility, ie. FakeAPI functions.