Automobilista 2 Custom Force Feedback - Overview & Recommendations

Oohh, nice one Daniel. I'll be sure to try this one out once I got home.

You're right about not translating the loss of grip. Which is why I mentioned the custom profiles giving me unintended "assists" previously. With the custom profiles, I can go much much faster than I'm usually able to. It's fun but I feel like I'm cheating lol.

 

does this latest file work well with the TX/T-300 bases, tried a few and some i like some i dont. I have switched off the boost from the thrustmaster settings btw

 

Hello Touc! Just try it and decide for yourself what you like

 

Due to the last note I had to change the custom again. This is now a definitive Finale Custom of mine. I will retire because now it will only be tuning in the custom. But everyone can do that according to their personal taste. I also think 1.4 of Reiza will not change anything about the custom if they do not change anything about the ffb. All the best for all of you and enjoy Ams2. Daniel

Best of Karsten Hvidberg V44 from Daniel

 

Looks like an old problem has risen again with the latest Beta for me. If any Atmos file is even in the Documents Folder, and you load the Super V8 and Bathurst first up, it completely crashes the game back to the Desktop. If I run Super V8 at any other track first, then go to Bathurst, all is fine. @Danielkart's file does not do it. Thought we had this one nailed. Any ideas?

 

sorry the custom still has a wrong value in it. I'll post the correct one tonight, daniel

 

For my problem, your file is fine. Just seems to be the Atmos ones. I do like yours, but I just can't get rid of the constant harsh vibrations. If I turn FEI right down, it certainly helps, but then I lose other information.

 

I'm currently using Karsten's latest file, and it works great with the beta.

 

Hi Michael! It has nothing to do with her problem. I just haven't changed my custom values yet when reviewing them again. I know that my custom doesn't have this problem, but thanks for your info

 

You are correct that your Custom does not cause CTD. But there is something in the your Custom that causes constant vibrations on my wheelbase. I have a CSW 2.5 with a Formula rim. I have tried changing several values, but nothing removes these vibrations. Unfortunately it is only your custom that does it to me. I am disappointed that this is the case. I will continue to try different values. Any suggestions on what I could change, that might reduce these effects? Thank you.

 

Hi Michael! Yes, I know your problem from before. Try reinstalling everything. And everything to update your base and your wheels with Fanatec. This constant looping can be felt with default and especially with default+ . The higher the speed, the harder the grinding. With the custom, everything is okay for me and also for other people. The FEI value can also cause this because it is an amplifier. If you have high FEI, definitely work with damping in-game and on the base. I hope you get this problem under control

 

J

 

Best of Karsten Hvidberg V44 from Daniel

 

I've done a bit more testing on the CTD when I load Bathurst and Super V8 first up. This crash does not happen with Danielkart's custom file. It only happens when I have an Atmos file in the AMS2 Documents Folder. At first I thought it was any Atmos file, but on further testing, it seems that the Atmos file 'Without Yaw' is fine. No CTD. As soon as I put the Atmos file 'With Yaw' in the AMS2 Documents Folder, I get the CTD. So it seems it is to do with the extra lines of code for the Yaw. I have no idea how to check the code, other than commenting out 1 line at a time to see if the CTD stops. Any help would be greatly appreciated.
BTW, this has only just started happening again with the 2 latest Beta releases of AMS2.

 

Here no problem with last ATMOS 1.4 YAW Version (and 1.3.3 FIX Yaw version), i use last game version 1.3.8.3 and I don't have access to the beta realeases, I think this anomaly is now accidental (it does not happen to everyone and only on old version 1.2-1.3.2) and only Reiza can could give eventual explanations.
We will see if the anomaly occurs when the final version of the game 1.4 is released and then we will redo the tests. But if I reiza that it receives the CTDs it does not give information on the why of the error (on old version of ATMOS), I am more inclined to think of an anomaly of the game than of the file which in any case would remain equally correctable if only we knew why, but I repeat with the 1.3.3 Fix and 1.4 ATMOS files no problem here!!!

 

+2
T300 and DD1
Same here no crash with 1.3.8.3 and ATMOS 1.4.
No access to beta for testing, i wait game 1.4 for test.

 

That is why I said it was only with the latest Beta Release from 1.4.0.2 onwards. I also have no problems with 1.3..... Just started again the other day when Beta updated. Problem could be, that if this Beta release makes it to Main, then those of us who use the Atmos 1.3 and up, may have to get use to not running V8's first up until a solution is found.

 

Well I would rest assured, as has already happened in the past yours, your in-depth analysis on the fact that the game 1.4.xxx beta does not crash by eliminating the yaw is already a very important clue if not already a partial solution , moreover (even if I am not at all good like the author) if that wasn't enough I think I can change something in the yaw by copying it from previous versions of Stakanov, if then the author would make himself heard he would not mind but I have not heard for months, I will send him a message if we have problems with versions 1.3.3 fix or with 1.4.

The fact remains that it would be useful to know from Reiza what could be the reasons that lead an FFB file to crash the game, or what rules to apply to the code so that this does not happen ... it is not only important for the ATMOS (file currently affected because at today is the olny file with different or extended code) but it is important for any ORIGINAL Karsten or DERIVED file even if for the moment not interested because not involved ... in the future it could happen with updates.

 

I asked the question on the Beta Forum, but unfortunately I have had no reply from anyone at Reiza.

 

I wouldn’t expect much aid from Reiza for one particular file that has issues, The custom files aren’t their responsibility, and in the past they have only assisted with providing core calculation adjustments and providing Karsten with possible adaptions.

the problem would likely be a case of too many physics conflicts in the code that is heavily modified and also that the file is too long and has too many things to process.
If the file is too big, it put a heavy load on memory.