🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.ibm.pc.games.action
Article #694615

Re: Lets talk about gamestreaming

#694615
From: Werner Punz
Date: Thu, 29 Oct 2015 18:37
48 lines
4345 bytes
Am 29.10.15 um 16:02 schrieb Rin Stowleigh:
> On Thu, 29 Oct 2015 08:51:33 +0100, Werner Punz <we...@gmx.at> wrote:

> Here's a question, what if your PC is pushing 144fps in most games
> only because it's the upper limit of a Gsync monitor (in other words
> unless the game is locked at 60hz its always going to be more)?  But,
> the refresh rate of the TV is 60hz (actually both my large TVs are
> plasma, so technically spec'd at 600hz for purposes of this question
> let's just say its could be higher or lower than the frame rate the PC
> is capable of).
>

The 600MHz is pure marketing, they count the internal double or triple 
buffering and motion compensation and inflate hz numbers. If you have a 
good panel then you most likely will end up with 120Hz max most tvs only 
have 60Hz max. But even then you cannot really pump 120Hz over HDMI at 
the moment.

> This was always my problem with LCD monitors prior to GSync/Freesync.
> Unless the game is always running at a fps that matches the refresh
> rate of the monitor, there was always going to be some tearing or
> stuttering, and because 60hz felt too slow for fast FPS games (I know
> these are not what most game streaming enthusiasts play), the only
> time this worked out well was when the game was playable at 60hz (for
> example Rainbow Six series which is usually slower-moving and doesn't
> require lots of fluid motion), and simultaneously lockable at that
> rate (sometimes via config files, sometimes via the UI).
>
No tearing, it behaves like if you turn on vsync in a game. The 
rendering is done basically on the host side and a pure h264 video is 
pumped to the client. As for stuttering YMMV I dont have any problems 
with this for the slower paced games I play. Stuttering definitely can 
be encountered if you are lower than 60Hz if you have vsync on in a game 
it probably will lock the game to 60Hz max but only if it can render the 
game that fast. I definitely cannot see stuttering unless the game 
cannot pump out at least 60Hz, but I dont get more than 60Hz.

Thats the beauty of GSYNC/Freesync btw. you get a dynamic vsync hence no 
tearing like with static vsync but no stuttering either due to lost frames.

> I'm just wondering how all this works with streaming, since it seems
> the GPU on the host PC would have no clue about the hardware
> capability of the TV, so no matter what some games are going to end up
> a tearing/stuttering nightmare.
>
The GPU does not have to have a clue regarding the client, it just has 
to render a 1080p/UHD (depending on your streaming config) H264 video 
and pump it over via RTSP (real time streaming protocol) to the client.
Technical Details
Message-ID: <n0tosb$9a7$1@dont-email.me>
Path: mbox-mo1.pugleaf.net!z4ni40070ign.0!nntp.google.com!news.glorb.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
References: <n0am5c$kd6$1@dont-email.me> <slrnn2ouvl.726.google@asktoby.eternal-september.org> <n0or3c$crg$1@dont-email.me> <slrnn316el.726.google@asktoby.eternal-september.org> <n0sj21$jqq$1@dont-email.me> <d5c43bdjmvn5qhjoe5aqgeelg5t8lam4nf@4ax.com>

Show Full Headers
Complete Article Headers
X-Received: by 10.182.251.230 with SMTP id zn6mr2526393obc.8.1446143824549;        Thu, 29 Oct 2015 11:37:04 -0700 (PDT)
X-BeenThere: comp.sys.ibm.pc.games.action@googlegroups.com
Received: by 10.50.50.179 with SMTP id d19ls333158igo.2.gmail; Thu, 29 Oct 2015 11:37:02 -0700 (PDT)
X-Received: by 10.66.255.70 with SMTP id ao6mr2724737pad.3.1446143822859;        Thu, 29 Oct 2015 11:37:02 -0700 (PDT)
Path: mbox-mo1.pugleaf.net!z4ni40070ign.0!nntp.google.com!news.glorb.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Werner Punz <we...@gmx.at>
Newsgroups: comp.sys.ibm.pc.games.action
Subject: Re: Lets talk about gamestreaming
Date: Thu, 29 Oct 2015 19:37:01 +0100
Organization: A noiseless patient Spider
Lines: 50
Message-ID: <n0tosb$9a7$1@dont-email.me>
References: <n0am5c$kd6$1@dont-email.me> <slrnn2ouvl.726.google@asktoby.eternal-september.org> <n0or3c$crg$1@dont-email.me> <slrnn316el.726.google@asktoby.eternal-september.org> <n0sj21$jqq$1@dont-email.me> <d5c43bdjmvn5qhjoe5aqgeelg5t8lam4nf@4ax.com>
Mime-Version: 1.0
Injection-Date: Thu, 29 Oct 2015 18:34:51 +0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="b450c8f0ace1cd360df2922d3898cbd5"; logging-data="9543"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX1+4tu+NVn3f43tnYh1oeAXe"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
In-Reply-To: <d5c43bdjmvn5qhjoe5aqgeelg5t8lam4nf@4ax.com>
Cancel-Lock: sha1:gaZWwnxRkiW2bR002+R8cxtY9X0=
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit