Document tips for using UnityDataTool with Library AssetDatabase artifacts
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- unity
- Domain
- documentation, game-dev, tooling
Research direction
Start with UnityDataTool's dump command and the Import Activity window's "Show in Explorer" workflow. Verify whether public scripting APIs can retrieve artifacts and account for version differences such as Unity Data Store; the documentation is done when it explains artifact access, relevant use cases, and those caveats.
Written by the indexing model from the issue text.
Description
The AssetDatabase uses binary serialized files to represent imported Assets.
UnityDataTool can read such files, e.g. the dump command and can be a nicer alternative to the older binary2text tool that is typically used for this case.
It should only be necessary to look in these files in quite advanced cases. But it could be useful when developing custom scripted importers, or education about how Unity works, or for tracking a problem through the full pipeline from source to build output (e.g. for FBX files, or Scenes)
The Import Activity window shows Artifacts and has a "Show in Explorer" option for retrieving that artifact as a file. This is worth describing. We should also show how to do this from script (if possible using public APIs?)
Note: There are some changes in how these artifacts represented in recent versions of Unity, e.g. introduction of Unity Data Store (UDS) so the topic may have make information conditional on the version of Unity.
This task is to offer some
- Dominant language
- C#
- Stars
- 821
- Forks
- 71
- Avg merge
- 4h 54m
- Merged PRs (30d)
- 10
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Unity-Technologies/UnityDataTools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Unity-Technologies/UnityDataTools#116 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 65/100
All issues in Unity-Technologies/UnityDataTools
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·