• "My mind is always racing." - Justin Bieber
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Dear Guest. Follow RaceDepartment on Twitter, Facebook, Instagram, Twitch, Steam and YouTube.

LATEST WIN 10 UPDATE HAS CAUSED SOME ISSUES

Discussion in 'Automobilista' started by Buster, Sep 15, 2017.

  1. Buster

    Buster
    Premium

    Messages:
    217
    Ratings:
    +190
    For those of you whom may not already know ..

    The latest Windows 10 update from this week does not seem to like the Java version used with Dynhud.

    They are (Reiza Studio) currently working on a "hotfix" ...you can get the sim working by removing d3d9.dll from the sim folder (root directory)........or of course maybe a better idea, just rename this file ....d3d9_2.dll

    Of course if you rename this file or remove it, Dynhud and most 3rd party software will not run, this also includes SweetFX

    I personally have been able to run the sim still using the d3d9.dll file, but can not select anymore than approximately 10 AI to practice/race against.

    Source - Reiza Forums
     
    • Like Like x 1
    • Love Love x 1
  2. Marc Collins

    Marc Collins

    Messages:
    546
    Ratings:
    +158
    The actual instructions are:

    Until we force a hot fix through, you can get the game working again by removing d3d9.dll from the game folder (rename d3d9_2.dll to d3d9.dll if you wish to keep SweetFX).

    This will stop Dynhud from loading in the short term.

    You can also simply rename d3d9.dll to d3d9.dll.temp before renaming d3d9_2.dll to d3d9.dll.
     
  3. Phil Etty

    Phil Etty

    Messages:
    47
    Ratings:
    +2
    Hi,
    Can anyone help to advise what error you get before the hotfix? I am able to select a car, load track. Get taken to car in the garage, but then game crashes. Is that this error or something that else?
     
  4. Buster

    Buster
    Premium

    Messages:
    217
    Ratings:
    +190
    @Phil Etty
    Yes that is exactly what happens, you can of course (although extreme) uninstall the latest update that is causing the problem .. this is the problem update ..(KB4038788) or of course just wait for the "hotfix"
     
    • Love Love x 1
  5. Tony

    Tony
    APIA RACING Staff Premium

    Messages:
    1,412
    Ratings:
    +544
  6. Nick Milton

    Nick Milton
    Nick Premium

    Messages:
    928
    Ratings:
    +263
    Mine seems solved, removed files, and then won update uninstalled my pedals, hence no brakes, I did integrity check, reinstalled it all, flicked on pretty much everything in nividea control panel, and stable? No stutters, no tearing, just good. May be different in multiplay I guess, we'll see.
     
  7. Andrew

    Andrew
    I'm not lazy, I'm just very relaxed. Staff Premium

    Messages:
    4,224
    Ratings:
    +2,758
    Just saying.... ;)

    Hz0hQdo.jpg :cool::p
     
    • Love Love x 1
  8. Andy Jackson

    Andy Jackson
    Retro PC Sim Racer Premium

    Messages:
    6,589
    Ratings:
    +3,049
    So glad I stuck with Windows 7.:thumbsup:
     
    • Agree Agree x 1
  9. BillGuy

    BillGuy

    Messages:
    29
    Ratings:
    +5
    Is this problem is being discussed in any further depth anywhere? The IT nerd in me is just curious to know more about what the actual issue is. I’ve seen two items mentioned as a possible cause: Java used by DynHUD and something inside the September Cumulative update KB403878. The Microsoft article for KB4038788 only mentions one item that jumps out as a candidate to me. “Security updates to Microsoft Graphics Component” in the final bullet point. Maybe this change caused the DynHUD Java problems interacting with the display?

    Personally, I’m not at all a fan of any application using its own app-local copy of Java. That was one of the contributing factors for me abandoning DynHUD and switching to GID. If you’re going to use Java, make an OS-installed JRE a requirement and call that. I fully recognize that Java is no longer the security and update nightmare it was 5+ years ago. Still, I don’t want to spend any effort worrying about an AMS-specific instance of it even if the degree of concern is minor.