Automobilista v1.5.24 out now - Hotfixed to v1.5.3

Guys, an AMS1 question:

Does anyone have huge FPS drops, lap by lap getting worse, when using the Fanatec Driver 380 and connected firmwares? (CSL and CSW users in particular)

I already had stuttering issues, connected to usage of a Fanatec device, when using the 1.5.24 build, but this phenomenon showed up after the last 3 or 4 Windows updates, with newer Fanatec drivers and firmware in combination.
The FPS fluctuation and drops disappear, when disconnecting the wheel.

 

@CrimsonEminence lookup AMS1 beta topic in reiza51 pls, we had such issues when updating Fanatec SDK and there were causes and solutions to what you describe,
iirc @Marc Collins had a great deal of slowdown issues.

I do understand for you it started with driver updates, versions which were distant future at the time of "original" issues, but it's worth to revisit tried things.

 

It started with every driver, higher than 328, with its included firmwares after windows got an update some months ago.

Before that, it was already wonky with FPS/stutter/tearing, when the wheel was plugged in, but was actually eliminable by unplugging the wheel, while in the car and plugging it in again (or switching between PC->PS4->PC mode with the CSL). This is now not possible anymore...i found the override function in the controller.ini and will test this, next...

 

v1.5.16 is stable overall. (had winXP compatibility activated, forgot to deactivate, this solved some FPS problems, when using the old firmware and drivers, forgot about that) Decent FPS, still sometimes dropping a bit harsh from 220, but doesn't drop under 130 FPS most of the time. FFB feels actually better, less clipping, more steering forces and more fine detail, for some reason.

v1.5.3r and 1.5.24 are crashing, when on track, pressing ESC and exit to the pits.

It's definetly unstable, with the versions, that feature the Fanatec settings in the controls menu. I tried the override option, no change.

I'm inclined to ask, if there is a DIY possibility to completely revert the Fanatec controller workwise to the v1.5.16 one, while keeping v1.5.24/3r?

 

It shouldn't affect ams2, as it's multithreaded, only if some major system hickkup related to newer driver hoggs resources, - such thing may maniphest itself as game slowdown.

 

There are some controller.ini settings where extended features can be disabled all together.
Last bug standing which I believe we had fixed internally but didn't push yet, combination of thrustmaster and fanatec pieces of hardware causing crashes.

You can run with trace log and attach it.

 

Do you know the lines?

Interesting, i use a TH8A, indeed. Will test later, after unplugging it^^

I will do so later in 1.5.24/1.5.3r...probably not today anymore, but very interesting insight!

The FFB on the CSW here is nice with 380 and firmware bundle, to be honest. High frequencies and "noisy accelerations" in FFB are more pronounced, you can differentiate even better, when touching anything off-track. Maybe playing with the For setting could make sense, endured steering forces are a bit weaker than the 328 config. Overall "clarity" is higher, though.

 

What helped for me was deleting a file. I think its was d3d9.dll or so. Also that removed stuttering, and using the native instead of the fancy hud helped.

Thank me later!

 

It's not a GPU dependent issue. It's controller-related. FPS and functionality are normal without activated wheel.

 

Hmmm. I will test tonight.

 

@CrimsonEminence
You can try setting Fanatec rumble override="1" to disable rumble motors as first test,

second you can try this and then see if there is any change:

Fanatec controllers special features update rate="0"