Common Issues
This can happen when you right-click on an asset in the asset list and click on go to hierarchy, the tool will try its best to link assets and game objects, but sometimes it still fails. Your workaround there is to either search your game object directly in the hierarchy or reconstruct the game object by extracting the mesh, textures, etc. This issue is especially notable in instances where MonoBehaviors are used to modify GameObjects or Components at runtime.
This can happen when trying to preview / export meshes or characters, especially if you are on ZZZ, try the acl_fix branch. If it still doesn't work, there is not much you can do, sadly.
This issue can also arise when you try and export an animator which does not have meshes attached to it. Some games, like ZZZ, use a LoD manager to swap out meshes at runtime using a MonoBehavior, so those meshes must be manually bound to the asset hierarchy in order for Studio to export them. Typically, these objects may be identified by having MeshFilter or SkinnedMeshRenderer components with a null Mesh. The correct meshes for these objects may be identified either by searching for the mesh manually by name, or by reverse-engineering the MonoBehavior responsible for binding the meshes.
You tried to load your game directly, or too many assets at once 😉
Certain high-DPI displays on certain versions of Windows result in issues where the UI fails to display itself properly. This issue can usually be mitigated by manually resizing the window containing the problematic elements. In other cases, we recommend the following:
If your AnimationClip YAML contains bones named similarly to path_<some number>, ensure that an Avatar, Animation, or Animator which uses that AnimationClip has been loaded by manually selecting it in the Asset Browser. At this time, the CAB map cannot automatically resolve these dependencies.