Support SerializedFile v27 (Unity 7000.0)
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 45/100
Rechercherichtung
Start with SerializedFileDetector.MaxMetadataParseVersion and the serialized-file metadata parser; then inspect the native UnityFileSystemApi snapshots and dump handling for data-component payloads. The issue also points to UnityProjects/LeadingEdge and the docs describing the format. Rebuild reference files with Unity 7000.0, ideally including a data component, and verify v27 metadata commands, dump, and analyze work while older versions remain supported.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Unity 6.7 writes v26 of the SerializedFile format (supported since #130). Unity 7000.0 (current trunk) has moved to v27:
kDataComponentOwners = 27, // Data components' owner GameObject references move from the front of their payloads to a metadata table after the user information string; the payload is exactly what the stored TypeTree describes
Today every SerializedFile from a 7000.0 build is rejected:
SerializedFile version 27 is not supported. UnityDataTool supports up to version 26. Please use a newer version of UnityDataTool to read this file.
As a result, dump, analyze and most serialized-file subcommands don't work on 7000.0 output. serialized-file header still works and shows the version.
Format change
The metadata section gains one table after the user information string. It is always present in v27, even when empty:
SInt32count- per row, two fileIDs (each
SInt64, 4-byte aligned like other fileIDs in the metadata): the data component's fileID, then the fileID of its owner GameObject, which is in the same file.
A row exists only for data-component objects. Previously the owner reference was stored at the front of the data component's payload, so the payload is now exactly what its TypeTree describes.
Quick experiment
I built a Content Directory with a local trunk editor and tried two local changes:
- Raising
SerializedFileDetector.MaxMetadataParseVersionto 27 was enough for theserialized-filemetadata commands. The parser stops before the user information string, so it never reaches the new table. dumpandanalyzealso need a newer native library. The current UnityFileSystemApi snapshot rejects v27 files ("File may be corrupted or was serialized with a newer version of Unity"). With the UnityFileSystemApi.dll from the trunk editor build (Data/Tools), both commands worked.
That build had no data components, so the new table was empty.
Work includes
- Update to a new UnityFileSystemApi snapshot (Windows/Mac/Linux) from a 7000.0 build.
- Raise
MaxMetadataParseVersionto 27 and keep reading older versions. Optionally parse the owner table, e.g. soserialized-filecan report it. - Check that
dumphandles data components correctly now that their payload no longer starts with the owner reference. - Add v27 reference files for automated tests, e.g. by rebuilding
UnityProjects/LeadingEdgewith 7000.0, ideally with a data component so the owner table isn't empty. - Update docs that describe the SerializedFile format and its version history.
- Vorherrschende Sprache
- C#
- Sterne
- 841
- Forks
- 75
- Ø Merge
- 1 T. 7 Std.
- Gemergte PRs (30 T.)
- 3
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus Unity-Technologies/UnityDataTools
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Unity-Technologies/UnityDataTools#116 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 56/100
-
enhancement
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100
-
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
Alle Issues in Unity-Technologies/UnityDataTools
Ähnliche Issues
-
type:task ux
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
elsa-workflows/elsa-foundation#5253 ·
Maintainer antworten meist innerhalb von 1 Tag