When doing an analyze there may be references to serialized files that are not included in the analyze input (or where the references serialized file does not have typetrees or otherwise cannot be analyzed)
This commonly happens for Player builds with unity default resources, the built-in resource file that ships with the Unity Editor without TypeTrees and so cannot be analyzed without a specially built copy
Currently such references get assigned a id for the object table, but never written. So the only sign of these references is through gaps in the normally sequential ids. We lose the extra information about these dependent objects that is present in the reference itself (the serialized filename and LFID)
The idea of this issue is to add another table, possibly called dangling_refs that would record each unresolved reference. We would record the serialized filename in the serialized file table and reference its id in dangling_refs. So this table would have the assigned object id, the serialized file id, and the LFID. This won't take up much space and will account for all the ids that are missing from the main object table. Unfortunately we don't have the object type or enough detail to give a lot of details about the dangling ref beyond this basic info.
When doing an analyze there may be references to serialized files that are not included in the analyze input (or where the references serialized file does not have typetrees or otherwise cannot be analyzed)
This commonly happens for Player builds with
unity default resources, the built-in resource file that ships with the Unity Editor without TypeTrees and so cannot be analyzed without a specially built copyCurrently such references get assigned a id for the object table, but never written. So the only sign of these references is through gaps in the normally sequential ids. We lose the extra information about these dependent objects that is present in the reference itself (the serialized filename and LFID)
The idea of this issue is to add another table, possibly called
dangling_refsthat would record each unresolved reference. We would record the serialized filename in the serialized file table and reference its id in dangling_refs. So this table would have the assigned object id, the serialized file id, and the LFID. This won't take up much space and will account for all the ids that are missing from the main object table. Unfortunately we don't have the object type or enough detail to give a lot of details about the dangling ref beyond this basic info.