Automobilista 2 Custom Force Feedback - Overview & Recommendations

go back one page and look for the comment from Danielkart

 

I can totally recommend that file. It's on the previous page , second post from the top .
I have a simplicity direct drive wheel and it works brilliantly for me . You will have to experiment with settings though as everyone has different opinions on what you should and shouldn't be feeling through the wheel.

 

THINGS NOT DONE AND THINGS NOT TRUE AND FALSE
- I have not changed the ATMOS code;
- there was no typing error (no one checked before speaking);
- the length of the code was not the problem (no one removed lines before sentencing);
- there were no problems related to physics (no one has proved anything) and from here to say that there was the wrong physics was as usual a coward;
- the file manifested the bug only in an explicit configuration and only if you started the game with the Super V8 / Burstust combination otherwise the game would always work in any other situation, so you will understand that supporting the above is even more cowardly.

THINGS I HAVE ADJUSTED KNOWING THE PREVIOUS PROBLEMS AND THANKS TO THOSE FEW USERS WHO HAVE TESTED IN A USEFUL AND CONSTRUCTIVE WAY (I do not quote you but you know that I thank all of you):
- Clean up only a few notes after the values (it has nothing to do with the fix but you have also come to say this);
- Removed the redundant descriptions because the meaning was already clear from the name of the item and did not require repetition (this also has nothing to do with the fix but only to avoid making someone laugh stupidly and also like);
- Removed the deadzone lines on the variables grip_fl, grip_fr, grip_rl and grip_rr, this too is not necessary for the fix if you want you can restore them from the previous file;
- Removed the lines of code of the rear wheels for the activation of curb, kerb, tire_l, tire_r & slope ... only this was the code that, even if it worked everywhere, crushed the game in the only combination described above.

All the rest of the file and the code (98%) has remained unchanged and untouched ... I sincerely hope that the author Stakanov will return, who has a greater capacity and competence than me, but I perfectly understand why this absence.

These are the new ATMOS 1.4 FIX files which, as usual for the author Stakanov, i public in YAW and NO YAW version and i attached the Original Karsten File to allow comparison.

 

It seems ok now, thanks to everyone for the efforts made, on the rest I do not comment so as not to cheer or add ugliness.
Good night.

 

Perfect, no problem with this FIX and AMS2 update 1.4.1.0 and no CTD with combination car/track V8/Bursturst thanks to all of you.

 

I will do some more checking today, but it seems the initial problem of trying to load Bathurst and Super V8 first up is fixed. Unfortunately I now get Random CTD. This may not even be related to the file so I will continue to experiment. I do not, however, get these Random CTD with the No Yaw file. Mmmmm. Hopefully just a glitch.

 

@EcoBrum, @AntoAntoDD
And it does not end here, I am with ease but calmly creating 5-6 ATMOS files, the first is the latter 1.4 FIX, then without changing the tuning, I will create the others by replacing the bases of the 5.0.1.4 code with that of Karsten's files in version 5.0.1, 5.0.1.3, Mix 5.0.1-5.0.1.4 and 5.0.1.4, so that the user can easily compare with your taste the evolution of Karsten's code in ATMOS format without differences between the values of the tunes.
From this it is easy to understand that if the user knew what to do, he could take any file (his favorite) and turn it into an ATMOS version.
Stop being respectful and we begin to understand the difference between peoples that tuning and peoples that adapting the code, even copying the values of others to learn how to achieve their goals and make comparisons correctly without anyone telling us what to do or what to use. Time for this 2-3 day!!!

For now I'd like to talk about hidden errors that don't create crushes or problems, unaware to users who boast their praise. Let's wait a few files ....

 

For now we have notice that this CTDs are random with files ffb in folder or no, and with a lot of pc but not with all pc, i think a glitch, in my pc not happen for now and i have delete all folder documents/AMS2 … but i think whitout evidence that is the game … i hope in a fast solution.

 

I played for prob 2 to 3 hours today. No crashes, glitches or anything, so you are prob correct about it being just a random thing. Hope so.

 

Even among us we have noticed this tendency to stability, I still have never had crashes, but those who have sporadically had it since yesterday morning no longer have any, a symptom of progressive stabilization of the game, if I am not saying nonsense and if I am not mistaken, silent updates have also arrived on the game's *. exe in the meantime.
Anyway good symptom thanks for the feedback @Michael Enright .

 

Maybe I will try un commenting those lines of code, and try it again with the latest AMS2 version. Can't hurt. If it works, great. If not, just comment them out again.

 

Just tried with the original coding in, no comments. It now doesn't crash when loading V8's and Bathurst, but instead crashes when you try to Exit the track. Thought we were on a winner.

 

Until yesterday it was ok, I will try again tonight at home, last night they made an update of a few Mb that I did not test, but it is clear that it is the game that behaves strangely in this combination of car/track, how can affect the exit of the race a ffb file?? And whatever it is,...
Anyway no problem we will find what does not digest that goes into the output of the file, provided that I also encounter this problem!! Always available...

 

Here I do not detect anything abnormal, even coming out of the race
I also try to do other tests

 

I know that I could have taken the screenshot at the exit of any race or just entering the game (if you have any doubts I can only make you a video), but after launching the game 15 times by selecting the race in combination Super V8 / Bursturst , at the exit I had no problems.

This is the screenshot at the exit of the race from which you can also view the version of the game that I have on my pc (after the further update and using the ATMOS 1.4 FIX file).


At this point I would not be strangled that in a few days the file can be restored to the previous conditions, but since I am not the creator, this result is enough for me for now.

I have the 5 ATMOS files ready in this 1.4 FIX configuration (from 5.0.1 to 5.0.1.4) I will wait to be sure that the game and the file are stable and then I will publish them, it makes no sense if I have to rearrange something.
I also don't forget that I also promised you a post about errors not detected by users on this forum, which do not create crushes to the game, but which are sold like gold in the market.

 

Here is all ok, same version game.

 

Well you guys are lucky. I have turned everything off that is normally on, and still get the CTD. Oh well, I'll just stick with the modded 1.4 or the No Yaw versions. Still great versions.

 

Yes @Michael Enright you are right, everything works with modded version 1.4 (not the original where still CTD) so I'm talking about Manolo's ATMOS 1.4 FIX both with YAW and without YAW

 

That's the strange thing. The original 1.4 Without Yaw works without CTD, it's only the one With Yaw.

 

I've been trying The "ffb_custom_settings - ATMOS 5.0.1.4 - MOD V1.4 FIX (WITH YAW)" and like it, except for the "front bite". At this point, I guess, my problems has more to do with FFB perceptions than physics engine.

What I'm seeking: more FFB around the center - example: turning the wheel in a long straight should produce more FFB strenght, I mean, the FFB should depend more on speed and less on wheel angle (effective lateral forces). As a matter of fact, it could be lighter, that it is now, in slow turns (<100Km/h, for instance).
I want the FFB to have a more logarithmic curve than an exponencial one (it appears to have now).

What I may need: Where (if possible...) can I get some descriptions of custom file variables?