Unity-Technologies / Unity-Technologies/UnityDataTools
Usage from within Unity
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 821
- Forks
- 71
- Avg merge
- 3h 13m
- Merged PRs (30d)
- 9
Description
I tried using these tools from inside Unity to analyze import artifacts and for build postprocessors of generated data, which to be best of my understanding fall under SerializedFile.
However, it seems that the app doesn't properly work with domain load and unload, after a first attempt I'm always getting

for subsequent tries.
Are there plans to get this to work?
I found a relevant comment in the UnityFileSystem constructor that leads me to believe this is a bug / not implemented:
static UnityFileSystem()
{
// Initialize the native library.
var r = DllWrapper.Init();
HandleErrors(r);
// TODO: should Cleanup be called by the AppDomain.Unload event or something else?
}
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.
Research direction
Start with the UnityFileSystem static constructor and its DllWrapper.Init call, then inspect the TODO about cleanup during AppDomain.Unload. Reproduce the failure by loading and unloading the domain, then trying another analysis. Done means repeated use from Unity works without the reported error and native-library cleanup is handled appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100