![]() The following arguments are not specific to Pixel Streaming. MyPixelStreamingApplication.exe -PixelStreamingURL="ws://127.0.0.1:8888" Unreal Engine Launch Arguments MyPixelStreamingApplication.exe -PixelStreamingIP=127.0.0.1 -PixelStreamingPort=8888 This must include the websocket protocol too. If used replaces both -PixelStreamingIP and -PixelStreamingPort. Only required if -PixelStreamingIP and -PixelStreamingPort are not present. The Signalling and Web Server uses the default value of 8888. Specifies the port that the Signalling and Web Server is listening on for incoming communications from the Unreal Engine application. Specifies the IP address or domain name of the computer running the Signalling and Web Server. The following launch arguments must be specified when launching an Unreal Engine application that uses Pixel Streaming:\ This section contains console commands and launch arguments that are useful for applications that use Pixel Streaming. Pixel Streaming Console Commands and Launch Arguments To change this value, set both the -matchmakerPort parameter for the Matchmaker Server and the -matchmakerPort parameter for the Signalling Server.Ĩ889- Opens connection between the Signalling Server and the SFU. To change this value, use the -httpPort parameter for the Matchmaker Server.ĩ999 - for all messages sent by the Signalling Server. To change this value, set both the -streamerPort parameter for the Signalling Server and the -PixelStreamingPort parameter for the UE4 application.ĩ0 - for all HTTP requests coming from clients. ![]() To change this value, set the -httpsPort parameter for the Signalling Server.Ĩ888 - for all incoming connection requests from the Unreal Engine application. To change this value, set the -httpPort parameter for the Signalling Server.Ĥ43 - for all HTTPS requests coming from clients, when the Signalling Server is running in HTTPS mode. You'll need to make sure that these ports are open on the host that runs each of these components.Ĩ0 - for all HTTP requests coming from clients. ![]() The components of the Pixel Streaming system communicate using the default ports specified below. We recommend using the H.264 codec as this is the codec we develop and test against. The encoding speeds listed here are estimates and were taken on an RTX 3060 and an AMD 3900X. With a 1080p stream, as bitrate increases above 20mbps the quality of all 3 encoders would be similar. Has highest image quality at lowest bitrates, compared to other encoders. Produces a better image quality at a lower bitrate.ĬPU performance scales linearly with peers. GPU only encodes one session regardless of peer count. Widely supported across many devices at hardware level. Other browsers such as Microsoft Edge and Opera may require add-ons or plugins, and may not work on all systems.įast encoding/decoding speed. For example, it has been tested and is known to work in recent versions of the following browsers without additional configuration: Pixel Streaming playback works on any modern browser that supports the WebRTC protocol. They have not been tested on any other operating systems, including Windows 7 or 8. However, the Pixel Streaming Plugin and the accompanying Signalling and Web Server have only been tested on Windows 10 and Ubuntu 18.04/20.04. The Pixel Streaming Plugin supports Windows and Linux platforms. If you receive the error message No compatible GPU found, or failed to load their respective encoder libraries when you try to use the Pixel Streaming Plugin, it is very likely that your GPU does not support NVENC or AMF.
0 Comments
Leave a Reply. |