1. Trouble with the game?
    Try the troubleshooter!

    Dismiss Notice
  2. Issues with the game?
    Check the Known Issues list before reporting!

    Dismiss Notice
  3. Before reporting issues or bugs, please check the up-to-date Bug Reporting Thread for the current version.
    0.32 Bug Reporting thread
    Solutions and more information may already be available.

Failed to initialize Direct3D

Discussion in 'Troubleshooting: Bugs, Questions and Support' started by CoffeeCrazy, Jan 22, 2015.

  1. CoffeeCrazy

    CoffeeCrazy
    Expand Collapse

    Joined:
    Aug 4, 2013
    Messages:
    75
    This error started at launch ever since I replaced my main monitor with a TV. Yes, the game worked perfectly fine before I got the TV. I haven't changed anything else. After re-installing the game after this error occurred, it worked about 3 times. Then the error
    started to happen again. I tried running the game through steam, or without steam. I am not using the experimental version.

    TV is 1920x1080, plugged in via HDMI.
    Windows 7 64
    i4 4770k
    16gb ddr3
    GTX 780

    This person is also having a similar issue, and also using a TV as a monitor:
    Failed-to-initialize-Direct3D!

    Help would be appreciated.
     

    Attached Files:

    • xerror.png
  2. The Sturmovik

    The Sturmovik
    Expand Collapse

    Joined:
    Aug 28, 2013
    Messages:
    110
    Maybe try running the experimental, as the devs may have fixed something in that direction with the newer updates. Other than that, if it doesn't work, you could also go back to the monitor.
     
  3. CoffeeCrazy

    CoffeeCrazy
    Expand Collapse

    Joined:
    Aug 4, 2013
    Messages:
    75
    Experimental does the same after a day or so of playing. Also going back to the monitor isn't a viable solution. That would require completely re-doing my desk, and not using the TV which I got to replace the monitor. Sure it would work, but screw that.

    If anything I would just like this to get patched eventually.

    EDIT: Nvidia's new 1/22 drivers may have fixed it, maybe. Tomorrow might be back to not working again.
     
    #3 CoffeeCrazy, Jan 24, 2015
    Last edited: Jan 24, 2015
  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