-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Gpu Driven Rendering By Default #1342
Copy link
Copy link
Closed
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-PerformanceA change motivated by improving speed, memory usage or compile timesA change motivated by improving speed, memory usage or compile times
Metadata
Metadata
Assignees
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-FeatureA new feature, making something new possibleA new feature, making something new possibleC-PerformanceA change motivated by improving speed, memory usage or compile timesA change motivated by improving speed, memory usage or compile times
Performant Rendering
the default gpu pipeline used in bevy should be one that takes in to consideration concepts from guides like this https://vkguide.dev/docs/gpudriven/gpu_driven_engines/. In this way, bevy can render objects with extreme performance, and will never bottleneck on the cpu. In general, GPU Driven Rendering has some tradeoffs that would need to be made, but would increase performance, sustainability, and would enhance any future efforts to include ray-tracing and other novel tech.