Posts

Post marked as solved
1 Replies
502 Views
I have an issue with a metal vertex function - I'm just using it to transfrorm vertices from one verex buffer and store them in another (in lieu of using a compute stage).The input buffer has a vertex stride of 32-bytes and the output buffer has a stride of 48-bytes. The problem I'm having is that Metal seems to assume the wrong stride for the input buffer. No matter what I do, it seems to use the same stride as the output buffer. So when I capture a GPU frame and inspect the buffer contents, it only contains 5 items of 48-bytes each instead of 8 items of 32-bytes each.Any ideas on what might eb the cause?
Posted Last updated
.