Skip to content
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

Handle case where render component not always on root object #3

Closed
lukeskt opened this issue Sep 15, 2021 · 1 comment
Closed

Handle case where render component not always on root object #3

lukeskt opened this issue Sep 15, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@lukeskt
Copy link
Owner

lukeskt commented Sep 15, 2021

There is a hack fix implemented where code tries to find render component on same object, then looks up if you have specified one manually, then if those fail gets the first render component it finds on child.

Not ideal, is there a way to composite child object render components together?

@lukeskt lukeskt self-assigned this Sep 15, 2021
@lukeskt lukeskt added the bug Something isn't working label Sep 15, 2021
@lukeskt
Copy link
Owner Author

lukeskt commented Dec 15, 2021

rewrote focus component to resolve this and other issues, should now account for renderers (and colliders) on parent object or combination of those on children through a combined render bounds.

@lukeskt lukeskt closed this as completed Dec 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant