FileNotFoundException still happens on burst 1.8.14

was only patch note but doesn’t seem to have fixed error

3 Likes

I had this… and wouldn’t compile a build… next day did a build and it worked fine

For the record I have an unconventional but 100% repro for this if needed

  • start a full project burst recompile with a lot of assemblies
  • hit reimport on a large subscene with a lot of physic objects (just want something that takes forever to bake)

  • cut com.unity.physics out of \Library\PackageCache and put it into \Packages
  • get unity to refresh

50% of time I get a mix of file not found exceptions + burst function pointer corruption

The other 50% of the time it only results in file not found exceptions

1 Like

Do you remember what steps in the wild lead to the exception being thrown?
E.g. were you doing stuff to the \Library\ folder of your project or something completely else

In the future if something like this blocks you, just close unity and delete the BurstCache folder in /Library/

Normally (not my weird repro above) it simply happens on a recompile but i haven’t noticed a specific trigger except maybe doing 2 recompiles in a short period of time.

I’m pretty sure that it’s happened just after loading the project on first compile - but I’m not sure this is true in 1.8.14

I’ll try note when I get it in 1.8.14 specifically otherwise I’m going to mix up old cases.

also get this all the time even in 1.8.14 - usually during a recompile, it’s plausible a recompile caused by script define symbols changing, which may have added or removed burst jobs from the overall application

I got it today after recompiling from making some minor code changes + deleting a couple of files.
The thing is though, none of these files were used by burst - they were managed authoring scripts.