-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add a GltfProcessed
marker to objects
#144
Comments
Agreed ! That is a pattern I often use already to restrict the queries, good fit, simple, efficient. |
kaosat-dev
added a commit
that referenced
this issue
Mar 4, 2024
* chore(crates): updated crates to Bevy 0.13 * updated deps * updated / changed code where relevant * updated README files * bumped version numbers for upcoming release * updated rust-toolchain * updated assets where relevant * closes #132 * feat(bevy_gltf_components): * added GltfProcessed flag component to improve performance of iteration over added<gltfExtras> * closes #144 * light & shadow processing is now integrated, to match lights coming from Blender: you can now control whether lights cast shadows, the cascade resolution , background color etc from Blender * closes #155 * feat(bevy_registry_export): added boilerplate to make registry path relative to assets folder * closes #137 * feat(tools): added boilerplate for internal tools * clean zip file generator for blender add-on releases * example gltf file generator * feat(lighting): added components, exporter support & testing for blender-configurable shadows * added BlenderLightShadows component to bevy_gltf_components * added writing shadow information to gltf_auto_export * updated tests * closes #157 Co-authored-by: Jan Hohenheim <jan@hohenheim.ch>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As we discussed in Discord, we currently iterate over all Gltf models on every frame. If we add a
GltfProcessed
marker to the objects after reading theirGltfExtras
, we can constrain the query with aWithout<GltfProcessed>
, which is an archetype and thus makes the query not need to loop over everything.The text was updated successfully, but these errors were encountered: