Search Issue Tracker
Duplicate
Votes
0
Found in
2019.1
2019.1.1f1
2019.2
2019.3
Issue ID
1151889
Regression
No
[MacOS][Frame Debugger] Debugging "Render Opaques" doesn't draw "DrawMeshInstanced"
Reproduction steps:
1. Open "addressables-build-issue.zip" project
2. Build MacOS Standalone with "Development" build enabled
3. Open and Enable the Frame Debugger and attach to build
4. Select "Render Opaques"
5. Notice that in the Standalone the four cubes aren't rendered
Expected Result: Frame Debugger draws "DrawMeshInstanced"
Actual Result: Frame Debugger doesn't draw "DrawMeshInstanced"
Reproduced with: 2019.3.0a4, 2019.2.0b4, 2019.1.4f1
Couldn't verify on 2018.4.1f1 because of Addressable errors
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
- NullReferenceException is thrown when creating the TextMeshPro component and entering the Play Mode without importing TMP Essentials
- [Linux] Player crash on Shader::SRPBatcherInfoSetup when opening player build
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
This is a duplicate of issue #1261959