Blueprint pitfalls and death traps

[n00854180t]

@Mike.Beach;118214

Yeah, usually there’s one asset that’s problematic. The one that “completed the loop”. Any assets in the chain can generally be removed to unblock you, and allow for a successful load. This can help narrow down assets that are part of the circular dependency chain. Usually you only have to roll back a singular asset, but narrowing it down can be tough if you underwent a lot of changes in one session.

So if you hit something like this, try removing the most recent files that you’ve worked on. It can help narrow down the culprit(s), and help you identify the dependency chain that you may have been unaware of. This is obviously not THE solution, like I said we have a plan in place to address this, but this advice could help unblock people in the meantime. And like I said, if you figure out the dependency loop, then please let us know so that we ensure the scenario is fixed by our refactor.

I wanted to briefly add on to this that the error logs are invaluable for fixing a crash issue like this. I had one recently when porting up to 4.3 from 4.2.1, which resulted in one of the assets I had not loading its collision volumes right.

I was just about to roll back the project to a previous revision (which would have undone a fair amount of work) when I went through to the logs and found that it was one particular asset crashing - so I was able to revert that one single asset and get the project working again.