 So, a new commit just happened, right, in Lambda 2.8? Yes, yes. Now, groups are gone and the collection system is more powerful because we can now do everything that groups used to do. And so the reason we made this change is for animation pipelines where in the past you would have to set up your scene and then set up your group separately and those could get out of sync and it could get really confusing like which ones are visible, which ones aren't. And so we decided to unify them so there's just collections now. What are the advantages of this? So the advantages, I mean, the main thing is just this whole character pipeline setup, animation pipeline setup where instead of having to define a separate group you can just say now I want this part of my scene and just transplant it into another scene and you basically get everything along as you would expect. So there's a new blog post that explains all the details like how you do instancing, how this works with linking, how this works with visibility. So basically one thing is the instancing. So previously you would have to create a group for instancing, now you can create a collection which is mostly the same thing from the instancing point. If you were just going to create a collection with some objects in it that you can instance. The one difference is that the collection can now exist directly in the scene instead of being somewhere floating out. So in the old behavior to link a character I will link a group from another plan file. I can just link a collection right now and it will make a duply collection. A duply collection, that's just called a collection instance. Okay, yes. And this also works with, is compatible with the way cycles had for excluding, right? Or including players. So another change that we're making is the visibility. In 2.8 the visibility was purely per view layer which didn't work so well with linking because it wouldn't come across when you linked it. And so now we have visibility controls on the collection itself which get linked along. Or per view layer you can also still say I want to exclude like this part. Like if you want to have a separate render layer for like your character and your background and then compose them together later you can still do it. But those are not separate. You know just the visibility for everywhere or just the visibility in a specific view layer. Also, is this compatible with all files? If I open a file from 2.8.7? I would say it's like 90% compatible at the moment and like the other 10% will be like the view layer override system that the UI is working on. So it's mostly, it's a lot closer than it was before. So opening 2.7 files would 90% be all there. The layers, the all layers will be now collections and the groups will be collections as well. Yeah, they will just be collections that are not in a specific scene. Just unlinked from the scene somewhere. So check out the blog post. It's in the code of Blender of Dark, right? Yep. Nice. Cool. So thank you very much. Thank you. Wait, I almost throw away like look at the mess. We're moving here, so.