Have you been able to reproduce this is a new blank project, or are you testing the same project? This does not mean a new level or new project with the content migrated over. I mean a completely new blank blueprint or C++ project.
Just in case there are things you haven’t tried yet, take a look at the guide below.
Swarm Agent Troubleshooting Guide
Can you provide me with your ‘dxdiag’ so I can take a look at your machines specs?
Make sure your firewall is disabled for Swarm Agent as this can prevent your lighting from building as well.
I have tried it on the same project, in a fresh .umpa scene, with just a few BSD’s, and starter-content materials. Works great. I have been able to delete all of the migrated assets from the troubled .umap, and it works. So it seems clearly an asset in the Content folder, which only bugs things up when it’s in a .umap. I am going to try divide and conquer on bringing back in the migrated assets. I’ll try the dxdiag before I do that: one on the old .umap that has all of the migrated assets, and is failing; and one on the new .umap devoid of them migrated assets.
ran into to this again today(feels like this is a monthly occurence). Went through all of my streaming levels, turning them off one at a time, until it baked properly to find which level contained the issues. After that I deleted 1/2 of the assets, which allowed it to bake properly… So I undid that and deleted half of those assets, until I could narrow it down to one asset that was causing this issue. I deleted that, and went on with my day
Funny(and by that I mean infuriating) enough when I reloaded the level in again with that bad asset after successfully building lights it worked fine… no idea why but yet another reason I have no hair after using this engine for 3 years