Here are the photos. My game works perfectly. Without crash
Jeremie,
I can confirm this is working for me as well. However wheel still wants to go from side to side. If you let it go it will go crazy from side to side. What can I adjust to help with that? Also vibrating sound on turning. I update to the 0.9.5
It appears from watching various youtube videos, that the on-screen steering vibration also happens on “commercial” wheels. I suspect the effect is only well noticeable on DD wheels. I will let codemasters know that… 
Here is my video on my youtube channel. You will see the FFB in game.
Unfortunately I don’t have a G-Sync monitor 
This is not a problem because we have to turn off G-Sync
The game just doesn’t like high fps according to my findings. i got it running now too since i made that video this is how i did it.
–
I think its best to run it in windowed mode i manged to run it with vsync off. but you might wanna try vsync on for more stability but even more input lag.
And clock your video card down to the lowest speeds possible in msi afterburner or other tool and put the temp/power target on its lowest to get less fps too. and probably put all graphics on max.
The ffb is really horrible. if you let your video card run at full speed it feels a hair less broken.but it crashes within a few seconds. i bet all the problems are linked to the FFB and FPS it get broken with more fps it go’s out of sync or something and than the game crashes.
I will try your solution. Seen your video, looks promising…not
Although solutions point towards V-sync and G-sync and FPS, it does seem to be an exclusive problem in combination with the SimuCUBE Firmware.
With my Logitech G29 I don’t have to alter any settings to run F1 2017 without any problems, a friend with a TS300 same thing.
Hi,
I’m one of the devs, and wanted to confirm that this issue has finally reached me Today…
We’ve not had any of these devices for our testing and/or target for 2017, hence the lack of support. Also hisorically the sim crowd is not our main target. But we’ve made some strides with 2016 - 2017 to have a more realistic tyre model and as a result data suitable to FFB, also without just faking it.
As to the issue at hand, we’ve just had a similar sim focused device (Leo Bodnar SimSteering) at our disposal, which exhibited a similar issue (vibration, inverted forces), I’ve read from some of your reports. I’ve identified the wheel reporting some state different to any other wheels we’ve used sofar (Logi, SimExperience, Fanatech Thrustmaster etc.). To this we’ve a fix, which might apply to SimuCube just the same.
Regading the lockup (the watchdog timer crashes the game after 20+ seconds of inactivity), we are stuck in the windows directinput software layers in FFB, which is puzzling. Anyhow we have it with a repro, and are exploring all the possible ways we can think of to resolve this, and allow the game to run without VSYNC Off, and at the best possible frame rate.
Thanks for all the useful information!
6 Likes
Thanks for posting here. I think we all very much appreciate your efforts! 
Hi Tamas,
thanks for the update - do you think that this issue exists also in F1 2016, as this behaves similar, sometimes it crashes when the lights turn green sone after a few seconds, and if yes is there a possibilty to fix this game also? I‘m usually driving Dirt Rally (>1000h) but I would like to race in Monte Carlo and Baku again.
Regards
Guenther
OK, it seems that the problem was in fact the same that we had just recently with the SimSteering firmware.
We get a status report from the driver, that directs the code to recovery mode continuously recreating the FFB effect. Since we don’t have this with any other devices using the same code path, I think its a Firmware problem of SimuCUBE and SimSteering.
The exact techical details in the following lines of code:
HRESULT result = DI_OK;
result = m_device->GetForceFeedbackState( &ffbState );
if ( (ffbState & DIGFFS_STOPPED) != 0)
{
// FFB effect stopped
… recovery code …
and recovery did we run, all the time, which might have confused the driver and/or clashed with the input side of the device.
F12018 will come out with this condition handled(ignored), but I’m afraid fixing it for F12016 / 2017 is on the table of the firmware developers of the problematic devices, as our support cycles have ended. Please keep in mind that I don’t have a final say on this, this is just my technical understanding.
2 Likes
Yes a firmware fix would be the best lets hope that part of code can help:) some part of it may be a firmware problem too since other wheels don’t have it.
But its weird when the game runs with “Low” fps it doesn’t crash.
the ffb is still messed up dough. so maybe this helps:)
Rest assured, that you can not judge the FFB from this broken state 
1 Like
Hi
It will be interesting to know whether this worked on MMOS, and if it did what has changed?
We have decided to take further detail discussion to email as per Codemasters request.
From what I’ve heard, things did in fact work with MMOS, but up to the point of crash, I didn’t see any functional differences in the USB packets being sent either way. The content of the packets were somewhat different, as the SimuCUBE firmware specifies different number of buttons and axises, though.
2 Likes
Hopefully it will all be situated can we at least get to feel what it is like to be behind these amazing machines
i hope it will work properly soon, than i can make a new video
We have possibly found a cause for the crash, but definitive fix is still something that needs further analysis.
1 Like
is it on the game side or on the simucube side or both 
?