Pixel Streaming Plugin 2 Compatibility

Epic Games introduced Pixel Streaming Plugin 2 (PSP2) with major architectural changes and improvements to Unreal Engine’s Pixel Streaming system.

Eagle 3D Streaming currently supports Pixel Streaming Plugin 2 only with Unreal Engine 5.7 and newer versions for standard Pixel Streaming playback.

However, browser-to-Unreal and Unreal-to-browser communication features are currently not supported with Pixel Streaming Plugin 2. If your app requires communication between the browser and Unreal, use Pixel Streaming Plugin 1.

Current Compatibility Status

Main Known Issue

Issue 1. Video Stream Doesn’t Start

Applications built with:

• Unreal Engine 5.5

• Unreal Engine 5.6

using:

• Pixel Streaming Plugin 2

may experience a critical issue where:

The WebRTC connection successfully negotiates, but the video stream fails to start (Figure 2)

Issue 2. Communication between browser and Unreal

Pixel Streaming Plugin 2 may also have limitations with browser-to-Unreal and Unreal-to-browser communication. Features such as frontend messages, UI interaction messages, and Unreal-to-browser responses are currently not supported with PSP2.

Why This Happens

The issue appears to be highly dependent on:

• Geographic region of the streaming machine

• Geographic region of the end user

This behavior originates from Epic Games’ Pixel Streaming Plugin 2 implementation in Unreal Engine 5.5 / 5.6.

Eagle 3D Streaming only replicates Epic Games Pixel Streaming infrastructure and behavior. Therefore, this issue is not platform-specific and also occur when using Epic’s own signaling server and infrastructure directly.

Example

Let’s say:

• Your application is hosted in the USA (Streamer Machine Location is in USA)

• The app is built with:

  • Unreal Engine 5.5 or 5.6

  • Pixel Streaming Plugin 2

User Connection Results:

Similarly:

Recommended Setup

Important Note About Internal Testing

Many teams do not immediately notice this issue because:

• Local testing often works correctly since both the streamer and browser are under the same network and geographic location

As a result, applications may appear to function correctly during development and internal QA testing.

However, the issue becomes significantly more visible during:

• Public deployments

• Global user access

• Cross-region streaming scenarios

This is why some applications work perfectly during internal testing but experience video stream failures after being deployed to users in different geographic regions.

Also, if your application uses browser-to-Unreal and Unreal-to-browser communication, make sure to test features such as frontend messages, UI interaction messages, and browser-to-Unreal and Unreal-to-browser responses. These communication features are currently supported with Pixel Streaming Plugin 1, but not with Pixel Streaming Plugin 2.

What’s Next?

• Once Epic Games fixes the Pixel Streaming Plugin 2 video stream issue, the fix should automatically apply to Eagle 3D Streaming as well.

• We are working to add browser-to-Unreal and Unreal-to-browser communication support for Pixel Streaming Plugin 2. Until then, use Pixel Streaming Plugin 1 for communication features.

Need help?

If you need any assistance, feel free to reach out through any of the following channels:

🛠️ Support Portal: Contact Our Support Team

💬 Discord Community (Faster Support): Join Our Discord Community

📧 Email Support: support@eagle3dstreaming.com

🆓 Get Started for free

Follow us on:

Facebook | GitHub | LinkedIn | YouTube