Artur Zięba
Artur Zięba
## Describe the issue On the "Installing O3DE for Linux" documentation page in the "Installing O3DE from a Snap package" section, a link to the O3DE page for manual snap...
## Describe the issue briefly Currently, there is no dedicated documentation page for the Asset Browser. It should be noted that other similar "core" tools have such pages, for example...
## Describe the issue Description under the *Assign a physics material* section contains information and 3 screenshots referencing *PhysX Collider* component. This component was split into *PhysX Mesh Collider* and...
## Describe the issue briefly Currently, on the https://www.o3de.org/docs/user-guide/programming/gems/creating/ documentation page, the Gem registration commands are global, and the deregister command listed on the https://www.o3de.org/docs/user-guide/project-config/register-gems/ regards projects. As explained in...
## Describe the issue All of the tables on this documentation page (sections: "PhysX tab properties", "Triangle mesh asset", "Convex asset", "Primitive asset", "Decompose meshes"), are missing "Value" and "Default"...
## Describe the issue All of the tables on this documentation page (sections: "System configuration", "Scene configuration", "Editor configuration", "Wind configuration"), are missing "Value" and "Default" columns, which contain used...
## Describe the issue Following issues have been found with the PhysX Character Controller Component documentation page: * "PhysX Character Controller Properties" section - Component screenshot is deprecated. Current screenshot:...
## Describe the issue There are multiple content issues with the Add the Open 3D Engine Multiplayer Gem to a Project documentation page: 1. Paths listed use "Code" instead of...
## Describe the issue It has been noticed that multiple screenshots and paragraphs in the Shadow properties table do not contain the latest information on the component. Component icon in...
## Describe the issue briefly Currently, there is no documentation page containing detailed description the .xmlschema assets, nor describing any basic workflow which would utilize them. It should be noted...