I’m running into an issue where Pixel Streaming connects successfully, but the browser only shows a flat colour instead of the rendered scene, while the same packaged app displays correctly when I run it locally.
Setup:
- UE 5.7 on macOS (Apple Silicon, M4)
- Pixel Streaming 2 plugin
- Signalling server from PixelStreamingInfrastructure (EpicGamesExt, UE5.7 branch)
- App packaged for Mac and launched via terminal/
.commandscript
Symptom:
The WebRTC connection establishes normally. The stats overlay shows a steady FPS count and normal ping/heartbeat. But the actual video shown in the browser is just a solid colour (it shifts between blue and green depending on which way the in-game camera is facing), not the scene itself. The local windowed instance of the same app renders the scene correctly the whole time. What I’ve come to noptice is that the colour that is there in the top left corner of the packaged app is only being streamed to the browser. The image shows the views side by side and I’ve drawn a red box around the area I think gets streamed.
What I’ve tried:
- Tested in both Chrome and Safari, same result in both
- Tested locally on the Mac and over Wi-Fi to a phone, same result
- Packaged two different test projects (a VR template and a plain game), both showed the same flat colour
Question:
Has anyone else seen the stream connect cleanly (good FPS, good heartbeat) but output a flat colour rather than the actual frame? I’m trying to figure out whether this points to a macOS/Apple Silicon-specific rendering path issue in Pixel Streaming 2, a viewing volume/FOV misconfiguration, or something else in how the encoder is reading the framebuffer. Any pointers on where to dig next would help a lot.