Add marker components for different camera types #1854
Labels
Comments
|
As part of the PR to fix this issue, it might be nice to demonstrate how to use it in a small example (or as part of one of the games). Combine it with |
|
While we're fixing this, we should probably just rework how Bevy's internal systems manage cameras as well. It's probably worth removing the name field entirely, to avoid exposing / using an inferior API. Now that sparse set storage exists, there's no reason not to use marker components for all of the "name X" use cases. |
|
This resulted in a confusing problem for a user trying to make their own camera variant. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problem does this solve or what need does it fill?
Selecting particular camera types is frustrating, relying on checking the name field within a system.
What solution would you like?
Add a simple marker components for
UiCameraandGameplayCamera.What alternative(s) have you considered?
Users can add their own marker components manually.
Only tag
UiCameraand useWithout<UiCamera>.Add a unique marker component for each of
2dCamera,3dCameraand so on. This is less clear, and it seems extremely rare that you will have more than one different type of gameplay camera at once.Additional context
Example of this problem in #help
The text was updated successfully, but these errors were encountered: