Closed IoIoToTM closed 2 months ago
Heya, thank you for a detailed report!
I have just tried reproducing this and cannot - I downloaded the package, created a new 2D Unity project and then double-clicked the package that was downloaded (same as importing using context menus) and all files were imported without errors and the sample scenes/Flow Engine and Window all opening and working as expected.
I will try to reproduce this again and then try another machine to ensure it works across devices!
Thank you for your patience.
After some back and forth, and a lot of testing, it turns out that the basic new project in my version of Unity doesn't install Burst automatically, and somehow, the dependencies didn't take care of that when importing the package. Basically, to fix the issue, I installed Burst, and then imported the package, and it worked.
Describe the bug Pretty much what the title says, using Unity 2022.3.10f1.
To Reproduce Steps to reproduce the behavior:
Asstets->Import Package->Custom Package
and selectLUTE.unitypackage
from where I downloaded itImport
Project Settings
Desktop:
Additional context At the end of the Editor.log file that is created after a crash (I just replaced the path on the first line). It looks like maybe it's something with the Burst compiler: