Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.1.0b1
2018.2.6f1
Issue ID
1078885
Regression
Yes
MeshTopology.Quads generates a draw call that uses 3 point patches instead of 4 point
According to Unity Documentation (https://docs.unity3d.com/ScriptReference/MeshTopology.Quads.html), MeshTopology.Quads should generate a draw call that uses 4 point patches, however, it uses a 3 point patches instead.
Steps:
1. Open user's attached project "New Unity Project (3).zip"
2. Open Assets/Sccenes/SampleScene and enter Play mode
3. Record a frame using RenderDoc
4. In RenderDoc, in EventBrowser, select Camera.Render/DrawIndexed()
5. In API Inspector. select ID3D11DeviceContext::IASetPrimativeTopology/Topology
Expected: 4 point patch is used (D3D_PRIMITIVE_TOPOLOGY_4_CONTROL_POINT_PATCHLIST)
Actual: 3 point patch is used (D3D_PRIMITIVE_TOPOLOGY_3_CONTROL_POINT_PATCHLIST)
Reproduced with: 2018.1.9f2, 2018.2.8f1, 2018.3.0b2, 2019.1.0a1
Not reproduced with: 2017.4.11f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment