Please explain additive scene workflows

News & General Discussion
1

We’ve definitely been plagued by the yaml merge issues (and the new yaml smart merge just isn’t working for us (like literally at all)). We’ve explored several options but most just sound like way more hassle than it’s worth.
But I just recently, and am embarrassed by this fact, heard about the additive scene workflow, where people work on different aspects and combine scenes later.

Would you guys be willing to elaborate on this workflow? Preferably people that use it. Having never tried it it seems like it would be difficult to keep things straight, but if done well could be really useful.

Also any other advice for teams working on the same scene… that’s good too. :slight_smile:

EDIT: Another thing I’ve heard of I believe are something like asset bundles? Where there are actually multiple projects that are then combined into one project. So a UI team has a project, and level designers have a project, and gameplay logic, etc etc. Any thoughts on that would be neat as well.

Oh and I can read specific in the documentation, so I’m really just looking for workflow implementations here. Thanks guys’n’gals.

2

As far as I know it just means certain assets are not freed up as the scenes switch, allowing them to retain their settings/state and presence in the next scene as if they are in both scenes. Unless there’s more to it than that.

3

What are the issues you are experiencing with the smart merge tool?

4

I posted this before I got smart merge working. This was completely a user error. I had never used an external merge tool before as the default Git merge system worked for me. I didn’t realize I needed to call the mergetool directly from the command line, and just assumed it would work automatically on a conflict.