Entities Invisible with Hybrid Renderer v2

That function has an overload that takes a command buffer.

That's the point. There's a ridiculous mess of components involved depending which render pipeline you're using, it's not something we should need to be concerned about just to get something to render.

And yes, there's unfortunately some frustrating undocumented stuff like needing to update renderbounds manually if you change a mesh. Hybrid renderer seems to change a lot between versions, I wouldn't expect super detailed documentation for something like dynamic meshes which is far from the common use case as far as I know. And I say that as someone who does a lot of stuff with dynamic meshes.

 

No doubt most just want a quick out of the box solution for these things while getting the boost of ECS. I know i'm looking forward to 'BatchRendererGroup' seems to be the new goto for custom render solutions. (Graphics class had some limitations)
But my UI was using the default hybrid, and unlit shaders. But upgrading to v0.11 broke them. But only like sometimes? It was weird. I thought it was broken, I still kinda do.. I'm not sure. But my custom < 100 line render systems had no issues. The only issue is I had to code a bit extra to push the instance data through and add custom shaders.
I guess ill just keep staying on the old package until I write a render system for it lol but it's weird that it's kinda broken

 

Same problem, is there any solution?

 

Is that using a prefab entity? Will a entity archetype do the same job?
I did convert my spawning to using EntityCommandBuffer.ParallelWriter.Instantiate in parallel systems, however this involves an extra step of sending creating an event component back onto the parent object, and then passing in any uninitialized entities... in order to link them.. This hasn't really caused issues yet though in performance, but perhaps any adding and removing components will causing the main thread to stall? So in general we should do any adding and removing in OnCreate, and the rest of our systems to use use EntityCommandBuffer.ParallelWriter.SetComponent! Reducing any add and remove components that occur. I guess even if its convenient to use set and add, it's better to have prefab entity variations right?

Also regarding the rendering issues.. not sure how I fixed it, but after updating my unity editor from 2020.1 to 2020.2 it seems to of been fixed.

Edit: I've posted around, but still stumped. What's the best way to create a camera using pure ECS? Is there a way yet or will there be? (same goes for audio listeners)

Edit2:
What is the best way to do events based on the above best practices. Would you recommend adding event components onto entities (AddComponent<ButtonClickEvent>). Or just creating new entities (with ButtonClickEvent) from a prefab entity, and then injecting those into other entities to trigger event functionality, and destroying the even entities after.
So I am wondering whether EntityCommandBuffer's CreateEntity would be better then AddComponent in terms of events.

 

I need Instantiate a lot of entities from a prefab entity, should i use entity command buffer or just use EntityManager?

 

If you use a command buffer you can only instantiate one at a time. With EntityManager you can instantiate many at once with overloads using a NativeArray as output. https://docs.unity3d.com/Packages/c...llections_NativeArray_Unity_Entities_Entity__

 

Yes, i found that and use EntityManager now. But i think that is weird, why entity command buffer can't do this.
Addtionally, my entities are invisible too and i can't find the reason.

 

I saw in another thread that command buffer should be getting nativearray versions of instantiate in the next release.

 

This is good news, thank you !
I wonder if it will be more efficient to spawn a list of the entities then spawn one at a time when command buffers get that functionality. Perhaps it is faster due to the way it handles the memory there.

 

Did you find a solution to this?

 

For me, switching to vulkan worked on device

 

Anyone got a good simple example of how to do this, currently generating entities from a GO Manager as per another example but this is not working vie EntityManager now?

 

I would create the 'spawn lots of things' event from the go manager and add the prefabs to that. Then with the spawn system using ScheduleParallel, pass in the prefab data! Atm I spawn them individually using that Instantiate function.. So really hoping for the batch function later.
I recommend using the unity ecs documentation for the functions. I'm not sure what code you have as reference, but you just declare the prefab outside the job to pass it in.

 

I find this confusing as I thought that once an entity was added to DOTS it would be incorporated within the systems relevant to it *automagically?

*Well some internal system would ensure new entities were added to the relevant chunks.