why I cant use pixel streaming in UE4 4.24 verson.

[mjqi]

i cant find any WebRTC files in verson 4.24 ,so how to run pixel streaming .

[S-Dot]

It's still in beta. So maybe post your question in the 4.24 preview threat or wait till the first real version comes out. Those features often only get implemented at the end.

[mjqi]

It's still in beta. So maybe post your question in the 4.24 preview threat or wait till the first real version comes out. Those features often only get implemented at the end.

thanks,maybe you are right.

[Pixelpirates]

Now it's out of beta and I still can't run Pixel Streaming. Documentation says that WEBRTC aren't needed anymore, but when I run the pixelstreaming demo, I get to the screen with "click to start". but when I click, nothing happens. Both on mobile and desktop, using local connection.

[chengqing.zhou]

Based the feedback I got from Andriy from dev team.
“WebRTC Proxy was removed in 4.24. Documentation is still not updated. Now to enable streaming you need to provide additional command-line args: "-PixelStreamingIP=localhost -PixelStreamingPort=8888" ("localhost" points at Signalling Server location)”

[Stuart.Hill2]

Hi,

Indeed, there have been some changes with Pixel Streaming in the new 4.24 version.

The WebRTC Proxy has now been removed.

The SignallingWebServer has moved and I now find mine in the location: C:\Program Files\Epic Games\UE_4.24\Engine\Source\Programs\PixelStreaming\WebServers\SignallingWebServer

You need two additional command line parameters to be added to your UE4 application; for example, if I am doing a basic local test (with everything running on the same machine) then I would add:

-PixelStreamingIP=localhost -PixelStreamingPort=8888

If you make these changes then you should be able to connect via Pixel Streaming again.

Thanks, Stuart.

[noted1]

Hi,

Indeed, there have been some changes with Pixel Streaming in the new 4.24 version.

The WebRTC Proxy has now been removed.

The SignallingWebServer has moved and I now find mine in the location: C:\Program Files\Epic Games\UE_4.24\Engine\Source\Programs\PixelStreaming\WebServers\SignallingWebServer

You need two additional command line parameters to be added to your UE4 application; for example, if I am doing a basic local test (with everything running on the same machine) then I would add:

-PixelStreamingIP=localhost -PixelStreamingPort=8888

If you make these changes then you should be able to connect via Pixel Streaming again.

Thanks, Stuart.

Where do I have to add that two additional command lines parameters? In the signallyingWebServer file? In the pre-compiled project? Or after open all the server files and run out my UE4 application opening the console commands?

[Stuart.Hill2]

The command line parameters are for UE4, so when I am running a test then I run:

UE4Editor.exe ..\..\..\Collaboration\Samples\PixelStreamingInput\PixelStreamingInput.uproject -game -RenderOffScreen -PixelStreamingIP=localhost -PixelStreamingPort=8888

Or if you are running via Play-in-Editor (Standalone Game) then you would add these options in the Advanced Settings:



The Signalling Web Server can just be run with the run.bat script in the C:\Program Files\Epic Games\UE_4.24\Engine\Source\Programs\PixelStreaming\WebServers\SignallingWebServer directory. You don't need to change that script normally.