Search Issue Tracker

Fixed in 2018.2.10f1

Fixed in 2018.2



Found in


Issue ID




Book of the dead: Environment crashes on GfxDeviceD3D11Base::DrawBuffersBatchMode when entering Play Mode in Windows 7

Graphics - General


Hwo to reproduce:
1. Download and open attached project "BotD"
2. In open About window click button "Load Book of the dead: Environment"
3. Enter Play Mode

Expected result: Unity does not crash
Actual result: Unity crashes

Reproduced with: 2018.1.9f2, 2018.2.5f1
Could not test with older versions since Book of the Dead came out with 2018.1, also 2018.3 has code compilation errors

Note: the issue only reproduces with Windows 7

Update: fixed in 2018.3.0a11 and backported to version 2018.2.10f1

Comments (3)

  1. 8c7007ee5ca61e08522478999dad9330?d=mm


    Apr 08, 2020 12:30

    resume company which leads you to make your resume standing out in others.

  2. 2190ee59a2b0d8be779aa39fca5bf0f8?d=mm


    Dec 08, 2019 12:49

    This processor logic is not working. I used several modifications to this process. I needed to create an animated field model for an educational site The design with Java helped create a pop-up for visitors. An animation bug may be related to error 3456 in the registry. You can simply replace the file.

  3. 96b3f2ac0c44fc5c9ccc88096ba02759?d=mm


    Aug 10, 2019 08:43

    Hi, i managed to fix my code without testing first. So i could run it. The issue was that the vertex count was lower than the triangle count, and that seemed to create some kind of endless loop or deadlock of some kind that killed Unity editor on my machine.
    As soon as the counts were the same, the game runs smoothly without issue.
    Also i took the code out of the Coroutine, so it does not lag behind the main thread. But i suspect this did not have any issue..

    What bothers me is that you could not reproduce the crash on win 10. Its amazing how much an old machine can do for your experience.

    Can i suggest that you develope a "emergency exit playmode" button, so even if theres an unintended deadlock or endless loop, the developer kan prematurely stop playmode, without needing to click the button. because if the editor freezes up because of bad user code, then there should be a way to stop runtime.
    Makes sence?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.