12-06-2023, 06:06 PM
(12-06-2023, 12:16 PM)josemendez Wrote: This has nothing to do with Obi, since it doesn't do any version control or file handling of its own. It's just a bunch of static files in your project. Unlikely for Unity to be related to this issue either.
Make sure all required scripts/files are tracked by the VCS you're using (git, mercurial, svn, plastic, etc). Failing to track all files will likely lead to missing files.
Note it's specially important to track your project's metadata (.meta) files. Ignoring them will break your project in all sorts of ways.
Everything is most definitely tracked and I only get this in regards to Obi, but I agree, it's strange. The exact error I get is
Failed to find entry-points:
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Obi, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null'
at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name, Mono.Cecil.ReaderParameters parameters) [0x00105] in <ebb9e4250ed24cbfa42055e3532ef311>:0
at zzzUnity.Burst.CodeGen.AssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00039] in <a2dd15248a25411e914af2a2c82fb63f>:0
at Burst.Compiler.IL.AssemblyLoader.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00079] in <a2dd15248a25411e914af2a2c82fb63f>:0
at Burst.Compiler.IL.Server.EntryPointMethodFinder.FindEntryPoints (System.String[] rootAssemblyNames, Burst.Compiler.IL.Hashing.CacheRuntime.HashCacheAssemblyStore assemblyStore, Burst.Compiler.IL.AssemblyLoader assemblyLoader, Burst.Compiler.IL.NativeCompilerOptions options, Burst.Compiler.IL.Server.ProfileDelegate profileCallback, System.Boolean includeRootAssemblyReferences, System.Boolean splitTargets, Burst.Compiler.IL.Helpers.DebugLogWriter debugWriter) [0x00055] in <a2dd15248a25411e914af2a2c82fb63f>:0
at Burst.Compiler.IL.Server.FindMethodsJob.Execute (Burst.Compiler.IL.Server.CompilerServerJobExecutionContext context) [0x00133] in <a2dd15248a25411e914af2a2c82fb63f>:0
While compiling job:
So burst (which I don't even use) fails to compile some assemblies. This is indeed probably not Obi's fault, I'll dig a bit when I have time.