WEBVTT

00:00:00.240 --> 00:00:05.759
Windows on steam deck it's here

00:00:03.439 --> 00:00:09.360
on thursday valve released the drivers that we needed to run the operating

00:00:07.120 --> 00:00:15.519
system that they have spent years trying to make sure we won't need Linux users

00:00:12.400 --> 00:00:18.320
have literally begged us not to do this

00:00:15.519 --> 00:00:23.600
or at least not to recommend it but they forgot one simple fact

00:00:20.160 --> 00:00:26.720
i own this device it's mine so whatever

00:00:23.600 --> 00:00:28.880
i do what i want and besides even i

00:00:26.720 --> 00:00:33.200
don't know if i would recommend this yet what i would recommend is our sponsor

00:00:31.039 --> 00:00:36.559
build redux build redux offers competitive pricing compared to building

00:00:34.800 --> 00:00:40.200
a pc yourself their website makes it easy to configure your build alongside

00:00:38.160 --> 00:00:45.120
their helpful support guides so head to buildredux.com Linus and start creating

00:00:42.879 --> 00:00:48.079
your pc today we will talk about how we got to this point but i don't want to

00:00:46.480 --> 00:00:52.399
keep you guys waiting and i'm going to dive right in starting with desktop

00:00:50.079 --> 00:00:57.039
controls you can use either the right joystick or the right trackpad to move

00:00:55.520 --> 00:01:01.199
the mouse cursor around and i gotta say right out of the gate

00:00:58.960 --> 00:01:07.439
having this track pad here compared to something like the joy x off on the ineo

00:01:05.439 --> 00:01:11.040
wow is that ever a lot better but there's one thing i immediately notice

00:01:09.360 --> 00:01:15.119
missing push to tab

00:01:13.200 --> 00:01:21.920
how is that not a thing no instead and this is sort of intuitive

00:01:19.119 --> 00:01:26.880
you actually use the right trigger for left click and the left trigger for

00:01:24.799 --> 00:01:31.119
right click pretty much every other handheld i've seen defaults the other

00:01:28.799 --> 00:01:36.240
way around left is left right is right but it seems like valve is of the mind

00:01:33.280 --> 00:01:40.799
that the dominant hand should be the one that is the most often clicked

00:01:39.360 --> 00:01:45.280
okay how do i scroll down the page though it's probably left yeah there we go left analog stick

00:01:44.399 --> 00:01:50.880
oh okay we just brought up an on-screen keyboard by pushing down on the d-pad

00:01:49.040 --> 00:01:54.960
i'm gonna close steam for now we can use the touchscreen as well i guess that's

00:01:52.479 --> 00:01:59.119
worth mentioning oh wait no you need steam running in order to

00:01:57.680 --> 00:02:02.399
wait nope my mouse cursor's back

00:02:00.880 --> 00:02:06.159
the right joystick doesn't work for it anymore though only the trackpad does

00:02:04.640 --> 00:02:09.840
basically there's two control schemes there's the Windows default which allows

00:02:07.680 --> 00:02:12.480
you to use this as a trackpad and yeah it's still right to left and left to

00:02:11.680 --> 00:02:16.879
right or if you have steam launched it'll

00:02:14.959 --> 00:02:20.879
actually treat the entire controller as a seam controller and you can use the

00:02:18.879 --> 00:02:25.599
joystick to control the mouse as well now that i've got steam launched again

00:02:22.319 --> 00:02:27.360
let's try to launch an application

00:02:25.599 --> 00:02:32.080
okay is i've seen this on other handhelds as

00:02:29.120 --> 00:02:36.480
well for whatever reason uac prompts disable whatever software is allowing

00:02:34.080 --> 00:02:40.400
you to joystick to mouse on the steam deck though at least you

00:02:38.319 --> 00:02:44.959
can still use the okay i swear the touchpad worked a second ago now

00:02:42.640 --> 00:02:48.720
it's not working to be clear a lot of these annoyances are kind of

00:02:47.120 --> 00:02:53.440
universal whenever you're trying to use Windows on a handheld device it's just

00:02:51.360 --> 00:02:58.159
a very imperfect experience let's have a look at how this soc appears in CPU-z

00:02:55.599 --> 00:03:04.400
since we've got it AMD ryzen we don't know exactly what kind custom

00:03:00.840 --> 00:03:06.640
apu-045 super cool nope does not know

00:03:04.400 --> 00:03:12.319
that this is lpddr5 all right then how about gpuz

00:03:09.920 --> 00:03:17.120
same thing has no idea what to make of this mess GPU clock zero megahertz

00:03:15.200 --> 00:03:22.640
custom apu0405 fair enough GPU custom GPU 405. picks up

00:03:21.040 --> 00:03:27.680
the memory speed at least it doesn't seem to indicate in any way that this

00:03:24.400 --> 00:03:30.000
memory is shared between the GPU and CPU

00:03:27.680 --> 00:03:34.879
although it does note that 1.2 gigabytes of it is hardware reserved which would

00:03:32.319 --> 00:03:38.480
be what's reserved for our GPU wi-fi works bluetooth appears to be here

00:03:36.799 --> 00:03:42.000
actually i should fire up device manager clearly all the drivers are not uh

00:03:40.720 --> 00:03:46.400
working yet unknown devices

00:03:43.920 --> 00:03:50.959
multimedia controller multimedia controller would be the onboard audio so

00:03:48.799 --> 00:03:55.360
the three and a half millimeter jack and the speakers do not work so you can use

00:03:53.439 --> 00:03:59.599
bluetooth or you can use a type c to headphone adapter for now

00:03:58.000 --> 00:04:03.840
i think we should launch a game and of course we have a second steam deck

00:04:01.519 --> 00:04:09.200
i can already tell that this is running like absolute dog poo on Windows

00:04:06.480 --> 00:04:15.040
compared to Linux it's not even close it's not even just that the FPS is lower

00:04:12.239 --> 00:04:20.479
it's just a difference in responsiveness and like stutteriness

00:04:17.280 --> 00:04:22.880
super unresponsive it's funny while i

00:04:20.479 --> 00:04:26.560
was testing this with the haptics going i thought that the speaker was going for

00:04:24.320 --> 00:04:30.000
some reason yeah because the haptics are so weak the haptics are well there's no

00:04:28.880 --> 00:04:35.199
haptics it's just the vibration in the touch

00:04:32.720 --> 00:04:41.600
pads yeah so they've tuned that in Linux so it doesn't feel so like kind of cheap

00:04:38.800 --> 00:04:45.280
and ugly sounding but in Windows clearly that same tuning hasn't taken place well

00:04:43.759 --> 00:04:50.639
how about on Windows what does the steam button and the overlay button do

00:04:48.240 --> 00:04:55.360
big fat load of nothing i mean the steam button should pull up the steam overlay

00:04:53.199 --> 00:04:58.720
or something but oh oh it does it does it pulls up the

00:04:57.199 --> 00:05:02.000
steam overlay which does allow me to exit the game so it's just the quick

00:05:00.639 --> 00:05:06.560
access menu button that doesn't do anything okay that's that's that's good

00:05:04.320 --> 00:05:11.520
obviously it's a less comprehensive steam overlay let's try something else i

00:05:09.280 --> 00:05:16.240
have not played elven ring yet so far launch time looks pretty similar i

00:05:13.120 --> 00:05:18.720
started the Windows once lately before

00:05:16.240 --> 00:05:21.440
that's a solid Linux win right there that doesn't look right on the Windows

00:05:19.919 --> 00:05:26.240
side it really doesn't when i was testing it earlier the loading screens

00:05:23.280 --> 00:05:29.919
are only 16x9 so the actual background like the game assets loading in could be

00:05:28.160 --> 00:05:33.600
seen in the seams at the top and bottom of the screen oh hilarious let's try

00:05:31.919 --> 00:05:37.120
borderless windowed i've had better luck with that in some ca

00:05:35.600 --> 00:05:41.759
what hello weird

00:05:38.800 --> 00:05:45.280
oh oh hey hey we're back time to not mess with that again i'm loading up a

00:05:43.520 --> 00:05:48.880
new game here because we did all the benchmarking on this steam account where

00:05:47.520 --> 00:05:52.960
we're actually a little bit into the game but i wanted to be able to play

00:05:51.120 --> 00:05:56.400
them side by side with you guys so we got a new account for the Linux machine

00:05:54.880 --> 00:05:59.440
and we wanted to be able to just switch back and forth between them

00:06:00.160 --> 00:06:05.280
okay wow big picture has

00:06:03.280 --> 00:06:10.400
work to do i mean valve has said that they're going to adapt big picture

00:06:08.000 --> 00:06:17.120
based on the steam os steam deck interface like this oh man

00:06:14.720 --> 00:06:22.720
night and day so much better there it is you can see the seams oh

00:06:19.199 --> 00:06:24.880
that's weird this is a famously bad port

00:06:22.720 --> 00:06:28.960
Linux for the win for loading times again

00:06:26.720 --> 00:06:32.639
wow is Windows really that far behind oh shoot i didn't open frame view this is

00:06:30.880 --> 00:06:37.520
another thing that i'm not expecting to be a great experience on the steam deck

00:06:34.880 --> 00:06:40.720
other handhelds have a button to minimize the game and jump to the

00:06:39.360 --> 00:06:45.600
desktop i suspect valve has integrated no such

00:06:43.280 --> 00:06:48.639
functionality i mean i don't need frame view to tell me

00:06:47.120 --> 00:06:55.599
that's terrible i've read about hitches and stutters in

00:06:51.280 --> 00:06:57.680
this game but this is unbelievable

00:06:55.599 --> 00:07:03.639
valve apparently used the fact that they are translating

00:07:00.240 --> 00:07:06.639
directx to vulcan to implement a

00:07:03.639 --> 00:07:08.960
pre-shader compilation routine

00:07:06.639 --> 00:07:13.759
that prevents it from starting the crazy thing about Windows though is that this

00:07:10.639 --> 00:07:16.880
isn't even behaving like on-the-fly

00:07:13.759 --> 00:07:19.039
shader compiling like it should stop

00:07:16.880 --> 00:07:23.520
doing it it should after i do a full rotation but it doesn't and so the fact

00:07:21.840 --> 00:07:28.319
that we're running this translation layer actually results in better

00:07:25.599 --> 00:07:32.720
smoothness i think it's time for us to stop the side-by-side comparison and get

00:07:30.479 --> 00:07:38.479
into the empirical data then we ran benchmarks on three great on-deck

00:07:36.160 --> 00:07:42.639
games and Linux users can breathe a sigh of relief because steam os handily

00:07:40.800 --> 00:07:46.960
outperformed Windows particularly in hitman 3 where steam os gives playable

00:07:45.039 --> 00:07:53.440
if inconsistent frame rates while Windows averages a painful 19 FPS due

00:07:50.879 --> 00:07:58.319
maternal hit a 60 FPS average on steemos while Windows was stuck in the high 40s

00:07:55.520 --> 00:08:02.479
and eldon ring famously far more playable on deck than on Windows pulls

00:08:00.160 --> 00:08:07.039
ahead in terms of frame rate and as you guys saw didn't suffer from the same

00:08:04.400 --> 00:08:11.160
stuttering that the pc port has treated Windows gamers to our swackets don't

00:08:09.360 --> 00:08:15.680
suffer either by the way lttstore.com but what about controls

00:08:13.520 --> 00:08:18.160
outside of steam we already saw that launching steam takes over the deck's

00:08:17.039 --> 00:08:22.479
controller can we do the same in say an emulator uh

00:08:20.960 --> 00:08:27.680
what emulator should you put on here i just put on retroarch oh

00:08:24.879 --> 00:08:31.280
crap i don't have screen cap it did this in testing too for whatever reason

00:08:29.599 --> 00:08:35.360
retroarch what you're seeing on your screen is not what i'm seeing on this

00:08:32.719 --> 00:08:40.399
screen this screen shows the desktop oh beautiful

00:08:37.440 --> 00:08:43.599
oh my god come on retroarch i just

00:08:41.599 --> 00:08:48.480
i mean this could be a steam controller issue how do i go back if my controller's not

00:08:46.399 --> 00:08:52.800
allowing me to go back wait oh and this is off now wait what

00:08:50.399 --> 00:08:57.040
back instead of going back negatively toggles a setting and then

00:08:54.880 --> 00:09:01.760
confirm activates the setting that is the strangest behavior i think i've ever

00:08:59.120 --> 00:09:07.120
seen out of a controller ever is steam still running uh yes that might be

00:09:05.120 --> 00:09:11.279
the problem i don't even know if i'm going to be able to close this software

00:09:09.279 --> 00:09:16.080
there's no task manager button or control alt delete button like you would

00:09:12.880 --> 00:09:17.279
see on a Windows optimized handheld

00:09:16.080 --> 00:09:21.040
that's the kind of thing that you could probably bind i mean the steam

00:09:19.120 --> 00:09:23.760
controller is infinitely customizable it's one of the best things about it

00:09:22.880 --> 00:09:29.760
but Anthony i don't think i can close retroarch

00:09:27.120 --> 00:09:33.120
because i can't go back this is crazy x and y

00:09:30.640 --> 00:09:36.640
will sometimes go down our up and down multiple items in the menu and sometimes

00:09:35.440 --> 00:09:39.920
just one see here it does just one what is

00:09:38.880 --> 00:09:45.279
happening oh you activated the on-screen keyboard

00:09:42.720 --> 00:09:49.200
i did yes you can't see it but i can unless there's an escape key on that no

00:09:47.040 --> 00:09:53.839
i don't think president quit yes full disclosure i expected that to happen oh

00:09:51.519 --> 00:09:57.680
thanks Anthony well this is just as bad back doesn't go

00:09:56.080 --> 00:10:01.600
back how do i go back b is trying to close retroarch the

00:09:59.519 --> 00:10:06.240
default control scheme in Windows without steam running for the steam deck

00:10:03.920 --> 00:10:10.560
is that that key is escape so is that a valve issue or is that a Windows issue

00:10:08.880 --> 00:10:13.600
that would be a valve's controller mapping issue now normally that makes

00:10:11.920 --> 00:10:17.680
sense for navigating Windows because the up and down arrows are just the just

00:10:15.519 --> 00:10:22.079
like the yeah the d-pad is the up and down arrows left and right

00:10:19.920 --> 00:10:27.279
so you can navigate everything with the buttons pretty well we have an xbox

00:10:24.240 --> 00:10:28.720
controller here right because now b is

00:10:27.279 --> 00:10:33.360
back because it's picked up as a controller not as a Windows

00:10:31.600 --> 00:10:38.480
pointer device yeah so i think retroarch is going to

00:10:35.440 --> 00:10:39.680
have to add a controller definition file

00:10:38.480 --> 00:10:46.560
or something to hook into it like they do with the steam deck and with the xbox 360 controller and xbox one well will

00:10:44.079 --> 00:10:49.760
the game work the game should work okay let's try the game then at least

00:10:53.760 --> 00:11:01.760
what it doesn't work even in game it's still in oh man all right well i still

00:10:59.600 --> 00:11:07.279
want to know about the latency i mean i guess it'll be fine it's just

00:11:04.079 --> 00:11:09.680
Windows i mean it should be

00:11:07.279 --> 00:11:13.040
oh yeah i mean this feels great mostly i just wanted to show off the fact that

00:11:11.279 --> 00:11:18.720
the controls are hot garbage and broken yes got it so

00:11:16.880 --> 00:11:24.160
better use steam yeah pretty much oh no not charging

00:11:21.839 --> 00:11:29.680
chuck oh i want to get up there

00:11:26.079 --> 00:11:31.200
oh balls and there are a lot of other

00:11:29.680 --> 00:11:36.079
things to keep in mind if you want to run Windows on deck for one you're not

00:11:33.839 --> 00:11:40.320
able to dual boot steam os and Windows until valve releases the final steamos

00:11:38.320 --> 00:11:43.680
installer with support for this baked in i already mentioned there isn't an audio

00:11:41.920 --> 00:11:48.560
driver for the speakers or the 3.5 millimeter headphone jack yet but audio

00:11:45.680 --> 00:11:52.800
via usbc or bluetooth does work apparently a driver will be coming for

00:11:50.320 --> 00:11:57.600
that sooner rather than later what we don't have an eta for is things like the

00:11:55.839 --> 00:12:00.959
brightness slider fix okay it works fine sometimes and

00:11:59.279 --> 00:12:05.680
sometimes it doesn't respond to the full drag yeah so you need to kind of like drag it

00:12:04.000 --> 00:12:09.680
back and forth towards the end that you want to go to so if you want to get it brighter you need to go to max and drag

00:12:08.399 --> 00:12:12.959
it back and forth you want to go darker you need to i think if it goes slow it's

00:12:12.079 --> 00:12:18.079
fine so it might be an acceleration

00:12:15.440 --> 00:12:21.440
issue with the uh like the touch to mouse input detection or whatever i

00:12:19.920 --> 00:12:25.200
don't know the proper technical terms for it but it seems to be that if you go

00:12:23.200 --> 00:12:28.800
fast it doesn't make it the whole way which could be a touch screen

00:12:26.240 --> 00:12:34.000
responsiveness issue in Windows i i'm sure it's fixable but we don't know

00:12:31.120 --> 00:12:37.040
when or if that will ever be fixed and there's also the much larger problem

00:12:35.600 --> 00:12:42.399
where the deck doesn't like to come out of sleep in Windows either it takes

00:12:38.959 --> 00:12:44.399
forever or never wakes up so you'll want

00:12:42.399 --> 00:12:47.680
to disable sleep unless you're into hard powering off in

00:12:46.240 --> 00:12:53.040
order to get back into Windows but that's not a great experience for a handheld device

00:12:51.360 --> 00:12:56.720
what's more when you go to actually install Windows you're going to notice

00:12:54.480 --> 00:13:00.000
that the display is rotated 90 degrees that's actually pretty common for

00:12:58.000 --> 00:13:04.399
devices like this because they often use panels that were designed originally for

00:13:01.920 --> 00:13:07.440
tablets it just means that until you get to the Windows desktop you're going to

00:13:05.680 --> 00:13:11.120
have to deal with that you won't have any wi-fi so you'll have to install

00:13:09.839 --> 00:13:16.320
without a product key if you don't have a type c Ethernet dongle and speaking of

00:13:14.079 --> 00:13:21.440
you're probably going to want a type c to usb-a adapter or ideally a multi-port

00:13:19.600 --> 00:13:26.000
dongle like this one so that you can plug in a usb flash drive and a keyboard

00:13:23.440 --> 00:13:30.880
and mouse it can be done without but it's definitely not as seamless

00:13:28.720 --> 00:13:34.880
all of which raises the big question here

00:13:31.760 --> 00:13:37.839
why would anyone want to run Windows on

00:13:34.880 --> 00:13:42.800
the steam deck well i can think of a few reasons even ignoring familiarity with

00:13:40.480 --> 00:13:46.720
the interface and the apps access to xbox services comes to mind while

00:13:44.959 --> 00:13:52.240
alternative launchers and storefronts for epic game store and gog are

00:13:49.199 --> 00:13:53.839
available on Linux xbox still isn't and

00:13:52.240 --> 00:13:59.360
that means there are some games that you simply cannot play on steamos right now

00:13:56.399 --> 00:14:02.560
even ignoring anti-cheat problems and you're certainly not going to get access

00:14:00.639 --> 00:14:06.240
to game pass unless you're streaming from a Windows device or from

00:14:04.480 --> 00:14:10.480
microsoft's own servers i've also personally run into some very

00:14:08.399 --> 00:14:14.800
frustrating bugs while gaming on the deck i just completed a run-through of

00:14:12.639 --> 00:14:21.360
horizon zero dawn start to finish on my personal deck and i saw everything from

00:14:18.079 --> 00:14:24.480
drops down to 1 FPS for extended periods

00:14:21.360 --> 00:14:26.720
like i'm talking 10 30 seconds at a time

00:14:24.480 --> 00:14:32.480
to hard game crashes back to the steam interface to even black screens that

00:14:29.199 --> 00:14:34.399
necessitated a full system shutdown this

00:14:32.480 --> 00:14:38.079
raises serious questions for me about the thoroughness of valve's game

00:14:35.680 --> 00:14:41.600
verification program horizon zero dawn is a great on deck game but my

00:14:40.160 --> 00:14:46.399
experience was anything but great and i sincerely doubt

00:14:44.320 --> 00:14:51.040
that if sony had actually been involved in this certification process they would

00:14:49.279 --> 00:14:56.160
have signed off on it being advertised as great on deck in fact there's a great

00:14:54.399 --> 00:14:59.920
blog post on gaming on Linux from the lead developer of f audio which is a

00:14:58.079 --> 00:15:03.920
core component of proton the compatibility layer that allows Windows

00:15:01.760 --> 00:15:08.160
games to run on Linux criticizing valve's collaboration or lack thereof

00:15:06.079 --> 00:15:12.240
with third-party developers so if valve is just yellowing it what's the process

00:15:10.480 --> 00:15:16.639
there are only so many hours in a day and valve seems to be validating a lot

00:15:14.399 --> 00:15:20.560
of freaking games based on my experience with horizon zero dawn what i suspect

00:15:18.480 --> 00:15:25.440
they're doing is they're just firing up the game playing early areas which in

00:15:23.279 --> 00:15:29.680
many games tend not to be as demanding and going yep seems good

00:15:27.760 --> 00:15:34.079
rubber stamp and i actually didn't have any issues in the first five hours of my

00:15:32.079 --> 00:15:38.800
playthrough of horizon zero dawn but by the end i was getting crashing or

00:15:35.920 --> 00:15:42.959
stuttering about every 30 minutes or so not a great experience

00:15:40.639 --> 00:15:47.120
other than that though steamos is objectively the

00:15:44.720 --> 00:15:50.199
much more polished experience the quick access menu with its convenient

00:15:48.639 --> 00:15:55.120
diagnostics and controls is conspicuously absent from Windows and

00:15:52.639 --> 00:15:58.880
even basic functionality like charging still seems to have issues in Windows we

00:15:57.120 --> 00:16:02.240
actually observed our steam deck discharging while plugged in which is

00:16:00.639 --> 00:16:05.199
something that i have never seen running steam os

00:16:03.839 --> 00:16:09.600
so valve is allowing users to run Windows

00:16:07.839 --> 00:16:14.160
even facilitating it by providing drivers and public help dogs good guy

00:16:12.079 --> 00:16:16.399
valve 100 and we're going to have those linked down below if you want to do it

00:16:15.440 --> 00:16:21.279
yourself but the roughness of the experience does

00:16:18.880 --> 00:16:26.160
make me wonder are they ever going to put in the effort that it would take to

00:16:22.800 --> 00:16:28.720
make it as smooth as steam os

00:16:26.160 --> 00:16:32.399
my gut feeling is no which makes me wonder how much of the performance

00:16:30.560 --> 00:16:36.959
difference we saw is down to a lack of optimization i mean theoretically the

00:16:34.880 --> 00:16:39.600
same hardware should perform very similarly across Windows and Linux and

00:16:38.800 --> 00:16:44.399
this our results were not even close now

00:16:42.320 --> 00:16:49.279
admittedly that could be as much AMD's fault as valves and the steam deck also

00:16:46.880 --> 00:16:54.399
features a very unusual architecture for a Windows machine with the CPU and GPU

00:16:51.600 --> 00:16:58.320
course sharing common memory i'm sure steamos on the other hand was carefully

00:16:56.320 --> 00:17:01.920
tuned to account for this i just feel like there was a lot of Windows

00:17:00.000 --> 00:17:05.919
performance left on the table here and our investigation today has left us with

00:17:03.839 --> 00:17:09.039
more questions than answers the one answer we have right now though is that

00:17:07.360 --> 00:17:13.439
we wouldn't recommend Windows on the steam deck at least not in its current

00:17:10.799 --> 00:17:18.079
state so if your must-have games don't work in steam os you might just have to

00:17:15.600 --> 00:17:21.520
pony up for a competing handheld that is at least until valve makes dual booting

00:17:20.000 --> 00:17:25.360
possible which is something we're planning to explore along with a 2

00:17:23.600 --> 00:17:28.640
terabyte internal storage upgrade to the deck so make sure you are subscribed for

00:17:27.600 --> 00:17:34.160
that and make sure you're subscribed to hear about our sponsor dbrand the robots at

00:17:32.160 --> 00:17:38.720
dbrand drove a truck of money to our office to push their new project kill

00:17:36.400 --> 00:17:42.480
switch on pretty much every steam deck video that we have what's project kill

00:17:40.559 --> 00:17:46.400
switch well it's a project to kill the switch i think basically it's similar to

00:17:44.720 --> 00:17:50.720
their grip cases for phones and other devices but for your steam deck it's got

00:17:48.880 --> 00:17:54.160
a rugged rubberized finish plus a kickstand for when you're gaming on the

00:17:52.240 --> 00:17:56.799
go but you want to pull out a controller they've also got their tempered glass

00:17:55.440 --> 00:18:00.720
screen protector for the steam deck which we tested out for them turns out

00:17:58.960 --> 00:18:05.280
regular tempered glass inhibits touch sensitivity but dbrand screen protectors

00:18:03.280 --> 00:18:08.960
are super precise and guaranteed to work on your display so why wait you can

00:18:07.280 --> 00:18:13.600
reserve projects kill switch now at dbrand.com killswitch or at the link

00:18:11.440 --> 00:18:16.799
down below thanks for watching guys go check out our initial review of the

00:18:15.120 --> 00:18:23.520
steam deck for more decky goodness it still blows my mind they managed to ship these

00:18:19.600 --> 00:18:23.520
things especially for this price