Post by Admin on Jul 16, 2016 3:42:35 GMT
JuDelCo @judelco Aug 20 2015 09:47
"Restored previous pool.DestroyEntity() behaviour" & "Disabled entity pool in Pool. Explicitly opt in by defining ENTITAS_ENTITY_OBJECT_POOL"
Mmmm interesting, you are working in a better replacement or that entity pool wasn't that good/necessary ?
Andreas Wilcox @svdvorak Aug 20 2015 19:25
I wrote a little about Entitas in a short blog post, though mostly just explaining what it is.
Simon Schmid @sschmid Aug 20 2015 20:31
@judelco We still have discussion about the actual behavior, when you call pool.DestroyEntity(e); We changed it in the last release, but I reverted it again for the next release
Having an object pool for entities can cause the problem we discussed earlier, where reactive systems have a reference to a collected entity, but this one got destroyed and is reused with pool.CreateEntity();
Simon Schmid @sschmid Aug 20 2015 20:48
By simply not having an object pool, we can solve this issue
JuDelCo @judelco Aug 20 2015 21:32
Having multiple internal entity pools like in my closed pull request could solve the issue, but i guess you didn't like that solution xD
"Restored previous pool.DestroyEntity() behaviour" & "Disabled entity pool in Pool. Explicitly opt in by defining ENTITAS_ENTITY_OBJECT_POOL"
Mmmm interesting, you are working in a better replacement or that entity pool wasn't that good/necessary ?
Andreas Wilcox @svdvorak Aug 20 2015 19:25
I wrote a little about Entitas in a short blog post, though mostly just explaining what it is.
Simon Schmid @sschmid Aug 20 2015 20:31
@judelco We still have discussion about the actual behavior, when you call pool.DestroyEntity(e); We changed it in the last release, but I reverted it again for the next release
Having an object pool for entities can cause the problem we discussed earlier, where reactive systems have a reference to a collected entity, but this one got destroyed and is reused with pool.CreateEntity();Simon Schmid @sschmid Aug 20 2015 20:48
By simply not having an object pool, we can solve this issue
JuDelCo @judelco Aug 20 2015 21:32
Having multiple internal entity pools like in my closed pull request could solve the issue, but i guess you didn't like that solution xD
