Search Unity

  1. Unity 2019.1 beta is now available.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We're looking for insight from anyone who has experience with game testing to help us better Unity. Take our survey here. If chosen to participate you'll be entered into a sweepstake to win an Amazon gift card.
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Unity 2018.3 is now released.
    Dismiss Notice
  6. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Unity tries to reach d3d11 with wrong path and then crash

Discussion in '2019.1 Beta' started by segant, Feb 1, 2019.

  1. segant


    May 3, 2017
    In editor log it shows as
    (Filename: C:\buildslave\unity\build\Runtime/GfxDevice/d3d11/D3D11Window.cpp Line: 186)

    As you see some slashes are backward after Runtime folder.
    It happens in keystore signing too.It's not fixed either

    Case number: 1122959
    Last edited: Feb 1, 2019
  2. superpig


    Quis aedificabit ipsos aedificatores? Unity Technologies

    Jan 16, 2011
    FWIW, the thing with the slashes is harmless.

    From looking at the editor.log attached to the bug report, it looks like
    fails for some reason, and then the crash happens when doing bookkeeping at the end of the following frame. I'll have to leave this for someone on the Graphics team to investigate exactly what is failing and why, though.