-
Notifications
You must be signed in to change notification settings - Fork 2
Refactor mesh component and resources #13
Copy link
Copy link
Open
Description
invor
opened on Dec 17, 2025
Issue body actions
- move handling of sub-meshes (surface?) from the mesh component manager to the resource manager
- organise free space in a GPU mesh resource using free ranges instead of allocated/used counter
- open question: if sub-mesh is unloaded, how will the mesh component manager know? Especially for procedural meshes? Additional ready/unloaded flag in mesh component? => sub-meshes need a dedicated ready flag, also when GPU mesh resource is ready, but the data of a sub mesh has not been copied yet!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels