Search Issue Tracker
Duplicate
Votes
0
Found in
2017.2.0b1
Issue ID
923386
Regression
No
[DrawMeshInstanced] Instanced meshes disappear when attaching FrameDebugger to standalone player
Steps to repro:
1. Open attached project and '02_RocksScene';
2. Go to Build Settings (File -> Build Settings);
3. Check 'Development Build' and 'Autoconnect Profiler';
4. Click 'Build And Run';
5. Choose build location and click 'Save';
6. In the Player configuration window select 'Windowed' flag and click 'Play!'
7. In Editor select Frame Debugger tab and click 'Enable';
8. Click once on Player window.
Expected result:
All instanced meshes are still rendered and their draw calls are visible in Frame Debugger window (see attached expected.png screenshot).
Actual result:
Instanced meshes disappear from Player window along with their draw calls in Frame Debugger window, so there is now way of debugging instanced draw calls for them (see attached actual.png screenshot and video).
Notes:
- Reproducible in 2020.1.4f1, 2017.1.0b1, 2017.1.0f1, 5.6.1p2;
- Reproducible on both Windows 10 and OSX 10.12.5;
- Reproducible only in Standalone Player, not reproducible in Editor - inconsistent behaviour.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1261959