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?
lowlevelsoul
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for