Unity-Technologies / Unity-Technologies/UnityDataTools
Support SerializedFile v26 (Unity 6.7)
未关闭
还没有人认领这个 Issue。
- 主要语言
- C#
- 星标
- 821
- 派生
- 71
- 平均合并
- 3 小时 13 分钟
- 30 天内合并 PR
- 9
描述
Unity 6.6 is v23 of the file format.
At end of alpha Unity 6.7 has reached v26, with several significant changes.
kIndependentTypeTreeVersion = 24, // 6000.7: TypeTree blobs are now versioned by their own TypeTreeFormatVersion instead of this enum; TypeTree format changes no longer bump the serialized file version.
kSerializeReferenceRegistryFirst = 25, // 6000.7: the [SerializeReference] registry is a leading frame in the object's data (v3 table format) instead of a trailing TypeTree-described node. Older readers would misparse the frame bytes as field data, so they must reject the file on version.
kSharedSubtreeSupport = 26, // Shared sub-typetree referencing: the file carries a table of compound subtrees stored once, keyed by content hash, that its types reference
This means the "dump", "analyze" commands will not work with the output from Unity 6.7
Most subcommands of the "serialized-file" will also not work (but the "header" command does work, that can be used to see the serialized file version)
Work includes:
- Updating to new snapshot UnityFileSystemApi dll (windows/mac/linux), e.g. take a snapshot from an official build of Unity 6.7 beta.
- Expose the API changes in UnityFileSystemApi through the C# wrapper
- Change the parsing code used by serialized-file command to reflect the updated file format (but continue to support reading older files)
- Add some reference files for automated tests
- e.g. rebuild the UnityProjects/LeadingEdge project with Unity 6.7)
- ideally add refernce files that demonstrate any new features and add specific tests for how this data is exposed
- Make sure docs / comments are updated to reflect the changes, e.g. any docs about TypeTrees should be revisited, and the serialized reference registry change may also influence the example.
- Update UnityDataTools version and create a release for download (along with other fixes).
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
先从 serialized-file 命令解析代码和现有的 UnityFileSystemApi C# 包装器开始,然后检查 Unity 6.7 beta 快照 DLL,了解所列出的 API 和文件格式变更。使用 Unity 6.7 重新构建 UnityProjects/LeadingEdge 以获取参考文件,为新数据添加覆盖,同时保留对旧文件的支持,并更新提到的 TypeTree 文档和注释。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- csharp, unity
- 领域
- devtools, tooling
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100