Skip to content

DOM: somewhat broken serialization for entites with MeshComponent in Editor. #18482

Open
@Aleks-Starykh-TR

Description

@Aleks-Starykh-TR

Describe the bug
Serialization for attributes of entities containing a MeshComponent (and also an ActorComponent and / or lights) in Editor has been broken since release 24.09.01 in development branch.
In Editor, selecting an entity containing a MeshComponent (and also an ActorComponent and / or lights) produces asserts (multiple under debugger / single and then ignored when running Editor standalone) on failures getting the attribute "LightningChannelConfiguration".
This behaviour was not noted in the point-release/24091 branch while it was available.

Assets required
No additional assets required. The bug is reproduced in an empty dummy project with empty dummy level.

Steps to reproduce

  1. Create an empty dummy project with development branch at f1e8590, compile profile Editor.
  2. Run the AssetProcessor (should go through without failures).
  3. Start the standalone profile Editor (or run profile Editor under debugger).
  4. Create a new empty Test level using default template.
  5. Go to 'Entity Outliner" -> expand "Atom Default Environment"
  6. Select the 'Shader Ball' with LMB
  7. Note the assert generated and put in ignored list (in case of running under debugger - note multiple asserts).

Expected behavior
No asserts generated when selecting entities with MeshComponent (and also an ActorComponent and / or lights)

Actual behavior
Asserts generated when selecting entities with MeshComponent (and also an ActorComponent and / or lights)

Screenshots/Video
FailedObject

AssertOnMeshNodeSelect.mp4

Found in Branch
https://github.com/o3de/o3de/tree/development,

Commit ID from o3de/o3de Repository
(f1e8590)

Desktop/Device (please complete the following information):

  • Device: PC
  • OS: Windows
  • Version: 10
  • CPU: Intel I7-7900F
  • GPU: NVidia GF GTX 1060
  • Memory: 64GB

Additional context
Editor.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.sig/contentCategorizes an issue or PR as relevant to SIG Content.sig/coreCategorizes an issue or PR as relevant to SIG Core

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions