nil display objects causing bugs in setParentGroup after 0v956c update

Hi dyson.

There appear to be some nil objects within the mastergroup which are causing the copying of display objects in setParentGroup to fail. I did a quick work around by just simply adding mastergroup as a child of the parent group. I guess another fix could be to check if a given child is nil before attempting to swap its parent.

  (could this be due to the recent noDraw updates?

are some objects being nulled before being removed from the mastergroup?

Thanks for bringing this to my attention steven3, I think you’re right about the noDraw update. On the other hand, display groups shouldn’t really contain nil children. I’ll look into it on my end. I’m knee deep in the rewrite right now, but I’m pretty sure this problem is going to become a non-issue when the new culling system is in place.

Thanks for bringing this to my attention steven3, I think you’re right about the noDraw update. On the other hand, display groups shouldn’t really contain nil children. I’ll look into it on my end. I’m knee deep in the rewrite right now, but I’m pretty sure this problem is going to become a non-issue when the new culling system is in place.