[plugin] ForceFeedback is not called

I believe it can't be called, if you even can express it like that, ie - "call a ffb function".

Realfeel was based on just sending the "SteeringArmForce" or something to steering wheel - force on steering arm suspension part "inside" physics engine.

Just checked the InternalsPlugin.hpp found inside rF2 Example Plugin.7z archive and there is this, which i think you should use if you are to create ffb plugin:

Code: 
  [COLOR="#006400"]// Misc[/COLOR]
  [COLOR="#0000FF"]double [/COLOR][COLOR="#808080"]mSteeringArmForce;[/COLOR]     [COLOR="#006400"] // force on steering arms[/COLOR]
 
I checked it and it worked fine for rF1 (ForceFeedback is called).
If this method did not called in rF2 and this behavior is normal ISI should describe it.

'mSteeringArmForce' - is just a telemetry info. I.e. just info without ability to change it.
 
Last edited by a moderator:
Hi problem with the plugin too none functions are called .
startup
initialise
updatetelemetry.
On RF1 no problem but it is not working on RF2 maybe I put the dll on the wrong directory?
Thanks
 
sdecorme said:
Hi problem with the plugin too none functions are called .
startup
initialise
updatetelemetry.
On RF1 no problem but it is not working on RF2 maybe I put the dll on the wrong directory?
Thanks
Click to expand...

Plugin should be in 'Plugins' folder of the game.
rf2 example plugin works fine i.e. call startup, startsession, enterrealtime, updatetelemetry.

Right now I see only one problem - ForceFeedback is never called. And still no any reply from ISI for this one.
 
ForceFeedback() is called if you change the incoming value to a double instead of a float (it's a double in the plugin interface definition files, if you check there). So you can read the FFB value. But setting it doesn't work, the game ignores it.

You could probably use a dinput 'hack' to set the FFB on the wheel yourself? Not sure anyone will bother, probably better to wait for a later update that might enable this or give us more built-in options anyway.
 
Any update on this? Seems like changing the ffb value in a plugin is still not enabled. It might be useful to enable it to allow plugins implementing wheel-specific FFB filtering and other processing.
 
I'd like to know the status of this myself. I understand that there might be more important things to work on, but any news on this would be appreciated.
 
Hmm.. I'm having the same problem.. I need this value to make a non HID compliant FFB wheel work. Changing it from float to double didn't make any difference for me...

I'd also like to know very much what the unit of SteeringArmForce is. I get fancy values from -3000 to +3000 typically in the +/- 200 range in the CR6. Those values can't be Nm or mNm, any ideas what the actual conversion rate is?

Gesendet von meinem XT894 mit Tapatalk
 
bberger said:
Hmm.. I'm having the same problem.. I need this value to make a non HID compliant FFB wheel work. Changing it from float to double didn't make any difference for me...
Click to expand...

Silly question: did you enable the force feedback call in your header? :)

I haven't tested recent builds but had no trouble reading the incoming FFB value.
 
bberger said:
Hmm.. I'm having the same problem.. I need this value to make a non HID compliant FFB wheel work. Changing it from float to double didn't make any difference for me...
Click to expand...
You must be doing something wrong as it works for me in both the Telemetry CSV plugin and the Pedal Overlay plugin.

Can you paste the ForceFeedback lines from your .hpp and .cpp?

bberger said:
I'd also like to know very much what the unit of SteeringArmForce is. I get fancy values from -3000 to +3000 typically in the +/- 200 range in the CR6. Those values can't be Nm or mNm, any ideas what the actual conversion rate is?
Click to expand...
Newtons I believe.
 
You must log in or register to reply here.
Back
Top