Search Issue Tracker

Fixed in future release

Votes

0

Found in

5.6.0f3

Issue ID

898793

Regression

No

Crash in <RenderStaticBatch> and artefacts appear with a particular mesh and dynamic batching enabled

Graphics - General

-

-

Priority: 7Not yet prioritized for a release

-

Severity: 1Crash or major loss of functionality

Reproduction steps:
1. Open the attached project "case_898793_Crash.zip";
2. Open the scene "Scene";
3. Go to Game window and scale the view;
4. Observe artefacts in the view;
5. Enter Play mode;
6. Observe artefacts in the view (artefacts.gif);
7. Click on Main Camera -> Make Crash (Script) and enable "Make Crash";
8. Switch Game and Scene windows till the crash;

Actual result: in the off/on Play mode you can see some artefacts between the objects. When Camera and the objects start to change their positions and settings (when the script "MakeCrash.cs" is turned on) and switching Game and Scene windows, Unity crashes.

Expected result: there should not be the artefacts in the view and Unity should not crash.

Note: Unity crashes with NVIDIA GPU. With AMD GPU, Unity does not crash, but sometimes freezes and shows up an error (error.jpg). If you change the prefab "P_HPS_Light" into static, the crash does not happen and the artefacts in Play mode will not appear. Also, if you change the prefab "P_HPS_Light" Mesh Renderer into some basic mesh (like cube or sphere), everything will work fine. In the standalone the artefacts show up, but the crash does not happen.

Reproduced with: 5.5.0b1, 5.5.3f1, 5.6.0f3, 2017.1.0b1

Verified with 2017.3.0a2

All about bugs

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