Is your feature request related to a problem? Please describe.
Users have different collections of data (e.g. physics suface properties and particle effects) that they want to associate with mesh data in different ways: per collision volume, shape volume, triangle of collision mesh/volume, render mesh, or per pixel. By default, for simplicity and performance reasons, the default experience is that this data is associated per-collision. Historically, calculating collision raycasts against individual triangles in a render mesh has resulted in high computation costs in the physics systems, but as modern renderers make it possible to render highly detailed models, it is important to have highly accurate physical behaviors modeled as well.
Describe the solution you'd like
O3DE should support a physics material pipeline to enable highly accurate physical behaviors in a Physics API-agnostic and performant manner.
Is your feature request related to a problem? Please describe. Users have different collections of data (e.g. physics suface properties and particle effects) that they want to associate with mesh data in different ways: per collision volume, shape volume, triangle of collision mesh/volume, render mesh, or per pixel. By default, for simplicity and performance reasons, the default experience is that this data is associated per-collision. Historically, calculating collision raycasts against individual triangles in a render mesh has resulted in high computation costs in the physics systems, but as modern renderers make it possible to render highly detailed models, it is important to have highly accurate physical behaviors modeled as well.
Describe the solution you'd like O3DE should support a physics material pipeline to enable highly accurate physical behaviors in a Physics API-agnostic and performant manner.