Peter Mathen

Ok, so now with 1.5 it's gone worse. Don't know what CM needs to fix it, but at the moment it's going in the wrong direction. Before 1.5 it was a simple stutter, but know the frame stutter repeats itself in the stutter ... frame times up to 74 ms.

So this means CM has used the new SDK but has not adapted to the changes? After Kunos worked it out CM could now adapt ...

So what's going on? Just tried DR2 and the same problems as before, now with V 1.4.1 nothing changed. Stutter every few seconds, it's like the pictures freezes a short time and then jumps a few frames. This way it's no fun to play. Also the long list of other bugs even the smallest bugs as REV light on Fanatec wheels going the wrong direction are not fixed.

So finally it's clear that CM has problems to flawless use system resources like audio devices and HID devices. This results in stutter and audio cut out.

Nice finding, I would say this is a workaround (one of the many). But nevertheless it's a bug in setting up the Soft Lock feature.

Wrong, the stutter in frame pacing drops 2-5 frames and that's very annoying.

I personally think that the track degradation is only in the graphics. I don't think that the underlying 3D mesh is changing over time and so there is no way to feel the degradation.

Just to remind at the rhythmic stutter bug. To make it clear, that's a HID reading problem, here an Afterburner picture where you can see the rhythmic stutter (only sitting at the starting line) and then after a while I unplugged a device (where the larger frame drop is) and you can clearly see after that the stutter is completely gone. Even driving the stage after a while (where the graph of the GPU workload is starting to move) no frame drop at all.

To make it clear, that's a HID reading problem, here an additional Afterburner picture where you can see the rhythmic stutter (only sitting at the starting line) and then after a while I unplugged a device (where the larger frame drop is) and you can clearly see after that the stutter is completely gone. Even driving the stage after a while (where the graph of the GPU workload is starting to move) no frame drop at all.

Just to remind at the rhythmic stutter bug. This bug is nearly as annoying as the career reset, but after some discussion after the release there seems nothing happening to solve this bug. After the FFB patch I tried the game but it's not really playable if you have this stutter each few seconds. I have attached a Afterburner picture which shows very clearly these rhythmic stutter where the screen stop and drops 5 fps and the runs smooth on until the next stutter as you can see the graphics card is only used up to 35% it's not related to graphics or CPU power, it's a problem with the HID reading of DR2. Added also DxDiag_2019-05-18.txt if some of the devs would have a look.

This thread is about bugs and @Riggs you know all the bugs. This is not about fiction in CM development. CM is now for month on this bugs but they don't get them solved

FFB is still unchanged and missing beside the SAT forces. That the forces of the road are not existing could also be a problem with not existing road mesh for the physics. Maybe the road bumps and degradation are only graphics and the road is smooth as a new tarmac road. The only road feedback is coming from the cattle grids and that is completely oversaturated. If there will be no changes then DR 2 will faster abandoned by players as you can discuss.

After they announced the VR version I bought DR 2 Deluxe only to get a game full of bugs and the weakest FFB implementation I played in the past years. From my point of view in VR the FFB is even more important, so the uninformative FFB will not help to immerse in DR 2. Think about landing after a large jump in VR and feel nothing at all in your wheel ... sometimes I think they accidentally implemented the FFB code of their newest hovercraft racing game.

This reminds me at Dirt 4 times ... so wait, hope and let's see.

Thanks for this honest answer (without anything said). At least for me it seems, that CM does not have any clue what's the problem with FFB and so I lost any hope that DR 2 will ever move on to a pleasure to drive like DR 1. So after Dirt 4 I feel with DR 2 the 2nd time ripped off.