Search Unity

  1. Unity support for visionOS is now available. Learn more in our blog post.
    Dismiss Notice

Feature Request [1.2.0-exp.3] GhostAuthoringInspectionComponent: Can't inspect all components at child entity

Discussion in 'NetCode for ECS' started by optimise, Nov 25, 2023.

  1. optimise

    optimise

    Joined:
    Jan 22, 2014
    Posts:
    2,109
    Up until 1.2.0-exp.3, GhostAuthoringInspectionComponent still only can inspect all components at parent entity and additional entity baked using CreateAdditionalEntity() but still can't inspect all components at child entity that it's baked from child game objects attached into parent game object as child at authoring.
     
  2. CMarastoni

    CMarastoni

    Unity Technologies

    Joined:
    Mar 18, 2020
    Posts:
    873
    You need to add the GhostAuthoringInspectionComponent to one of the child game objet to see what it is replicated or not.
    Also, remember the limitation that only the first-level children can have replicated components.
     
    optimise likes this.
  3. optimise

    optimise

    Joined:
    Jan 22, 2014
    Posts:
    2,109
    :eek: Ya. I dun want to add GhostAuthoringInspectionComponent 1 by 1 to all child game object and inspect them 1 by 1. I would like to have improvement to make it just add GhostAuthoringInspectionComponent at parent game object then I can inspect all the ghost component at parent game object and all the child game objects. I think I change title label to feature request.

    I see so can't have child game object of child game object.
     
  4. CMarastoni

    CMarastoni

    Unity Technologies

    Joined:
    Mar 18, 2020
    Posts:
    873
    Ah, so you want it to work the way it was originally (you can see all replication properties on the root).
    It was like that not so long time ago, but we thought it was more scalable this way.
    I would say, from my perspective, a better tool window for inspecting and setup ghosts is necessary and provide a way more wider set of features.

    Not at the moment. We have a way to remove this limitation, but at the moment you need to live with it.
     
    optimise likes this.