I can connect on my instance on localhost:3000 though.

This issue seems to be all over the internet in regards to Unreal Pixel Streaming. It might not be associated with AWS per se but it is still an issue that is affecting the end result that this repo is trying to do.

The issue is that clients are not able to connect properly. Users are greeted with the "Click to start" page. Clicking this updates the page with a few controls and the text "Starting connection to server, please wait...". From this point on nothing more will happen.

I believe this to be a networking issue with the TURN server but still have to dig for more information.

Also note that I have tried to connect from multiple machines directly connected to the internet. Any ideas would be great.

I looked at the logs, I saw this:
A D3D11-compatible GPU (Feature Level 11.0, Shader Model 5.0) is required to run the engine.

I think the default instance doesn't have a compatible GPU. I don't know how to proceed.

Thus, the build is not running. Please note the webserver does start:

with the current implementation, if a user doesn't change the default password, then it can be exploited. turns out the default password isn't needed because if removed it will force the end user to create the password, which is the behavior desired.

When connecting from public domain using the dns generated after the cloud formation deployment;
I am stucked at Starting connection to server, please wait
Kindly assist....

I followed the documentation, and it turns out I need to add specific roles which took me hours to searched for it. maybe the documentation needs to be updated?

Here is an update that is required to make this work with 4.27
I tried setting it up and I had issues for first because of changes Unreal did to the Pixelstreaming in 4.27.
In order to make it run for 4.27, this change has to be made on the bootstrap.ps1:

Change the Folder path of runAWS_WithTURN.bat from

'C:\PixelStreamer\WindowsNoEditor\Engine\Source\Programs\PixelStreaming\WebServers\SignallingWebServer\runAWS_WithTURN.bat'

to

'C:\PixelStreamer\WindowsNoEditor\Samples\PixelStreaming\WebServers\SignallingWebServer\platform_scripts\cmd\runAWS_WithTURN.bat'

Just writing an update to this repo. Please see Post #6 at https://forums.unrealengine.com/unreal-engine/feedback-for-epic/1869186-pixel-streaming-not-working-in-chrome-version-89-ue4-will-crash-when-i-access-signallingwebserver

For the fix.

"This is happening due to the recent change in Chrome M89 to use the extmaps-allow-mixed SDP attribute by default."

Thought I might make a request here so it can be updated for others.

In the ps1 script that starts the turn server, the flag -UseBasicParsing is missing. This means it fails to run the turn server when run as a scheduled task under SYSTEM. Tested on AWS.

the DCV Server install script: https://s3-eu-west-1.amazonaws.com/nice-dcv-cfn/dcv-server-install.ps1 says "Permission denied" when attempting to access it. Therefore the cloud formation script does not finish at the moment and perpetually sits in a "WindowsInstanceWaitCondition"

Is there an updated version for UE5?

UE5 is a total game changer... Lumen, Nanite..... !

What I'm expecting:
I wanted to set up a pixel streaming application in an auto scalable group, with an internet facing load balancer. With that, I hoped users would have personal access to the engine such that they can run their own 3D experience without seeing what happens to the others.

What I've done:
I built a Cloud Formation stack as I followed the instructions given in the guide. The stack worked well. With the EC2 instances allocated, I took a snapshot and initiated a custom AMI. Then, I launched EC2 g4dn.xlarge instances with this AMI. At that point, I created an auto-scalable group and I attached a load balancer to the group.

The issues:
Several issues occurred when I tested the built application :

• This error raised on console : WebRTC: ICE failed, your TURN server appears to be broken, see about:webrtc for more details

  and the page is stuck on “Starting connection to server, please wait”

• I tested with two instances, and if one works, the other one does not. The other one is stuck on “Starting connection to server, please wait” or “Streamer disconnected”

• If a new user try to connect to the load balancer, for all the other users who are running the application, the page is reloaded.

I would be thankful for any help.

Hello!
How to adapt Pixel Streaming from MetaEditor.io to AWS?

Hi, I'm using your solution to deploy pixelstreaming client. Everything works fine. But when I change the resolution of the Unreal Project on launch in the ps1 script the Unreal client doesnt connect to the Signaling Server and it crashes. I assume it's because the default screen resolution without monitor is 1024x768.

Here is the command I use: $action = New-ScheduledTaskAction -Execute "C:\PixelStreamer\WindowsNoEditor$buildExecutable" -Argument "-AudioMixer -PixelStreamingIP=localhost -PixelStreamingPort=8888 -ContentIDs=1,2,3,4,5,6,7,8,9 -WinX=0 -WinY=0 -ResX=1920 -ResY=1080 -Windowed -RenderOffScreen -ForceRes"

Note: When I connect with dice viewer screen resolution of the windows instances is changed to 1920x1080 and I can also launch Unreal client now with this resolution. So I assume I need to install a display adapter or similar. But was wondering if there is a simple solution. Not much to find at google about this.

Thanks in advance for help.

Best,
Dom

We need to serve the Pixel Streaming in an iframe inside our page served via HTTPS. But due to the browser's security policy, we need to load the Pixel Streaming page as HTTPS as well.

How can we get the key.pem and cert.pem files from AWS certificates?

To point new connection/players directly to new/available instances and sessions, which is the preferred method, creating an Elastic Load Balancer or somehow setting up a Pixel Streaming Matchmaker server?