Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Merged by Bors] - Directly extract joints into SkinnedMeshJoints #6833
[Merged by Bors] - Directly extract joints into SkinnedMeshJoints #6833
Changes from all commits
272e029
196cc27
b37a3cd
f07dccb
935fe6c
4c203b3
92b13ef
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this comment still relevant/would it be possible to move it to prepare?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did test this and omitting this computation dropped many_foxes by about 80us on my machine (250us->170us). However this does mean we need have to extract the inverse bindposes and move the compute to prepare them in Prepare. This basically eliminates the win we have in Prepare. It's probably that the memory bandwidth is the bottleneck here and not the actual computation: copy/move less and you'll see the bigger gains.
This might have the benefit of moving it out of the hotspot blocking both main and render worlds, but it incurs a heavier cost in render. Not sure if this is worth it.