search

o3de / o3de.org

The O3DE website
Other
85 stars 159 forks source link

[DOCS] Document the TerrainDataRequestBus #1337

Open FiniteStateGit opened 2 years ago

FiniteStateGit commented 2 years ago

Describe the issue briefly

The Terrain Gem provides a bus that is not tied to a specific terrain component, rather supplements and in some cases duplicates functionality provided by the individual component busses. The TerrainDataRequestBus is reflected to scripting systems whereas the component busses are largely not. I suggest to document this bus on the terrain component's reference landing page and link to it from the individual components Ebus subsections.

Which page(s) / section(s) are affected?

https://o3deorg.netlify.app/docs/user-guide/terrain/_index.md

Does this work have an engineering dependency? What is it?

None known.

FiniteStateGit commented 2 years ago

The TerrainDataRequestBus only contains broadcasts where I'd expect events. Also, I'm unable to determine some of the parameters.

sptramer commented 2 years ago

This may be a product bug or feature request if the bus isn't reflected.