1. Do you need support for Assetto Corsa Competizione? Please use the proper forum below and ALWAYS zip and attach the WHOLE "Logs" folder in your c:\users\*youruser*\AppData\Local\AC2\Saved. The "AppData" folder is hidden by default, check "Hidden items" in your Windows view properties.
    Dismiss Notice

Fatal Errors - where is the patch?

Discussion in 'ACC General Discussions' started by Axel Vogelsang, Oct 11, 2018 at 7:21 PM.

  1. 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.;)

  2. Similar Threads
    Forum Title Date
    ACC Troubleshooting Fatal Error Today at 4:00 PM
    ACC Troubleshooting Fatal Error Sunday at 5:08 PM
    ACC Troubleshooting Fatal error- ACC CRASH Sunday at 11:04 AM
    ACC Troubleshooting Fatal Error crash Sunday at 8:25 AM
    ACC Troubleshooting Fatal Error Sunday at 6:51 AM
    ACC Troubleshooting Fatal error crash Sunday at 3:45 AM
    ACC Troubleshooting fatal error Sunday at 2:22 AM
    ACC Troubleshooting crash fatal error Saturday at 8:18 PM
    ACC Troubleshooting Fatal error crash Saturday at 4:39 PM
    ACC Troubleshooting Fatal error crash after 29 mins race Saturday at 1:18 PM
    ACC Troubleshooting Fatal Error FMallocBinned2 Saturday at 1:07 PM
    ACC Troubleshooting Fatal Error after one hour hotlaping Saturday at 12:31 PM
    ACC Troubleshooting Fatal Error Saturday at 9:52 AM
    ACC Troubleshooting Fatal error crash Saturday at 5:12 AM
    ACC Troubleshooting New fatal error Saturday at 1:23 AM

  3. 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.
    aotto1977, Typer and pons like this.
  4. dermonty

    dermonty Hardcore Simmer

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

    dermonty Hardcore Simmer

    Edit: doublepost, pls delete.
  6. PLebre

    PLebre Hardcore Simmer

    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 .
  7. 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!
  8. Of course I did.
  9. iggor

    iggor Rookie

    they will fix..all good

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice