Project Tiny preview-0.16.1 (C#) available, and upcoming changes

Thanks for the update!

To be clear -- does this mean that the idea of a pure DOTS editor is going away (forever?) and we'll need to write conversion scripts for all ECS components from MonoBehaviours if we want to be able to use them in the editor, as with the current workflow for non-Tiny ECS? (I hope not!)

 

Always good to see new updates! Great work! Glad that generating our Tiny projects is getting easier!

Interesting going to a gameobject workflow, I was quite enjoying the Entity workflow. Although im sure it will be worth it in the end! Id love to hear a little more about how this is going to work exactly (specifically with calling the components in scripts(more specifically how in Tiny transforms are called translations))

Will this mean we will be able to do editor scripting in Unity Tiny sooner than i was originally expecting it to work?

Also im assuming this is going to increase your guys workflow quite alot with not having to create all new components for tiny specifically. With that being said, is tilemaps (and other features) going to find its way back into Project Tiny faster do to this change?

 

Still no 3D....

 

Will DOTS Mode be used on the normal project(Non-Tiny) in the future? just curious.

 

I'm having this error after updating to new version.

Code (CSharp):

1. error: Sequence contains no matching element (System.InvalidOperationException)
2.   at System.Linq.Enumerable.First
3.   at DotsConfigs+<>c.<.cctor>b__13_1 in C:/Unity/tinygit/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsConfigs.cs(49)
4.   at System.Lazy`1[T].CreateValue
5.   at System.Lazy`1[T].LazyInitValue
6.   at Il2Cpp+<>c.<.cctor>b__35_1 in C:/Unity/tinygit/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/Il2Cpp.bee.cs(70)
7.   at System.Lazy`1[T].CreateValue
8.   at System.Lazy`1[T].LazyInitValue
9.   at DotsRuntimeCSharpProgram.Construct in C:/Unity/tinygit/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(67)
10.   at DotsRuntimeCSharpProgram..ctor in C:/Unity/tinygit/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(56)
11.   at BuildProgram.Main
12.   at System.RuntimeMethodHandle.InvokeMethod
13.   at Bee.StandaloneBeeDriver+<>c.<CreateBuildGraph>b__42_0
14.   at Bee.StandaloneBeeDriver.RunBuildProgramInBeeEnvironment
15.   at Bee.StandaloneBeeDriver.CreateBuildGraph
16.   at Bee.StandaloneBeeDriver.BuildMain
17.   at Bee.StandaloneBeeDriver.Main
18. [E] DAG generator driver failed: "C:\Unity\tinygit\Library\PackageCache\com.unity.tiny@0.16.1-preview\DotsPlayer\bee~\bee.exe" build --beemode=ToCreateBuildGraph --commandlinerequest=get-editor-tools --commandlinerequest=story-windows-dotnet-release --root-artifacts-path=artifacts --bee-driver-buildprogramroot=.
19. *** Tundra build failed to setup error (0.70 seconds), 0 items updated

 

Yiiiiikes.

I've been avoiding dipping my foot into the DOTS stuff exactly because the hybrid mode and auto-conversion seem like insane, temporary hacks "just to get something working". The pure dots view you had in 0.15 was what made me want to try it in the first place. It's a complete solution where I understand what's going on.

The megacity approach seems to have an absurd amount of black magic going on. I probably won't ever be comfortable building games in this "lets create objects in one abstraction in the editor and then magic magic now we're in a different abstraction at runtime" way.

Is the dots editor coming back once it's better, or have you locked into DOTS forever being tied to GameObject in a very confusing way?

 

I have also faced the same issue and now waiting for a solution from here.

 

I have to agree with Baste, abstracting entities with GameObjects seems wrong. From my pov Entities/EntityGroups approach was not too hard to get into.

 

No I didn't. I just upgraded the Project Tiny.

Also just to be sure, I created a new project. Then I installed version 0.16.1 of Project Tiny directly and got the same error. Then I downgraded it to 0.15.3 and I could get a build.

 

My off-the-cuff concerns so far:
- It will require that extra scaffolding code be written for each ECS component that we want to use in the editor. (Unless there will be an auto-generated editor-time-only MonoBehaviour for ECS components as part of this infrastructure?)
- It will discourage ECS-like thinking at author time. It would be nice if it were possible to visualize, by means of the Hiearchy Window and Inspector, what your data is actually going to look like without having to press play.

 

We're using some super-duper unsupported techniques at the moment, but my team is in the process of integrating Raylib (https://www.raylib.com/) into Tiny for 3D support, and it's coming along slowly, but very nicely.

 

Completely disagree. Conversion workflow is all against of magic. You authorize it by yourself, you decide how convert data from edit format to runtime format, you decide how it looks in editor, at the same time you can use all old good MB editor stuff.

 

Thanks for the answer. I just do not like abstracting something just so it does not look intimidating. But the way you explained it in the previous answer makes sense.

 

After reading through this thread I'm a little less concerned about the Pure Entities to GameObjects plus Conversion change... But i really don't like the weird jargon when it comes to referring to these converted-to-entities-at-runtime "GameObjects". Because really, are they actually GameObjects at this point? Heck they don't even exist within the game anymore!
They're more of "Hybrid Entity Blueprints" now, so i feel like we should change the jargon to reflect that (even if it comes at the expense of increasing the entry barrier slightly for newer people since they have to refer to them as something new). Simply calling them EntityObjects would be fine with me, although there are probably better names. Like maybe HybridObject? HybridEntityObject? ObjectEntity? What about Will-Be-Converted-Soon-TM-Object? Is that too wordy?

Anyways just thought i should throw in my two cents about the subject.

- Also, does anyone know how to reference another soon-to-be-converted GameObject's created entity within the editor? Like... Without getting errors? Since the GameObject gets destroyed, anytime you reference it the editor gets mad -- so you can't do that. And the entity created is pretty arbitrary too, you don't know if it will be Entity 1 or Entity 2, and hardcoding in a "reference" to Entity 1 would make me cry... So is there like auto conversion of a GameObject reference to Entity "reference" or something when the GameObject gets converted to an entity?

 

conversionSystem.GetPrimaryEntity

 

Is it always going to be the intention to limit the exposed .NET libraries that are available? I ask because I find the idea of Unity TIny interesting in that it has the potential of starting our non-game web application faster when we only really want to use Unity's API for basic rendering but still have access to third party libraries for doing runtime processing of different data formats. I get there is some effort to "fine-tune" this but ultimately is the end-goal still going to be a limited .NET Standard 2.0 subset that would make using off-the-shelf .NET libraries impossible?

 

We could just drop prefab I think

It's my wish all along that we should have a way to make prefab be the same as edittime and runtime. But the way I have came up with is something like edittime data orient UIElements. It was getting away from being prefab. It become something that dynamic generating things inside both prefab view, editor view, and also in playmode

And I think this should be better approach for unity. Everything should be data orient and react to data. Then we just serialize the data instead of prefab. And so prefab should be legacy

 

This all sounds great!

This is great for performance, and for sure something we'd want for builds.
But when debugging the game - ie. playing from the editor - we really need the edit time hierarchy to understand what we're looking at. One of the biggest performance killers in GameObject world is deep transform hierarchies of essentially folder gameobjects. Those are 100% necessary in order to move related objects together, and to give meaningful names to things.

We have tried, for performance reasons, to flatten those hierarchies when we go into play mode, and quickly found out that we lost a ton of information about what we were looking at. It becomes way harder to link what you're seeing in-game back to what's there at edit-time when the hierarchies have changed. So we switched to only do the flattening at build-time.
In short, when everything's just a single blob of data, it runs faster, but our ability to reason about it at runtime is reduced.

It doesn't feel like a hack. I just had assumed it was a hack that you put in place until you had the pure ECS editor ready to go. Color me surprised when you ship a pure ECS editor and then ditch it in less than a month.


I think the best thing in Unity - it's killer feature - is the ability to click a thing in the scene view in play mode, in order to see what data is attached to it, and what behaviours are running on it in the inspector.
I realize that tying together data and behaviour is slow, and DOTS is all about splitting those two apart, but boy will it be hard to debug anything if I can't click on a thing to see what's running on it.

So what seems hacky is that you've thrown out what I consider the best part of Unity on the road to DOTS. Take the boid demo. I can select the shark, but I have to find it in the hierarchy, I can't click it in the scene view. I can't select an individual fish without going through the entity debugger, and there's no way for me to link the fish there to the fish in the scene.

What the Project Tiny preview has is the ability to click an entity in the scene view. That was one of the main thing I felt was missing from entities, and now it's going away again.

 

When i upgraded my project to this new release, every time i click "open DOTS C# project" instead of reloading my current IDE, it opens a completely new one, and my newly created scripts wont work correctly. I had also just switched from jetbrains back to VS because my license expired, so it may be VS specific, because when i downgraded back to the last version it continued, but at least after i downgraded when it opened the new IDE the script were usable and i just had to close the previously opened IDE

 

Coming from Entitas background, i don't really mind losing the editor flexibility.

About DOTS:

• Is is possible to Add/Remove components in runtime, like entity.AddMyComponent(A,B,C) ?
• What would be an equivalent for Reactive Systems. systems that reacts to an entity being added once instead of looping constantly through them ?
• Can we control the script execution order of systems ?

the samples are running perfectly and runs on both webasm and asmjs on a low end phone.

 

I was able to execute the project before, but suddenly I could not execute the project.
Even the HelloWorld project is impossible.
Widows SDK is the latest version, and Jobs and Burst are also the latest version.
The symptoms occur during a build after pressing the run button.
The editor freezes when the progress message is "Running bee ...".
This symptom occurs with any execution method.
I do not know the solution method. help me.
(I'm not good at English.Therefore, I used Google translation.)
(There may be incorrect sentences. I'm sorry.)

 

In that case it sounds great!

Can you please tell us when do you plan to publish the roadmap?

 

Still not building =(

Code (CSharp):

1. Build failed. Open D:\YOU\beta9_tiny\Library\DotsRuntimeBuild\build.log for more details.
2. [     0s] Build frontend of artifacts\buildprogram\buildprogram_buildprogram.dag ran (no suitable previous build dag file)
3. [1/6  0s] CSProject buildprogram-build.gen.csproj
4. [2/6  0s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/7za-win-x64/.StevedoreVersion (+1 other)
5. [3/6  1s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/referenceassemblies_v46/.StevedoreVersion (+1 other)
6. [4/6  2s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/roslyn-csc-win64/.StevedoreVersion (+1 other)
7. [5/6  1s] Csc artifacts/buildprogram/buildprogram_buildprogram.exe (+2 others)
8. [     5s] Build frontend of artifacts\buildprogram\tundra_buildprogram.dag ran (no suitable previous build dag file)
9. [ 1/13  0s] WriteResponseFile artifacts/rsp/1008532451738831585.rsp
10. [ 2/13  0s] WriteResponseFile artifacts/rsp/16678227308262555357.rsp
11. [ 3/13  0s] CSProject D:/YOU/beta9_tiny/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramBuildProgramSources/buildprogrambuildprogram.gen.csproj
12. [ 4/13  0s] CSProject D:/YOU/beta9_tiny/Library/DotsRuntimeBuild/buildprogram.gen.csproj
13. [ 5/13  0s] VisualStudioSolution build.gen.sln
14. [ 6/13  0s] CopyTool artifacts/buildprogram/bee.exe
15. [ 7/13  0s] CopyTool artifacts/buildprogrambuildprogram.exe/Release/bee.exe
16. [ 8/13  0s] Download and unpack artifacts/Stevedore/7za-win-x64/.StevedoreVersion (+1 other)
17. [ 9/13  0s] Download and unpack artifacts/Stevedore/referenceassemblies_v471/.StevedoreVersion (+1 other)
18. [10/13  2s] Download and unpack artifacts/Stevedore/roslyn-csc-win64/.StevedoreVersion (+1 other)
19. [11/13  1s] Csc artifacts/buildprogrambuildprogram.exe/Release/buildprogrambuildprogram.exe (+2 others)
20. [12/13  1s] Csc artifacts/buildprogram/buildprogram.exe (+2 others)
21. error: Error reading JObject from JsonReader. Path '', line 1, position 390. (Newtonsoft.Json.JsonReaderException)
22.   at Newtonsoft.Json.Linq.JObject.Load
23.   at Newtonsoft.Json.Linq.JObject.Parse
24.   at Bee.Stevedore.Program.FileList.ParseFromString
25.   at Bee.Stevedore.Program.FileList.ParseFromString
26.   at Bee.Stevedore.StevedoreArtifact.GetFileList
27.   at EditorToolsBuildProgram.SetupGetEditorToolsFromStevedore in D:/YOU/beta9_tiny/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/EditorToolsBuildProgram.cs(144)
28.   at BuildProgram.Main in D:/YOU/beta9_tiny/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/BuildProgram.bee.cs(167)
29. [E] DAG generator driver failed: "D:\YOU\beta9_tiny\Library\PackageCache\com.unity.tiny@0.16.1-preview\DotsPlayer\bee~\bee.exe" build --beemode=ToCreateBuildGraph --commandlinerequest=get-editor-tools --commandlinerequest=helloworld-windows-dotnet-debug --root-artifacts-path=artifacts --bee-driver-buildprogramroot=.
30. *** Tundra build failed to setup error (14.40 seconds), 0 items updated
31.  
32. UnityEngine.Debug:LogError(Object)
33. Unity.Debug:LogError(Object) (at Library/PackageCache/com.unity.entities@0.0.12-preview.33/Unity.Entities/Stubs/Unity/Debug.cs:10)
34. Unity.Editor.Build.BuildStepRunBee:Run(BuildContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildStepRunBee.cs:83)
35. Unity.Editor.Build.BuildPipeline:RunBuildSteps(IReadOnlyList`1, BuildContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildPipeline.cs:137)
36. Unity.Editor.Build.BuildPipeline:Build(BuildSettings) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildPipeline.cs:110)
37. Unity.Editor.Application:Build() (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor/Application.cs:133)
38. Unity.Editor.Application:BuildAndRun() (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor/Application.cs:144)
39. Unity.Editor.Modes.PlayBar:PlayCommandHandler(CommandExecuteContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Modes/PlayBar.cs:15)
40. UnityEditor.CommandService:Execute(String)
41. Unity.Editor.Modes.PlayBar:DrawPlayBar(CommandExecuteContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Modes/PlayBar.cs:80)
42. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
43.  

Code (CSharp):

1. Build failed. Open D:\YOU\beta9_tiny\Library\DotsRuntimeBuild\build.log for more details.
2. [     0s] Build frontend of artifacts\buildprogram\tundra_buildprogram.dag ran (folder contents changed: ../PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramBuildProgramSources)
3. error: Error reading JObject from JsonReader. Path '', line 1, position 390. (Newtonsoft.Json.JsonReaderException)
4.   at Newtonsoft.Json.Linq.JObject.Load
5.   at Newtonsoft.Json.Linq.JObject.Parse
6.   at Bee.Stevedore.Program.FileList.ParseFromString
7.   at Bee.Stevedore.Program.FileList.ParseFromString
8.   at Bee.Stevedore.StevedoreArtifact.GetFileList
9.   at EditorToolsBuildProgram.SetupGetEditorToolsFromStevedore in D:/YOU/beta9_tiny/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/EditorToolsBuildProgram.cs(144)
10.   at BuildProgram.Main in D:/YOU/beta9_tiny/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/BuildProgram.bee.cs(167)
11. [E] DAG generator driver failed: "D:\YOU\beta9_tiny\Library\PackageCache\com.unity.tiny@0.16.1-preview\DotsPlayer\bee~\bee.exe" build --beemode=ToCreateBuildGraph --commandlinerequest=get-editor-tools --commandlinerequest=helloworld-windows-dotnet-debug --root-artifacts-path=artifacts --bee-driver-buildprogramroot=.
12. *** Tundra build failed to setup error (3.88 seconds), 0 items updated
13.  
14. UnityEngine.Debug:LogError(Object)
15. Unity.Debug:LogError(Object) (at Library/PackageCache/com.unity.entities@0.0.12-preview.33/Unity.Entities/Stubs/Unity/Debug.cs:10)
16. Unity.Editor.Build.BuildStepRunBee:Run(BuildContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildStepRunBee.cs:83)
17. Unity.Editor.Build.BuildPipeline:RunBuildSteps(IReadOnlyList`1, BuildContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildPipeline.cs:137)
18. Unity.Editor.Build.BuildPipeline:Build(BuildSettings) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Build/BuildPipeline.cs:110)
19. Unity.Editor.Application:Build() (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor/Application.cs:133)
20. Unity.Editor.Application:BuildAndRun() (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor/Application.cs:144)
21. Unity.Editor.Modes.PlayBar:PlayCommandHandler(CommandExecuteContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Modes/PlayBar.cs:15)
22. UnityEditor.CommandService:Execute(String)
23. Unity.Editor.Modes.PlayBar:DrawPlayBar(CommandExecuteContext) (at Library/PackageCache/com.unity.tiny@0.16.1-preview/Unity.Editor/Unity.Editor.Modes/PlayBar.cs:80)
24. UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)
25.  

 

Code (CSharp):

1. [     0s] Build frontend of artifacts\buildprogram\buildprogram_buildprogram.dag ran (build file timestamp changed: bee.config)
2. [     0s] Delete 5 artifact files that are no longer in use. (like artifacts\Bee.CSharpSupport\referenceassemblies\buildprogram_buildprogram.exe\1088064819024506472.dll)
3. [1/6  0s] CSProject buildprogram-build.gen.csproj
4. [2/6  0s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/7za-win-x64/.StevedoreVersion (+1 other)
5. [3/6  0s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/roslyn-csc-win64/.StevedoreVersion (+1 other)
6. [4/6  0s] Download and unpack artifacts/buildprogrambuildprogram/Stevedore/referenceassemblies_v46/.StevedoreVersion (+1 other)
7. [5/6  0s] Csc artifacts/buildprogram/buildprogram_buildprogram.exe (+2 others)
8. [     1s] Build frontend of artifacts\buildprogram\tundra_buildprogram.dag ran (build file timestamp changed: ../PackageCache/com.unity.tiny@0.15.3-preview/DotsPlayer/bee~/BuildProgramBuildProgramSources/BuildProgramBuildProgram.cs)
9. [       0s] Delete 18 artifact files that are no longer in use. (like C:\Space\Projects\NewTinyTest\Library\PackageCache\com.unity.tiny@0.15.3-preview\DotsPlayer\bee~\BuildProgramBuildProgramSources\buildprogrambuildprogram.gen.csproj)
10. [ 1/13  0s] WriteResponseFile artifacts/rsp/16678227308262555357.rsp
11. [ 2/13  0s] WriteResponseFile artifacts/rsp/1008532451738831585.rsp
12. [ 3/13  0s] CSProject C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramBuildProgramSources/buildprogrambuildprogram.gen.csproj
13. [ 4/13  0s] CSProject C:/Space/Projects/NewTinyTest/Library/DotsRuntimeBuild/buildprogram.gen.csproj
14. [ 5/13  0s] VisualStudioSolution build.gen.sln
15. [ 6/13  0s] CopyTool artifacts/buildprogrambuildprogram.exe/Release/bee.exe
16. [ 7/13  0s] CopyTool artifacts/buildprogram/bee.exe
17. [ 8/13  0s] Download and unpack artifacts/Stevedore/7za-win-x64/.StevedoreVersion (+1 other)
18. [ 9/13  0s] Download and unpack artifacts/Stevedore/referenceassemblies_v471/.StevedoreVersion (+1 other)
19. [10/13  0s] Download and unpack artifacts/Stevedore/roslyn-csc-win64/.StevedoreVersion (+1 other)
20. [11/13  0s] Csc artifacts/buildprogrambuildprogram.exe/Release/buildprogrambuildprogram.exe (+2 others)
21. [12/13  0s] Csc artifacts/buildprogram/buildprogram.exe (+2 others)
22. error: Sequence contains no matching element (System.InvalidOperationException)
23.   at System.Linq.Enumerable.First
24.   at DotsConfigs+<>c.<.cctor>b__13_1 in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsConfigs.cs(49)
25.   at System.Lazy`1[T].CreateValue
26.   at System.Lazy`1[T].LazyInitValue
27.   at Il2Cpp+<>c.<.cctor>b__35_1 in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/Il2Cpp.bee.cs(70)
28.   at System.Lazy`1[T].CreateValue
29.   at System.Lazy`1[T].LazyInitValue
30.   at DotsRuntimeCSharpProgram.Construct in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(67)
31.   at DotsRuntimeCSharpProgram..ctor in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(56)
32.   at BuildProgram.Main
33.   at System.RuntimeMethodHandle.InvokeMethod
34.   at Bee.StandaloneBeeDriver+<>c.<CreateBuildGraph>b__42_0
35.   at Bee.StandaloneBeeDriver.RunBuildProgramInBeeEnvironment
36.   at Bee.StandaloneBeeDriver.CreateBuildGraph
37.   at Bee.StandaloneBeeDriver.BuildMain
38.   at Bee.StandaloneBeeDriver.Main
39. [E] DAG generator driver failed: "C:\Space\Projects\NewTinyTest\Library\PackageCache\com.unity.tiny@0.16.1-preview\DotsPlayer\bee~\bee.exe" build --beemode=ToCreateBuildGraph --commandlinerequest=get-editor-tools --commandlinerequest=testtinyproject-windows-dotnet-debug --root-artifacts-path=artifacts --bee-driver-buildprogramroot=.
40. *** Tundra build failed to setup error (3.42 seconds), 0 items updated
41.  

after restart unity

Code (csharp):

1.  
2. [ 9/13  0s] CSProject C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramBuildProgramSources/buildprogrambuildprogram.gen.csproj
3. error: Sequence contains no matching element (System.InvalidOperationException)
4.   at System.Linq.Enumerable.First
5.   at DotsConfigs+<>c.<.cctor>b__13_1 in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsConfigs.cs(49)
6.   at System.Lazy`1[T].CreateValue
7.   at System.Lazy`1[T].LazyInitValue
8.   at Il2Cpp+<>c.<.cctor>b__35_1 in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/Il2Cpp.bee.cs(70)
9.   at System.Lazy`1[T].CreateValue
10.   at System.Lazy`1[T].LazyInitValue
11.   at DotsRuntimeCSharpProgram.Construct in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(67)
12.   at DotsRuntimeCSharpProgram..ctor in C:/Space/Projects/NewTinyTest/Library/PackageCache/com.unity.tiny@0.16.1-preview/DotsPlayer/bee~/BuildProgramSources/DotsRuntimeCSharpProgram.cs(56)
13.   at BuildProgram.Main
14.   at System.RuntimeMethodHandle.InvokeMethod
15.   at Bee.StandaloneBeeDriver+<>c.<CreateBuildGraph>b__42_0
16.   at Bee.StandaloneBeeDriver.RunBuildProgramInBeeEnvironment
17.   at Bee.StandaloneBeeDriver.CreateBuildGraph
18.   at Bee.StandaloneBeeDriver.BuildMain
19.   at Bee.StandaloneBeeDriver.Main
20. [E] DAG generator driver failed: "C:\Space\Projects\NewTinyTest\Library\PackageCache\com.unity.tiny@0.16.1-preview\DotsPlayer\bee~\bee.exe" build --beemode=ToCreateBuildGraph --commandlinerequest=get-editor-tools --commandlinerequest=testtinyproject-windows-dotnet-debug --root-artifacts-path=artifacts --bee-driver-buildprogramroot=.
21. *** Tundra build failed to setup error (0.43 seconds), 0 items updated
22.  

same here

 

Investigate the

DotsConfigs.cs

file from the buildlog and found out that the project don't create file

selectedconfig.json

it required to

So I just hack it like this in the meantime (you can just edit and overwrite that file directly)

Code (CSharp):

1.  
2.     private static DotsRuntimeCSharpProgramConfiguration ReadConfigFromSelectConfigFile()
3.     {
4.         Console.WriteLine("ReadConfigFromSelectConfigFile : 56");
5.         var file = NPath.CurrentDirectory.Combine("selectedconfig.json");
6.         Console.WriteLine(file);
7.         Console.WriteLine(file.FileExists());
8.  
9.         string configName = "wasm-debug";
10.         if(file.FileExists())
11.         {
12.             var json = file.ReadAllText();
13.             Console.WriteLine(json);
14.             var jobject = JObject.Parse(json);
15.  
16.             Console.WriteLine(jobject);
17.  
18.             configName = jobject["Config"].Value<string>().ToLower();
19.         }
20.  
21.         Console.WriteLine("configName : " + configName);
22.         return _configs.Value.FirstOrDefault(c => {
23.             Console.WriteLine(c.Identifier + " == " + configName);
24.             return c.Identifier == configName;
25.         });
26.     }
27.  

Still disappointed that this is official unity package and it not opensource but having a seriously annoying bug like this leak out for many days

 

More investigation leads me here

We need to press this menu at least once (WHY?) to make the unity generate

selectedconfig.json

for the bee.exe to read the config line

Will investigate more about this case. I think it should always generate selectedconfig when we press play button. So it seem like a bug in unity

 

Found out that it was a bug in

com.unity.tiny@0.16.1-preview\Unity.Editor\Unity.Editor.Build\BuildStepGenerateBeeFiles.cs

In the Run function it was like this

Code (CSharp):

1.  
2.  
3. public bool Run(BuildPipeline.BuildContext context)
4. {
5.     BuildProgramDataFileWriter.WriteAll(context.OutputDirectory.FullName);
6.     WriteBeeExportManifestFile(context);
7.     WriteBeeBuildSettingsFile(context);
8.     return true;
9. }
10.  
11.  

But it actually need to be like this

Code (CSharp):

1.  
2. public bool Run(BuildPipeline.BuildContext context)
3. {
4.     var workspaceManager = context.Project.Session.GetManager<WorkspaceManager>();
5.     var selectedConfiguration = workspaceManager.ActiveBuildTarget.GetBeeTargetName() + "-" + workspaceManager.ActiveConfiguration;
6.     BuildProgramDataFileWriter.WriteAll(context.OutputDirectory.FullName,selectedConfiguration);
7.     WriteBeeExportManifestFile(context);
8.     WriteBeeBuildSettingsFile(context);
9.     return true;
10. }
11.  

 

Open DOTS project in webGL cause weird error. Can build and run but it also make vscode cannot reference

Unity.Tiny.HTML

. And so I can't coding or running test runner properly

 

Please just opensource the tiny repo in github so we could fix all the problem

 

I'm excited that they're letting us see (and change!) the source at all! That's a huge step in the right direction for Unity, and it's the only thing that's made my company's current project possible.

 

there seems to be some dependency's for the tiny project that does not update automaticly , I had to update the burst compiler manually.

also when working with it I need to restart unity very often or script changes wont compile.

 

Is there one particular version of the 2019.2 beta which is recommended for this version of the Tiny package?