Discussion in 'Other' started by Lazza, Jul 18, 2015.
Thx for your sharing your workspace!
@Lazza - I'm not sure if I've already asked this in the past - what does the FFB Output % channel actually represent? I can see the Steering Shaft Torque (Nm) channel - I expect this to be the torque 'demand' for the FFB - which is then scaled depending on car-specific multiplier, theoretical torque limit (JSON) and whatever wheel software scaling there is.
Dividing the Shaft Torque by the FFB Output % doesn't appear to be a constant number - but it is in the ballpark of the max torque setting I've defined for my wheel in the controller.json...
First, and I don't know if it's you or someone else I've responded to similarly to this already, these channels - like most of them - are data produced by the game. The plugin isn't calculating them from anything else. So to a fair extent, your question isn't for me
But yes, the FFB Output is the percentage of full force your wheel (software/driver) is told to produce, by the game.
The 100% point is determined by the car-specific FFB mult, steering torque capability per controller profile (json), and the car's nominal max torque value. As you know there's a little bit of logic there determining how that ceiling is calculated.
The steering shaft torque (which presumably is calculated directly from forces acting through the steering arms from the wheels & tyres, as modeled by the suspension/chassis file) would then be divided by that threshold/maximum value, to get the FFB output % to send to the wheel. Smoothing and minimum torque may or may not be applied to the data - I'm not sure I've tested both of those.
The wheel's software setting is applied after this, as it's outside the game.
As far as variations between FFB Output and the Steering Shaft Torque channels, it could be I haven't synced the two correctly (FFB output is at 400Hz, vs 100 Hz for all other telemetry) and any influence from FFB parameters like smoothing etc won't be applied to the steering shaft torque. I don't think I've seen anything to suggest there's any other added variation to the FFB output (a cynic might suggest anything artificial is also added to the steering shaft torque value, to hide the addition ).
So I guess this is the correct setting?
What is the suggested setting for the bin width? Im new to that Motec stuff and trying to learn how to setup the dampers for the BTCC cars using Motec.
Without checking I'll guess that's the correct setting. Should be fairly apparent if you check logs with very different damping settings.
Bin width doesn't have a right or wrong. Just need enough but not too many.
I am running V188.8.131.52 of Motec i2 pro but unsure which version of Damp.
I get this error when tring to open RF2 files:
"This version of i2 only supports pro logging enabled files"
Any suggestion how to resolve please?
I'm using the same motec version, working fine.
It works fine for me as well
@petrolhead check you don't also have the old telemetry plugin installed. A surprising number of people seem to have both running...
Should this be here
I have made sure I have the correct Damp plugin but still get the same error
There seem to be two logs, one in rFactor2/\ogs a - 2022-10-31 - 16-57-15 - Brands Hatch Indy - P1.ld which is 398kb (this is the one that causes the error) and two files in a folder C:\Users\Petrolhead\Documents\acti\logs\RF2 - 2022-10-31 - 16-57-15 - Brands Hatch Indy - P1.ld which is 1177kb (This works fine) and - 2022-10-31 - 16-57-15 - Brands Hatch Indy - P1.ldx which is 9kb
So why am I getting logs in 2 different folders
MotecPlugin is the wrong one. DAMPluging the right
As your screenshot shows. You have both plugins.
Cheers, I'll remove the Motec one
Howdy chaps, just a quick one.. does anyone know if there's an issue logging engine and water temps?
Only if the car blocks them.
Oops, probably should've added it was the Oreca... Would that be expected?
I would say yes
Apologies, guilty of not using the search function
Separate names with a comma.