New Samples and packages released now

Hello,
I have problem with samples. When I'm openning sample project with 2018.1.0f2 I get DllNotFoundException, Unity can't find burst-llvm.dll file. I checked this directory and .dll file is on its place. I can start project despite this exception, but frame rate is low and editor crashes a lot. Old custom build (2018.1.0b12) works just fine.

 

Why is

Code (CSharp):

1. EntityManager.CreateComponentGroup

now internal instead of public?

 

Hello,

Like @Bitslide, I was surprised to discover that CreateComponentGroup has been made internal.

Currently, I'm using CreateComponentGroup to retrieve entities in a test fixture from which I inherit all of my game's unit tests. Is there an alternative that I should be using for retrieving entities containing specific components from outside of a ComponentSystem?

Of course, in my case, I can create spy ComponentSystems to get their entities, but I'm curious about the benefit of that change.

Thank you in advance and be well!
- S.

 

From the doc:
EntityManager.CreateComponentGroup is no longer public, use ComponentSystem.GetComponentGroup instead.

 

@vanxining:

Thank you for sharing that quote from the changelog.

I did read that, which that is why I mentioned creating a spy ComponentSystem.

Since EntityManager.CreateComponentGroup is a protected method, the only way to access it is from within a ComponentSystem instance, or a class that inherits from ComponentSystem. Thus, one approach to creating unit tests to confirm the contents of a ComponentSystem would be to create, for example, a TestExampleSystem that inherits from ComponentSystem and has a public method that calls GetComponentGroup within it.

While I acknowledge that this is a valid approach, it's far more complicated than simply invoking EntityManager.GetComponentGroup() from a test function. What once only required a single line of code now also requires an a ComponentSystem spy class with a getter method.

I'm simply curious as to the logic/benefits behind making EntityManager.CreateComponentGroup internal, and by implication, also whether or not its affects on Unit Tests/Test Driven Development were considered.

Apologies if my original message is unclear.

Thank you and be well!
- S.

 

Hi @henrikpAtUnity, any plan to release rough ECS roadmap?

 

We have to add this to every ComponentSystem now just for tests?? Why make EntityManager.CreateComponentGroup internal?

Code (CSharp):

1.         new public ComponentGroup GetComponentGroup(params ComponentType[] componentTypes)
2.         {
3.             return base.GetComponentGroup(componentTypes);
4.         }
5.  
6.         new public ComponentGroupArray<T> GetEntities<T>() where T : struct
7.         {
8.             return base.GetEntities<T>();
9.         }

 

Please read other post instead of asking the same things twise!

I think it wasn't considered to be public! GetComponentGroup will return either a new ComnponentGroup or will create one for you. Instead of CreateComponentGroup which will just create one.

-> Performance

Thats I think why...

 

Hi! Unite Berlin is getting nearer by the minute. We're currently planning to expand on our roadmap plans there.

For now, ECS continues to be polished and changed based on your feedback. The larger steps ahead will be clear soon enough.

 

I am not seeing any Entities package in the package manager window of 2018.1.0f2. Is the package only available for the beta version?

 

That is if you already have the Entities package "update your existing Entities package".

If you don't then you will need to edit your manifest like the one you provided in your quote

 

I'm getting similar errors on 2018.1.0f2

Code (csharp):

1.  (0,0): GetAnalyzersFromCompilation threw an exception: System.ArgumentException: Illegal characters in path.
2.   at System.IO.Path.GetFileName (System.String path) [0x0001b] in <e1a80661d61443feb3dbdaac88eeb776>:0
3.   at UnityEditor.Compilation.CodeAnalyzerManager.GetAnalyzersFromCompilation (System.String assemblyFilename, System.String[] unityCompilerArguments) [0x0002e] in <50909ec437ba4fef93e6aebf9535f3b9>:0
4. System.Threading.ThreadHelper:ThreadStart()
5.  
6. (0,0): Unable to start the incremental compiler service:System.Exception: Subscribe exception: EAGAIN(11): Resource temporarily unavailable
7. System.Threading.ThreadHelper:ThreadStart()
8.  
9. (0,0): Object reference not set to an instance of an object

Also, the Package Manager disappeared from Window menu after importing Entities package.

---

Edit:

Removing spaces from the path fixes these errors, as can also be found here.

 

Hi @MartinGram, can know when Reactive System will be released? I think that's the super important feature to write simple code.

 

Hi I'm getting this error in 2018.2.16f1 (It happens in 2018.2.15 and 14)

Read only asset Packages/com.unity.package-manager-ui/node_modules has no meta file.