You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The o3de github repo provides a good wiki section with information that is not currently available on the O3DE website. Things such as :
Using the CPU or GPU profiler
Shader compilation
IDE setup
Exporting LUA symbols to an external IDE
etc
I believe this wiki should be nuked and all of its content moved to appropriate pages, so that there is always a single source of truth, and that these section can be discovered more easily when looking for them (searching for o3de profiler on google does not return anything)
Which page(s) / section(s) are affected?
Too many to list them all
Does this work have an engineering dependency? What is it?
Yes with sig-graphics, sig-core and maybe sig-content. While it is possible to just copy-paste the actual content, it might be the opportinity to refresh some of it with images and so on, and would need to be double checked by engineer of the sig listed
The text was updated successfully, but these errors were encountered:
Describe the issue briefly
The o3de github repo provides a good wiki section with information that is not currently available on the O3DE website. Things such as :
I believe this wiki should be nuked and all of its content moved to appropriate pages, so that there is always a single source of truth, and that these section can be discovered more easily when looking for them (searching for o3de profiler on google does not return anything)
Which page(s) / section(s) are affected?
Too many to list them all
Does this work have an engineering dependency? What is it?
Yes with sig-graphics, sig-core and maybe sig-content. While it is possible to just copy-paste the actual content, it might be the opportinity to refresh some of it with images and so on, and would need to be double checked by engineer of the sig listed
The text was updated successfully, but these errors were encountered: