It is not a Steam game as I got it from another platform but non Steam games work with literally 0 issue for me to stream, except Rogue Trader for some odd reason.

I click the exe. The game launches. In the loading screen I can move my cursor around. Once it loads the cursor becomes frozen and everything is stuck on the input side. Someone who goes up to my PC can interact with it just find but my laptop to where it is streamed just does not give it any input.

If I add it as a non Steam game it turns on but now I just get a black screen with only the cursor being visible which I can move around. Eventually the cursor dissapears too and the game enters main menu and now it is just a blackscreen with music.

Anyone know what might cause such issues? It seems odd to be an issue taking place in one game only :/

Hi there!

I bought the steam link box in January, and I'm fairly happy with it, despite its age. I'm using it with Sunshine, Moonlight and Playnite. My pc is connected to a powerline, and a ethernet cable links the router to the steam link. However, there's something that's bothering me, and I wonder if you can help me.

Generally the image quality is fine, but it suffers severely when there's fast movement and/or dark scenes. In these situations the macroblocks rear its ugly head. Banding is also present, too. I've tried to tweak the Sunshine configurations, as well as increasing the bitrate in the Moonlight options, to no avail.

Did this happen to someone else? Is this unavoidable, since it can only support H.264, or is there a solution?

PC specs:
i7 8700K
32 GB DDR4 RAM
SSD SATA 860 EVO 1TB
Nvidia GTX 1050ti

For the past two days I have had this issue where for some god forsaken reason the Steam Link app for PC has been refusing to open and would just send my cursor to the bottom-rightmost side of my screen. I have tried reinstalling the app, but of course that didn't work (because why would it =w=).

Please help i'm legit becoming desperate atp.

Hello. I am new to VR and I want to connect to Steam via steam link to play some games, but there is no sound and it is not detecting my microphone. I have followed a few tutorials on youtube and none seemed to work. Any tips would be great.

I have an ethernet connection and the client is a Amazon firestick with a device that surpasses the 100mbs limit. Speed test I get roughly 250mbs on the firestick speed test and the steam link speed test

Based on my photo, I know the ping is very high. So my computer is wired, and gets 1gig speeds. 1 travel for work and don't have access to wifi a lot of times, so im forced to use my 5G cell with verizon. On my phone 1 get roughly 100mbs+ speeds. I know speeds arnt the only factor. But someone - ran into uses the app, and he's able to play on 5G with no problem. So im not sure what I might be doing wrong.

My ISP gave me a gateway, so I don't know if that might be an issue or not. I checked and im not behind a cgnat thing. My nat type is open. Im getting nearly 1gig speeds with less than 15ms ping as far as my ethernet computer goes.Verizon is just that, verizon. The guy I ran into has T mobile. So I dont know if network really matters or not. But usually 100mbps speeds plus, and less than 15ms pink test. I haven't tried pinging my phone to my computer yet.

But any help or thoughts would be greatly appreciated. Thank you.

I have recently switched from Windows over to Fedora, and I seem to recall there being a setting present in the Windows distribution of Steam that allowed me to tell the host machine to match the client screen resolution. That option doesn't exist now, so when I stream from my ultrawide PC to my TV, I get a letterbox effect.

What's weirder is that when I play with settings to fix it, the client side will lose all video. The only fix is to fully reboot the host steam application.

I definitely had my steamlink dialed in when I was running Windows, so it would be nice to get it working with Linux as well. Anyone found a fix for this before?

Hola, he añadido AC Origins (comprado originalmente en Ubisoft) a Steam Link para poder jugar en mi tv, tengo un control Cyclone 2, sin embargo el mando no funciona como debe y no puedo jugar (ocurre solo con este juego).

1. Cuando conecto a la pc y abro el juego desde Steam usando Steam Input, funciona normal y puedo jugar.

2. El control no funciona cuando abro Steam Link en la tv (con el mando conectado por Bluetooth).

3. Ya seguí las sugerencias de la IA (como desactivar superposición) y no funciona.

¿A alguien le ha ocurrido? Cabe decir que otros juegos que conecte a Steam Link, como de Epic Games funcionan normal. Solo me pasa con Ubisoft.

not sure what's up with it. i have steam link set to my ipad so i can draw on various drawing games. i have it set to the mouse click and whatnot but it's not letting me click anything on the screen at all no matter how many times i reset. am i doing something wrong?

TL;DR: I managed to turn on my Windows PC from my phone using mobile data, even after a complete shutdown in order to run steam games.

Give this guide to any AI and use this as a prompt to go step by step, at least it's what I always do.

Requirements:

No VPN, Raspberry Pi, TeamViewer subscription, smart plug, or additional things required.

The solution was to configure a static local IP, enable UDP port forwarding on my router, and use a free Wake-on-LAN app.

This worked for me from both Sleep and a complete shutdown. Whether it works for you depends on your router, ISP, and PC's Wake-on-LAN support.

Okay so, let's start. Wake on lan works sending a "power on" signal through your router, and that turns on your computer.
The issue? it only works on LAN. but I figured a way to make it work using mobile data to run steamlink. Magic.

1. Make Sure Wake-on-LAN Works Locally

Before trying to turn on your PC over the Internet, make sure Wake-on-LAN works while your phone is connected to your home Wi-Fi.

Your PC should be connected to your router using an Ethernet cable.

You may need to enable Wake-on-LAN in your BIOS/UEFI and network adapter settings.

In Windows:

1. Open Device Manager.
2. Expand Network adapters.
3. Right-click your Ethernet adapter and open Properties.
4. Under Advanced, look for settings such as Wake on Magic Packet and Shutdown Wake-on-LAN.
5. Under Power Management, enable the option allowing the device to wake the computer, if available.

The exact options depend on your motherboard and adapter.

Once configured, put your PC to Sleep and try waking it with a Wake-on-LAN app while connected to your home Wi-Fi.

If it works, continue.

2. Find Your MAC Address and Local Network Details

Open Command Prompt and run:

ipconfig /all

Find your active Ethernet adapter.

Write down:

• Physical Address (MAC)
• IPv4 Address
• Subnet Mask
• Default Gateway
• DNS Servers

Don't confuse your Ethernet MAC address with your Wi-Fi MAC address.

Your IPv4 address is your computer's address within your home network. Your default gateway is normally your router's local IP address.

3. Configure a Static Local IP Address

Your PC should keep the same local IPv4 address so your router can consistently forward packets to it.

If your router supports DHCP reservations, use that.

Otherwise, you can manually configure a static IPv4 address in Windows.

First, make sure the address you choose is not being used by another device and will not be assigned by your router's DHCP server.

Depending on your router, this may require adjusting its DHCP allocation range.

In Windows, press:

Win + R

Enter:

ncpa.cpl

Then:

1. Right-click your Ethernet adapter.
2. Select Properties.
3. Open Internet Protocol Version 4 (TCP/IPv4).
4. Select Use the following IP address.
5. Enter your chosen local IP address, subnet mask, and default gateway.
6. Configure your DNS servers using your existing network settings.
7. Save the changes.

Check your configuration:

ipconfig /all

You should now see your selected IPv4 address and DHCP Enabled: No for that Ethernet adapter.

Verify that your Internet connection still works.

4. Create a UDP Port-Forwarding Rule ON YOUR ROUTER/MODEM SETTINGS

Open your router's administration page using its local gateway address.

Look for a section called:

• Port Forwarding
• NAT
• Virtual Server
• Ports

Create a new forwarding rule:

Save and enable the rule.

Important: A rule like this does not work on every router.

When your PC shuts down, some routers lose the IP-to-MAC association required to deliver the packet.

Certain routers require static ARP entries, broadcast forwarding, or another Wake-on-LAN mechanism.

In my case, ordinary UDP forwarding worked without additional configuration.

Security warning: Exposing a forwarded UDP port to the Internet creates an unauthenticated network entry point. It is not as secure as a VPN or authenticated wake-up mechanism. Only use it if you understand the implications, and disable the rule when it isn't needed.

Do not enable DMZ or expose your router's administration interface.

5. Find Your Public IPv4 Address

While connected to your home Internet, visit:

https://whatismyipaddress.com/

Find your public IPv4 address.

This is the address your phone will use to contact your home router over the Internet.

It is different from your PC's local IPv4 address.

Important: Some Internet providers use CGNAT, which may prevent ordinary inbound port forwarding.

If possible, compare the public IPv4 shown on the website with the WAN IPv4 displayed by your router.

If your router's WAN address is private or shared, ordinary forwarding may not work.

Also, your public IP address may change over time. Dynamic DNS can help avoid having to update it manually.

6. Configure Your Wake-on-LAN App

I used Wolow, but other Wake-on-LAN apps may offer similar functionality.

Create a new device entry.

Save the device.

The IP Address field is especially important.

For remote Wake-on-LAN, it must point to your home network's public address, not the local address of your computer.

The Ping Address may not work when you're outside your home network. A PC can still wake successfully even if the app reports it as offline.

7. Test Using Mobile Data

Time for the first test.

1. Put your PC into Sleep mode.
2. Disable Wi-Fi on your phone.
3. Make sure you're connected through 4G/5G.
4. Open your Wake-on-LAN app.
5. Select your remote device.
6. Send the magic packet.

Wait a few seconds.

If your PC wakes, congratulations! Your remote Wake-on-LAN setup is working.

If nothing happens, check your forwarding rule, public IPv4, and router compatibility before changing random network settings.

8. Test From a Complete Shutdown

This is where things get interesting.

Wake-on-LAN from Sleep is relatively common, but waking from a complete shutdown depends on your motherboard, BIOS, and network adapter.

To test a full Windows shutdown, save your work and open Command Prompt:

shutdown /s /t 0

Wait until the computer is completely off.

Leave its power supply connected to electricity.

Then:

1. Turn off Wi-Fi on your phone.
2. Connect through mobile data.
3. Open your Wake-on-LAN app.
4. Send the magic packet.
5. Wait for your PC to power on.

In my case, it worked!

I was able to turn on my PC remotely even after a full shutdown.

No VPN, second computer, subscription, or additional hardware was required.

9. Troubleshooting

Works on Wi-Fi but not mobile data

Check whether your app is using your public IPv4 address, your router's forwarding rule is correct, and your Internet connection allows inbound traffic.

Works from Sleep but not Shutdown

Check BIOS/UEFI settings, Ethernet adapter power management, Wake-on-LAN from S5 support, and standby power availability.

Stops working after a few hours

Your router may be forgetting the powered-off PC's IP-to-MAC association. Static ARP or another compatible wake-up method may be required.

Stops working after several days

Your public IPv4 address may have changed. Update your app or configure Dynamic DNS.

App shows PC as offline

If the app is pinging a private local address from mobile data, its status indicator may not work even if waking the computer does.

--------------------------------------------------------------------------------------------------------------

Final Thoughts

I originally thought Wake-on-LAN only worked while connected to the same Wi-Fi network.

I discovered that my router could forward Wake-on-LAN magic packets directly from the Internet to my desktop.

By combining a static local IP, UDP port forwarding, and a Wake-on-LAN app, I managed to wake my PC from anywhere using mobile data.

The biggest surprise was that it also worked from a complete shutdown.

This isn't guaranteed on every router or Internet connection, but it is absolutely possible without buying additional hardware.

Hopefully this helps someone who has been trying to figure out how to make Wake-on-LAN work outside their home network.

complete noob at this - just trying to use this to draw on animal jam with an overlay program. is the app supposed to look like this?

Hello, I was hoping someone could help me out. My girlfriend really wants to play Silent Hill F so I downloaded the steam link app on our bedroom google tv/chromecast. I thought I had all my stettings right for the remote play but the stream starts strong but just degrades over time to where it just starts sounding and playing poorly. My Pc is connected via Ethernet but the tv is not if that matters at all

Thanks :)