Hi guys, can someone please help me figure out what is wrong with this thing? I set up my project, enabled the plugins (VirtualCamera, virtualCameraCore, LiveLink, LiveLinkControlRig, LiveLinkCamera) Ik i overdid it but i wanted to have it work so enabled few that were not asked. I also saw few people enabling apple but since I use android, i enabled android ones which were already enabled tbh. I also changed Frame Buffer Pixel Format to 8bit RGBA under project settings.
I chose the right IP address on my Engine under plugins-UDP Messaging, made sure my PC and android phone are on same network but I still can’t connect the application to my project. I even created a new blank project, but it’s the same effect. and yes I have tried to manually enter my IP address on the app, it gives me the same error message. “Unable to connect to xxx.xxx.x.xxx:xx, please check the IP adress and the network status of the Unreal Engine instance and try again”.
On some forums it was mentioned that i change streamer Port and viewer port under Pixel Streaming but those doesnt work either, unless i’m doing something wrong.
Please help, your input will be truly appreciated _/_
~ guy who is tired of troubleshooting this darn thing since last 2 projects
There is a bug if you have the -noaudio option enabled that will be fixed in 5.4.4. Do you happen to have that enabled? What android device are you using?
Also can you make sure its not a firewall issue? Can you check the Unreal is allowed access to the private network.
And you mention getting IP from plugins UDP messaging - I would not recommend that. Please use the IP from the Pixel Streaming toolbar, when you click it, it will show your IP options - e.g. like 192.168.0.20 or something like this.
I’m having the same issue as the OP. I’ve tried using all the IP options provided under Pixel Streaming but none have worked. I’ve tried connecting using the app both on an iPad and an Android phone. Both can see the Unreal project connection, but both get the same “Failed to connect” message when I tap on them.
The VCam1 component in the Live Link panel, under Pixel Streaming, shows a yellow dot. I can see the VCam HUD in the Unreal viewport, and I’ve temporarily disabled the Windows Defender firewall to discard that as a possible issue.
I’m not sure if this is helpful, but when I enable “Start Streaming” (under the “Pixel Streaming” menu) I get this output repeatedly in the output log:
LogPixelStreamingSS: Failed to connect to SS ws://127.0.0.1:8888 - signalling server may not be up yet. Message: "HS: ws upgrade response not 101"
LogPixelStreamingServers: Websocket client connected. Remote=192.168.40.139:49817 | Local=192.168.40.12:80
LogPixelStreamingServers: Sending to player id=396: {"type":"config","peerConnectionOptions":{"iceServers":[]}}
LogPixelStreamingServers: From Player id=396: {"type":"listStreamers"}
LogPixelStreamingServers: Sending to player id=396: {"type":"streamerList","ids":[]}
LogPixelStreamingServers: Websocket client connected. Remote=192.168.40.139:49818 | Local=192.168.40.12:80
LogPixelStreamingServers: Sending to player id=397: {"type":"config","peerConnectionOptions":{"iceServers":[]}}
LogPixelStreamingServers: From Player id=397: {"type":"listStreamers"}
LogPixelStreamingServers: Sending to player id=397: {"type":"streamerList","ids":[]}
LogPixelStreamingSS: Closing websocket to SS ws://127.0.0.1:8888
LogPixelStreamingSS: Reconnecting to SS ws://127.0.0.1:8888
LogWebSockets: Warning: Lws(Warning): lws_client_handshake: got bad HTTP response '400'
I’d appreciate any help as I’ve poured hours trying to get the vcam to work but I’m still stumped.
EDIT: I tested my iPad with a friend’s workstation who has Unreal 5.4 installed, and the vcam worked instantly without any problems, so the problem seems to be with either my workstation or my local install of Unreal. I still don’t know how to fix it, but I thought I’d post an update with this information in case it helps narrow down the issue.
Ok, I was finally able to fix my issue, so posting here in case the information can help someone else. It turned out port 8888 was being used by another application. In my case it was BTSync, which I had set up as a windows service running in the background years ago. I now don’t need that anymore, and in fact I had forgotten it was set up as a service at all.
The way I figured it out was by running this command in a shell, which will tell you if there are any processes using port 8888:
netstat -ano | findstr :8888
If you do, the command may return something like this:
TCP 127.0.0.1:8888 0.0.0.0:0 LISTENING 4696
Which means the there’s a process with ID 4696 using port 8888. Then, to figure out which program the process belongs to, you can run this other command (replace the last number with whatever process ID you get):
tasklist /fi "PID eq 4696"
When I ran it, the command told me that the name of the process was BTSync.exe, which I uninstalled and then all the issues went away.