WEBVTT

00:00:12.200 --> 00:00:17.800
I am recording now please go all right so the core thing about gsync uh that

00:00:16.119 --> 00:00:21.560
they're touting here is the ability that lets you get away from completely

00:00:19.279 --> 00:00:25.359
isochronous or fixed time slices for your games now time slices have been

00:00:23.760 --> 00:00:28.840
with us for the 50 years since television when you've got you had to

00:00:27.199 --> 00:00:33.360
refresh the screen in these continuous patterns because the from the phosphor

00:00:30.880 --> 00:00:38.200
just decayed it went away with back lit LCD displays the light's continuous

00:00:35.840 --> 00:00:41.760
there so there is no sensible reason why we have to be doing that and because we

00:00:39.760 --> 00:00:46.320
are we get these artifacts of either tear or jutter so it's really good to

00:00:43.879 --> 00:00:49.680
get away from that now if you try for a high frame rate like 60 frames per

00:00:47.960 --> 00:00:54.480
second which I've been a big proponent of if you miss it hurts really bad you

00:00:53.000 --> 00:00:58.960
you know you drop all the way down to 30 frames per second while with something

00:00:56.480 --> 00:01:03.920
like g-sync if you if you take 17 milliseconds instead of 16 milliseconds

00:01:01.359 --> 00:01:07.880
nobody can even tell it just comes out as a tiny delay on the frame and that's

00:01:06.119 --> 00:01:12.280
a wonderful thing so that's one real Advantage if you're trying hard for a

00:01:09.600 --> 00:01:15.680
frame rate it makes your inevitable Miss imperceptible if you're not even trying

00:01:14.520 --> 00:01:20.680
if you're just making a game that's randomly running at whatever the hell frame rate it turns out it magically

00:01:19.080 --> 00:01:25.040
works out on this if you're going between 20 and 80 frames per second like

00:01:23.479 --> 00:01:29.040
you know a lot of games will if they're unconstrained there this makes that

00:01:26.920 --> 00:01:35.000
beneficial it means that it's smooth at 20 but then at 80 it's silky and this is

00:01:31.799 --> 00:01:37.320
a really great thing now the interesting

00:01:35.000 --> 00:01:42.040
tension that we've got here is that I didn't really appreciate this a year ago

00:01:39.640 --> 00:01:46.640
but the persistence on a display the fact that it is continuously illuminated

00:01:44.439 --> 00:01:50.479
contributes to a lot of subtle blurring effects on the screen when you look at

00:01:48.399 --> 00:01:54.159
like a text uh you know like a web page if you pan it across the screen smoothly

00:01:52.600 --> 00:01:57.880
or if you scroll like an iPad or something even if it's scrolling at a

00:01:55.880 --> 00:02:00.799
perfect 60 frames per second smoothness it's hard to read because it feels

00:01:59.439 --> 00:02:04.399
blurred in the direction that it's moving and that is a consequence of the

00:02:03.039 --> 00:02:09.640
persistence the fact that it's continuously illuminated the solution to

00:02:07.079 --> 00:02:13.840
that is to only illuminate it very briefly now this happened automatically

00:02:11.560 --> 00:02:18.480
for CRT displays as the Electron Beam scanned over you only had you know

00:02:16.160 --> 00:02:21.360
micros seconds of Illumination from that before it went away and there's a

00:02:19.959 --> 00:02:26.000
category of people that would talk about like sports broadcasting where they'd complain it's never been the same since

00:02:24.440 --> 00:02:30.360
you got flat panels because everything is a little bit more smeared on the pans

00:02:28.120 --> 00:02:33.920
I never really noticed that so much but in a head mounted display it is night

00:02:32.319 --> 00:02:37.599
and day it is one of the more dramatic technology demos that you can do to have

00:02:36.080 --> 00:02:42.319
a display that you can switch between low persistence and full persistence

00:02:39.800 --> 00:02:46.080
it's a big deal now the interesting thing is in the last couple years

00:02:44.560 --> 00:02:50.920
NVIDIA's had their light boost technology for the 3D uh Vision stuff

00:02:48.879 --> 00:02:54.560
and you could put that in you could use that as a low persistence monitor people

00:02:52.760 --> 00:02:59.400
wrote firmware hacks to be able to do this so if you made 120 HZ game and Doom

00:02:57.599 --> 00:03:02.200
3 BFG was one of the few things that because it's old game and we paid a

00:03:00.959 --> 00:03:06.280
little bit of attention you could run it at 120 frames per second locked and you

00:03:04.599 --> 00:03:11.200
could put it into a mode like this and it was pretty awesome but no modern game

00:03:09.159 --> 00:03:14.879
runs at 120 frames per second you know let alone stereo for a head mounted

00:03:12.799 --> 00:03:19.760
display because right now people will just say uh I'm a 30 HZ game and why

00:03:17.400 --> 00:03:23.680
bother and even if you try for 60 you know that's enough Blood Sweat and Tears

00:03:21.840 --> 00:03:28.120
to get there pushing further Beyond his hard but g-sync makes it a smooth

00:03:26.120 --> 00:03:32.280
Continuum so every bit that you do to help helps you know it is better to be

00:03:30.120 --> 00:03:36.599
at 70 than to 6 then 60 it's better to be at 40 than 30 this is a good thing

00:03:35.000 --> 00:03:39.560
and I think that this will be a path that can start bringing some games up

00:03:38.319 --> 00:03:43.360
now we've got the other tension of like 4K displays it's like okay let's go back

00:03:41.400 --> 00:03:48.439
down to 30 frames per second to do a 4K display but at least there's the option

00:03:45.519 --> 00:03:54.599
of possibly pushing up because once you get over 90 95 Hertz ideally up to 120

00:03:52.319 --> 00:03:58.200
or 144 some of these monitors will run at you can start doing this low

00:03:56.239 --> 00:04:03.120
persistence stuff but the problem with this and this is an interesting tension

00:04:00.599 --> 00:04:07.120
I if you do the low persistence and you vary your frame rate then it changes the

00:04:05.120 --> 00:04:11.959
intensity of what you're looking at so what needs to happen is you need to vary

00:04:09.680 --> 00:04:16.720
the length of the illumination based on how long the frame rate was Now g-sync

00:04:14.360 --> 00:04:19.880
can do all of these things they actually they they didn't want us to really talk

00:04:18.280 --> 00:04:24.080
about this aspect of g-sync because they thought it would confuse the you know uh

00:04:21.919 --> 00:04:28.120
the people listening but I I actually think that's pretty important where it's

00:04:25.600 --> 00:04:32.280
got the low persistence option right now it's binary you can go to 120 Hertz and

00:04:30.120 --> 00:04:36.240
be low persistence or you can be at variable frame rate but there's no

00:04:34.120 --> 00:04:40.160
reason why this can't be combined where you start adapting one towards the other

00:04:38.320 --> 00:04:44.360
then you get this option where the best world the best case of this would be the

00:04:42.320 --> 00:04:47.919
game is running if it's running at 20 30 frames per second it's full persistence

00:04:46.160 --> 00:04:52.120
it's just variable but as the game creeps up and it gets over 90 frames per

00:04:50.280 --> 00:04:55.680
second then it can start adapting the backl to it and that'd be great so you

00:04:54.240 --> 00:05:00.240
might have a game where only in some simple scenes are you at low persistence

00:04:57.720 --> 00:05:03.120
wonderfulness while in your mass outdoor exploding everything then it's falling

00:05:01.800 --> 00:05:07.360
down it's full persistence but that would be great it's making things better

00:05:04.800 --> 00:05:10.880
where they can be better and there's a lot of other uses for this type of thing

00:05:09.600 --> 00:05:15.280
like I had mentioned Android specifically because I did complain that

00:05:13.199 --> 00:05:19.800
you take the like the NVIDIA Shield where it's got should have plenty of

00:05:17.320 --> 00:05:23.520
horsepower but if you play Sonic on it it drops frames every now and then and

00:05:21.880 --> 00:05:27.759
that's not the fault of the GPU or the CPU it's the fault largely of the power

00:05:25.720 --> 00:05:31.960
management and what happens on Android where they're they're constantly trying

00:05:29.440 --> 00:05:35.800
to save power by adapting the core count and the frequencies on these things and

00:05:34.039 --> 00:05:39.400
unfortunately what happens is they often pull the power down until you start

00:05:37.680 --> 00:05:43.520
dropping frames which is exactly the wrong thing to do so we could fight that

00:05:41.800 --> 00:05:47.360
by saying well we want a dedicated amount of core cores and frequency but

00:05:45.680 --> 00:05:51.039
then you waste power where really the optimal thing would be let them manage

00:05:49.120 --> 00:05:55.440
the power as they do now and use variable refresh technology to just mean

00:05:53.080 --> 00:05:59.800
when you slightly Miss it's it's it will be imperceptible if you go to 17

00:05:57.960 --> 00:06:03.919
milliseconds for your frame in instead of 15 there and that will be a great

00:06:01.600 --> 00:06:07.120
thing but even NVIDIA's knows that even though they own that platform it's going

00:06:05.319 --> 00:06:10.199
to be integrating with another display vendor pushing things through

00:06:08.400 --> 00:06:14.759
integrating with more Android stack these are hard cross compan issues and

00:06:12.919 --> 00:06:18.800
NVIDIA it's great that NVIDIA did this I've been harping on this for a number

00:06:16.319 --> 00:06:22.800
of years but it took something a company like NVIDIA that can change gpus and

00:06:21.520 --> 00:06:27.319
that can change the hardware that can write the driers for that can you know

00:06:25.199 --> 00:06:30.479
leverage the display vendors to actually put something like this in it could have

00:06:29.000 --> 00:06:34.520
happened five years ago it would have been good to happen 5 years ago but you

00:06:32.720 --> 00:06:39.160
know it's finally happening now well that's fantastic thank you very

00:06:37.440 --> 00:06:43.639
much I'm sure everyone appreciated you taking the time I would offer to shake

00:06:41.680 --> 00:06:47.720
your hand and thank you but I'm pretty burdened here right now okay all right

00:06:46.319 --> 00:06:50.720
we're going to go try to intercept Tim Sweeney

00:07:01.240 --> 00:07:05.840
hey Tim can I borrow you for just a

00:07:04.280 --> 00:07:11.720
couple minutes just to basically say hi to the viewers sure okay I am going to

00:07:09.080 --> 00:07:15.800
have to okay this is very challenging okay but you can you kind of reach past

00:07:13.360 --> 00:07:20.039
me here and do you see channel one where it's there's an A and an M yeah can you

00:07:18.280 --> 00:07:24.560
switch that to a and then same with Channel

00:07:21.840 --> 00:07:29.240
2 so there you guys have it Tim Sweeney touched my

00:07:27.000 --> 00:07:33.080
camera um so we've got about 3,000 viewers on here right now that are that

00:07:30.960 --> 00:07:36.319
are watching live so if uh you know what I guess probably the most appropriate

00:07:34.599 --> 00:07:41.720
thing given that we're at NVIDIA's event is can you talk a little bit about g-sync and how important you think it is

00:07:39.720 --> 00:07:45.960
oh sure um it is a really important piece of technology it enables a games

00:07:44.120 --> 00:07:50.440
Runing at any frame rate to have the smoothness uh that you get from running

00:07:48.440 --> 00:07:55.199
at a constant frame rate you know right now to achieve 60 frames a second

00:07:52.840 --> 00:08:00.919
perfect smoothest um you have to make great sacrifices in the game um and if

00:07:57.960 --> 00:08:04.720
you just go one frame below it to 59 and suddenly your gain's interrupted by

00:08:02.360 --> 00:08:10.879
these massive stutters and the gsync tech uh really creates a Continuum um so

00:08:08.840 --> 00:08:14.319
that whatever level of uh frames the game is outputting can be displayed

00:08:12.360 --> 00:08:19.639
smoothly and without these crazy artifacts that you have in games

00:08:16.599 --> 00:08:21.599
nowadays it means uh Gamers game

00:08:19.639 --> 00:08:25.800
developers will be able to create really awesome levels of content and still

00:08:23.400 --> 00:08:30.319
achieve the sort of smoothness uh that you get in games like Call of Duty for

00:08:27.560 --> 00:08:33.360
example I mean one of the things that the average person I think really

00:08:31.879 --> 00:08:37.560
doesn't understand is they'll they're quick to blame any kind of a frame rate

00:08:35.279 --> 00:08:41.800
issue on well the game optimization isn't very good can you talk a little

00:08:39.360 --> 00:08:45.760
bit about the Bal the delicate balancing act that you guys go through to deliver

00:08:43.599 --> 00:08:49.000
both great level of detail and a smooth gaming

00:08:46.760 --> 00:08:53.640
experience sure it's a constant trade-off for a game developer um you

00:08:51.480 --> 00:08:57.000
know with Gears of War for example we aimed at uh creating the most impressive

00:08:55.519 --> 00:09:00.120
visual experience we could while trying to hit 30 frames a second pretty

00:08:58.800 --> 00:09:03.959
consistently um but uh you know once in a while

00:09:02.440 --> 00:09:07.760
there's a moment when the game drops below that and it really impacts the

00:09:05.440 --> 00:09:11.640
quality because you're not dropping to 29 or 28 frames a second you're

00:09:09.959 --> 00:09:15.760
jittering back and forth between 20 and 30 and it's just a it's just really bad

00:09:14.360 --> 00:09:20.519
this Tech makes it much easier to develop games that have a high level of smoothness and that's going to mean a

00:09:18.959 --> 00:09:25.079
lot more games will be smooth in the future it's it's one of those kind of

00:09:22.440 --> 00:09:28.200
magical technologies that you don't necessarily look at the screen and

00:09:26.440 --> 00:09:35.040
recognize exactly what's going wrong it just looks wrong and it looks uh jittery

00:09:32.279 --> 00:09:37.800
and unrealistic for uh reasons that are hard to identify but when you see it

00:09:36.279 --> 00:09:47.000
working perfectly it's an entirely different experience so in your mind would we see

00:09:42.360 --> 00:09:49.560
something akin to gsync on handhelds

00:09:47.000 --> 00:09:53.000
televisions along with PC monitors and how far out do you see that in the

00:09:50.800 --> 00:09:57.160
future I mean how much would you love to have this on the console we'd love to

00:09:54.920 --> 00:10:01.320
have this everywhere um televisions projectors uh mobile LCD display plays

00:09:59.920 --> 00:10:04.880
um it's going to be especially important for you know products like Oculus uh

00:10:03.560 --> 00:10:08.839
where you want to have a very high and consistent frame rate uh for past

00:10:07.040 --> 00:10:13.000
response time this technology it's starting like almost everything um it's

00:10:11.640 --> 00:10:16.920
an innovation in the industry it's starting on high-end PC and it will work

00:10:15.519 --> 00:10:20.320
its way throughout the rest of the industry over the coming

00:10:18.519 --> 00:10:23.079
years all right well I don't want to take up too much of your time I know

00:10:21.760 --> 00:10:27.920
that you're supposed to be up here for the panel but I appreciate you uh just

00:10:25.440 --> 00:10:33.480
taking the time to say hi to the viewers and uh I I would Shake sh your hand but

00:10:30.760 --> 00:10:38.560
um if nothing else I'm going to try we'll have like a photo op sort of there

00:10:37.040 --> 00:10:41.839
like gster that's the best we were able to do thank you so much for taking the

00:10:40.279 --> 00:10:46.000
time yeah so there you guys go have you

00:10:44.000 --> 00:10:51.440
forgiven the enforcer now forcer is not a bad guy because he he he helped us

00:10:48.639 --> 00:10:55.320
sync up with Tim Sweeney so there you go yeah that's what they call me now

00:10:53.560 --> 00:10:59.920
there there's Tim over there actually he wandered away from us over

00:10:57.760 --> 00:11:04.440
to the g-sync demo you can see he's got his face about 4 in

00:11:02.760 --> 00:11:07.560
from the screen okay maybe we're not going to leave him alone just

00:11:08.000 --> 00:11:12.839
yet oh okay just for fun we're going to

00:11:11.040 --> 00:11:16.839
bother you again here you're you're playing around with the demo right now

00:11:14.240 --> 00:11:22.079
correct yes yes this has three modes vsync no vsync and gsync um of course in

00:11:19.920 --> 00:11:26.079
a video of this you are not going to see any of what I'm talking about um but the

00:11:24.760 --> 00:11:32.800
difference in smoothness is really impressive with vsync you see uh

00:11:30.040 --> 00:11:35.480
uh you don't see tearing artifacts but you do see an inconsistency with the

00:11:34.360 --> 00:11:40.560
frame rate consistently you know jittering back and forth between one frame rate and another because of the

00:11:38.519 --> 00:11:46.959
way that the frame rates are discretized well I never knew what was wrong vsync

00:11:43.079 --> 00:11:49.040
always felt off to me I never liked it

00:11:46.959 --> 00:11:53.320
well it's subtle so you turn off vsync and you have a different set of areas

00:11:50.399 --> 00:11:58.079
which is that each scan line is independently experiencing its own um

00:11:56.399 --> 00:12:01.320
discretization but now you're getting this tearing where uh half of the screen

00:11:59.880 --> 00:12:06.399
is the previous frame and half of the screen is the next frame wherever

00:12:03.519 --> 00:12:10.200
arbitrarily in time the they change head and then what you think it's always

00:12:08.360 --> 00:12:13.639
flipping at the right time it's displaying frames at a consistent rate

00:12:12.200 --> 00:12:18.000
and so you get a lack of jittering artifacts and look here the frame rate

00:12:15.600 --> 00:12:24.320
is varying here in places it's dropping probably even below oh definitely around

00:12:20.800 --> 00:12:27.160
30 frames a second uh but this smooth

00:12:24.320 --> 00:12:32.600
dropping from 60 down to 30 is much much less disturbing than dropping frames one

00:12:30.720 --> 00:12:36.120
at a time and what you're looking at right now looks like a very extreme

00:12:34.279 --> 00:12:40.760
example it looks like the first looks like the first thing Tim did when he got

00:12:37.839 --> 00:12:44.160
here was cranked the frame time minimums all the way down and the maximums all

00:12:42.839 --> 00:12:47.760
the way up or was it already like that when you got here uh no I did this this

00:12:46.000 --> 00:12:51.079
is really the worst case so when the de so the way the Demo's running here let

00:12:49.000 --> 00:12:54.360
me show you this guys this is like a Mayhem and a multiplayer game where

00:12:52.600 --> 00:12:59.519
they're enormous numbers of players just causing crazy spikes in frame time all

00:12:56.760 --> 00:13:03.800
the time but here what you think you won't appreciate it in this video uh

00:13:01.760 --> 00:13:08.680
because it's a video of a screen with a different display resolution and uh

00:13:06.240 --> 00:13:12.519
sampling rate but it's just uh it is Flawless to the point where there's this

00:13:10.079 --> 00:13:16.440
Sol text on the spinning pendulum and you can actually read it um which is

00:13:14.800 --> 00:13:20.399
astonishing because if you go turn off bsync then it's tearing it makes it hard

00:13:18.480 --> 00:13:25.120
it's distracting your eye away from it um it's a it's making a really big

00:13:23.360 --> 00:13:28.680
quantitative difference very cool okay thank you we

00:13:27.360 --> 00:13:32.399
really will we really will stop bothering you you know thank

00:13:33.720 --> 00:13:41.720
you so guys I mean you would never really see okay so the way the demo set

00:13:38.360 --> 00:13:44.720
up for minimum and maximum frame times

00:13:41.720 --> 00:13:47.760
uh so it's it's kind of swinging between

00:13:44.720 --> 00:13:49.279
60 and 30 and that really does present a

00:13:47.760 --> 00:13:54.279
very worst case scenario I mean that's kind of like an artificial situation

00:13:51.680 --> 00:13:58.839
where you're looking down at something intensive like a scene with a bunch of

00:13:56.120 --> 00:14:03.360
stuff exploding and then swinging your your camera up to the ceiling and then

00:14:01.720 --> 00:14:06.639
back down and then back up and then back down and back up and you're trying to

00:14:05.399 --> 00:14:10.880
make the experience disconcerting and that's the

00:14:09.480 --> 00:14:17.279
worst case scenario that we're kind of looking at over there and even

00:14:13.240 --> 00:14:17.279
then it's pretty darn

00:14:18.480 --> 00:14:25.759
smooth someone says g-sync

00:14:22.920 --> 00:14:31.839
will somehow adoption will affect it it doesn't g-sync will affect the people

00:14:28.600 --> 00:14:33.800
who by the gear that runs it there

00:14:31.839 --> 00:14:38.680
there's no we don't have to wait for any industry adoption other than making sure

00:14:36.120 --> 00:14:42.120
that there are monitors that have the technology built into them which NVIDIA

00:14:40.320 --> 00:14:48.680
is saying will be available as as early as q1 next year so it'll be up to the

00:14:44.759 --> 00:14:51.240
individual to adopt it and enjoy it and

00:14:48.680 --> 00:14:56.040
that's that it'll work on any game uh it'll work on any Kepler based GPU and

00:14:53.880 --> 00:14:59.160
it'll work on any g-sync enabled Monitor and you don't have to wait for game

00:14:57.360 --> 00:15:02.399
developers to enable anything you don't have to wait for any else anything else

00:15:01.720 --> 00:15:07.399
to happen Okay my uh my last question is

00:15:05.399 --> 00:15:10.680
you guys talk about how you'll be able to develop games differently if you

00:15:08.880 --> 00:15:14.800
don't have to Target a particular frame rate using a technology like g-sync but

00:15:13.320 --> 00:15:20.279
with g-sync we're going to be looking at a very small initial user base because

00:15:17.360 --> 00:15:24.240
it's based on a Kepler GPU and a particular monitor that has a particular

00:15:22.079 --> 00:15:28.720
Hardware chip in it um pull up the crystal all again so is this within the

00:15:26.680 --> 00:15:33.720
next 5 years that you'll be able to actually forget about a Target frame

00:15:30.880 --> 00:15:38.399
rate with the game and assume that the end user can experience it the way that

00:15:35.839 --> 00:15:42.279
JN can deliver I think this is going to be pretty broadly picked up because this

00:15:40.240 --> 00:15:46.720
is not like it doubles the size of the die of something to do this it's not

00:15:44.319 --> 00:15:51.800
that expensive of the technology I have no idea what nidia's licensing costs and

00:15:48.720 --> 00:15:53.839
what are going to be on here but uh I

00:15:51.800 --> 00:15:58.639
this is something that should be broadly adopted from a pure technology

00:15:56.079 --> 00:16:02.360
standpoint this is just the right thing and I obviously in early years this is

00:16:00.839 --> 00:16:06.079
just going to be a smoothness benefit for for people but in the space of five

00:16:04.959 --> 00:16:10.920
years or something I would hope something like this is pretty much this

00:16:08.600 --> 00:16:14.319
absolutely you also there's a limited amount of of things a monitor

00:16:12.680 --> 00:16:18.440
manufacturer or TV manufacturer can actually compete on once you have 4 put

00:16:16.360 --> 00:16:22.360
stupid things in a lot of cases this is actually a good thing please remove the

00:16:20.079 --> 00:16:27.519
the sharpening the detection and the motion compensation and actually add

00:16:24.600 --> 00:16:31.480
this and W 4K pixels would be nice also and 120 HZ or more

00:16:29.600 --> 00:16:35.079
uh I think there will be when people actually see it and play it as you guys

00:16:33.079 --> 00:16:39.319
been doing and more and more people see that there will actually be a lot of lot

00:16:37.399 --> 00:16:42.160
of movement in the overall industry to transition to something like this really

00:16:40.839 --> 00:16:48.759
quite quickly and that's what I'm hoping for because then we can actually just I say Target games more specifically for

00:16:46.720 --> 00:16:53.790
this yeah exactly the rest of the industry needs to Hardware up

00:16:57.839 --> 00:17:02.519
um every display device every platform

00:17:01.000 --> 00:17:06.799
including you know the mobile platforms we need to adopt this kind of Technology

00:17:04.120 --> 00:17:12.240
over the next uh few years because it's it's visually striking um doesn't show

00:17:09.000 --> 00:17:14.280
up in a TV commercial but it's uh to any

00:17:12.240 --> 00:17:18.240
player playing the game it's incredibly apparent um the difference and visual

00:17:16.039 --> 00:17:21.120
quality here and so it's got to be a major Initiative for everybody or else

00:17:19.839 --> 00:17:26.640
people are going to look at and say oh wow that looks like you know the last generation and actually one one wish I

00:17:25.079 --> 00:17:30.520
have there is that while you're going to these uh well these retail stores with

00:17:28.919 --> 00:17:35.120
sell tons and tons of TV displays or monitors and you see all of them

00:17:32.520 --> 00:17:39.600
standing there really nice monitors well really nice big screen TVs and they look

00:17:37.720 --> 00:17:44.679
amazing and all of them are set on actually a a startup showroom mode that

00:17:42.480 --> 00:17:49.080
just cranks up all of the colors I would like to replace that remove that mode

00:17:46.360 --> 00:17:51.840
showroom mode is the is does not exist anymore instead you just have this

00:17:50.440 --> 00:17:55.200
variable refresh rate and you actually see the difference on that the false

00:17:53.880 --> 00:17:58.280
colors you don't want to have that anyway that's not calibrated to anything

00:17:56.919 --> 00:18:01.520
that we actually create it just creates a complet artificial environment plus

00:18:00.120 --> 00:18:04.559
all the other that you're do there to support Legacy

00:18:05.440 --> 00:18:08.640
cont well

00:18:08.799 --> 00:18:17.640
said look like we're going to be here for a little while longer let me take a bathroom

00:18:13.120 --> 00:18:20.159
break absolutely so uh by is there

00:18:17.640 --> 00:18:25.840
Logistics wise you know got a time here I think it's it's 2:30 hey guys just

00:18:24.039 --> 00:18:29.000
just one second this is Jensen hey John don't don't

00:18:30.480 --> 00:18:36.400
hold it for just just a second it turns out I've got to go catch a flight I

00:18:34.559 --> 00:18:41.520
didn't want to I didn't want to take off without thanking you guys properly uh

00:18:38.760 --> 00:18:47.600
you you guys you guys not only made made the show um made the launch uh you guys

00:18:45.480 --> 00:18:52.480
made made our year I mean this it is it is a quite a privilege to have you guys

00:18:50.520 --> 00:18:56.360
anywhere but to have the three of you guys in the same place at the same time

00:18:54.799 --> 00:19:00.240
and having this kind of access to you guys is really really a privilege it's a

00:18:58.880 --> 00:19:04.840
privilege for me I know it's a privilege for everybody in the audience and it's just so much fun to listen to you guys I

00:19:03.720 --> 00:19:08.960
want to thank you guys for everything you've done for the game industry but

00:19:07.440 --> 00:19:13.360
not just the game industry for the computer industry the technology

00:19:10.440 --> 00:19:17.919
industry and just good oldfashioned human beings in general okay I think you

00:19:15.440 --> 00:19:23.280
guys are fantastic I love you guys love your friendship and love your

00:19:19.320 --> 00:19:23.280
partnership thanks for everything

00:19:33.799 --> 00:19:38.960
uh 4K versus gsync what is more

00:19:37.000 --> 00:19:43.400
important to gaming J yeah I mean at this point we'll get we

00:19:41.720 --> 00:19:47.640
will always be able to suck up more resolution but right now people migrate

00:19:45.760 --> 00:19:51.360
to 4K and they get much lower frame rates on the experience and I think the

00:19:49.039 --> 00:19:57.159
trade-offs already a little bit south of optimal I that people are making now and

00:19:54.039 --> 00:19:58.760
quadrupling down on that yeah I don't

00:19:57.159 --> 00:20:02.600
think while a GN will just make everything somewhat

00:20:00.400 --> 00:20:06.240
better think you don't want to go back to anything

00:20:03.799 --> 00:20:09.960
else well I've got the whole issue about the the low persistence displays that

00:20:08.840 --> 00:20:16.400
that I have to deal with on the head mounted uh display systems and but I

00:20:14.360 --> 00:20:20.600
think that for a conventional desktop monitor I would I really want to see

00:20:18.320 --> 00:20:24.120
this just absolutely ridiculous the good news is it doesn't

00:20:22.480 --> 00:20:28.679
have to be or there either yes it's a shame that those 4K

00:20:26.679 --> 00:20:32.080
monitors fact there are not GCC because you see them jutting and tearing and

00:20:30.640 --> 00:20:35.679
exactly the problems we've been talking about now uh it's actually almost an

00:20:34.280 --> 00:20:43.080
object lesson there and it's a shame that we don't have those we're working on it we're working

00:20:39.400 --> 00:20:45.559
on it sc4k is kind of a workstation

00:20:43.080 --> 00:20:49.000
application for the next few years right uh in that time frame we'll be using

00:20:47.440 --> 00:20:55.960
those monitors for building games because we want to have a huge set of complex tools open uh photographers will

00:20:53.039 --> 00:21:00.080
be using for their were videographers lots of people will be using but I don't

00:20:57.880 --> 00:21:04.120
think it's the right output resolution for rendering until your GP is get

00:21:02.360 --> 00:21:09.240
significantly faster at consumer levels like once that 20 terap fops is in a

00:21:06.200 --> 00:21:11.200
single GPU uh costing 300 bucks that's

00:21:09.240 --> 00:21:19.440
when you want to go 4K it's when you can sustain 30 to 60 to 90 frames a second

00:21:14.720 --> 00:21:22.159
and actually just to to roll up on that

00:21:19.440 --> 00:21:26.840
the environment of where I work just on my own desk essentially have well I

00:21:24.679 --> 00:21:31.240
guess it's score portrait mode with 4in screen and a 4K screen next to that and

00:21:29.039 --> 00:21:34.760
they they're putting them in half circle around you is actually a really good

00:21:32.559 --> 00:21:40.000
work work environment work space so having a single 4K screen that's that's

00:21:37.799 --> 00:21:43.080
curved and 50 in or something that would actually replace four of my screens and

00:21:41.279 --> 00:21:47.039
would be amazing work environment for that and I probably W could definitely

00:21:45.240 --> 00:21:50.440
play games in an extremely immersive way there also and you're starting to see

00:21:48.440 --> 00:21:55.480
these curved screen curved OLED screens in that size so ad JN on it and B to 120

00:21:53.720 --> 00:21:59.679
HZ you have perfect gaming and perfect workation while we're at it I want

00:21:57.360 --> 00:22:04.200
spical section SC SC so that everything focuses properly on that's also