This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Processing order of vertices and fragments in arm gpu

When the ARM GPU processes vertices and fragments, in what order are they distributed and processed? Vertices are in index order? What about fragment? Can we try to control the order of the index on the cpu side to improve the efficiency of the GPU?
For example: Does the optimization of the link below improve the gpu of arm? If there is an improvement, what features of the GPUs they use? github.com/.../meshoptimizer
Parents
  • In actual drawing, the index buffer only uses three vertices 0, 5, and 7. But the GPU side will also execute the calculation of the five vertices 1, 2, 3, 4, and 6?

    Yes. Don't leave unused indices in the active index range, aim to reference every vertex between min and max. 

    For implementing mesh level-of-detail, duplicate vertices and have a compacted index range for each LOD, don't make low resolution meshes by sparsely sample from the LOD 0 mesh.

Reply
  • In actual drawing, the index buffer only uses three vertices 0, 5, and 7. But the GPU side will also execute the calculation of the five vertices 1, 2, 3, 4, and 6?

    Yes. Don't leave unused indices in the active index range, aim to reference every vertex between min and max. 

    For implementing mesh level-of-detail, duplicate vertices and have a compacted index range for each LOD, don't make low resolution meshes by sparsely sample from the LOD 0 mesh.

Children
No data