Usage from within Unity

Open
#3 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, unity
Domain
game-dev, tooling

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.

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
20220816-192134-APN1-Unity_FBNg

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?
}
Dominant language
C#
Stars
821
Forks
71
Avg merge
3h 13m
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unity-Technologies/UnityDataTools

All issues in Unity-Technologies/UnityDataTools

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.