Official DOTS development status and next milestones - November 2022

just checked 1.0.8 and subscenes still not working
is it problem with my setup or this is not that version which has webGL fixes?

 

It's mostly Editor related issue, Unity version with fix for that still not available yet, but it's on the way (Correct me if I'm wrong @IsaacsUnity)

 

So with the release of the entities package, do you have guys a vision for when IJobEntity<T> will be supported ?

 

Unity 2022.2.20
Webgl still now working with subscenes
Am i stupid or once again that was not the right version with fixes?

Edit: Just read in docs
To use the Entities package, you must have Unity version 2022.3.0f1 and later installed.
I guess that version was ment

 

Appreciate the speedy work here! Just to be sure, do you know when the fix will make into a release? I know it can be very hard to control/predict this, but just want to make sure our timeline is going to fit

 

Good news: on 2022.2.21f and Entities 1.0.10 in WebGL subscenes now working \o/
Bad news: when i try to switch scene by pressing UI Toolkit button i have very strange error (see attachment)

Spoiler: Button code

Code (CSharp):

1. world.clickable.clicked += () =>
2.                 {
3.                     title.text = "World";
4.                  
5.                     if (!sceneData.ValueRO.StartedLoad)
6.                     {
7.                         sceneData.ValueRW.WeakSceneReference.LoadAsync(new Unity.Loading.ContentSceneParameters()
8.                         {
9.                             loadSceneMode = UnityEngine.SceneManagement.LoadSceneMode.Single
10.                         });
11.                         sceneData.ValueRW.StartedLoad = true;
12.                     }
13.                 };

How should I report this?

 

haha finally someone else has this!
I've already reported this (months/years ago) and have been informed josephs hasn't worked at unity for a while.
When it was investigated I was also told i shouldn't have to worry about it

So unless it's causing issues in an actual release build I'd just continue ignoring it like I do now.