I have looked around at the other swarm questions but it doesn’t seem that anyone’s had this particular problem.
I have another client that connects to the coordinator, reports that its available and is even assigned to my machine for work b ut never actually gets assigned any. I’m testing this by building lighting in the Sun Temple example so I get a nice hefty build job to ensure that Swarm will want help from remote machines.
[Log][1]
Did you ever find a solution for this? We are having the same issue, also testing on a huge map. The computers are assigned but remain “Available” and never actually do any work.
Same problem here.
Can’t get it to work.
Only the machine that is starting the building process also renders the lightmass.
I resolved it with me:
The clients had no permission to access the network drives where the Unreal project was stored.
Share the source folder of unreal engine in the computer that is not running the Swarm Coordinator.
Hi, some informations there : Swarm Coordinator is not coordinating - Platform & Builds - Unreal Engine Forums
I’ve got a similar issue with additionnal ping problem during rendering though.
A.) Run as Administrator
B.) Manually open up TCP port ranges 8000-8010
C.) Disable Password protected file sharing/discovery in the network settings
D.) Pray to the lightmass gods for leniency and forgiveness
Hi,
I had this problem as well, was getting really frustrated. Went to do a light build yesterday and the server would only show the PC working away while not joining in on the coordinator at all. Checked settings (which haven’t changed since December 2018) over and over. Couldn’t figure it out.
Restarted all coordinators and clients, same problem. Server’s swarm wouldn’t even show in it’s own coordinator. So I get it to ping itself… Then it worked. Was able to render. Keep in mind - I changed nothing at all. No setting changes whatsoever of any kind. Restarted coordinator and swarm clients, pinged the server with it’s own client, and it worked.
Now today, I go to do one, server won’t pick up at all. Just sitting and waiting to become available. I look and look. Well… Windows 10 just up and decided to switch off network discovery and sharing on my PC. I was literally using it last night. I definitely, when powering down, didn’t decide to go and just turn off network discovery as a last step.
So Windows 10, sometime this morning or before I went to bed, decided completely on it’s own that I was done with all this “networking stuff”. Turning it back on, obviously, has solved the problem…
