PC Sims & Other Games > Assetto Corsa

Force Feed Back (FFB)...

<< < (2/4) > >>

Brindle:
Finished mine last night and I can't believe how much better it is now.  I strongly recommend doing this.   :)

Wheel: Logitech G25

Profiler Settings:
Overall Effect: 95%
Everything else 0%

In Game:
Gain: 96%
Filter: 0
Damping: 0
Min Force: 6
Kerb Effects: 40
Road Effects: 20
Sip Effects: 0

Brindle:
Ex wrote...



--- Quote ---Open office is tricky.

Double click on the .csv file.  In the screen that pops up, under "separator options", make sure "separated by" is ticked, then only "comma" and "space" have a check mark.  That will import the file properly for making the chart.

Also, for some reason, force is the "x" data range and deltaX is "y" range. Use X,Y scattered as chart type. 

Good luck.  :)

--- End quote ---

this is now pissing me off... I know how to make charts.  I do it for a living, but for some reason, I cannot get Excel or Open Office Calc to do what you and the other thread describes.

There is no point at which either chart wizard asks me what I want to put as axis columns.  I also don't understand how to scale the FOrce so that it is at 100 max as a reference.

IF you can post some screens it might be helpful, thanks.

Brindle:
After importing .csv, I assume your deleting the columns between "force" and "deltaXdiag"?  If not, that's step 2.  Next click on the "force" cell.  Now select chart and choose type "x,y scatter". 


Skip to number 3 "data series" and remove an the "force" data series.  It should now be blank.  Click add and in the right box, you should see name, x-values, y-values.  Put "force" (you should rename cell to FFB %) for the name "data range", use "force" column (cell A2-A52) as x-value and "deltaXdiag" column (cell B2-B52) as y- value. 

Now click finish and it should be done.

Don't worry about scaling, just leave it as is. 

Brindle:
Ex wrote...


Dittos on that Thank you back to you, Brindle.

What you typed helped, even if it wasn't still 100% (my fault)  I eventually abandoned Open Office and went to Excel over on the work machine...

The key to what you typed, that no one else explained previously, is that you do not need to define the data points themselves, ONLY the axes.  I work in more sophisticated programs than Excel, so doing these operations there is just so foreign.  I hate that Excel, for instance, won't let you move where your fucking columns are.  I should just be able to drag A over between B and C, and have it be okay with that.  Fucktards...

Onto the actual info of this post ;)

I'm going to post my spreadsheet with chart already formatted here so other T300RS users may just use it as a way to input their specific data from the WheelCheck app, or just trust that their wheel is exactly like mine and steal the settings based on my findings...

But before I do that, I need to find some findings :)

Please help me interpret these two charts.  I went ahead and plotted data for 100% gain down to 50% gain, because the trend was towards more linearity.

(You'll notice that the Thrustmaster curve is much more pronounced than your Fanatec wheel's.  Yours is by leaps and bounds, more linear by nature, so it appears.)

It may look like 50% is the most linear overall (Chart A), but what is going on around the 0-10% range?  See (Chart B)

(A)


Is this erratic behavior near the zero deg and force area anything to be concerned about, and based on its existence, what do you think it is suggesting as a setting for Min Force in the game?

I suppose, the erratic behavior could be smoothed out if I did several runs per % Gain.  Some of those data points could just be random outliers.  However, the trend visually does appear to be that the lower % Gain goes, the more erratic at lower % Force.  Perhaps it suggests that the THrustmaster is not very good at doing minute forces as it is at doing strong sustained forces?
(I'd be curious to see what your Fanatec wheel looks like when you reduce % Gain more than just 15%, not that you have to do it on my account)

(B)

Brindle:
REK wrote...


T500RS

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version