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

Ability to extract any number of cameras #4239

Closed
Azorlogh opened this issue Mar 17, 2022 · 2 comments
Closed

Ability to extract any number of cameras #4239

Azorlogh opened this issue Mar 17, 2022 · 2 comments
Labels
A-Rendering Drawing game state to the screen C-Usability A targeted quality-of-life change that makes Bevy easier to use

Comments

@Azorlogh
Copy link
Contributor

What problem does this solve or what need does it fill?

I have a use case with an unlimited number of cameras per frame rendering to different targets.
Before PR #3635, I stored an ID in their name to identify these cameras and extract them.
Right now it seems the extract phase puts active cameras in resources, therefore I can only extract 1 camera per frame.

What solution would you like?

A way to extract any number of cameras at once in a system.
It would be neat to be able to store data in the marker component (I don't know if the name marker would still make sense though).

What alternative(s) have you considered?

I've considered moving a single camera around a bunch of times during rendering, but this means I have to keep track of all the render targets, and also since the cameras are attached their parent's transforms I'd have to keep track of that as well.

@Azorlogh Azorlogh added C-Feature A new feature, making something new possible S-Needs-Triage This issue needs to be labelled labels Mar 17, 2022
@alice-i-cecile alice-i-cecile added A-Rendering Drawing game state to the screen C-Usability A targeted quality-of-life change that makes Bevy easier to use and removed C-Feature A new feature, making something new possible S-Needs-Triage This issue needs to be labelled labels Mar 17, 2022
@Azorlogh
Copy link
Contributor Author

As a workaround it's possible to manually extract the cameras' render phases and add the necessary components as per this system:

pub fn extract_cameras<M: Component + Default>(

@Azorlogh
Copy link
Contributor Author

Azorlogh commented Dec 7, 2022

This is obsolete since the new camera-driven rendering I believe 👍

@Azorlogh Azorlogh closed this as completed Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Usability A targeted quality-of-life change that makes Bevy easier to use
Projects
None yet
Development

No branches or pull requests

2 participants