O3DE Known Issues List

[mcphedar]

Known Issues List

AI

• AI: AI Components are unusable due to missing Agent Types. #1768

Atom

• Atom: Atom debug information is not currently displayed in the O3DE Editor. #1769
• Atom: Duplication of entities throws an Out of Memory error. #1770
• Atom: Rendering errors using Vulkan with NVidia’s Titan X hardware. #1771
• (macOS only) AutomatedTesting.GameLauncher and the O3DE Editor cannot be started. #1772
• Atom: Large Dynamic Vegetation areas cause an Editor crash with DX12 but work with Vulkan. #1773
• Atom: The forward pass results in artifacts on Mac M1 hardware. #1774

Global Illumination and Reflections

• Atom: Diffuse probes incorrectly alter BoxShape sizes. #1775

Raytracing

• Raytracing: Vulkan ray tracing crashes on NVidia 10-series cards. #1776

Render Hardware Interface (RHI)

• RHI: [Android] [Vulkan] If validation is enabled, errors may be reported #1737
• RHI: [Android] [Vulkan] Mali Driver crash for SMAANeighborhoodBlending pass #1777
• RHI: [Android] [Vulkan] SSR not rendering #1778
• RHI: [Android] [Vulkan] Bloom not rendering #1779
• RHI: [Android] [Vulkan] Rendering artifacts and issues with reflections. #1780
• RHI: AMD only: RHI\TriagleConstantBuffer renders incorrectly on AMD machines #1781

Character

• Character: Hot reloading for meshes is not functioning as expected. #1782
• Character: Automatic LOD generation based on skinning information is not working. #1783
• Character: The orientation of the skeleton joints need to be uniformed in the fbx source model. Otherwise there might be unexpected result in the actor skeleton. #1784
• Character: Actors don't store their meshes within the .actor files anymore and refer to a .azmodel (Mesh group). Currently it is only possible to export a single actor and single mesh from an fbx. In case multiple actor groups are added, they will all refer to the first mesh #1785

Editor

• Editor: O3DE Editor layout is broken moved to a second monitor if the two monitors have different scaling settings. #1786

Editor UI Canvas (LYShine)

• UI Canvas: UI Canvas cannot meet Mesh component dependencies at this time. #1787
• UI Canvas: The Masking function does not currently work with the Atom renderer. #1788

Platforms

• Platform: (iOS only) CMake generator expressions used in the Find<3rdParty>.cmake files don’t currently work. #1789

Prefabs

• Prefabs: Prefabs with entities that have the input component cause Asset Processor errors #1790
• Prefabs: There are issues when detaching multiple prefabs in deep prefab hierarchies #1791

Scripting

• Scripting: The Lua IDE cannot connect to the Editor due a GridHub related failure. #1792

Systems

• Systems: After an o3de project is built, the project_path is still incorrectly points to “AutomatedTest”. #1793
• Systems: AZStd::vector::emplace does not support arguments that refer to a value already in the container #1794

NVIDIA Blast

• Blast: The supplied pre-compiled plug-ins support Houdini 18.0 only. #1795
• Blast: Some Houdini installations might create the Houdini user directory at C:\Users\user_name\houdini18.0\ rather than in the Documents directory. #1796
• Blast: The number of chunks generated by Fracture Hierarchy grows exponentially. #1797
• Blast: The .assetinfo file prevents the mesh assets from being processed automatically by Python Asset Builder #1798
• Blast: Passive forces like gravity can have a cumulative damage effect on a NVIDIA Blast assets #1799

NVIDIA Cloth

• Cloth: Debug Visualization will not show when running from Launchers. #1800
• Cloth: does not support LOD meshes. #1801
• Cloth: does not support scaled transforms. #1802
• Cloth: An Actor Component using a mesh with cloth modifiers will not preview animation in the editor #1803
• Cloth: Cloth does not collide with Actor cloth colliders in the O3DE Editor’s Preview Mode. #1804
• Cloth: The O3DE debug display system is always rendered with a 1 frame delay. #1805

PhysX

• PhysX: It may be possible for the PhysX Character Controller to climb slopes or steps higher than expected if the Step Height value is set to 0 #1810
• PhysX: There is currently no mechanism to automatically disable collisions between a PhysX Character Controller and a PhysX Ragdoll belonging to the same character #1811
• PhysX: Joint limits may be exceeded in the ragdoll because of interactions with animated movements. #1812
• PhysX: If the PhysX collider and the mesh are the same size, you will observe jittering during rendering. #1813
• PhysX: Functional and rendering issues, such as jittering, occur if you apply impulse to parent-child entities that have PhysX Rigid Body components. To work around this issue, use joints. #1814
• PhysX: increasing the Position Iteration Count and Velocity Iteration Count parameters of one ragdoll affects the other ragdolls. #1815
• PhysX: Modifying the World Transform of entities with non-kinematic PhysX Rigid Body Components at game-time (with scripts) is not supported #1816
• PhysX: The existing cases of using RayCast and ShapeCast must be evaluated to see where the hits from the inside of collision mesh are desired.Note: This only applies to triangle meshes. Primitives and Convex meshes are considered to be solid and will give the hit from the inside if ray starting position is inside the shape (the distance will be 0 in this case). #1817
  Note: This only applies to triangle meshes. Primitives and Convex meshes are considered to be solid and will give the hit from the inside if ray starting position is inside the shape (the distance will be 0 in this case).
• PhysX: If the PhysX TGS solver is enabled, ragdolls with high position or velocity iteration counts can become unstable. #1818
• PhysX: V-HACD Mesh Decomposition: Mesh decomposition is only available if the export type is selected as Convex or Primitive. #1819
• PhysX: V-HACD Mesh Decomposition: The actual results achieved by the decomposition depend mostly on the V-HACD library and are out of our control. #1820
• PhysX: Automatic Target Shape: Almost any FBX mesh will be exportable, but the accuracy of the result will depend on how close the mesh is to one of the supported primitives. #1821
• PhysX: Automatic Target Shape: O3DE will attempt to fix one primitive for each node selected for export. It will not recognize multiple primitive shapes contained within the same node. #1822
• PhysX: Automatic Target Shape: the algorithm considers only the vertices of the mesh, not edges/faces. Apart from some edge cases, this is usually sufficient, but the user may need to configure the export parameters correctly before a desirable result is obtained. #1823
• PhysX: Automatic Target Shape: The algorithm is subject to mathematical restrictions and does not work well if the mesh has extreme proportions or sizes. Likewise, a vertex cloud that predominantly occupies a lower dimension subspace (plane, line or point) will not work well. #1824
• PhysX: Automatic Target Shape: Non-uniform scaling of automatically fitted primitive colliders can have unintuitive behavior and is not recommended. #1825
• PhysX: PhysX parameter changes in the PhysX Configuration window may only take effect when the editor is restarted. #1826
• PhysX: Using multiple ragdolls with pose moves may result in poor performance. #1827
• PhysX: Entity transforms would not be updated correctly for ragdolls if physics is disabled on the character controller. #1828