Fatal Errors - where is the patch?

I was really convinced that there will be a patch today to remove the frequent errors.
I am not able to do 20 laps without a breakdown of the system.
Last month KS was very quick with the first patch just one day after initial release.

 

Patience... Fixing issues in non-trivial codebases takes time. Especially if re-creation is also time consuming.

For context I run a large software team. In our world which I imagine isn't too dissimilar from Kunos...Generally speaking (unless you're lucky enough that a log/crash report tells you enough to know where the issue is) we have to get a developer(s) to the point of recreating it on their machine to see exactly where in the code it died [so imagine if some of the reports are happening only after x amount of laps are completed ... that could be in your case 30-40mins of playing until it goes boom], isolate it, fix it, then test that specific issue [maybe a few repeated runs of an hour to make sure it's truly solved], build it, then regression test the software, then release.. assuming of course you can easily recreate the error, and you don't have weird environmental factors (eg windows versions, driver issues) impacting the error.

The find, fix, build, test issue, regression test application, then release cycle can get pretty lengthy. Don't forget the other patches they might have had items well already underway before their release day.

 

Maybe this error is not so easy/quickly to fix as others.

 

Edit: doublepost, pls delete.

 

Did you report the problem on the correct forum section? Uploaling the log file?
Guess the developer will look first for issues that are effecting the larger amount of people .

 

You're right! I know the rules of finding, fixing, testing etc. as well. I was just a bit spoiled caused by the extreme quick fixes in the first release.
No offense meant!

 

Of course I did.

 

they will fix..all good