![]() ![]() One big problem was overdampening and through that lost information of what car is doing. It might be that you have testing systems that shows its the same but then its in the game engine.Īnd for the love of god dont use PC-mode in ACC, try Comp mode and be surprised. In Comp I can catch slides better, the whole FFB range is "saturated" better there is no empty feeling in middle. I know Maurice said its same but I feel its not. Now I am 100% sure that PC-mode and Compatibility mode has different FFB at least on ACC with in game profile for wheel selected in Comp mode. This then introduces the possibility of TCS/ABS or whatever you have mapped to your dials, to be in completely different positions than what your setup file calls for, leading to unexpected situations while driving, which is obviously not desireable.īoth methods have their pluses and minuses I suppose, but personally I prefer PULSE. Now, I haven't tested the following to verify, but with your encoders set to CONST, I suspect what will happen is this: same situation as before with the car set to 2 and the wheel set to 1 - despite your setup file calling for the TCS level to be 2, your wheel setting will override it and it will be set to 1 when you actually take to the track. What I usually do when I load a setup is just to pop over to the Electronics tab and check the TCS/ABS levels stored in the file, and then manually change my dials to match that when I head out on track, and from there on out, no problems. However, the advantage to this is that you can load a setup file and know that what you're feeling on track is how the car is supposed to feel, and is not being overridden by an errant dial position on your wheel that you forgot to change. ![]() To get them to match up, you would need to turn the knob to send a signal to the game, and then the game's TCS level will sync with your wheel. With the encoders set to PULSE, you will be out on track, driving around with your car's TCS set to 2, but your Fanatec wheel showing 1. Now say your car's TCS level, as saved in the car's setup file, is 2. ![]() Say one of your encoder knobs controls the TCS level, and is currently set to position 1. The second reason is a bit more complicated. I prefer to use PULSE for two reasons: one, simply because that's what finally worked for me when I was trying to figure it out on my own. Admittedly, I don't use CONST personally, that method is just what I've seen recommended here on the forums. ![]()
0 Comments
Leave a Reply. |