Support SerializedFile v27 (Unity 7000.0)

Aberta
#158 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp, unity
Domínio
testing, tooling

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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:

  • SInt32 count
  • 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.MaxMetadataParseVersion to 27 was enough for the serialized-file metadata commands. The parser stops before the user information string, so it never reaches the new table.
  • dump and analyze also 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 MaxMetadataParseVersion to 27 and keep reading older versions. Optionally parse the owner table, e.g. so serialized-file can report it.
  • Check that dump handles 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/LeadingEdge with 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.
Linguagem predominante
C#
Estrelas
841
Forks
75
Merge médio
1d 7h
PRs com merge (30d)
3

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Unity-Technologies/UnityDataTools

Todas as issues de Unity-Technologies/UnityDataTools

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.