Originally posted by _I_:

Originally posted by Ew00D:

This sadly is not possible, as it gives me a black screen. Also, using a resolution with the same aspect ratio or lowering the resolution to 2K does not work.

you need to enable gpu scaling, so the host will display something

Yes, that setting was already on. The issue was that I was unable to add the 4K resolution because the screen went black. After fumbling around in the dark, I was able to add the 4K resolution and activate it in the NVIDIA Control Panel.

Originally posted by _I_:

Originally posted by Ew00D:

I'm having almost the same issue, only on my 4K TV. The host monitor is an ultrawide 49" display. It does not matter what client or host settings I change. The host resolution will not change.

using gpu control panel, create the non native res 3840x2160@60hz and enable gpu scaling

This sadly is not possible, as it gives me a black screen. Also, using a resolution with the same aspect ratio or lowering the resolution to 2K does not work.

* At moments of sudden high-intensity visual effects (reliable, reproducible trigger: Starting a new game in Elden Ring and scrolling left/right in the
class select menu).

* The host PC's own display output shows no corruption or issue during these events — the problem is isolated to the Steam Link's received/decoded stream.

1.
As a workaround, Moonlight was sideloaded onto the Steam Link hardware and paired with Sunshine as the host streaming server, replacing Steam's built-in Remote Play entirely.

* This eliminates the AMD AMF flicker issue, supporting the conclusion that the root cause is specific to Steam's own AMF integration rather than the AMD driver, the Steam Link decoder hardware, or the display chain

Originally posted by HACKhalo2:

Thing is, I can't enable Hardware Encoding since I have an RX9070XT and it causes what I can only describe as "Display Lag". Like, inputs and the mouse cursor get drawn/executed correctly, but the image will "hang" for upwards of two minutes before it catches up, and then it'll just randomly do it. Unless that issue has also been fixed recently

The hardware encoding lag is fixed in the latest AMD drivers, and the software encoding black screen is fixed in today's Steam beta update.

I get a very consistent frame hiccup pattern when streaming a game that is locked by the developer at 60 FPS (Elden ring, sekrio, megaman zero collection) and is shown on the steam link detailed performance graph (red line and the frame loss counter rises to ~3). Interestingly, starting a screen capture/recording on my Samsung phone completely eliminates these hiccups and the game runs smooth as it records. These hiccups do not occur in games that run at 120hz+

I think I may have pinpointed it down to the Samsung displays LTPO tech that dynamically lowers the refresh rate and this is somehow messing with/conflicting with the steam link stream. Very confusing issue. Is this something the dev team is aware of?

Anydesk was working perfectly until yesterday when the Steam Deck update started causing issues with the "display_server_not_supported" …

Today I tried using Steam Link. After successfully streaming the Steam Deck, switching to desktop mode resulted in a black screen.

Adjusting these settings to lower output display resolution/refresh rate or enable/disable CEC does not resolve issue occurrence.

• For controllers, I use either an official Xbox controller (newer dual-radio version), an official DualShock 4 controller, or the original Steam Controller. I connect one of these at a time to the Steam Link hardware using official Xbox Wireless USB Adapter (smaller form-factor version), official Sony Wireless Controller USB Adapter, or the original Steam Controller's included 2.4Ghz USB Adapter. (Update: confirmed issue persists across multiple types of controllers.)

If it helps, high-level host specs are:

• MSI X470 Gaming Pro Carbon mobo
  
• Ryzen 7 5700X3D
  
• 32Gb DDR4
  
• Radeon RX 6700XT 12Gb
  
• 1TB WD-BLACK SN750 NVMe SSD

I'd try to give a snapshot of the Detailed Performance output in hopes that it could help, but after the first micro-blackout occurs, the graph (and the rest of the hotkey-based Streaming Overlay menu) ceases to display on-screen until I've completely exited and restarted the stream.

So the actual failure case you're seeing hasn't changed, just that Steam is now detecting it and the Steam Link client is able to display a message about it.

If you quit Steam, and then run it from the command-line with "steam -pipewire-dmabuf", you should get a permissions dialogue asking to let you capture the screen. If it does, and you approve that permissions request, does it stream correctly?

If so, then the issue is simply that in desktop mode, Steam isn't starting up in Pipewire capture mode...

But I cant get it work properly on my gaming pc (Nobara, Host), I struggle with several issues, such as a screen sharing window which pops up sometimes I connect with my steam link client (Raspberry Pi, iPhone or Debian .deb).

Everything works very fine after I confirm the screen sharing manually on my gaming pc (Host) and when I keep the display/monitor activated. I think I am not the only one on linux who likes to use steam link?

Extra remarks: Things I like

• Loved using this in flat screen with iPhones/iPads as controllers, the gyro input was hard to figure out but eventually worked great
  
• Can't wait for the Steam Frame!
  Link is really optimized and vertically-integrated, allowing for lower latencies and for VR specifically, not needing to use OSC for tracking, making it way more accurate and way less drifty

Extra remarks: Other small Issues

• In SteamVR spatial menu, clicking 'desktop' shows the desktop but only for the first time clicked in the session, leaving then trying to reopen will just leave blank space where the screen should be, DE: Cinnamon 6.6.7 (X11)
  
• Sometimes at random the spatial menu will go from the old steam interface to a new sort-of 'pacified' interface that only allows games to be launched and does not have a way to access the storefront nor mess with launch options, compatibility settings, or whatever else needs tinkered with and it requires using the desktop to actually access any of that.