Automobilista 2 Custom Force Feedback - Overview & Recommendations

try starting from zero to go up

 

greetings to all
I would like to find the line, if there is one ....
that decreases or increases the vibration in the steering wheel
when we brake?
same when accelerating....?
on the file of @stakanov, rFuktor 5.0.1.4 Original Karsten Files

thanks to you

 

Adding to the fun... I finally got my FFB the way I like it thanks to all you guys and the custom files... Then after the most recent update, my Fanatec wheel is no longer recognized by the preset I have been using for weeks. After many other posts the solution from Reiza is to create a "custom wheel" which I did, and of course, now the FFB feels completely different... frustrating to say the least. there is some hiccup in the button definition that is preventing the wheel shifting from being recognized on my previous setting so I cannot use it any longer.
So adding to the discussion, the definition of two people who have identical wheels, may not get the same feed back...

 

Is not a vibration but for the brake is the force that you feel on the steering wheel during brake, the item is
(brake_feel 1.35) up for more down for less

If you want more dynamic movment (during brake and bump) that follow weight the item is
(brake_feel_follow_weight 0.35) up for more moviment down for less

The same for accelerating but the contrary, the wheel is more light during accelerate, the item is
(accel_feel 0.35) up for more light, down for less

If you want more dynamic movment (during accel and bump) that follow weight the item is
(accel_feel_follow_weight 0.35) up for more moviment down for less

The rest and the vibration are set in the other item that are for the tyres, the slide, the drive ...... the mix of all create your outpout or your sensation with your vibration, the item are mutch.... up for more, down for less
(front_drive_torque_feel 1.10)
(rear_drive_torque_feel 0.10)
(front_tyre_stretch_feel 0.10)
(rear_tyre_stretch_feel 0.20)
(stretch_tyres_power_feel 0.50)
(front_grip_loss_feel 0.150)
(rear_grip_loss_feel 0.150)
(grip_tyres_smooth 0.000)
(slide_factor 0.85)
(on_off_throttle_feel 0.00)
(road_rolling_slip_feel 0.85)
(rear_end_feel 0.05)

To this above we have all the item for the road and the effect ... i hope help you

 

I just tried it again, and for me it doesn't seem to matter if I load V8 and another track first, I still get CTD when I go to Bathurst. Only with Atmos 1.3 and up. But the strangest thing is, it will do it even if you have Default or Default+ selected. If that file is in the Documents folder, BAM, CTD. Very strange. I put the file n the Beta forum so we'll see what they come up with. Fingers crossed someone comes up with something.

 

yes very well thank you

 

The other track is Brands Hatch?? With Super V8 try first this track, here Brands Hach fix the problem when after i go to Bathurst ... anyway is a non sens ... but thanks a lot @Michael Enright very useful and courteous

 

I tried Brands first then went to Bathurst, straight away CTD. So for me, it seems I just can not race Bathurst with the V8 and Atmos 1.3 and up.I am using 1.2 with no issues, but I prefer 1.3.3, but now that is not an option. As I said, I past the file along to Reiza. Hopefully they may be able to see something. I wondwr if @Karsten Hvidberg would have an idea?

 

I have modify the 1.3.3 in the curb and in the suspension, i copy and replace the original code (reduced the istructions and the number of lines of code), and here the file is again ok in Bathurst (if you want test i can send you), but the sensation is not pleasure and if i change one line of code in all the file the game crashed again only in this track/car ... it is as if the maximum limit of information that the game can handle has been reached, but this limit is only in one track and with only one car ... moreover the crash occurs only at the end of the track / car loading as if the game loaded something different or bad compared to all the other possible combinations

@Michael Enright with 1.3.3 yes crash but try the 1.3.4Wip in the private message ... and try first Brands ... if after this Bathurst is ok, for now is a temporary solution for use the file without limit and you can applied your harmony as before

 

I've been using R3E since it was free in SIM FEST a few days ago, them I bought it!
The FFB with my TM TS-PC (with ACELITH formula wheel) is superb, on par with rF2 (if not better).

Well, that leaved AMS2 a little behind... until I also tested @Danielkart latest release.
I do like it a lot, much better than my tweaked version of 4W variants.
I changed a few constants to tame down some FX, because I believe the result is different in ANY other wheel. Let alone subjectivity - we tend to adhere to information and sensations that already make sense to us. That's a (normal) cognitive bias (confirmation bias), no problem whatsoever. Our brains needs to train themselves to identify different stimulus as normal - it's called learning.

I'll continue to test but, for now, AMS2 is not behind, per si, just different.
And AMS2 has an advantage... FFB can be whatever we like! Anytime!

 

-

 

As usual, I attach two Atmos files (with and without YAW) ... and as usual the last original Karsten's file v.5.0.1.4 ....

Name: rFuktor 5.0.1.4 Original Karsten Files

Name: MOD ATMOS 4.1 V.1.3.3 FIX by Stakanov (with & without "Yaw") and based on 5.0.1.4

Note 1: The file ATMOS is the same of the original 1.3.3, with same harmony and same value, but now it is fixed from crash when you load the game and going to Bathurst with Super V8 car. I hope!!

Note 2: Being identical to the previous one, if you have changed some values, you can safely overwrite them without problems.

Note 3: We have found or rather you have found the solution to the steering shake when the car is starting on the track and you leave the clutch by accelerating to the maximum, here on the low end it is not a huge problem (then for now a leave the original value) but for those who want to avoid this it is enough to lower it a lot this voice (the advise is in alternative value):
(slide_factor 0.85) ----> set to 0.50 or down 0.45-0.40 to taste.
By changing down to around 0.50 to 0.45, shake is just right and completely disappears when set lower then 0.45-0.40. If you change this i think that is necessary retune some items because the attitude of the wheels/tires changes a lot in relation to slip and speed, I think that in this item (under indicate) you could start not from values in the file but from Karsten's standard values and raise/reduce them as you like or at yor taste:

(velocity_res_scale 0.40)
(velocity_res_offset 0.60)
(vel_rot_scale 1.00)
(vel_rot_limit_coef 1.00)

This will probably be tuned next time in the v 1.3.4 or 1.4 but nothing is stopping you from doing it to your taste however you like!!!

I will thanks all of you who have directly or indirectly helped me on the forum (both for the shake, for the fix and for others), I don't quote all of you so as not to forget anyone and for your privacy ... thanks again to all.
I hope you like and if you have any advice or doubts you are welcome, if you dont like use direct other I live peacefully, Instead for everything else I remain silent, really disgusting (personal taste of course)!!!

 

Thx for the file, for the fix (I did only one test and go ok ) and for all other @Stakanov, in the end there was a very specific cause for the crash??

 

It was a pleasure to help you test and it was a pleasure to talk to you (available to everything) I have not had or have problems saying/doing it publicly but I appreciate your silence and kindness ... thanks for the file, I will only replace the values that I had changed before with those of now, right??

 

Sorry for long text.... and for my english
No, there was not a specific error in the code of the 1.3.3 file and if there had been this should not have happened ... from how the defect manifested itself I am convinced that the game in the Bursthust-SuperV8 combination has a different behavior in loading of the game itself and in loading the FFB file, among other things I would tell Reiza to investigate, not for my mod (not important), but because it should not happen that the presence of a custom file in the documents folder sends the game in error and above all even if you use the Default/Default+ profile shouldn't happen that an FFB file crashes the game completely.
The use of the file should be tight and only affect the outpout sensations on the wheel and be read only on the data acquisition side (not change the game performance), if the file is bad, the FFB should either not work (flat output) or at most work out of order (inconsistent output) ... in this case the problem has traced back and invalidated both, the game (with crash when use combination car/track) and the use of Default/Default+ profiles (then again the game fail) symptom of something wrong.

Trying to keep it short, I isolated the things that are different in my MOD than the other files and Karsten's original, which are:
- The length of the code (everything is almost double);
- Some lines remodeled and not the same as Karsten's original;
- Blank spaces and added lines for info;
Then I analyzed the fact that the problem occurred only using the following files v 1.2 and 1.3.-1.3.1-1.3.2-1.3.3 and I then identified the 1.1 file as fully functional and then I identified the different code (curb and suspension) and remodeled it in 1.3.3 using the same shape as the original and 1.1 (without the precious indications of the users I would have looked for serch defects for at least a week ... many thanks).

Then I noticed/modify that:
- code of curb suspension modify with form of 1.1 otherwise the game crashed again (only in that combination of Car/Track) ;
- I don't know why but as soon as I added the smooth in the variables FL.FR.RL.RR_start_load in the suspensions the game crashed again (only in that combination of Car/Track) and then I eliminated the smooth;
- I don't know why but the bumps, the details, the kerbs and all the effects should NOT have been divided between a front code and a rear code (and then unified) but be accounted for directly in a single entity otherwise the game crashed again (only in that combination of Car/Track);
- Finally, I don't know why but I deleted all the spaces and the unused code for reduce the instruction and the lines.

Luckily, the game did not show more rubbish, but I repeat I have not made any corrections only reduced the amount of code and the aggregative form.

Can the shape and quantity of lines of code alter the stability of the game? No and in fact the defect occurred only in that combination of Car/Track ...

 

Yes and Thx for the tests!!!

 

Just a note. For me, you Atmos 1.2 did not crash for me, only 1.3 and up. I'll try your latest and see how that goes. Like you said, it's pretty bad that a file, just sitting in a folder, can crash a game, whether it is actually being used or not. Thanks for sorting it out.

 

Hi Daniel. I finally got around to trying your v36, and don't mind it. But, I still get the constant vibrations. I have turned micro_bumps_scale down, but still does it. Any suggestions please? Thank you.

 

Maybe I'm a lucky guy or maybe even the luckiest one but I haven't get any CTD of any kind since about one year ago.
Tried Single race+Test Day/SuperV8/Bathurst using Stakanov's 1.3.3

So I'm not tempted to upgrade to 1.3.3fix am I right?