Update: I found a workaround.
- Open the Output Log (Window → Output Log in the top menu)
- Stop both the servers by entering these commands:
You’ll see each command appear in green in the output log as you enter it. In my case,
StopServer reported that the service was stopping;
StopWebSocketServer ran without any output. Both commands were necessary to avoid “cannot bind to port” errors.
Repeat this each time you open the editor. It doesn’t seem to be necessary one build to the next.
– Edit –
This lets me get through the packaging process, but the packaged app displays all black. Checking the logs, I see the same error, “unable to bind to port.”
For comparison, I created a new project from the “Game → Blank” template, and this one doesn’t encounter the error during cooking, packaging, or running the packaged game. My “broken” project is based on a video production template – I suspect the issue is around ndisplays, but I only think that because it’s what I’m trying to learn right now
– More edit! The whole story as it develops! –
In my original project – the production template where I’m trying to use ndisplays – I went into Project Settings → Plugins → Web Remote Control and disabled “Auto Start” for both Web Server and Web Socket Server. Then, I did my above workaround to get through the packaging phase.
The good news: the packaged app runs and shows the scene! No more black view when launched standalone. When launched through NDisplayLauncher, the “cannot bind to port” error no longer appears. Progress!
The bad news: Launched through NDisplayLauncher, the app still shows a black screen.
In the logs for the instance, there are some “failed to load” errors right at the top for aqProf.dll, VtuneApi.dll, and VtuneApi32e.dll, and then a ton of warnings about unreadable Slate resource files. Attaching my log file in case someone more knowledgeable wants to take a look.
ue5blankstarter.log (152.8 KB)