WEBVTT

00:00:00.160 --> 00:00:07.600
although there's still a lot of arguing between gamers who prefer the power of a

00:00:04.640 --> 00:00:11.840
pc and those who prefer the convenience of a console

00:00:09.120 --> 00:00:18.000
one thing most of us can agree on is that any particular title should just

00:00:14.400 --> 00:00:21.359
plain work as advertised regardless of

00:00:18.000 --> 00:00:23.680
the platform be it pc xbox playstation

00:00:21.359 --> 00:00:28.320
or atari 2600 but unfortunately there's been a

00:00:25.519 --> 00:00:35.600
noticeable trend over the years in which games initially developed for console

00:00:31.840 --> 00:00:38.160
just don't translate that well to the pc

00:00:35.600 --> 00:00:44.320
and when these games drop on steam they might have wonky controls underwhelming

00:00:41.040 --> 00:00:45.680
visuals or even outright game breaking

00:00:44.320 --> 00:00:50.960
bugs so why does this happen

00:00:47.840 --> 00:00:53.280
well a huge part of the issue is that at

00:00:50.960 --> 00:00:59.760
any given time there are only really about three or four major living room

00:00:56.320 --> 00:01:01.920
consoles and aside from minor updates

00:00:59.760 --> 00:01:09.040
every two years or so every single xbox one or playstation 4

00:01:05.519 --> 00:01:10.720
in existence is using the exact same

00:01:09.040 --> 00:01:16.560
hardware inside this means that developers writing games

00:01:13.280 --> 00:01:19.439
for these platforms know exactly what

00:01:16.560 --> 00:01:24.880
configurations and apis they're coding for making it easy to optimize

00:01:22.000 --> 00:01:28.640
performance and functionality for that specific device

00:01:26.400 --> 00:01:32.960
especially as consoles tend to have exclusive developer features to make

00:01:31.200 --> 00:01:36.640
programming for them even more straightforward

00:01:34.560 --> 00:01:42.320
pcs on the other hand present an additional challenge in that games must

00:01:39.119 --> 00:01:46.000
be written to work on an enormous

00:01:42.320 --> 00:01:49.200
variety of different computers and

00:01:46.000 --> 00:01:52.560
although the dominant setup is a modern

00:01:49.200 --> 00:01:55.040
64-bit version of Windows and a CPU and

00:01:52.560 --> 00:01:58.399
GPU from one of just two different manufacturers each

00:01:56.960 --> 00:02:01.680
there's still tons of variation in terms of

00:02:00.399 --> 00:02:07.520
performance driver revisions and what other kinds of

00:02:04.799 --> 00:02:12.560
hardware and software are installed and remember that on a pc

00:02:09.759 --> 00:02:18.319
games are sharing resources like memory and CPU time with other programs to a

00:02:16.160 --> 00:02:22.800
far greater extent than on a console that was built to consistently

00:02:20.480 --> 00:02:28.720
prioritize gameplay and because of all these factors every

00:02:25.200 --> 00:02:31.840
time a game is installed on another pc

00:02:28.720 --> 00:02:34.879
chances are high that it's a brand new

00:02:31.840 --> 00:02:37.920
environment the game has never actually

00:02:34.879 --> 00:02:39.599
seen before so the game's code has to be

00:02:37.920 --> 00:02:46.080
adjusted to work with general technologies such as directx and

00:02:43.040 --> 00:02:48.879
the x86 instruction set which can be an

00:02:46.080 --> 00:02:53.760
imperfect solution that as we know doesn't work flawlessly on every pc

00:02:52.239 --> 00:02:59.519
every time and even to get it as close as possible

00:02:56.480 --> 00:03:02.480
can be very time consuming and sometimes

00:02:59.519 --> 00:03:08.640
tens of thousands of files have to be rewritten to play nicely with an NVIDIA

00:03:05.360 --> 00:03:11.200
or AMD desktop graphics driver instead

00:03:08.640 --> 00:03:16.480
of some specialized API that was specifically designed for the

00:03:12.640 --> 00:03:19.760
playstation 4 meaning that pc ports also

00:03:16.480 --> 00:03:22.720
add months to development time which by

00:03:19.760 --> 00:03:28.560
the way costs money money that many game studios would rather spend on making new

00:03:25.040 --> 00:03:31.599
games marketing existing ones new dlc or

00:03:28.560 --> 00:03:33.519
heck why not ice cream at that point

00:03:31.599 --> 00:03:36.720
and since consoles are generally underpowered compared to current gen

00:03:35.280 --> 00:03:41.360
gaming computers games originally developed for consoles

00:03:39.360 --> 00:03:47.840
are often designed to be less graphically demanding so

00:03:43.840 --> 00:03:50.159
creating more high def visuals for

00:03:47.840 --> 00:03:57.439
you know whiny vocal minority customers with top of the line graphics cards like

00:03:52.799 --> 00:04:00.239
gtx 1080s and rx 580s can also result in

00:03:57.439 --> 00:04:05.760
months of additional work and this combined with the translation of visual

00:04:02.879 --> 00:04:10.239
elements so pc apis and drivers can understand them has resulted in more

00:04:08.000 --> 00:04:13.040
than a handful of games looking like a mess

00:04:11.200 --> 00:04:17.120
on a computer and of course a game being written for a

00:04:15.519 --> 00:04:21.199
certain console means it was also written with a specific controller

00:04:19.120 --> 00:04:25.919
scheme in mind meaning that the experience may not map well to a

00:04:23.840 --> 00:04:30.800
keyboard and mouse and although the concept of simply mapping a controller

00:04:28.880 --> 00:04:35.759
button to a keyboard key seems very simple this process can still involve

00:04:33.199 --> 00:04:40.160
modifying a great deal of code under the hood the good news is that while there

00:04:37.919 --> 00:04:44.639
are still plenty of bad pc ports floating around consoles have been

00:04:42.400 --> 00:04:50.080
moving towards more pc-like architectures and tools like microsoft's

00:04:47.360 --> 00:04:55.759
new universal Windows platform might make porting games at least from xbox to

00:04:52.400 --> 00:04:59.040
pc much less labor-intensive as games

00:04:55.759 --> 00:05:01.680
written for uwp like gears of war 4

00:04:59.040 --> 00:05:05.919
don't have to be rewritten for desktop computers

00:05:03.440 --> 00:05:11.199
but with that said at least for now underwhelming ports are just part of the

00:05:08.400 --> 00:05:17.360
price you pay for being a member of the pcmr

00:05:14.000 --> 00:05:20.880
do you need a gorgeous powerful simple

00:05:17.360 --> 00:05:23.440
and reliable website squarespace is the

00:05:20.880 --> 00:05:27.919
way to go you just pick one of their gorgeous templates that works great

00:05:25.680 --> 00:05:32.479
whether you're on a desktop or a mobile device they're all scalable with

00:05:29.759 --> 00:05:35.600
responsive design and it's all a cloud-based tool that you basically just

00:05:34.240 --> 00:05:39.759
go yeah okay my picture there my text there customize

00:05:38.000 --> 00:05:44.639
a little bit of this use their logo designer there oh no i don't know what

00:05:41.360 --> 00:05:46.800
to do i contact their 24 7 support via

00:05:44.639 --> 00:05:52.560
live chat and email and boom website and it starts at just 12 bucks a

00:05:49.840 --> 00:05:57.520
month with a free domain thrown in if you buy squarespace for the year every

00:05:55.680 --> 00:06:01.919
website comes with tons of great features including a free online store

00:06:00.720 --> 00:06:06.960
and new for this summer there are 16 new

00:06:04.639 --> 00:06:11.520
templates to choose from so start a trial with no credit card required and

00:06:08.800 --> 00:06:16.080
start building your website today then when you sign up for squarespace make

00:06:13.440 --> 00:06:20.800
sure you use offer code Techquickie to get 10 off your first purchase

00:06:19.199 --> 00:06:26.240
so thanks for watching guys like dislike leave a comment check out our other

00:06:22.400 --> 00:06:26.240
channels and don't forget to subscribe