Sunshine – an open-source gamestream server for Windows and Linux
github.com
github.com
Some of that is configuration, some of that is equipment, often you could instantly solve the problem with fiber.
Low latency DOCSIS is starting to be deployed, though-- which over the next 2-3 years will really chip away at the problem (in addition to fiber rollouts, etc, helping).
Although the original Nvidia implementations are proprietary, Moonlight + Sunshine work on non-Nvidia and non-Windows machines.
I had to look up Moonlight because I also had no clue: https://moonlight-stream.org/
https://github.com/moonlight-stream/moonlight-docs/wiki/Setu...
so.... i can set this up on a vm and get cloud gaming with all the inefficiencies ? nice
Could this be it?
My suggestion is GeForce Now because it has the best GPUs and supports both Steam and Epic and doesn't lock you in to a third party lib the way Stadia does. And Google seems to be giving up on consumer Stadia anyhow.
Shadow.tech is an actual Windows/Steam VM (but much cheaper than AWS) if you want full control (along with the PITA of having to update Windows, Steam, and your games all the time... something the other services take care of transparently).
Renting GPU hours and running it yourself actually ends up costing a LOT more, last time I checked. Nvidia subsidizes their own service while Amazon has to upcharge you.
No offense but either you're at a really low level or else you're playing games that aren't actually very dependent on reaction time.
On the flip side - if you live in the same city as a stadia server and you have real fibre to your house, you could realistically expect single digit ms latency to the stadia (edit: or knock-off stadia, using a cloud server or similar) box - it would still be noticeable, but 5ms is the same difference in input lag as dropping from 90fps -> 60fps - obviously it's not nothing at all, but if you aren't investing in a dedicated gaming computer it's unlikely it'd annoy you that much
Anecdote: I've used a lot of cloud gaming providers with fiber to the home, and while the experience is great, it's very noticeably laggier in first person shooters compared to going from 90fps to 60fps. It's a different kind of latency... beyond 60+ FPS, there are more frames in between, and so motion is smoother. But even at 60fps, your "time to first frame (update)" is still very low, compared to over the internet (or even to a local Steam remote desktop). Cloud gaming at 100Hz/FPS still feels laggier than 60fps local because of that mouse lag.
Modern graphics cards are very good at rapidly encoding frames using hardware accelerators, but it's still nowhere near as good as drawing directly to the screen. Even the fastest multi-gig networks are orders of magnitude slower than your internal buses and ports, especially in latency.
I don't hate money but I love the space and freedom from not having a physical rig at my desk slightly more than money. (Also worth mentioning that I have like an hour a week for video gaming at most.)
Though technically I should be able to start them through steam, I would like to keep the setup simpler: copy over binary and resources, ./game.
That way I can set it up with a small shell script or Ansible playbook from scratch, and I don't have to rely on Amazon-specific file system images and such. (So I can quickly switch to a different provider if I find a cheaper/easier option.)
Microsoft's native RDP, for example, knows to send a window's start location and end location when you move it, and the client just recalculates how it should appear in the new place, with only the x-y coordinate changes needing to be sent over the wire. A naive protocol would instead send every frame in between as though it were a video. On Linux, I think remote X11 operates on similar principles... it might've been designed that way from the start, but that use case never really seemed to gain widespread popularity for some reason. On the enterprise front, I think Citrix has their own protocol (ICA) with heavy optimizations, but I'm not sure how it works.
These days, I think a lot of apps (IDEs, etc.) have real-time collaboration and streaming built-in at the data layer, without needing an actual remote desktop (i.e. they sync state changes, not pixels). VSCode and IntelliJ, for example, can both stream their actual app into a web browser and/or also host your development environment remotely through a transparent tunnel. You don't even have to use VPN or SSH.
We've come to a pretty interest hybrid of thick/thin clients, where apps and UIs can be compactly sent as a javascript package and trivially rendered by any laptop made in the last decade or so, but all the heavy lifting can still be done remotely -- just in the cloud now instead of internal mainframes. (Although I suppose you could run those containers in a LAN too.) I guess there's not much need to stream the desktop anymore when hardly anyone uses the desktop anyway, just specific apps and a ton of websites.