1
00:00:00,120 --> 00:00:03,480
Randy Pitchford says something 
stupid, multiple websites with 

2
00:00:03,480 --> 00:00:07,840
their false article titles and 
more in today's side podcast. 

3
00:00:07,920 --> 00:00:09,800
Sit on back. 
Let's discuss. 

4
00:00:09,800 --> 00:00:12,600
First thing I got is a question 
from a viewer. 

5
00:00:12,680 --> 00:00:17,440
King Liquef this is this is 
already starting out awesome 

6
00:00:17,720 --> 00:00:21,000
Carrick years ago, back when the
world was fertile and untouched 

7
00:00:21,000 --> 00:00:24,320
by man, you said something about
a new algorithm change that some

8
00:00:24,320 --> 00:00:26,800
video makers had hit earlier. 
As a test. 

9
00:00:26,800 --> 00:00:30,160
I saw a video that looks like it
rolled out to others, but then I

10
00:00:30,160 --> 00:00:31,680
saw a video that tried to debunk
it. 

11
00:00:31,760 --> 00:00:34,880
Honestly that video though was 
sort of crap so I wanted to ask 

12
00:00:34,880 --> 00:00:37,200
your opinion on where you see 
that now. 

13
00:00:37,840 --> 00:00:40,360
So basically what I think you're
talking about is your AI search 

14
00:00:40,360 --> 00:00:42,520
summaries. 
GPT use changes to system 

15
00:00:42,520 --> 00:00:44,920
something you guys will see if 
you're on Twitter or you're 

16
00:00:45,240 --> 00:00:47,280
Instagram. 
We can't look at an algorithm 

17
00:00:47,280 --> 00:00:49,640
and realize that every single 
day we talk about something that

18
00:00:49,640 --> 00:00:52,880
pops up in our search 2 minutes 
later that it isn't adjusting 

19
00:00:52,880 --> 00:00:55,280
elsewhere. 
So trying to debunk it is sort 

20
00:00:55,280 --> 00:00:57,360
of like trying to say that the. 
World is flat. 

21
00:00:57,440 --> 00:01:00,480
It's pretty idiotic. 
Not only that, we have about 500

22
00:01:00,480 --> 00:01:04,920
people in our one YouTube 
creator group and all of them 

23
00:01:04,920 --> 00:01:07,120
have seen a drop on the exact 
same day. 

24
00:01:07,280 --> 00:01:09,920
I've seen people say oh maybe 
your quality of your video just 

25
00:01:09,920 --> 00:01:12,480
isn't as good as something or 
something like that. 

26
00:01:12,600 --> 00:01:15,960
However, they roll these out in 
waves and when you see that many

27
00:01:15,960 --> 00:01:19,400
people seeing a sudden shift in 
the same three to four days, and

28
00:01:19,400 --> 00:01:21,840
these are people that are 
seeing, you know, of you cut in 

29
00:01:22,320 --> 00:01:25,560
to 1/4 of what it was or even 
3/4 of what it was, you can 

30
00:01:25,560 --> 00:01:28,040
normally look. 
But outside of this, even 

31
00:01:28,040 --> 00:01:30,760
looking outside of gaming, 
that's actually what I do is I 

32
00:01:30,760 --> 00:01:34,160
don't just talk about the gaming
side and I don't just talk to 

33
00:01:34,160 --> 00:01:37,520
gaming Youtubers, but talking to
Youtubers who run channels of 

34
00:01:37,520 --> 00:01:41,120
one of the person in the group. 
I think he's got 7 channels, all

35
00:01:41,120 --> 00:01:43,160
of them with over 1,000,000 
subscribers. 

36
00:01:43,280 --> 00:01:47,160
Guy is prolific as shit and, and
he he was seeing it as well. 

37
00:01:47,160 --> 00:01:49,040
It's something that is for sure 
done. 

38
00:01:49,040 --> 00:01:50,600
So anybody trying to debunk 
that? 

39
00:01:50,600 --> 00:01:53,360
That's pretty much debunked 
instantly by math. 

40
00:01:53,560 --> 00:01:56,440
So math and facts. 
That's just sort of the way it 

41
00:01:56,440 --> 00:01:58,280
was. 
I got to see it early because I 

42
00:01:58,280 --> 00:02:01,280
was in the first alpha roll out 
of it and was told that I was, 

43
00:02:01,400 --> 00:02:04,560
but I was only told that I was 
after I ended up querying a 

44
00:02:04,560 --> 00:02:07,400
bunch of people and trying to 
figure out where I was and why I

45
00:02:07,400 --> 00:02:08,840
was seeing a very particular 
thing. 

46
00:02:09,000 --> 00:02:11,480
I've sort of rebounded from it a
little bit and changed some of 

47
00:02:11,480 --> 00:02:13,760
the way I do things, but this is
the way the world's going right 

48
00:02:13,760 --> 00:02:14,960
now. 
So we're going to see some of 

49
00:02:14,960 --> 00:02:17,720
the those changes. 
Next up, Randy Pitchford. 

50
00:02:17,800 --> 00:02:21,640
So people been posting multiple 
times to that the telegram 

51
00:02:21,640 --> 00:02:24,320
they've been DM ING me and 
asking about the Randy Pitchford

52
00:02:24,320 --> 00:02:26,280
thing. 
Here's here's here's how it 

53
00:02:26,280 --> 00:02:28,720
goes. 
Randy Pitchford as a dev has the

54
00:02:28,720 --> 00:02:31,520
right every right to push back 
on fans. 

55
00:02:31,640 --> 00:02:34,160
About four years ago in the 
podcast, I had stated that I 

56
00:02:34,160 --> 00:02:37,400
didn't feel that the future was 
going to look the same way as 

57
00:02:37,400 --> 00:02:40,520
that current time did when it 
came to developers talking to 

58
00:02:40,520 --> 00:02:43,040
gamers. 
I had noticed that distinctively

59
00:02:43,040 --> 00:02:45,000
negative slant this. 
Was prior to COVID. 

60
00:02:45,480 --> 00:02:48,360
And I was under the impression 
that at some point you'd start 

61
00:02:48,360 --> 00:02:50,680
to see a lot of developers 
pushing back on stuff. 

62
00:02:50,680 --> 00:02:53,360
Now, pushing back doesn't mean 
right because I don't think he's

63
00:02:53,360 --> 00:02:55,840
right. 
But pushing back and just not 

64
00:02:55,840 --> 00:02:59,600
sort of, you know, sitting back 
and taking it in that way of, 

65
00:02:59,760 --> 00:03:01,920
you know, I made something. 
You just need to live with it 

66
00:03:01,920 --> 00:03:03,720
kind of way. 
It's sort of like whenever you 

67
00:03:03,720 --> 00:03:06,080
get do a YouTube video and 
somebody says, I hate your video

68
00:03:06,080 --> 00:03:07,880
and you're like, well, then move
somewhere else and somebody will

69
00:03:07,880 --> 00:03:11,080
say, man, I can't believe you 
didn't adjust in every way for 

70
00:03:11,080 --> 00:03:13,800
this one person complaining. 
It really doesn't make sense. 

71
00:03:13,800 --> 00:03:16,320
And that's what Randy's doing. 
He's complaining about things 

72
00:03:16,320 --> 00:03:19,920
that don't make a lot of sense, 
but what he is trying to do, 

73
00:03:19,920 --> 00:03:22,280
there's a couple things and he 
probably shouldn't do any of 

74
00:03:22,280 --> 00:03:24,200
them. 
He's trying to defend the team, 

75
00:03:24,240 --> 00:03:26,520
of course. 
He's trying to explain things 

76
00:03:26,520 --> 00:03:29,560
when it comes to being a 
developer, and those fall to the

77
00:03:29,560 --> 00:03:33,440
wayside under 144 or a 244 
character limit. 

78
00:03:33,560 --> 00:03:36,960
And he's never really been that 
robust when it comes to 

79
00:03:36,960 --> 00:03:39,400
communication anyway. 
He's had multiple issues. 

80
00:03:39,400 --> 00:03:41,960
So this isn't something that is 
just Randy Pitchford. 

81
00:03:41,960 --> 00:03:43,680
You're going to see it with 
multiple developers. 

82
00:03:43,680 --> 00:03:45,040
We've started to see it 
overtime. 

83
00:03:45,120 --> 00:03:47,080
You started to see people 
starting to push back. 

84
00:03:47,240 --> 00:03:49,640
Just remember this, when I 
started the channel, you would 

85
00:03:49,640 --> 00:03:53,840
never ever, I mean, and I mean 
ever see a YouTube push back 

86
00:03:53,840 --> 00:03:56,960
like I did on Twitter. 
If somebody said something to a 

87
00:03:56,960 --> 00:03:59,280
person, they'd just be like, oh,
well, I'm really sorry you 

88
00:03:59,280 --> 00:04:00,720
didn't like it. 
You know, maybe you'll like the 

89
00:04:00,720 --> 00:04:02,800
next one, right? 
And I was always under the 

90
00:04:02,800 --> 00:04:05,120
impression I was always sitting 
there going like, I don't quite 

91
00:04:05,120 --> 00:04:08,120
understand if somebody's 
factually incorrect on something

92
00:04:08,320 --> 00:04:11,280
or if they're lying, why you 
don't just absolutely smash the 

93
00:04:11,280 --> 00:04:13,480
shit out of them. 
And you know, there's probably 

94
00:04:13,480 --> 00:04:16,720
some reasons why. 
But I think that one of the 

95
00:04:16,720 --> 00:04:20,040
reasons why I do believe that if
there's a true falsehood, a 

96
00:04:20,040 --> 00:04:23,160
developer should speak up, is 
because a lie spreads quite 

97
00:04:23,160 --> 00:04:26,480
quickly and it's believed just 
because it's said with. 

98
00:04:26,520 --> 00:04:28,160
Authority. 
Let me give you an example. 

99
00:04:28,280 --> 00:04:31,520
I was in my own discord a couple
days ago and I saw multiple 

100
00:04:31,520 --> 00:04:33,600
people just talking about 
something that had been 

101
00:04:33,600 --> 00:04:36,160
disproven. 
And I actually decided instead 

102
00:04:36,160 --> 00:04:38,840
of jumping in right away, I 
would watch what happened. 

103
00:04:38,880 --> 00:04:42,320
And what I saw was I would, I 
sort of called it the Christmas 

104
00:04:42,320 --> 00:04:44,040
tree effect. 
It starts at the top. 

105
00:04:44,040 --> 00:04:47,080
The little shining are of a 
myth, that person who lifts 

106
00:04:47,080 --> 00:04:50,400
aloft something that's 
absolutely asinine or not 

107
00:04:50,400 --> 00:04:53,520
researched, and they say it. 
And then what happens is if the 

108
00:04:53,520 --> 00:04:55,680
rest of the lights don't turn 
on, meaning people don't see 

109
00:04:55,680 --> 00:04:58,320
that, it's probably fine. 
It filters itself out. 

110
00:04:58,360 --> 00:05:01,400
But if they do, it starts, you 
just start seeing multiple 

111
00:05:01,400 --> 00:05:03,280
people pinging on that one 
thing. 

112
00:05:03,280 --> 00:05:05,120
You see a little light here, a 
little light here, like the 

113
00:05:05,120 --> 00:05:07,040
Christmas tree lights are 
warming up. 

114
00:05:07,240 --> 00:05:10,320
And each one is another person 
regurgitating the thought. 

115
00:05:10,320 --> 00:05:12,320
And you don't actually see a lot
of pushback. 

116
00:05:12,320 --> 00:05:14,520
And there's reasons why 
sometimes a person doesn't want 

117
00:05:14,520 --> 00:05:15,920
to push back, they don't want to
cause an issue. 

118
00:05:16,000 --> 00:05:18,840
Sometimes they don't care. 
But both of those things can 

119
00:05:18,880 --> 00:05:23,600
ultimately result in that entire
light system just being myths. 

120
00:05:23,760 --> 00:05:26,280
The entire Christmas tree is 
just a light with stupidity. 

121
00:05:26,280 --> 00:05:28,240
And you sit back and you look at
it and you're like, that thing's

122
00:05:28,240 --> 00:05:30,840
going to burn the fucking house 
down if somebody doesn't figure 

123
00:05:30,840 --> 00:05:33,240
it out. 
And my personal belief is I 

124
00:05:33,240 --> 00:05:36,480
think it's the responsibility of
people who create to, you know, 

125
00:05:36,480 --> 00:05:38,360
to stop any falsehoods that pop 
up. 

126
00:05:38,520 --> 00:05:40,600
That doesn't mean if somebody 
points out you made a mistake on

127
00:05:40,600 --> 00:05:42,880
something that you can't say, 
oh, I did make a mistake, sorry.

128
00:05:42,880 --> 00:05:45,600
But if somebody's just 
completely, you know, got a myth

129
00:05:45,600 --> 00:05:48,240
out there, if they're fucking 
got the Loch Ness Monster 

130
00:05:48,240 --> 00:05:51,040
version of video game myths, 
somebody should step in. 

131
00:05:51,200 --> 00:05:53,800
Randy's not doing that. 
Whatever's going on within their

132
00:05:53,800 --> 00:05:57,680
company internally and on their 
systems, he believes it performs

133
00:05:57,760 --> 00:06:00,240
either adequately or close to 
adequately. 

134
00:06:00,240 --> 00:06:03,280
And I think we all agree it 
doesn't yet. 

135
00:06:03,400 --> 00:06:05,880
And there's not as many issues 
with the stuttering. 

136
00:06:05,880 --> 00:06:08,520
There's actually issues with 
just ultimately the performance 

137
00:06:08,520 --> 00:06:11,840
as if, and I was describing this
to somebody yesterday, it's 

138
00:06:11,840 --> 00:06:14,280
almost as if. 
There are a couple ways to fix 

139
00:06:14,280 --> 00:06:17,720
this, and one of. 
Of those ways is to get away 

140
00:06:17,720 --> 00:06:21,640
from the stuttering, but induce 
that lower FPS, right Or have 

141
00:06:21,640 --> 00:06:24,720
the higher FPS and you're going 
to get the stuttering. 

142
00:06:24,720 --> 00:06:27,080
It's like the two are on this 
sort of fulcrum. 

143
00:06:27,080 --> 00:06:29,040
Now we do know. 
That there are. 

144
00:06:29,040 --> 00:06:33,120
Games that have both Hell is US 
is a prime example of that, with

145
00:06:33,120 --> 00:06:36,760
a massive draw distance, very 
good FPS and really no 

146
00:06:36,760 --> 00:06:39,120
stuttering to be heard of. 
I mean, there's a couple, but 

147
00:06:39,120 --> 00:06:42,120
it's very hard to tell if that's
Windows or if that's a system 

148
00:06:42,120 --> 00:06:45,840
glitch or just, you know, some 
kind of momentary memory thrash.

149
00:06:46,040 --> 00:06:47,920
So we do see that that can 
happen. 

150
00:06:47,920 --> 00:06:50,440
But I've wondered at times when 
I look at this if that 

151
00:06:50,440 --> 00:06:52,920
adjustment, if that fulcrum is 
there and there's something to 

152
00:06:52,920 --> 00:06:56,040
be said for, you know, hey, we 
want to get no stuttering. 

153
00:06:56,200 --> 00:06:59,640
But with the implementation 
we're using for our game, which 

154
00:06:59,640 --> 00:07:03,880
now is open world, we can't have
the FPS as high as we would 

155
00:07:03,880 --> 00:07:05,960
like. 
And maybe they made some kind of

156
00:07:05,960 --> 00:07:07,640
mistake. 
I personally believe there's a 

157
00:07:07,640 --> 00:07:10,040
couple things going on. 
I actually think there's some 

158
00:07:10,040 --> 00:07:13,120
mistakes in there in INI files. 
Now that might sound weird, but 

159
00:07:13,120 --> 00:07:15,040
bear with me here. 
If you go into the game and you.

160
00:07:15,120 --> 00:07:17,840
Change some of the settings. 
There's a couple settings that 

161
00:07:17,840 --> 00:07:21,880
make some massive differences to
the FPS, but they don't actually

162
00:07:21,880 --> 00:07:26,240
make it completely smooth until 
you start going down or high FPS

163
00:07:26,240 --> 00:07:27,960
until you start going down very 
low. 

164
00:07:28,080 --> 00:07:31,600
What it actually feels like to 
me is that whatever they did in 

165
00:07:31,600 --> 00:07:34,120
their INI files, and it could 
just what I mean by that is it 

166
00:07:34,120 --> 00:07:37,480
could be in their INI files, but
maybe their estimate estimation 

167
00:07:37,480 --> 00:07:39,560
of what people have for systems 
power. 

168
00:07:39,640 --> 00:07:44,080
But what it feels like to me is 
that high is ultra and your your

169
00:07:44,080 --> 00:07:47,280
normal is high. 
High or even at this point very 

170
00:07:47,280 --> 00:07:50,720
high and definitely when I 
started dropping the different 

171
00:07:50,720 --> 00:07:55,120
levels of of systems and their 
effects, that's actually sort of

172
00:07:55,120 --> 00:07:59,040
borne out where low here is 
probably normal. 

173
00:07:59,120 --> 00:08:02,880
And they definitely need to go 
in and change that up and touch 

174
00:08:02,880 --> 00:08:04,200
it up and figure out what's 
going on. 

175
00:08:04,200 --> 00:08:06,000
They've done 1 patch, they need 
to do another. 

176
00:08:06,000 --> 00:08:08,480
But don't expect the developers 
to stop pushing back. 

177
00:08:08,600 --> 00:08:10,800
Randy, of course, this is just 
the way he is. 

178
00:08:11,000 --> 00:08:14,720
A lot of people, despite all of 
these issues, guys, a lot of 

179
00:08:14,720 --> 00:08:16,200
people. 
Internally at that company 

180
00:08:16,200 --> 00:08:19,560
actually do like him and I think
it's even the guy above him was 

181
00:08:19,560 --> 00:08:22,280
saying, you know, he may not 
communicate the best, but I 

182
00:08:22,280 --> 00:08:25,240
absolutely, I love the guy and 
so hey, you know, that's just 

183
00:08:25,240 --> 00:08:27,600
the way it is. 
He does say some stuff that is 

184
00:08:27,800 --> 00:08:31,680
intelligent outside of Twitter 
though, or or would be a useful 

185
00:08:31,680 --> 00:08:35,080
discussion to be said outside of
Twitter or at a different time. 

186
00:08:35,120 --> 00:08:39,120
Unfortunately, during these 
times, he says those same things

187
00:08:39,159 --> 00:08:41,840
and they just, they really do 
sound brain dead. 

188
00:08:41,960 --> 00:08:44,120
Speaking of brain dead, let's 
talk about the other thing. 

189
00:08:44,400 --> 00:08:46,760
So I was sitting there, they're 
looking at websites and I always

190
00:08:46,760 --> 00:08:50,240
like to read what I can when I 
can and do whatever research I 

191
00:08:50,240 --> 00:08:51,880
can. 
And I saw one that sort of 

192
00:08:51,960 --> 00:08:54,960
caught me a little bit by not 
necessarily by surprise, what 

193
00:08:54,960 --> 00:08:57,240
made me go, I think I need to 
click this. 

194
00:08:57,240 --> 00:09:00,680
I just have a feeling when I 
read this article, it's not 

195
00:09:00,680 --> 00:09:02,720
going to be what the article 
states it is. 

196
00:09:02,840 --> 00:09:05,080
And what was that article? 
It was by Kotaku. 

197
00:09:05,160 --> 00:09:08,440
It said Battlefield 6 dev 
struggled on the Xbox Series S. 

198
00:09:08,600 --> 00:09:13,280
So this is a classic case of 
feeding the headline. 

199
00:09:13,280 --> 00:09:15,400
If you guys don't know what 
feeding the headline is, that 

200
00:09:15,400 --> 00:09:20,200
means you use the word so that 
it sounds like the devs did the 

201
00:09:20,240 --> 00:09:23,880
question came up where the where
the devs were asked if they 

202
00:09:23,880 --> 00:09:26,240
struggled and let me read you 
this. 

203
00:09:26,400 --> 00:09:28,520
This is from their actual 
developer. 

204
00:09:28,600 --> 00:09:31,040
I'll say that the biggest thing 
we did that was a challenge for 

205
00:09:31,040 --> 00:09:34,680
us was dealing with the limited 
memory explain Christian Buell, 

206
00:09:34,880 --> 00:09:38,200
the technical director on 
Battlefield 6 Xbox Series S does

207
00:09:38,200 --> 00:09:40,680
have less memory than even our 
mid spec PC. 

208
00:09:40,680 --> 00:09:44,440
And so there was a point, I want
to say 6 to 12 months ago, where

209
00:09:44,440 --> 00:09:46,960
we kind of realized that a lot 
of our levels were crashing on 

210
00:09:46,960 --> 00:09:49,400
Xbox Series S. 
As a result, the team focused on

211
00:09:49,400 --> 00:09:51,720
optimizing memory usage in 
Battlefield 6. 

212
00:09:51,880 --> 00:09:54,960
Those improvements weren't just 
felt on the Series S, according 

213
00:09:54,960 --> 00:09:57,560
to Buell, this process made the 
whole game better and more 

214
00:09:57,560 --> 00:09:59,760
stable. 
We were doing so much testing. 

215
00:09:59,760 --> 00:10:01,840
We were collecting all this 
data, explained Buell. 

216
00:10:01,960 --> 00:10:04,440
Once we kind of started running 
all of our levels through it and

217
00:10:04,480 --> 00:10:06,760
we were able to see where the 
problems were, after a month or 

218
00:10:06,760 --> 00:10:09,800
two, we'd kind of resolved all 
of our memory issues on the 

219
00:10:09,800 --> 00:10:11,880
Series S. 
Now, you may think to yourself, 

220
00:10:12,040 --> 00:10:13,520
well, that does sound like 
struggle. 

221
00:10:13,520 --> 00:10:16,360
I'm going to tell you, I don't 
think there's a single developer

222
00:10:16,360 --> 00:10:19,360
in the world who's worked on any
type of game who would consider 

223
00:10:19,440 --> 00:10:22,840
that struggle. 
That kind of stuff happens all 

224
00:10:22,880 --> 00:10:25,560
the time. 
That kind of situation is quite 

225
00:10:25,560 --> 00:10:29,720
literally this is what's even 
stranger. 6 to 12 months ago, 

226
00:10:29,800 --> 00:10:32,960
that is way back in the 
development process. 

227
00:10:32,960 --> 00:10:34,840
That is way farther back than I 
thought. 

228
00:10:34,840 --> 00:10:37,480
I thought this was going to be 
in their optimization phase, 

229
00:10:37,480 --> 00:10:40,720
which was, let's say, you know, 
two to three months ago, 6-12 

230
00:10:40,720 --> 00:10:42,920
months ago and never said 
struggled. 

231
00:10:43,080 --> 00:10:46,080
The reason why these kind of 
things bother me just a little 

232
00:10:46,080 --> 00:10:49,240
bit, and this one may be less so
than others, is simply because 

233
00:10:49,400 --> 00:10:52,760
we all know that those systems 
with low memory are definitely 

234
00:10:52,760 --> 00:10:56,200
going to cause issues. 
But when you start to sit here 

235
00:10:56,200 --> 00:10:59,200
and you put words in developers 
mouths and then instead of 

236
00:10:59,200 --> 00:11:03,480
actually using their response, 
you use your question, it is 

237
00:11:03,480 --> 00:11:06,560
feeding the headline and it's 
actually considered really, 

238
00:11:06,720 --> 00:11:11,320
really, really poor journalism. 
Most people will not do that. 

239
00:11:11,320 --> 00:11:13,800
And most of the journalists 
we've had on the podcast, that 

240
00:11:13,800 --> 00:11:17,160
would be something that they're 
like, like, we are not doing 

241
00:11:17,160 --> 00:11:20,080
that because that is not the 
words they used. 

242
00:11:20,080 --> 00:11:22,240
There are many words here that 
they could have used that would 

243
00:11:22,240 --> 00:11:23,960
have maybe even hit just as 
hard. 

244
00:11:24,120 --> 00:11:26,720
But the idea of feeding that 
headline, it always ends up 

245
00:11:26,720 --> 00:11:29,880
adjusting things. 
And I think for the most part, 

246
00:11:30,040 --> 00:11:32,680
especially when you look at how 
these developers work, 

247
00:11:32,880 --> 00:11:35,760
optimizing memory usage in all 
of the systems would have 

248
00:11:35,760 --> 00:11:37,800
happened even if the crashes 
weren't occurring. 

249
00:11:37,800 --> 00:11:41,160
So, but let's be honest, it is a
completely different 

250
00:11:41,160 --> 00:11:43,760
architecture. 
So it's not necessarily like 

251
00:11:43,880 --> 00:11:46,120
that, doesn't mean they had to 
work hard, but it always bothers

252
00:11:46,120 --> 00:11:49,360
me a little bit, especially when
you find out that it's not even 

253
00:11:49,360 --> 00:11:53,280
as low as the low end system, 
it's as low as the mid to low 

254
00:11:53,280 --> 00:11:56,400
system, which most devs can 
figure out and work around. 

255
00:11:56,440 --> 00:11:59,040
And so the idea that they were 
struggling always bothers me. 

256
00:11:59,040 --> 00:12:02,360
It always puts them in a bad 
light just because the actual 

257
00:12:02,360 --> 00:12:04,680
author of the article wants the 
limelight. 

258
00:12:04,720 --> 00:12:06,800
I hate that shit. 
But what I don't hate is cool 

259
00:12:06,800 --> 00:12:09,760
questions. 
Gemma Dale has a question and 

260
00:12:09,760 --> 00:12:11,960
states. 
Can you please describe to me 

261
00:12:12,120 --> 00:12:16,960
how a system takes stereo audio 
and turns it into fake 5.1? 

262
00:12:17,160 --> 00:12:20,000
OK, so I'm assuming you're 
talking about headphones and 

263
00:12:20,000 --> 00:12:22,920
something like that. 
So those kind of situations, it 

264
00:12:22,920 --> 00:12:25,440
depends on if it's hardware or 
software based on what they use.

265
00:12:25,440 --> 00:12:27,200
But easiest way to describe it 
is this. 

266
00:12:27,400 --> 00:12:30,920
If there's a 5.1 and I think 
you're talking in reverse, the 

267
00:12:31,000 --> 00:12:33,280
other way is actually easier. 
Let's talk in reverse. 

268
00:12:33,280 --> 00:12:36,600
So you're talking about your 
system, your games got 5.1, you 

269
00:12:36,600 --> 00:12:39,880
put your headphones on and you 
have sort of a fake 5.1. 

270
00:12:39,880 --> 00:12:42,440
And why do those sometimes work 
and why do they sometimes not? 

271
00:12:42,480 --> 00:12:45,200
There's a lot of calculations 
involved, but the great the 

272
00:12:45,200 --> 00:12:48,520
latest and easiest way to 
describe it would be a very 

273
00:12:48,520 --> 00:12:51,080
hefty amount of processing on a 
signal. 

274
00:12:51,120 --> 00:12:55,400
So you get your 5.1 audio and 
you go into a set of headphones 

275
00:12:55,400 --> 00:12:58,560
and you've only got one set of 
ear ear holes, right? 

276
00:12:58,640 --> 00:13:01,320
So they have to figure out a way
to make it appear like it's 

277
00:13:01,320 --> 00:13:03,120
directionally coming from 
somewhere else. 

278
00:13:03,200 --> 00:13:07,600
So what they can do is they can 
put different layers basically 

279
00:13:07,600 --> 00:13:11,520
of echo and reverb and other 
processing effects, as well as 

280
00:13:11,520 --> 00:13:15,920
feeding the audio in lightly 
into the other headphone at 

281
00:13:15,920 --> 00:13:18,760
times. 
And by doing differentials, by 

282
00:13:18,760 --> 00:13:22,720
basically slicing that up a bit 
for each sound effect and 

283
00:13:22,720 --> 00:13:25,600
running those through 
algorithms, you can cause the 

284
00:13:25,600 --> 00:13:29,600
human ear to hear sounds that 
appear generally behind them 

285
00:13:29,600 --> 00:13:32,120
because you're mimicking what 
the ears do. 

286
00:13:32,240 --> 00:13:35,320
Because if you go back and you 
feel the flaps on the back of 

287
00:13:35,320 --> 00:13:39,000
your ears, the reason why a snap
behind your head and a snap 

288
00:13:39,000 --> 00:13:41,800
beside your head sounds 
different is because the sound 

289
00:13:41,800 --> 00:13:45,240
behind your head has to go 
around basically hit the those 

290
00:13:45,280 --> 00:13:47,400
earlobes and still get into the 
ear, right? 

291
00:13:47,400 --> 00:13:50,640
And has to bounce off of stuff. 
So what they do is they mimic a 

292
00:13:50,640 --> 00:13:53,760
lot of that. 
And they spend years, especially

293
00:13:53,760 --> 00:13:56,280
when this was first a thing 
where they didn't have 

294
00:13:56,280 --> 00:13:58,520
algorithms they could piggyback 
on like they do now. 

295
00:13:58,680 --> 00:14:01,560
But in the past, they had to do 
a ton of testing to sort of 

296
00:14:01,560 --> 00:14:05,360
figure out how do we fake that? 
What type of level of sort of 

297
00:14:05,360 --> 00:14:09,200
occlusion do we fake into these?
And we can get these to sound 

298
00:14:09,200 --> 00:14:10,760
like they're a little bit behind
you. 

299
00:14:10,960 --> 00:14:14,960
And then interestingly enough, 
if you notice there was a little

300
00:14:15,120 --> 00:14:17,680
trick, it doesn't happen as much
anymore, but there was a trick 

301
00:14:17,680 --> 00:14:20,640
that or a way you could tell 
that this was happening. 

302
00:14:20,760 --> 00:14:24,600
In older games, if you took a 2 
point or if you took a headset 

303
00:14:24,600 --> 00:14:27,560
and you took a 5.1 and you piped
it to the headset. 

304
00:14:27,560 --> 00:14:31,840
There were times where in many 
games, if an enemy was directly 

305
00:14:31,840 --> 00:14:35,480
behind you, as in almost 
perfectly lined up behind you 

306
00:14:35,480 --> 00:14:37,960
and they were talking, you may 
have noticed something. 

307
00:14:38,120 --> 00:14:41,120
And that is it stopped being 
able to be heard. 

308
00:14:41,200 --> 00:14:44,800
And the reason why is because a 
lot of those calculations had to

309
00:14:44,800 --> 00:14:48,160
do with playing with the offset 
of a person a degree or two to 

310
00:14:48,160 --> 00:14:50,920
the right or left behind you and
all the calculations. 

311
00:14:51,080 --> 00:14:54,240
But once you get a person 
directly behind you and you're 

312
00:14:54,240 --> 00:14:57,480
faking that, well, now that's 
all sorts of problems because 

313
00:14:57,480 --> 00:15:00,480
now you have to figure out a way
to double up on the fakery. 

314
00:15:00,560 --> 00:15:03,040
You have to figure out a way to 
where you can't sort of lie to 

315
00:15:03,040 --> 00:15:06,320
your right ear by slightly 
fading it a little bit delayed 

316
00:15:06,320 --> 00:15:09,080
to your left ear. 
So for example, if a person or 

317
00:15:09,080 --> 00:15:14,040
an enemy is 45° to your rear, 
right, you can play it to the 

318
00:15:14,040 --> 00:15:17,600
right ear and put a slight bit 
of delay as well as some 

319
00:15:17,600 --> 00:15:20,760
occlusion and all of your 
processing to make it sound a 

320
00:15:20,760 --> 00:15:22,600
little bit cloudier on your left
ear. 

321
00:15:22,640 --> 00:15:25,280
That'll trick your brain into 
thinking, oh, that guy's back 

322
00:15:25,280 --> 00:15:26,920
there. 
But directly behind you was an 

323
00:15:26,920 --> 00:15:28,800
issue. 
And there were some systems that

324
00:15:28,800 --> 00:15:31,680
would not play the audio if the 
enemy was directly behind you. 

325
00:15:31,840 --> 00:15:34,760
And it was usually enemy sounds.
It wouldn't be guns, it would be

326
00:15:34,760 --> 00:15:36,600
voices, guns and stuff like 
that. 

327
00:15:36,600 --> 00:15:38,960
There's ways in which you're 
bouncing that audio off of 

328
00:15:38,960 --> 00:15:40,880
walls. 
And because they're loud, it was

329
00:15:40,880 --> 00:15:43,000
much easier. 
But there's some old games where

330
00:15:43,000 --> 00:15:45,800
you'd be playing and if an NPC 
was giving you request and you 

331
00:15:45,800 --> 00:15:48,520
decided to turn around and look 
at the town behind you, it'd 

332
00:15:48,520 --> 00:15:51,440
just go like, yeah, so here's 
strangely, I think we can. 

333
00:15:51,600 --> 00:15:53,920
So if you want to go and you'd 
be like, wait, what? 

334
00:15:53,960 --> 00:15:56,880
Did I not hear that guy? 
And you could actually test 

335
00:15:56,880 --> 00:15:58,160
this. 
You could trigger it on older 

336
00:15:58,160 --> 00:16:01,200
games, you'd hit play and then 
you'd turn around and you that 

337
00:16:01,200 --> 00:16:03,440
would just go away. 
Now we have all kinds of 

338
00:16:03,440 --> 00:16:05,760
hardware algorithms and we have 
discrete levels. 

339
00:16:05,760 --> 00:16:10,200
So if you think about back in 
the past, you had, let's say 256

340
00:16:10,440 --> 00:16:13,000
layers of samples. 
That's a lot for a person in a 

341
00:16:13,000 --> 00:16:15,760
software package, meaning they 
have to program that in, They 

342
00:16:15,760 --> 00:16:17,840
have to get everything set up, 
they have to add in their own 

343
00:16:17,840 --> 00:16:19,560
levels. 
As the years have gone by, 

344
00:16:19,560 --> 00:16:22,320
algorithms have got better, 
systems have got better, and 

345
00:16:22,600 --> 00:16:24,800
discrete levels of effects have 
got better. 

346
00:16:24,840 --> 00:16:28,160
They've been able to do this to 
a much higher degree, which is 

347
00:16:28,160 --> 00:16:30,960
why you have your Atmos and you 
have all of your other things 

348
00:16:30,960 --> 00:16:32,840
that you can pipe into a set of 
headphones. 

349
00:16:33,080 --> 00:16:36,840
And for some people, they sound 
pretty much like 5.1. 

350
00:16:36,880 --> 00:16:38,920
I think it's a little bit more 
difficult than that. 

351
00:16:39,080 --> 00:16:42,320
I can usually tell what they're 
trying to do, but like if you 

352
00:16:42,320 --> 00:16:46,520
get a 5.12 to 5.1, so you're 
playing a game and you're you're

353
00:16:46,520 --> 00:16:49,000
playing on your headphones, I 
can usually tell if they're 

354
00:16:49,000 --> 00:16:52,560
trying to do a 7.1 audio and 
what happens is it just gets a 

355
00:16:52,560 --> 00:16:56,680
little bit muddied in the back. 
5.1 is fine or 4 is actually 

356
00:16:56,680 --> 00:16:59,080
pretty good that that actually 
works pretty well. 

357
00:16:59,080 --> 00:17:02,800
You can fake for quite well with
a little bit of delay if the 

358
00:17:02,800 --> 00:17:06,680
enemy is right or left and some 
processing effects that mimic 

359
00:17:06,800 --> 00:17:11,160
passing by the ear or being 
ultra clean, being in front of 

360
00:17:11,160 --> 00:17:14,560
you, right or left, you can end 
up faking it quite well. 

361
00:17:14,640 --> 00:17:16,680
So that's what you have. 
Those are the things you have. 

362
00:17:16,680 --> 00:17:20,359
Now, if you are talking about 
the other way around and you 

363
00:17:20,359 --> 00:17:25,520
have a stereo sound output for 
some reason and you go to a 5.1,

364
00:17:25,680 --> 00:17:28,400
that requires sort of a reversal
of those. 

365
00:17:28,440 --> 00:17:32,200
And honestly, what happens a lot
of times is it's pretty dirty. 

366
00:17:32,240 --> 00:17:36,000
A lot of the hardware that does 
that, it isn't really the 

367
00:17:36,000 --> 00:17:39,200
greatest. 
Luckily most games, most audio, 

368
00:17:39,200 --> 00:17:42,720
most everything is already 
decoded and encoded at much 

369
00:17:42,720 --> 00:17:45,200
higher channels than you'll 
probably have to your home, so 

370
00:17:45,200 --> 00:17:46,160
you don't have to worry about 
it. 

371
00:17:46,160 --> 00:17:48,880
In the past though, those would 
sound ultra shitty because they 

372
00:17:48,880 --> 00:17:52,520
usually would just slice up the 
different levels and layers and 

373
00:17:52,520 --> 00:17:54,160
sort of try to put them in 
different places. 

374
00:17:54,160 --> 00:17:57,240
So it sounded like it was wider 
on your home theater if you were

375
00:17:57,240 --> 00:18:01,440
using a 2.0 kind of source. 
But that's really not done 

376
00:18:01,440 --> 00:18:03,360
anymore. 
I can't think of any reason why 

377
00:18:03,360 --> 00:18:05,960
you would do that. 
Most systems these days, if 

378
00:18:05,960 --> 00:18:09,080
somehow you did have a stereo 
source, they're able to do it 

379
00:18:09,080 --> 00:18:11,120
via hardware. 
Add some effects. 

380
00:18:11,320 --> 00:18:14,240
Honestly, a lot of those effects
just end up being reverb and 

381
00:18:14,240 --> 00:18:18,520
echo, and they sort of muddy up 
the sound on purpose to to fool 

382
00:18:18,520 --> 00:18:20,480
the ear into thinking they're 
hearing different things. 

383
00:18:20,480 --> 00:18:23,200
That's why whenever you get an 
audiophile or somebody who takes

384
00:18:23,200 --> 00:18:26,040
audio super seriously, they'll 
get all mad whenever this kind 

385
00:18:26,040 --> 00:18:28,920
of stuff is done because they 
can usually tell. 

386
00:18:28,960 --> 00:18:30,760
Speaking of telling, I figure 
I'll tell some of you. 

387
00:18:30,760 --> 00:18:33,760
You may not have seen it, but I 
did a video today for a game 

388
00:18:33,760 --> 00:18:37,040
called The Lift, which weirdly 
enough, this is pretty rare. 

389
00:18:37,160 --> 00:18:39,680
They didn't really want anybody 
knowing the game existed 

390
00:18:39,680 --> 00:18:43,320
whatsoever until they did the 
previews, which I sort of dug 

391
00:18:43,320 --> 00:18:45,040
being a part of that. 
A lot of times when I do a 

392
00:18:45,120 --> 00:18:47,440
preview, there's already 
official trailers out, there's 

393
00:18:47,440 --> 00:18:49,360
already a bunch of discussion. 
This was one where they were 

394
00:18:49,360 --> 00:18:52,120
like, hey, we want everybody to 
be quiet about it so we can just

395
00:18:52,120 --> 00:18:55,000
show it all at one time. 
And it wasn't necessarily the 

396
00:18:55,000 --> 00:18:56,960
biggest game, but it was fun to 
be involved in that. 

397
00:18:57,040 --> 00:18:59,920
And so I got to check it out. 
You know, it's a weird game. 

398
00:18:59,920 --> 00:19:02,840
It's a little bit like a 
simulator mechanic simulator 

399
00:19:02,840 --> 00:19:05,960
title mixed with Control or 
Pacific Dr. You're on a space 

400
00:19:05,960 --> 00:19:08,600
station or a station of some 
kind, and you have to keep it 

401
00:19:08,600 --> 00:19:12,160
repaired or repair what's been 
broken so that this energy wave 

402
00:19:12,160 --> 00:19:14,160
continues to resonate out into 
the universe. 

403
00:19:14,160 --> 00:19:17,480
Now, that may sound some DMT 
shit, and it sort of was. 

404
00:19:17,480 --> 00:19:20,960
They even stated this story may 
not be exactly the way it's 

405
00:19:20,960 --> 00:19:22,800
going to end up rolling out 
because this game's not coming 

406
00:19:22,800 --> 00:19:26,920
out till 2026. 
Which again, shows how odd or at

407
00:19:26,920 --> 00:19:30,360
least unique for myself this 
particular situation was. 

408
00:19:30,360 --> 00:19:33,760
Because normally that actually 
wouldn't be the way it was. 

409
00:19:33,760 --> 00:19:35,240
It would be some trailers would 
come out. 

410
00:19:35,240 --> 00:19:37,440
They would solidify the story 
generally and be like here, 

411
00:19:37,440 --> 00:19:39,040
we're moving forward here. 
They're like, we just want 

412
00:19:39,040 --> 00:19:41,120
people to play it, see if they 
like it and we'll move from 

413
00:19:41,120 --> 00:19:42,400
here. 
And I did like it. 

414
00:19:42,400 --> 00:19:45,040
I was quite surprised. 
The story was interesting. 

415
00:19:45,120 --> 00:19:48,080
I actually thought it was it 
reminded me of something men a 

416
00:19:48,080 --> 00:19:52,480
little bit BBC, right, a little 
bit control, a little bit SCP. 

417
00:19:52,480 --> 00:19:55,720
So I wasn't quite sure there. 
Nothing super supernatural 

418
00:19:55,720 --> 00:19:59,200
happened when I played when it 
comes to directly to me, but I 

419
00:19:59,200 --> 00:20:02,480
did see some indicators of 
something very crazy going on on

420
00:20:02,480 --> 00:20:06,720
this station of some sorts. 
So what it is is it starts out, 

421
00:20:06,720 --> 00:20:09,680
and this is pretty eloquent. 
It starts out with a level of 

422
00:20:09,680 --> 00:20:13,080
puzzle work because it is a 
Vanishing of Ethan Carter style 

423
00:20:13,080 --> 00:20:15,040
puzzle walking simulator. 
Kind of. 

424
00:20:15,120 --> 00:20:17,400
Game at times and it starts out 
pretty lean. 

425
00:20:17,400 --> 00:20:20,520
It's like even opening the door 
in front of you requires like 

426
00:20:20,520 --> 00:20:24,240
pulling down a hatch number 
twist in a dial and then moving 

427
00:20:24,240 --> 00:20:26,400
your mouse to the left to open 
the door right so you get an 

428
00:20:26,400 --> 00:20:28,280
idea right away. 
OK, things are analog. 

429
00:20:28,400 --> 00:20:30,680
It's a really good setup 
actually, because it happens 

430
00:20:30,720 --> 00:20:32,680
right away you pick up on all 
right. 

431
00:20:32,800 --> 00:20:34,920
Well, if this is the way the 
door opens, I don't think 

432
00:20:34,920 --> 00:20:36,840
they're going to dumb everything
else down with an A button. 

433
00:20:37,040 --> 00:20:40,000
So you get out from there and 
you have your tools and you need

434
00:20:40,000 --> 00:20:42,960
to fix what's broken. 
Now fixing what's broken isn't 

435
00:20:42,960 --> 00:20:44,680
always the stuff you would 
expect. 

436
00:20:44,680 --> 00:20:46,720
This is I liked what they did 
here. 

437
00:20:46,880 --> 00:20:50,360
It's not just you know, putting 
in new wires for machines or 

438
00:20:50,360 --> 00:20:53,400
putting in new gears because 
those do happen the things that 

439
00:20:53,400 --> 00:20:57,240
you would expect do, but it's 
also tiny stuff like you're not 

440
00:20:57,240 --> 00:21:00,520
only picking up trash around the
game world that looks almost 

441
00:21:00,520 --> 00:21:03,600
multi dimensional has almost 
like 2 models flitting between 

442
00:21:03,600 --> 00:21:06,320
dimensions when you pick up some
of these items, but when you 

443
00:21:06,320 --> 00:21:09,480
smash them up when you destroy 
them, you get coins, which then 

444
00:21:09,640 --> 00:21:12,320
sells you items that you use to 
repair. 

445
00:21:12,320 --> 00:21:15,840
So for example, a light bulb or 
a screw, and when a light bulb 

446
00:21:15,840 --> 00:21:18,440
is shorted out, you put the 
light bulb in, that adds a 

447
00:21:18,440 --> 00:21:21,480
little bit more energy to the 
wave that's going out. 

448
00:21:21,520 --> 00:21:24,640
And the more you add, the more 
your chances of going to the 

449
00:21:24,640 --> 00:21:27,200
next open spot. 
You sort of, it's, it almost 

450
00:21:27,200 --> 00:21:30,560
felt psychic to me or something 
like that, or I couldn't quite 

451
00:21:30,560 --> 00:21:32,520
tell. 
Like some kind of bureaucracy 

452
00:21:32,520 --> 00:21:34,880
behind the scenes of the 
universe that you were working 

453
00:21:34,880 --> 00:21:36,240
for. 
And I liked that there was a 

454
00:21:36,240 --> 00:21:37,600
mystery there. 
I didn't quite know what was 

455
00:21:37,600 --> 00:21:39,720
going on. 
But I'm walking around replacing

456
00:21:39,720 --> 00:21:43,160
lights, I'm buying stuff, I'm 
looking and I start to notice 

457
00:21:43,160 --> 00:21:45,520
just how eloquent the puzzles 
actually actually were. 

458
00:21:45,680 --> 00:21:48,360
So that first puzzle, it showed 
you 3 or 4 moves. 

459
00:21:48,360 --> 00:21:51,280
Then the next puzzle shows you 
two or three other interactions.

460
00:21:51,440 --> 00:21:53,880
And as you go through the 1st 
area, there's a bit of 

461
00:21:53,880 --> 00:21:55,680
repetition for maybe one or two 
puzzles. 

462
00:21:55,680 --> 00:21:57,880
So you go here, you're like, I 
know what to do, Boom, boom, 

463
00:21:57,880 --> 00:21:59,760
boom. 
You fix that and then you close 

464
00:21:59,760 --> 00:22:02,040
up the panel and you move on. 
And you don't have to close the 

465
00:22:02,040 --> 00:22:03,840
panel, you just find yourself 
doing it. 

466
00:22:03,840 --> 00:22:06,720
Because quite quickly you do 
start to feel like a maintenance

467
00:22:06,720 --> 00:22:09,720
man because you have this little
side game of picking up just the

468
00:22:09,720 --> 00:22:12,840
occasional bits of trash to get 
the money to then repair some of

469
00:22:12,840 --> 00:22:16,080
the easier items. 
Which then causes you to feel 

470
00:22:16,080 --> 00:22:20,200
that when you're repairing a big
panel and it at the time you're 

471
00:22:20,200 --> 00:22:23,080
done, you have the ability to 
like pick up the junk and close 

472
00:22:23,080 --> 00:22:25,160
the panel and sort of, you know,
lock it. 

473
00:22:25,160 --> 00:22:27,200
And I dug that. 
It was actually pretty cool. 

474
00:22:27,320 --> 00:22:30,800
And as the game continued, those
puzzles got more complex. 

475
00:22:30,800 --> 00:22:33,880
There was a sophistication to 
them that was quite surprising, 

476
00:22:33,880 --> 00:22:37,560
not in their difficulty, but 
just in the different 

477
00:22:37,560 --> 00:22:39,480
interactions more and more of 
them. 

478
00:22:39,480 --> 00:22:42,880
And each time that I went to 
sort of a new section, there was

479
00:22:42,880 --> 00:22:47,160
a bit more of AI would say a 
complexity to the steps that I 

480
00:22:47,160 --> 00:22:49,720
would have to take that I 
already knew from the prior ones

481
00:22:49,880 --> 00:22:52,320
and would have to possibly turn 
on their head a little bit. 

482
00:22:52,400 --> 00:22:55,720
But what I liked here is they 
also threw a couple surprises 

483
00:22:55,720 --> 00:22:57,000
in. 
For example, there are these 

484
00:22:57,000 --> 00:23:00,200
temporary ladders, which I don't
think I've remember a temporary 

485
00:23:00,200 --> 00:23:02,200
ladder in a game. 
If you've seen them, I would 

486
00:23:02,200 --> 00:23:04,920
love for you to pipe off in the 
comments on Spotify or iTunes. 

487
00:23:05,360 --> 00:23:08,800
What game has had this? 
But this has this bow covered 

488
00:23:08,960 --> 00:23:11,640
secrets. 
I guess you'd call it a suitcase

489
00:23:11,640 --> 00:23:13,960
or briefcase with a temporary 
ladder in it. 

490
00:23:13,960 --> 00:23:16,320
I don't know why the little hair
bows on there, but whatever. 

491
00:23:16,720 --> 00:23:19,200
That was even a mystery. 
You get this thing and you 

492
00:23:19,200 --> 00:23:22,200
notice when you're playing the 
game, and especially in a lot of

493
00:23:22,200 --> 00:23:24,360
games like this, we have a 
tendency to sort of look 

494
00:23:24,360 --> 00:23:26,120
straight on, right? 
You're looking at the horizon, 

495
00:23:26,120 --> 00:23:29,040
you're walking and you've sort 
of got your your mouse cursor 

496
00:23:29,040 --> 00:23:31,480
leveled off. 
Well, in this game, I randomly 

497
00:23:31,480 --> 00:23:35,360
looked up and saw that there was
a air duct that was way above 

498
00:23:35,680 --> 00:23:38,400
really out of normal sight. 
And I was like, oh, what the 

499
00:23:38,400 --> 00:23:40,680
hell? 
OK, I can use the ladder to get 

500
00:23:40,680 --> 00:23:42,200
up there. 
And I got the ladder, went up 

501
00:23:42,200 --> 00:23:44,720
there and found some other stuff
and sort of started to realize 

502
00:23:44,880 --> 00:23:47,840
how these ladders, because 
they're temporary, they can 

503
00:23:47,840 --> 00:23:49,720
change how you do some things in
the game. 

504
00:23:49,720 --> 00:23:53,120
Now, it's not at this point 
breaking anything because the 

505
00:23:53,120 --> 00:23:56,080
game only had about 3 hours that
we could play, but I could see 

506
00:23:56,080 --> 00:23:59,120
if that's their first step. 
With those ladders, you could do

507
00:23:59,120 --> 00:24:02,480
some pretty impressive stuff 
because for example, if you put 

508
00:24:02,480 --> 00:24:05,480
the ladder down, you climb up 
into a duck, you can't shrink up

509
00:24:05,480 --> 00:24:07,680
the ladder and grab it from the 
floor because the ladder comes 

510
00:24:07,680 --> 00:24:09,280
down and fits back into the 
suitcase. 

511
00:24:09,280 --> 00:24:12,200
So I'm like, OK, so I can't, 
let's say grab this ladder and 

512
00:24:12,200 --> 00:24:14,280
go to another area. 
So is that going to require me 

513
00:24:14,280 --> 00:24:16,160
to have two of them? 
Because in one of the areas 

514
00:24:16,160 --> 00:24:17,880
there were two temporary 
ladders. 

515
00:24:18,040 --> 00:24:19,720
So I was like, that's some 
puzzle work that could be 

516
00:24:19,720 --> 00:24:21,800
awesome. 
And then as you do those, you 

517
00:24:21,800 --> 00:24:24,920
figure out, oh, I put this down.
I go up and there's a light bulb

518
00:24:24,920 --> 00:24:27,000
in one of the tunnels that needs
to be replaced. 

519
00:24:27,000 --> 00:24:28,960
And I had broken light bulbs 
only. 

520
00:24:28,960 --> 00:24:32,560
So then I went, I crushed those.
I got money, bought a good one, 

521
00:24:32,680 --> 00:24:34,760
went back. 
And what I even liked about this

522
00:24:34,760 --> 00:24:37,640
is you couldn't even buy one 
until you repaired the vending 

523
00:24:37,640 --> 00:24:40,480
machine that dropped them. 
And it wasn't a super long 

524
00:24:40,480 --> 00:24:42,000
repair. 
It wasn't difficult at all. 

525
00:24:42,000 --> 00:24:44,800
It gave you a little rule, a 
little idea of what you needed 

526
00:24:44,800 --> 00:24:46,800
to do. 
I also love the idea that when 

527
00:24:46,800 --> 00:24:50,400
you open the panel at the first 
time, like any electrical panel,

528
00:24:50,400 --> 00:24:53,520
any good panel made by a quality
manufacturer, you look at the 

529
00:24:53,520 --> 00:24:55,320
right on the inside of the panel
and it gives you the 

530
00:24:55,320 --> 00:24:57,200
instructions right, or it gives 
you a blueprint. 

531
00:24:57,280 --> 00:24:59,840
This did the same thing. 
So as somebody who's done the 

532
00:24:59,840 --> 00:25:03,320
occasional wiring job in a home,
it was nice to open up a panel 

533
00:25:03,320 --> 00:25:05,360
and look to the right and go, 
OK, all right, that's what I 

534
00:25:05,360 --> 00:25:06,920
need. 
And then it goes sort of crazy. 

535
00:25:06,920 --> 00:25:09,640
I mean, one generator I turned 
on looked like it was straight 

536
00:25:09,640 --> 00:25:13,880
from Firefly, the TV show with a
generator that spins super fast 

537
00:25:13,880 --> 00:25:15,840
on a giant piston, the entire 
entire body of it. 

538
00:25:15,920 --> 00:25:20,720
But it was driven by a basically
a fusion running bumblebee. 

539
00:25:20,880 --> 00:25:22,000
That's the only way I can 
describe it. 

540
00:25:22,000 --> 00:25:23,440
That's what they even described 
it as. 

541
00:25:23,640 --> 00:25:26,240
So you get this energy device 
that's in the shape of a 

542
00:25:26,240 --> 00:25:27,760
bumblebee and you put it in 
there. 

543
00:25:27,760 --> 00:25:30,240
And then that bumblebee also in 
a different device does 

544
00:25:30,240 --> 00:25:32,680
something different. 
And so as you're playing, there 

545
00:25:32,840 --> 00:25:35,520
were these levels of complexity 
that were just barely added to 

546
00:25:35,520 --> 00:25:38,200
each puzzle, which I genuinely, 
genuinely enjoyed. 

547
00:25:38,360 --> 00:25:41,200
And then at the same time, as I 
continue to move around, there 

548
00:25:41,200 --> 00:25:44,520
is more eclectic pieces such as 
the bumblebee that I was like, 

549
00:25:44,520 --> 00:25:46,680
OK, it's it's usable here, It's 
usable there. 

550
00:25:46,800 --> 00:25:49,440
What else could it be used for? 
You know, are there? 

551
00:25:49,800 --> 00:25:52,680
It looked like it might be able 
to be screwed into things. 

552
00:25:52,680 --> 00:25:54,960
So it's like, is there going to 
be a puzzle in the future where 

553
00:25:54,960 --> 00:25:57,400
if I don't have a light bulb, I 
can use this as a temporary 

554
00:25:57,400 --> 00:26:00,240
light bulb? 
Or could I augment the wave by 

555
00:26:00,240 --> 00:26:03,280
screwing 1 into the lighting 
system and powering up the wave 

556
00:26:03,280 --> 00:26:05,680
even more and maybe don't need 
to do everything in the game 

557
00:26:05,680 --> 00:26:07,680
world? 
And then as I was doing that, I 

558
00:26:07,680 --> 00:26:09,200
started to notice there were 
these chairs. 

559
00:26:09,200 --> 00:26:10,840
There were different items that 
were busted. 

560
00:26:10,880 --> 00:26:13,320
And as you repair them, even 
that fixes the wave. 

561
00:26:13,320 --> 00:26:15,680
So that's why I said it was sort
of psychic because you're sort 

562
00:26:15,680 --> 00:26:18,040
of fixing everything. 
You're bringing it back to a 

563
00:26:18,240 --> 00:26:23,440
workable, I guess you would say 
psychically correct status. 

564
00:26:23,440 --> 00:26:24,880
That's sort of what I got from 
this. 

565
00:26:25,000 --> 00:26:26,920
A little bit spiritual there, 
but that's the way it was. 

566
00:26:27,120 --> 00:26:30,360
So I came up to these, these 
benches, I put the wood back in 

567
00:26:30,360 --> 00:26:32,440
the benches, I tightened up the 
benches. 

568
00:26:32,640 --> 00:26:35,600
And I love the dichotomy there. 
There was this difference of the

569
00:26:35,600 --> 00:26:38,440
mundane, which is your benches, 
your chairs, the little things 

570
00:26:38,440 --> 00:26:41,560
you're fixing the lights. 
And then one step above that was

571
00:26:41,560 --> 00:26:44,520
the puzzles and the complexity 
of them and what I needed to do.

572
00:26:44,520 --> 00:26:47,520
And one or two places had some 
pretty arbitrary rules. 

573
00:26:47,520 --> 00:26:49,800
And I really like that. 
I was looking at this one puzzle

574
00:26:49,800 --> 00:26:52,920
panel and it had a slider, it 
had some numbers, it had some, 

575
00:26:53,480 --> 00:26:55,640
some dotted lights that you have
to hit. 

576
00:26:55,640 --> 00:26:57,800
And I was like, oh shit, man, 
this seems like it might be 

577
00:26:57,800 --> 00:27:00,840
above me. 
And yet because of the puzzles I

578
00:27:00,840 --> 00:27:04,920
had done prior, it it's, it's 
very hard to describe, but you 

579
00:27:04,920 --> 00:27:08,320
don't always do the exact thing 
from a puzzle prior that you've 

580
00:27:08,320 --> 00:27:10,800
learned. 
Sometimes it's the actual just 

581
00:27:10,800 --> 00:27:15,760
over overall steps or the idea 
of twisting something in sort of

582
00:27:15,760 --> 00:27:19,720
the same way or the idea of 
sliding A positional switch to a

583
00:27:19,720 --> 00:27:21,200
certain degree. 
Let me give you an example. 

584
00:27:21,200 --> 00:27:23,400
There's the generator and it's 
you got to get that thing 

585
00:27:23,400 --> 00:27:25,640
spinning right? 
So, but it's not just that it 

586
00:27:25,640 --> 00:27:26,960
would never be just that in this
game. 

587
00:27:27,040 --> 00:27:29,400
So you take that bumblebee, you 
put it in there, then you have 

588
00:27:29,400 --> 00:27:31,560
to close the door correctly. 
Then you have to go over and you

589
00:27:31,560 --> 00:27:33,680
have to do the switches in the 
proper order. 

590
00:27:33,800 --> 00:27:36,360
And as I was doing this and I 
was doing the switches, I was 

591
00:27:36,360 --> 00:27:39,200
like, OK, I got to remember 
that, you know, it's telling me 

592
00:27:39,200 --> 00:27:41,800
these switches are they're 
pretty easy on this particular 

593
00:27:41,960 --> 00:27:43,640
system. 
But I was like, I already have a

594
00:27:43,640 --> 00:27:45,880
feeling some switches are going 
to be have to have done in 

595
00:27:45,880 --> 00:27:47,480
different order in different 
areas. 

596
00:27:47,640 --> 00:27:50,960
But as I did it, when I turned 
it on, you had to actually turn 

597
00:27:50,960 --> 00:27:56,560
it on and move this large lever 
at a particular angle to get it 

598
00:27:56,560 --> 00:28:00,960
to get into the green section of
the pressure valve before the 

599
00:28:00,960 --> 00:28:03,200
engine would start. 
So couple mistakes here. 

600
00:28:03,200 --> 00:28:05,720
There finally got that working. 
And then when I went back to 

601
00:28:05,720 --> 00:28:08,840
that puzzle I had seen earlier, 
I looked and I saw another 

602
00:28:08,840 --> 00:28:10,920
slider and I was like, oh, OK, I
see. 

603
00:28:10,920 --> 00:28:13,880
So now I need to sort of take 
what I learned and maybe I won't

604
00:28:13,880 --> 00:28:16,720
have this green pressure, but 
maybe I still need, I need to 

605
00:28:16,720 --> 00:28:19,240
listen maybe this time or I need
to look out the window while I'm

606
00:28:19,240 --> 00:28:20,720
doing it. 
And I really enjoyed that. 

607
00:28:20,800 --> 00:28:23,880
It also performed well. 
Voice was good, music was good. 

608
00:28:24,360 --> 00:28:27,320
It was actually quite impressive
for a preview to hear that that 

609
00:28:27,320 --> 00:28:30,480
thing's coming out in 2026, at 
least right now. 

610
00:28:30,640 --> 00:28:34,560
I'm sort of profoundly surprised
how well it ran and what I 

611
00:28:34,560 --> 00:28:37,440
experienced. 
I'm a big fan of your Pacific 

612
00:28:37,440 --> 00:28:39,840
drives. 
I'm a big fan of games like 

613
00:28:39,840 --> 00:28:42,960
Vanishing of Ethan Carter. 
So this speaks to me. 

614
00:28:42,960 --> 00:28:46,520
It may not speak to you, but 
there was some more supernatural

615
00:28:46,520 --> 00:28:48,720
stuff that popped up. 
I was going through the levels 

616
00:28:48,720 --> 00:28:52,080
and at a later point in the game
you end up finding some enemies 

617
00:28:52,080 --> 00:28:54,920
that are basically covered in 
this goo and they're frozen in 

618
00:28:54,920 --> 00:28:57,200
place and you have a gun that 
removes the goo. 

619
00:28:57,200 --> 00:28:58,440
I couldn't remove it from the 
guy. 

620
00:28:58,440 --> 00:29:01,880
I don't know if I was doing it 
wrong or I just, it was right at

621
00:29:01,880 --> 00:29:04,400
the end of the demo, so it could
have just been me, but I was 

622
00:29:04,400 --> 00:29:07,200
removing it from the game world 
to get access to more doors and 

623
00:29:07,200 --> 00:29:08,680
stuff. 
But they were frozen in place 

624
00:29:08,680 --> 00:29:10,520
and they certainly didn't look 
happy about it. 

625
00:29:10,520 --> 00:29:13,440
There's a part in the video that
I said this particular thing 

626
00:29:13,440 --> 00:29:16,120
scared the crap out of me. 
There is one part where I came 

627
00:29:16,120 --> 00:29:19,280
up, I was fiddling at a desk, 
just thinking nothing was going 

628
00:29:19,280 --> 00:29:20,560
on. 
I turned to the left and there's

629
00:29:20,560 --> 00:29:22,320
a guy there who looks like he's 
screaming. 

630
00:29:22,320 --> 00:29:24,840
He's frozen in place like 
Pompeii, you know, somebody 

631
00:29:24,840 --> 00:29:27,880
frozen in the lava. 
And that actually impressed the 

632
00:29:27,880 --> 00:29:29,640
hell out of me. 
It caused me to go like, whoa, 

633
00:29:29,640 --> 00:29:32,000
what the hell was that? 
And you know what's going on 

634
00:29:32,000 --> 00:29:33,280
here? 
And I liked it. 

635
00:29:33,360 --> 00:29:37,120
So hopefully this thing turns 
out to be enjoyable, at least to

636
00:29:37,120 --> 00:29:38,880
the people who like these kind 
of games like I do. 

637
00:29:39,000 --> 00:29:41,480
I just have to swing back to 
this because I just got a news 

638
00:29:41,480 --> 00:29:43,680
alert that somebody posted 
something while I was talking. 

639
00:29:43,680 --> 00:29:48,680
So I decided, oh, you know, I'll
and now a completely different 

640
00:29:48,680 --> 00:29:51,920
website, games Radar plus, 
states this about Battlefield 6.

641
00:29:51,920 --> 00:29:55,720
This is their headline. 
Battlefield 6 nearly broke the 

642
00:29:55,720 --> 00:30:00,960
Xbox Series S that my friends 
wow wow man, we are so over the 

643
00:30:00,960 --> 00:30:03,720
top now with titles that that 
shit is nuts. 

644
00:30:03,920 --> 00:30:06,360
It is just going to continually 
change until at some point 

645
00:30:06,360 --> 00:30:08,880
they're going to be like, the 
only way that they were able to 

646
00:30:08,880 --> 00:30:12,240
get it running was by throwing a
small child into the sun three 

647
00:30:12,240 --> 00:30:15,720
times every single Saturday and 
it was just barely there. 

648
00:30:15,720 --> 00:30:19,040
Thank God for the devs who gave 
up their children to get this 

649
00:30:19,040 --> 00:30:22,280
game running on the Series S. 
But moving back to good stuff. 

650
00:30:22,280 --> 00:30:24,720
One thing I have to bring up, I 
got some PR on it yesterday. 

651
00:30:24,720 --> 00:30:27,240
Super excited. 
Twilight Imperium is coming to 

652
00:30:27,360 --> 00:30:30,120
PC now. 
Twilight Imperium is notorious. 

653
00:30:30,120 --> 00:30:31,160
You guys have heard me talk 
about it. 

654
00:30:31,160 --> 00:30:33,840
If you watch the podcast is 
notorious for having a many hour

655
00:30:33,840 --> 00:30:37,680
setup for being a game that you 
could easily put on 3-4 or five 

656
00:30:37,680 --> 00:30:39,680
tables if you have all the 
expansions. 

657
00:30:39,680 --> 00:30:42,680
Yes, it is that big, especially 
when you add in everybody 

658
00:30:42,680 --> 00:30:44,840
setting up the way they want to 
set up to play. 

659
00:30:45,120 --> 00:30:48,880
This game is a monster and you 
know adding it to PC. 

660
00:30:49,280 --> 00:30:51,280
I'm going to say this super 
excited. 

661
00:30:51,400 --> 00:30:53,480
Pretty goddamn disappointed. 
Let me describe this. 

662
00:30:53,640 --> 00:30:54,760
Super excited. 
It's coming. 

663
00:30:54,760 --> 00:30:56,280
I think that's awesome. 
I can't wait. 

664
00:30:56,440 --> 00:30:59,360
I'm looking at what they're 
doing with the game and the idea

665
00:30:59,360 --> 00:31:01,760
that I could possibly have a 
couple of my friends sit down to

666
00:31:01,760 --> 00:31:03,280
play. 
That would be great. 

667
00:31:03,440 --> 00:31:06,080
I don't know if they're speeding
up the gameplay because the 

668
00:31:06,080 --> 00:31:09,480
gameplay itself isn't like 
taking a great deal of time for 

669
00:31:09,480 --> 00:31:11,880
any other reason that people 
take a great deal of time 

670
00:31:11,880 --> 00:31:13,720
playing it. 
So I don't necessarily know as 

671
00:31:13,720 --> 00:31:16,280
if this game is going to 
alleviate the marathon. 

672
00:31:16,280 --> 00:31:20,560
Like just sessions of shit that 
you experience with Twilight 

673
00:31:20,560 --> 00:31:23,440
Imperium. 
I have seen people age while 

674
00:31:23,440 --> 00:31:27,440
playing that game at my house. 
Like it is abso fucking lutely 

675
00:31:27,440 --> 00:31:29,480
crazy. 
It is such a good game though. 

676
00:31:29,720 --> 00:31:33,200
Basically imagine this Stellaris
but a board game that you can 

677
00:31:33,200 --> 00:31:36,680
understand version of it. 
It's not as messy as Stellaris, 

678
00:31:36,680 --> 00:31:39,600
but it is definitely in that 
style, the 4X style. 

679
00:31:39,760 --> 00:31:44,040
It is just awesome. 
However, Ultra disappointed in 

680
00:31:44,040 --> 00:31:48,000
one thing Ultra and I prob I get
it, but I'm just going to say 

681
00:31:48,200 --> 00:31:51,560
after all this time finally 
getting this and seeing that 

682
00:31:51,560 --> 00:31:54,040
this is what's going to happen, 
it just disappoints me. 

683
00:31:54,200 --> 00:31:59,960
Graphically it's barely OK. 
And they decided for reasons I 

684
00:31:59,960 --> 00:32:05,080
can't quite imagine that all of 
the different ships are 

685
00:32:05,080 --> 00:32:08,040
color-coded to the characters 
just like they are in the board 

686
00:32:08,040 --> 00:32:09,600
game. 
And a lot of people who play the

687
00:32:09,600 --> 00:32:13,000
board game switch out those four
other ships from other games or 

688
00:32:13,000 --> 00:32:15,440
they paint them themselves 
because they're just red, 

689
00:32:15,440 --> 00:32:20,120
yellow, blue, Gray, black, 
green, orange plastic, right? 

690
00:32:20,240 --> 00:32:23,040
Very basic plastic. 
And sadly, they've copied that 

691
00:32:23,040 --> 00:32:26,480
exact look into the game. 
And So what happens is I went 

692
00:32:26,480 --> 00:32:29,280
from being like, Oh my God, I 
see it, I see the board that 

693
00:32:29,400 --> 00:32:30,680
that looks great, that looks 
great. 

694
00:32:30,680 --> 00:32:33,240
What the frig? 
And I looked at these little 

695
00:32:33,240 --> 00:32:35,480
ships and I was like, no, you 
got to be kidding me. 

696
00:32:35,600 --> 00:32:37,960
So that actually does bother me 
a bit. 

697
00:32:38,160 --> 00:32:40,320
I'm just pointing it out. 
You know, it's, it's because 

698
00:32:40,320 --> 00:32:42,360
it's taken so long. 
It's because it's been so many 

699
00:32:42,360 --> 00:32:45,040
years. 
I just think that this is a time

700
00:32:45,120 --> 00:32:47,440
where that doesn't need to be 
mimicked exactly. 

701
00:32:47,440 --> 00:32:51,240
Listen, if you're moving from a 
board game to a video game and 

702
00:32:51,240 --> 00:32:54,680
for some reason graphically 
there is a requirement for you 

703
00:32:54,680 --> 00:32:57,120
to continue in that old style, 
that's fine. 

704
00:32:57,240 --> 00:33:00,440
But in a game like this, there 
isn't a reason to none at all. 

705
00:33:00,520 --> 00:33:03,280
Would I like to have also seen 
some space battles where it 

706
00:33:03,280 --> 00:33:06,400
shows like a sort of a 3D, like 
maybe endless space kind of 

707
00:33:06,400 --> 00:33:07,760
thing with space battles? 
Yeah. 

708
00:33:07,960 --> 00:33:10,000
But I'm actually OK with that 
not being in there. 

709
00:33:10,000 --> 00:33:13,600
And it's not what I really wish 
was in there is just a tighter 

710
00:33:13,600 --> 00:33:17,720
control on the overall for all 
presentation to celebrate that 

711
00:33:17,720 --> 00:33:20,360
it's on a video game to 
celebrate and say, hey, listen, 

712
00:33:20,520 --> 00:33:22,960
you know, we're on a video game 
for we're a video game for a 

713
00:33:22,960 --> 00:33:24,560
reason. 
So we're going to sort of make 

714
00:33:24,560 --> 00:33:28,720
sure that in many ways you get 
to see that you get to see how 

715
00:33:28,720 --> 00:33:32,040
long it's been and a reward for 
how long people have waited to 

716
00:33:32,040 --> 00:33:34,000
get this game. 
Because if it was me, that would

717
00:33:34,000 --> 00:33:37,080
have been honestly, one of the 
very first things I did was I 

718
00:33:37,080 --> 00:33:39,600
would be adjusting those ships 
to make them look a particular 

719
00:33:39,600 --> 00:33:43,360
way so that that, you know, they
were they, they just looked more

720
00:33:43,360 --> 00:33:46,960
gamey than board gamey. 
Now that might change, but the 

721
00:33:46,960 --> 00:33:48,800
trailer I saw, that's the way 
they looked. 

722
00:33:48,960 --> 00:33:51,760
I'm also assuming a game like 
this is going to probably end up

723
00:33:51,760 --> 00:33:55,640
spinning around into the Games 
Workshop on Steam in a very 

724
00:33:55,640 --> 00:33:58,920
short amount of time. 
So I think overall pretty good 

725
00:33:58,920 --> 00:34:02,400
chance of either, you know, 
somebody changing it or now 

726
00:34:02,400 --> 00:34:06,560
these days with AI, somebody 
figuring out an easy program to,

727
00:34:06,600 --> 00:34:08,639
you know, switch out some 
textures here or there and get 

728
00:34:08,639 --> 00:34:11,080
those running. 
So not as worried as, you know, 

729
00:34:11,080 --> 00:34:14,360
I would be in the past, but like
I said, just a little bit sad. 

730
00:34:14,360 --> 00:34:17,080
Little bit sad because I feel 
like, hey, we're finally here. 

731
00:34:17,239 --> 00:34:19,280
This is great. 
Oh my God, why does it look like

732
00:34:19,280 --> 00:34:22,560
this? 
Let's see, Mark Ception, Mark 

733
00:34:22,719 --> 00:34:25,719
Marks, Markaton, Markaton. 
Sorry, I've read that while I 

734
00:34:25,719 --> 00:34:29,840
was leaning back, he asks where 
do I think DLSS or those kind of

735
00:34:29,840 --> 00:34:34,320
systems will go in the future? 
So I'll say this, I think we're 

736
00:34:34,320 --> 00:34:37,520
pretty close to at the end of 
your improvements. 

737
00:34:37,960 --> 00:34:40,600
OK, so if you consider 
improvements as a bell curve, 

738
00:34:40,600 --> 00:34:43,000
think about it like this. 
The very first point of that 

739
00:34:43,000 --> 00:34:46,800
bell curve is stunning and 
surprising and ultimately, 

740
00:34:46,800 --> 00:34:50,560
because we know it's the start 
of something disappointing at 

741
00:34:50,560 --> 00:34:52,600
times, that's FSR and DLSS one, 
right? 

742
00:34:52,760 --> 00:34:55,960
You get it, you see it and you 
see you can see that ramp up. 

743
00:34:55,960 --> 00:34:57,440
You can see the bell curve in 
front of you. 

744
00:34:57,440 --> 00:34:59,840
You see it, you're like looking 
at it going this thing's going 

745
00:34:59,840 --> 00:35:01,800
to get great, but it's not there
yet, right? 

746
00:35:01,960 --> 00:35:05,880
That's how DLSSFSR ones. 
That's how those appeared to us 

747
00:35:06,080 --> 00:35:09,160
and we saw what they could do. 
But at the time you don't want 

748
00:35:09,160 --> 00:35:11,560
to get on that ride, right? 
It's almost like you go to a 

749
00:35:11,560 --> 00:35:13,200
fair. 
There's a couple rides there, 

750
00:35:13,280 --> 00:35:16,280
but you see that one ride with 
the vinyl hanging out in the 

751
00:35:16,280 --> 00:35:18,960
corner smoking a Camel 
unfiltered with The Dirty pants 

752
00:35:18,960 --> 00:35:22,000
and a little bit of blood on a 
shirt and you're like that ride 

753
00:35:22,200 --> 00:35:24,160
I don't need to go on. 
That was DLSS one. 

754
00:35:24,600 --> 00:35:27,760
Now you start to get that climb 
up, you start to see two and 

755
00:35:27,760 --> 00:35:29,840
three and you start to see the 
improvements where you're 

756
00:35:29,840 --> 00:35:33,360
getting that bell curve. 
Each point is getting farther 

757
00:35:33,360 --> 00:35:36,240
and farther away from the bottom
line and you're seeing those 

758
00:35:36,240 --> 00:35:38,640
improvements. 
However, with DLSS in 

759
00:35:38,640 --> 00:35:42,640
particular, what we are actually
getting to is the very typical 

760
00:35:42,640 --> 00:35:46,320
tip or even possibly slide down 
when you start looking at 

761
00:35:46,320 --> 00:35:49,040
improvements, meaning you're not
going to see double or triple 

762
00:35:49,040 --> 00:35:52,080
unless you use frame gens. 
And that is beside the point 

763
00:35:52,080 --> 00:35:53,520
here. 
For example, the frame Gen. 

764
00:35:53,520 --> 00:35:56,080
thing is really a different 
situation than what we're 

765
00:35:56,080 --> 00:35:58,040
talking about, which is standard
DLSS. 

766
00:35:58,040 --> 00:36:01,600
So what you have is the ability 
to improve your color sampling. 

767
00:36:01,720 --> 00:36:05,440
You have the ability to improve 
your overall image quality. 

768
00:36:05,600 --> 00:36:08,360
However, we are at a point to 
where a lot of that is going to 

769
00:36:08,360 --> 00:36:11,800
be very, very difficult and 
require a great deal more power 

770
00:36:11,920 --> 00:36:14,560
to even get small improvements 
because what you're really doing

771
00:36:14,560 --> 00:36:16,960
is trying to get, that's what's 
behind a hair strand on 

772
00:36:16,960 --> 00:36:19,480
somebody's head. 
When you start to see the little

773
00:36:19,480 --> 00:36:22,480
shimmering around, let's say 
character's hair in video games,

774
00:36:22,600 --> 00:36:24,280
that's quite difficult to do, 
right? 

775
00:36:24,400 --> 00:36:27,080
So what you'll do is you'll 
start to see people coming up 

776
00:36:27,080 --> 00:36:29,480
with more, better denoisers for 
the ray tracing. 

777
00:36:29,480 --> 00:36:30,440
That's what we're starting to 
see. 

778
00:36:30,440 --> 00:36:31,600
We're starting to see them 
branch out. 

779
00:36:31,600 --> 00:36:35,000
So DLSS isn't just one thing 
now, it's starting to be other 

780
00:36:35,000 --> 00:36:36,720
things. 
And then you get frame Gen. you 

781
00:36:36,720 --> 00:36:39,400
start add to it, especially as 
this goes down the slope, 

782
00:36:39,400 --> 00:36:42,040
meaning the improvements are 
less and less, but the power is 

783
00:36:42,040 --> 00:36:44,840
required to be more and more. 
You start to see a pullback. 

784
00:36:45,160 --> 00:36:48,040
That's where we really are with 
DLSS right now and what it's 

785
00:36:48,040 --> 00:36:50,520
trying to do with particular 
things right now. 

786
00:36:50,560 --> 00:36:55,480
However, I personally feel that 
there is a good deal of work 

787
00:36:55,480 --> 00:37:00,120
that we've seen and a good deal 
to suggest that what we may see 

788
00:37:00,120 --> 00:37:04,400
in the future are improvements 
of a DLSS style or a procedural 

789
00:37:04,400 --> 00:37:07,320
style that adjusts particular 
elements of games. 

790
00:37:07,480 --> 00:37:10,240
That isn't just the entire 
screen picture, right? 

791
00:37:10,240 --> 00:37:12,080
That isn't just the entire 
screen. 

792
00:37:12,280 --> 00:37:16,440
And I think that's actually a 
place that we've already seen it

793
00:37:16,440 --> 00:37:18,480
in games. 
Shadow resolution in your old 

794
00:37:18,480 --> 00:37:20,600
Skyrim ini, you could turn that 
up or down. 

795
00:37:20,600 --> 00:37:22,400
You could see the shadows look 
better, but you weren't 

796
00:37:22,400 --> 00:37:24,440
adjusting the resolution on the 
entire screen, right? 

797
00:37:24,720 --> 00:37:28,560
I think that's where you start 
to see DLSS and improvements 

798
00:37:28,560 --> 00:37:32,200
coming back, where as engines 
continue to advance, you start 

799
00:37:32,200 --> 00:37:33,840
to see some things being left 
behind. 

800
00:37:33,840 --> 00:37:36,920
And maybe you get NVIDIA going, 
oh, here's a place where we can 

801
00:37:36,920 --> 00:37:40,280
improve shadows now, or just 
shadows in a game if there's a 

802
00:37:40,280 --> 00:37:42,920
new technique in particular. 
But you also have ray tracing. 

803
00:37:43,120 --> 00:37:45,920
Ray tracing, there are so many 
companies is working on so many 

804
00:37:45,920 --> 00:37:48,360
fixes and ray tracing doesn't 
just mean one thing. 

805
00:37:48,360 --> 00:37:51,520
There are many ways in which 
people sort of clump the 

806
00:37:51,520 --> 00:37:56,000
technologies that handle ray 
tracing into a sort of the name.

807
00:37:56,200 --> 00:37:59,280
And it can be, you know, super 
low sample ray tracing or 

808
00:37:59,280 --> 00:38:01,720
incredibly high path ray 
tracing. 

809
00:38:01,880 --> 00:38:04,880
And I think that that's where 
you see, I guess you would call 

810
00:38:04,880 --> 00:38:08,560
it a new DLSS coming up. 
They may not call it a new DLSS 

811
00:38:08,560 --> 00:38:09,800
at all. 
It may just be in the normal 

812
00:38:09,800 --> 00:38:12,640
package, but what you'll see is 
no real improvements to the 

813
00:38:12,640 --> 00:38:16,040
image quality, but you will see 
improvements and optimizations 

814
00:38:16,040 --> 00:38:19,400
to the ray tracing guesses as 
you will sort of like what's 

815
00:38:19,400 --> 00:38:22,800
going on with your normal 
texture improvements, but you 

816
00:38:22,800 --> 00:38:27,160
know a guessing of where those 
rays are going or a denoiser. 

817
00:38:27,160 --> 00:38:30,640
A denoiser for for you guys to 
understand is if you have a low 

818
00:38:30,640 --> 00:38:33,400
sample ray trace, you might look
at a shadow control was 

819
00:38:33,400 --> 00:38:35,480
notorious for this. 
You would look at the corners 

820
00:38:35,480 --> 00:38:37,560
and shadows and you would see a 
dimpling effect. 

821
00:38:37,560 --> 00:38:41,520
You would actually see the 
samples and the noise in that 

822
00:38:41,520 --> 00:38:43,640
dark area. 
It would look dappled, almost 

823
00:38:43,640 --> 00:38:47,120
like it was raining shadows. 
And as they've improved that, 

824
00:38:47,240 --> 00:38:50,680
they've been able to remove it 
or sort of, I guess you would 

825
00:38:50,680 --> 00:38:54,120
say, spread it out to the point 
to where it's nowhere near as 

826
00:38:54,120 --> 00:38:55,720
noticeable as it was in the 
past. 

827
00:38:55,840 --> 00:38:57,840
The same thing can be done with 
ray tracing and all the other 

828
00:38:57,840 --> 00:38:59,400
stuff. 
So that's where I see those. 

829
00:38:59,600 --> 00:39:03,720
I think when it comes to ray 
tracing, DLSS, it's just one fix

830
00:39:03,720 --> 00:39:06,840
on a car's engine, right? 
It's your fuel injector now. 

831
00:39:06,840 --> 00:39:08,920
You have your turbos, you have 
your superchargers. 

832
00:39:08,920 --> 00:39:11,440
What else are they going to add?
They're going to Add all kinds 

833
00:39:11,440 --> 00:39:13,280
of stuff. 
You got nanite vegetation. 

834
00:39:13,480 --> 00:39:15,880
Other companies are doing the 
same thing, have the mini 

835
00:39:15,880 --> 00:39:18,880
Polygon detail or what is it 
detail, Polygon effect that 

836
00:39:18,880 --> 00:39:21,240
Shadows did, Assassin's Creed 
Shadows did. 

837
00:39:21,240 --> 00:39:24,280
For far off objects, you have 
sort of the cheating, which was,

838
00:39:24,280 --> 00:39:27,200
by the way, brilliant, sort of 
the cheating that Red Dead 2 did

839
00:39:27,200 --> 00:39:30,240
with far off objects that a lot 
of games didn't do exactly what 

840
00:39:30,240 --> 00:39:32,400
they did. 
You can go and watch some videos

841
00:39:32,400 --> 00:39:35,240
or read some of the developer 
papers on some of the stuff that

842
00:39:35,240 --> 00:39:37,360
they did. 
For far off items, you know, do 

843
00:39:37,360 --> 00:39:38,640
that. 
Does that kind of thing get 

844
00:39:38,640 --> 00:39:40,200
built in? 
Probably not. 

845
00:39:40,280 --> 00:39:44,440
But there are ways in which you 
can clean up the image some more

846
00:39:44,600 --> 00:39:47,680
and you can clean up the ray 
tracing and you can adjust, 

847
00:39:47,840 --> 00:39:51,360
especially compared to whatever 
we see in the future, because we

848
00:39:51,360 --> 00:39:53,080
will see more of this in the 
future. 

849
00:39:53,200 --> 00:39:56,480
We'll see adjustments being made
where your video game card 

850
00:39:56,480 --> 00:39:59,120
makers are going to look at that
and say can we improve that with

851
00:39:59,120 --> 00:40:00,480
our drivers? 
Can we improve that with 

852
00:40:00,480 --> 00:40:02,760
something we have? 
I will also say I couldn't be 

853
00:40:02,760 --> 00:40:04,800
happier. 
There's no equivalent to ray 

854
00:40:04,800 --> 00:40:07,680
tracing coming out for this 
cards that just came out with 

855
00:40:07,800 --> 00:40:10,640
the 50 series. 
And from what I'm understanding,

856
00:40:10,640 --> 00:40:12,720
it doesn't sound like the 60 
series are going to have it 

857
00:40:12,720 --> 00:40:14,200
either. 
And that's magnificent. 

858
00:40:14,320 --> 00:40:19,520
I think ray tracing was a big 
mistake because it was delivered

859
00:40:19,520 --> 00:40:22,360
way too early. 
And what that did was it not 

860
00:40:22,360 --> 00:40:25,160
only made people buy something 
and then not really get. 

861
00:40:25,440 --> 00:40:28,200
I would say much for what they 
bought except for a couple 

862
00:40:28,200 --> 00:40:32,200
games, but additionally what you
ended up getting was this sort 

863
00:40:32,200 --> 00:40:37,200
of janky half rhythm to a game 
generation where now you have 

864
00:40:37,200 --> 00:40:39,520
the occasional game going. 
If you don't have a ray tracing 

865
00:40:39,520 --> 00:40:41,120
card, you just can't even play 
the game. 

866
00:40:41,280 --> 00:40:44,040
Gamers are already trying to 
update all the other stuff, let 

867
00:40:44,040 --> 00:40:46,800
alone jump in, and now you've 
also left the consoles behind 

868
00:40:46,800 --> 00:40:48,120
because they're not doing ray 
tracing. 

869
00:40:48,240 --> 00:40:51,000
Now you could say the companies 
that maybe the consoles should 

870
00:40:51,000 --> 00:40:53,320
have known that ray tracing was 
coming 5-6 years ago and they 

871
00:40:53,320 --> 00:40:56,280
taped these new systems off. 
I don't believe that that, but I

872
00:40:56,280 --> 00:40:59,280
think when you look at it 
holistically, you sort of take a

873
00:40:59,280 --> 00:41:00,960
step back, you try to see the 
whole picture. 

874
00:41:01,040 --> 00:41:02,840
There's going to be 
improvements, but you know, it 

875
00:41:02,840 --> 00:41:06,640
won't really necessarily be 
around the DLSS that we know and

876
00:41:06,640 --> 00:41:08,160
love. 
That's just going to see 

877
00:41:08,160 --> 00:41:10,920
iterative improvements unless 
something comes along that's 

878
00:41:10,920 --> 00:41:13,680
just crazy. 
Now people say what about AI? 

879
00:41:13,880 --> 00:41:18,600
If AI comes along and we push 
that in a way to the MPU's, 

880
00:41:18,720 --> 00:41:21,320
that's fine, right? 
But you already are doing that 

881
00:41:21,320 --> 00:41:24,280
technically on the the video 
cards themselves. 

882
00:41:24,280 --> 00:41:26,960
This is already being done. 
So if you did move them to an 

883
00:41:26,960 --> 00:41:31,640
MPU, their MPU's and the way 
they handle things, they are not

884
00:41:31,640 --> 00:41:34,320
well supported even for large 
language models. 

885
00:41:34,480 --> 00:41:35,840
And that's the big thing right 
now. 

886
00:41:35,840 --> 00:41:38,600
Bigger than games or large or 
large language models have 

887
00:41:38,600 --> 00:41:41,680
exploded to the point to where 
they're they became a billion 

888
00:41:41,680 --> 00:41:45,160
dollar industry, one of the 
fastest industries ever in human

889
00:41:45,160 --> 00:41:48,040
history with its growth. 
So if they're not even handled 

890
00:41:48,040 --> 00:41:51,200
well there, I wouldn't expect 
them to be handled super well in

891
00:41:51,200 --> 00:41:53,120
game. 
I think in game they've got 

892
00:41:53,120 --> 00:41:54,800
their tensor cores. 
That kind of stuff works. 

893
00:41:54,800 --> 00:41:57,240
AMD's got their stuff, they're 
going to catch up and then by 

894
00:41:57,240 --> 00:42:00,200
then NVIDIA probably look at 
something else, right, NVIDIA? 

895
00:42:00,480 --> 00:42:02,440
We'll try to figure out if 
there's another way to do it. 

896
00:42:02,600 --> 00:42:05,480
And I think there's many ways in
which we already see a little 

897
00:42:05,480 --> 00:42:08,040
bit of a step. 
So a lot of us look at the, you 

898
00:42:08,040 --> 00:42:11,360
know, 16, you know, gigs of RAM 
on some of the new cards. 

899
00:42:11,360 --> 00:42:13,360
You see the smaller and you're 
like, oh, that's bad. 

900
00:42:13,440 --> 00:42:15,480
Oh no, we compress that, blah, 
blah, blah. 

901
00:42:15,640 --> 00:42:18,040
Listen, compression is actually 
phenomenal. 

902
00:42:18,160 --> 00:42:20,960
They sell it poorly and they do 
a poor job supporting it, and 

903
00:42:20,960 --> 00:42:23,480
they do a poor job explaining 
how it can work, and they do a 

904
00:42:23,480 --> 00:42:25,800
poor job well in fucking 
everything. 

905
00:42:25,880 --> 00:42:28,560
But when it comes down to a 
compression, good compression 

906
00:42:28,760 --> 00:42:32,240
can speed things up and it can 
also leave room for other, 

907
00:42:32,840 --> 00:42:36,160
particularly leave room for 
other things to be fit into the 

908
00:42:36,160 --> 00:42:38,360
memory. 
Other other other ways that you 

909
00:42:38,360 --> 00:42:41,120
want to use your game engine 
doesn't always have to be 

910
00:42:41,120 --> 00:42:43,560
textures, right? 
So what I would like to see is 

911
00:42:43,560 --> 00:42:46,280
them to take advantage of the 
compression, things like that. 

912
00:42:46,280 --> 00:42:49,680
Put more cores in video cards 
that handle compression in 

913
00:42:49,680 --> 00:42:51,400
different ways. 
I like the idea of that. 

914
00:42:51,400 --> 00:42:53,080
I have no issue with that 
whatsoever. 

915
00:42:53,080 --> 00:42:55,360
It's just that they've described
it in poor ways. 

916
00:42:55,440 --> 00:42:57,200
They're like, Oh yeah, you know,
this card, it does this 

917
00:42:57,200 --> 00:42:58,600
compression. 
That's how we get away with it. 

918
00:42:58,600 --> 00:43:00,480
It does, you know, texture 
improvements. 

919
00:43:00,480 --> 00:43:03,840
And that way you can use a lower
level card or a lower, lower 

920
00:43:03,840 --> 00:43:06,440
level texture and you're like, 
OK, I sort of get that. 

921
00:43:06,440 --> 00:43:09,520
But at the same time there, 
that's not necessarily lossless.

922
00:43:09,520 --> 00:43:11,200
It's not even close to lossless 
actually. 

923
00:43:11,320 --> 00:43:13,440
It's still, it's still an 
improvement. 

924
00:43:13,520 --> 00:43:16,560
But what they really need is 
like let's say Lods on far off 

925
00:43:16,560 --> 00:43:19,680
textures where the AI runs on 
those, right? 

926
00:43:19,800 --> 00:43:22,800
And then up close you have your 
textures that are all higher 

927
00:43:22,800 --> 00:43:24,360
definition. 
Now, we're already doing that in

928
00:43:24,360 --> 00:43:27,040
different ways elsewhere, but I 
would love to see NVIDIA and AMD

929
00:43:27,040 --> 00:43:29,840
support that heavier in their 
drivers and figure out ways in 

930
00:43:29,840 --> 00:43:31,560
which they can support it quite 
easily. 

931
00:43:31,560 --> 00:43:34,480
So a company can come in and 
say, I'm making this game and it

932
00:43:34,480 --> 00:43:35,960
really won't matter what engine 
you're on. 

933
00:43:36,120 --> 00:43:39,480
Now that hinges also to Windows.
Windows is making sure that 

934
00:43:39,480 --> 00:43:43,080
DirectX is supposed to be able 
to handle all of the upscaler 

935
00:43:43,080 --> 00:43:46,000
calls. 
So supposedly DirectX already 

936
00:43:46,000 --> 00:43:48,360
has some of this by the way, but
they're they're doing more 

937
00:43:48,360 --> 00:43:52,600
support, which is where if 
you're running your AMD upscaler

938
00:43:52,600 --> 00:43:56,400
or your NVIDIA upscaler, they'll
both do a Direct X call, which 

939
00:43:56,400 --> 00:43:58,760
will make it compatible no 
matter what. 

940
00:43:58,760 --> 00:44:01,080
And that's really where we are 
right now when it comes to 

941
00:44:01,080 --> 00:44:03,280
games. 
You know, if you hate DirectX, 

942
00:44:03,280 --> 00:44:05,160
that's fine, but that is where 
we are. 

943
00:44:05,280 --> 00:44:07,920
And the developers are, you 
know, coming to grips with that 

944
00:44:07,920 --> 00:44:09,680
as well. 
And I can see some big 

945
00:44:09,680 --> 00:44:12,040
improvements coming when those 
all, when those three come 

946
00:44:12,040 --> 00:44:14,360
together and they sort of get 
together and they meet up and 

947
00:44:14,360 --> 00:44:16,000
they're like, this is the way we
want to move forward. 

948
00:44:16,000 --> 00:44:19,960
I think Microsoft is doing that.
And I think obviously AMD and 

949
00:44:19,960 --> 00:44:23,320
Intel who released AI, guess 
it's a pretty good card for a 

950
00:44:23,320 --> 00:44:25,360
lower cost of what is it 369 
for? 

951
00:44:25,440 --> 00:44:28,200
There's 16 gig. 
So there are some cards coming 

952
00:44:28,200 --> 00:44:30,040
out that's going to drive the 
competition, which is also 

953
00:44:30,040 --> 00:44:31,320
great. 
You always want that kind of 

954
00:44:31,320 --> 00:44:33,400
thing. 
And Intel's upscaling not 

955
00:44:33,400 --> 00:44:35,320
horrible. 
So they need to do some 

956
00:44:35,320 --> 00:44:37,800
improvements to theirs. 
And remember, as they're doing 

957
00:44:37,800 --> 00:44:40,440
it, as the other companies do 
it, they start to branch out and

958
00:44:40,440 --> 00:44:43,080
you start to see everybody 
taking on the ideas of others. 

959
00:44:43,080 --> 00:44:45,000
That's what we want. 
And this is a good question. 

960
00:44:45,120 --> 00:44:48,720
Backpack man, backpack man, he 
says, Carrick, you always talk 

961
00:44:48,720 --> 00:44:51,320
about if there would be 
improvements to controllers or 

962
00:44:51,320 --> 00:44:54,640
systems, but if you had your 
druthers, is there any tech you 

963
00:44:54,640 --> 00:44:57,760
would like to put into a system?
Is there any idea that has 

964
00:44:57,760 --> 00:45:01,400
popped into your head that you 
think might benefit systems? 

965
00:45:01,600 --> 00:45:03,200
Oh, he says, oh, he said 
controllers. 

966
00:45:03,200 --> 00:45:06,840
Oh, I think, OK, he meant to say
consoles or systems as a whole. 

967
00:45:06,840 --> 00:45:09,560
So like, I think what he's 
saying is if I had if it, if 

968
00:45:09,560 --> 00:45:12,320
there's ever been a random idea 
that I've had in my brain or a 

969
00:45:12,320 --> 00:45:14,760
mix of technologies. 
So that's a dude. 

970
00:45:14,760 --> 00:45:17,600
That's a fascinating question. 
I like that question because 

971
00:45:17,840 --> 00:45:21,040
sort of breaks us out-of-the-box
that we have right now. 

972
00:45:21,160 --> 00:45:25,800
OK, so if I if we took away that
these are X60 fours, right? 

973
00:45:25,800 --> 00:45:29,160
If we took those away and we 
took away that they're going to 

974
00:45:29,160 --> 00:45:32,400
be an APU on the chip and we 
were saying, oh right, you can 

975
00:45:32,400 --> 00:45:34,440
sort of put together the system 
that you want. 

976
00:45:34,440 --> 00:45:39,400
Are there any crazy technologies
that you would like to see in 

977
00:45:39,480 --> 00:45:42,200
those consoles or PCs or video 
cards? 

978
00:45:42,400 --> 00:45:46,240
Oh yeah, I got one for sure. 
OK, so when you look at the Xbox

979
00:45:46,240 --> 00:45:49,680
One and its release, they 
switched over to basically 

980
00:45:49,920 --> 00:45:53,240
Jaguar style CPUs, right? 
These are your portable CPUs. 

981
00:45:53,240 --> 00:45:54,720
That's why they were pretty 
underpowered. 

982
00:45:54,720 --> 00:45:57,720
And as they built up, as APU's 
have got more powerful, you see 

983
00:45:57,720 --> 00:45:58,880
more and more coming from them, 
right. 

984
00:45:59,000 --> 00:46:03,000
However, prior to that, what you
had were in order CPUs. 

985
00:46:03,040 --> 00:46:04,840
And these CPUs, they weren't for
OSS. 

986
00:46:04,840 --> 00:46:06,760
That's why those consoles did so
well. 

987
00:46:06,760 --> 00:46:09,480
They were in order CPUs. 
They they have their weaknesses,

988
00:46:09,640 --> 00:46:10,880
but they have a couple 
strengths. 

989
00:46:10,880 --> 00:46:13,520
One, they're better for games. 
They do work better and 

990
00:46:13,520 --> 00:46:15,560
developers were accustomed to 
them at that time. 

991
00:46:15,760 --> 00:46:19,720
Also, they usually run at a 
pretty high megahertz and that's

992
00:46:19,720 --> 00:46:22,280
one of the reasons why you might
look sometimes and you see a 

993
00:46:22,280 --> 00:46:24,400
device and you're like, man, the
megahertz on this seems slow. 

994
00:46:24,400 --> 00:46:26,360
And they're like, oh, don't 
worry about that, that's multi 

995
00:46:26,360 --> 00:46:29,040
threading or we've got multiple 
cores that take care of that, 

996
00:46:29,040 --> 00:46:31,360
that kind of stuff. 
So we switched over and you 

997
00:46:31,360 --> 00:46:34,520
know, I mean, PS4 was good, 
Xbox, they made some mistakes on

998
00:46:34,520 --> 00:46:37,920
how they set it up, but they got
back into the groove with the 

999
00:46:37,920 --> 00:46:41,320
Series X. 
So you look at this, where am I 

1000
00:46:41,320 --> 00:46:43,640
going with this? 
Well, I would say this, what I 

1001
00:46:43,640 --> 00:46:47,560
would like to see is not 
necessarily a return to that, 

1002
00:46:47,560 --> 00:46:50,200
but something that Intel did a 
patent on that. 

1003
00:46:50,200 --> 00:46:54,440
I like the idea of that. 
That goes a little bit towards 

1004
00:46:54,600 --> 00:46:57,160
locking things down specifically
for games. 

1005
00:46:57,280 --> 00:46:59,200
First of all, games. 
This is my personal opinion. 

1006
00:46:59,360 --> 00:47:02,680
Game console OSS are shit. 
Now, why are they shit? 

1007
00:47:02,680 --> 00:47:04,880
Well, because they try to treat 
them like Windows. 

1008
00:47:04,920 --> 00:47:06,840
Everybody does. 
This is the same by the way. 

1009
00:47:06,840 --> 00:47:09,480
You could say that PlayStation 
maybe tries to treat theirs like

1010
00:47:09,480 --> 00:47:12,800
Mint or Linux or something, but 
regardless, they both. 

1011
00:47:12,800 --> 00:47:15,960
They have absolutely no idea 
what originality is now. 

1012
00:47:15,960 --> 00:47:18,640
They did prior. 
Xbox's Blades was a very good 

1013
00:47:18,640 --> 00:47:21,840
system and a system that many 
people were accustomed to purely

1014
00:47:21,840 --> 00:47:24,400
at the time because it mimicked 
an analog. 

1015
00:47:24,520 --> 00:47:26,400
When you looked at the Blades, 
do you know what that mimicked? 

1016
00:47:26,520 --> 00:47:29,040
That mimicked something that 
many people have done, looking 

1017
00:47:29,040 --> 00:47:32,560
at books in a library or looking
at CDs on shelves. 

1018
00:47:32,560 --> 00:47:36,000
It actually mimicked something. 
How often in real life do you 

1019
00:47:36,000 --> 00:47:39,560
walk up to a fucking wall and 
you see a bunch of tiles, right?

1020
00:47:39,720 --> 00:47:41,120
Never. 
So what they did was they 

1021
00:47:41,120 --> 00:47:44,640
mimicked windows and they 
mimicked tiling in the Xbox OS. 

1022
00:47:44,640 --> 00:47:48,120
And what you have is an OS 
that's trying to do 400 fucking 

1023
00:47:48,120 --> 00:47:50,040
things, right? 
You have nine ways to get 

1024
00:47:50,040 --> 00:47:51,840
somewhere. 
You've got the PlayStation, 

1025
00:47:51,840 --> 00:47:54,320
which is abysmal. 
It's got lines on the top and 

1026
00:47:54,320 --> 00:47:55,720
those choices lines on the 
bottom. 

1027
00:47:55,880 --> 00:48:00,400
It's an MMO of OSS. 
Both of them suck donkey balls 

1028
00:48:00,600 --> 00:48:04,120
and they work better on the 
current CPU's that we have, 

1029
00:48:04,120 --> 00:48:07,520
CPU's that are accustomed to 
pausing and quick resuming and 

1030
00:48:07,520 --> 00:48:09,320
adjusting. 
Now, now bear with me. 

1031
00:48:09,440 --> 00:48:12,560
This question was what would I 
like, not what would be popular.

1032
00:48:12,640 --> 00:48:16,160
What I would like is a mimicry 
of what we're hearing Intel is 

1033
00:48:16,160 --> 00:48:19,280
thinking about, which is called 
their Super CPU or Supercell. 

1034
00:48:19,280 --> 00:48:22,040
So think about it like this. 
You have A and this is a problem

1035
00:48:22,040 --> 00:48:24,440
that's happened with multi 
threaded CPUs in the past. 

1036
00:48:24,440 --> 00:48:27,520
And I sort of like this idea. 
You have many cores and you've 

1037
00:48:27,520 --> 00:48:30,160
got your CPU running. 
So let's say let's just make it 

1038
00:48:30,160 --> 00:48:32,960
easier and say it's 8:00 and 
8:00, no hyper threading. 

1039
00:48:33,120 --> 00:48:35,800
So you've got 8 cores, 8 threads
and your systems running. 

1040
00:48:35,960 --> 00:48:39,400
A particular issue with a lot of
developers, even up until this 

1041
00:48:39,400 --> 00:48:42,840
day is multi threading and 
keeping every thread fed. 

1042
00:48:42,840 --> 00:48:47,160
Meaning you always have to have 
a sort of an over system 

1043
00:48:47,160 --> 00:48:49,800
hypervisor, something looking 
and saying, oh, do you have what

1044
00:48:49,800 --> 00:48:51,000
you need? 
Do you have what you need? 

1045
00:48:51,000 --> 00:48:53,360
Do you have what you need? 
Well, that person there, they 

1046
00:48:53,360 --> 00:48:54,920
don't really have what they 
need, right? 

1047
00:48:55,040 --> 00:48:58,040
That's a CPU that is unused, 
that is, that is power that's 

1048
00:48:58,040 --> 00:49:00,880
being unused, that is all this 
checking all these things. 

1049
00:49:00,880 --> 00:49:04,680
And the the developers for the 
OSS have done great fixing this 

1050
00:49:04,680 --> 00:49:06,480
up. 
But in particular, they're 

1051
00:49:06,480 --> 00:49:10,280
consistently having to do that 
because they're losing memory 

1052
00:49:10,280 --> 00:49:13,680
from the game that they can run 
to run the OS behind the scenes.

1053
00:49:13,680 --> 00:49:15,920
It's one of the reasons why it's
a big deal whenever you hear 

1054
00:49:15,920 --> 00:49:18,920
Sony or Microsoft patch the OS 
and they're like, hey, we gave 

1055
00:49:18,920 --> 00:49:23,560
256, you know, megs of RAM back 
to game craters or a gig of RAM.

1056
00:49:23,560 --> 00:49:25,560
That's, that's a good deal. 
It's very cool to have have 

1057
00:49:25,560 --> 00:49:28,160
that, but the reason why they 
had it originally is because 

1058
00:49:28,160 --> 00:49:30,800
these OSS suck. 
So what I would like to do is go

1059
00:49:30,800 --> 00:49:34,040
away from that and curb the OS 
craziness. 

1060
00:49:34,040 --> 00:49:36,000
First of all, you only need one 
store. 

1061
00:49:36,080 --> 00:49:40,800
You're I think a lot of people, 
or maybe because we have larger 

1062
00:49:40,800 --> 00:49:44,720
NVM ES coming. 
You put the particular apps in 

1063
00:49:44,720 --> 00:49:46,720
hibernate. 
Maybe you have a game that can 

1064
00:49:46,720 --> 00:49:48,440
be hibernated, right, quick 
resumed. 

1065
00:49:48,440 --> 00:49:51,040
So let's say you have two games 
that can be quick resumed, but 

1066
00:49:51,040 --> 00:49:54,960
what you do is you actually just
have some RAM allotted to the 

1067
00:49:55,000 --> 00:49:58,160
apps so that you don't have to 
spend a bunch of CPU power. 

1068
00:49:58,160 --> 00:49:59,040
You don't have to worry about 
them. 

1069
00:49:59,040 --> 00:50:00,760
They're sort of in resume all 
the time. 

1070
00:50:00,760 --> 00:50:02,280
They're sort of sitting there 
all the time. 

1071
00:50:02,400 --> 00:50:04,240
But outside of that, use what 
Intel's doing. 

1072
00:50:04,240 --> 00:50:07,320
So what Intel's got is a thing 
called the Supercell or Super 

1073
00:50:07,320 --> 00:50:09,680
CPU. 
What the plan is, is this when 

1074
00:50:09,680 --> 00:50:12,640
the game is running or when the 
OS is running or when a program 

1075
00:50:12,640 --> 00:50:16,040
is running? 
If there are a couple CPUs that 

1076
00:50:16,040 --> 00:50:19,920
are not being used, which by the
way is like legitimately all the

1077
00:50:19,920 --> 00:50:22,240
time. 
If you ever get any program and 

1078
00:50:22,240 --> 00:50:26,800
you look up if your cores are 
parking or not parking means, 

1079
00:50:26,800 --> 00:50:29,800
hey, I got nothing for you, I'm 
going to park you, which keeps 

1080
00:50:29,800 --> 00:50:32,760
your CPU power, you know, draw a
little low and your heat a 

1081
00:50:32,760 --> 00:50:36,160
little low and you can turn 
parking to be crazy to where a 

1082
00:50:36,160 --> 00:50:39,000
lot of cores get parked. 
You lose power on your system, 

1083
00:50:39,000 --> 00:50:40,800
but it's more energy efficient, 
stuff like that. 

1084
00:50:40,960 --> 00:50:44,600
And the Xbox and the PlayStation
do it on their own, their power 

1085
00:50:44,600 --> 00:50:47,000
saving, you know, modes that 
they run when you're not playing

1086
00:50:47,000 --> 00:50:49,200
a game. 
What this does is when it sees 

1087
00:50:49,200 --> 00:50:52,480
situations like that, if there 
is something that is important, 

1088
00:50:52,520 --> 00:50:57,880
it can lock down all of whatever
CPUs are available and turn them

1089
00:50:57,880 --> 00:51:01,160
into one CPU core. 
Basically what it does is 

1090
00:51:01,320 --> 00:51:04,920
imagine you have 8 CPUs and 
they're all interconnected in 

1091
00:51:04,920 --> 00:51:07,880
the normal way you would expect.
And I'm just explaining this in 

1092
00:51:07,880 --> 00:51:09,920
a physical way. 
This is not actually how it is, 

1093
00:51:09,920 --> 00:51:11,640
but I think it'll be easier for 
people to describe. 

1094
00:51:11,800 --> 00:51:13,920
So you have two lines of four 
CPUs, right? 

1095
00:51:14,000 --> 00:51:16,560
Or actually we'll just, we'll. 
Yeah, you have two lines of four

1096
00:51:16,560 --> 00:51:19,920
CPUs and they're connected by an
interconnect one to the other to

1097
00:51:19,920 --> 00:51:21,840
the other. 
So that means you're far left. 

1098
00:51:21,840 --> 00:51:25,200
One, if you're looking down, is 
only connected to, if it's in 

1099
00:51:25,200 --> 00:51:27,640
the lower left corner, is only 
connected to the one above it 

1100
00:51:27,760 --> 00:51:29,400
and to the one to the right, 
right. 

1101
00:51:29,520 --> 00:51:33,360
What these guys are doing is 
that they are all also connected

1102
00:51:33,360 --> 00:51:36,640
by a ring. 
So imagine sort of a ring around

1103
00:51:36,640 --> 00:51:39,520
them that isn't used until 
something important comes up. 

1104
00:51:39,560 --> 00:51:42,760
And if there is the ability, 
what this does is it locks them 

1105
00:51:42,760 --> 00:51:46,480
down as one CPU and they have 
instructions on board. 

1106
00:51:46,520 --> 00:51:49,800
And So what happens is they're 
able to have all those CPU's 

1107
00:51:49,800 --> 00:51:53,920
sort of lock their speed and 
lock that they're one CPU and it

1108
00:51:53,920 --> 00:51:58,640
sees those all as one CPU. 
So in a way, a current system, 

1109
00:51:58,800 --> 00:52:02,000
you have a CPU that can be seen 
as 2 with hyper threading, even 

1110
00:52:02,000 --> 00:52:05,200
though it's software, right? 
You can see it because they were

1111
00:52:05,200 --> 00:52:06,920
able to actually figure that out
on the software. 

1112
00:52:06,920 --> 00:52:10,600
This is sort of the opposite. 
And what it does is instead of 

1113
00:52:10,760 --> 00:52:15,040
calling just one CPU, you 
actually are able to say we're 

1114
00:52:15,040 --> 00:52:17,280
using, we're just going to call 
it super CPU. 

1115
00:52:17,280 --> 00:52:22,680
We're using Super CPU one, which
is really core 2-3 and five 

1116
00:52:22,680 --> 00:52:25,720
because 2-3 and five are 
connected all to 1 and another, 

1117
00:52:25,880 --> 00:52:29,400
and they're connected via the 
instructions that this new CPU 

1118
00:52:29,400 --> 00:52:31,480
will have. 
And so they all understand that 

1119
00:52:31,480 --> 00:52:34,720
they're basically just one large
CPU and it runs a quick burst. 

1120
00:52:34,720 --> 00:52:37,000
It does what it needs to do, 
ejects that back. 

1121
00:52:37,000 --> 00:52:39,080
And that's something Intel is 
looking at. 

1122
00:52:39,200 --> 00:52:41,560
And there's probably a ton of 
things in their patent. 

1123
00:52:41,560 --> 00:52:43,280
I did read their patent. 
It looked pretty cool. 

1124
00:52:43,280 --> 00:52:46,120
I love the idea of it because 
it's just an idea outside, but 

1125
00:52:46,120 --> 00:52:47,320
it's like, what could you do 
there? 

1126
00:52:47,320 --> 00:52:50,160
Well, if you do have these games
that have stalls or you have 

1127
00:52:50,160 --> 00:52:52,320
these situations where 
something's waiting for 

1128
00:52:52,320 --> 00:52:55,600
something else, but you can't, 
you know, it's with multi ready 

1129
00:52:55,600 --> 00:52:57,680
and you have to go. 
You have to prime this one 

1130
00:52:57,680 --> 00:53:00,960
single CPU with this data. 
Is it possible to prime three 

1131
00:53:01,080 --> 00:53:04,680
with a third of that data so 
that you can spread your your 

1132
00:53:04,680 --> 00:53:07,920
requirement around and then lock
them down as one CPU? 

1133
00:53:07,920 --> 00:53:10,160
Boom, they run it and then they 
turn off and they're back to 

1134
00:53:10,160 --> 00:53:12,960
their back to their sort of 
separate CPU style. 

1135
00:53:13,120 --> 00:53:14,680
Now the thing you have to worry 
about is leg. 

1136
00:53:14,680 --> 00:53:17,080
You have to worry about, you 
know, we're talking picoseconds 

1137
00:53:17,080 --> 00:53:19,120
here. 
We're talking like insanely low 

1138
00:53:19,320 --> 00:53:22,480
second responses for these. 
So you're hoping that you don't 

1139
00:53:22,480 --> 00:53:25,960
have an issue there with leg or 
something that happens where 

1140
00:53:25,960 --> 00:53:27,200
they're switching back and 
forth. 

1141
00:53:27,360 --> 00:53:28,880
I don't necessarily think they 
will. 

1142
00:53:29,040 --> 00:53:32,840
I think this will probably be 
started at a very, very low 

1143
00:53:32,840 --> 00:53:35,840
level where it's not super 
aggressive, but it does sound 

1144
00:53:35,840 --> 00:53:39,480
like a very smart way to do it, 
especially because multi 

1145
00:53:39,480 --> 00:53:42,960
threading, even on a PC, you 
will see it notoriously. 

1146
00:53:42,960 --> 00:53:45,800
You'll have two or three, you 
know, chips that just they don't

1147
00:53:45,800 --> 00:53:47,840
have, there's not enough for 
them to do. 

1148
00:53:47,840 --> 00:53:50,200
So they're just parked right. 
They're just not doing as much. 

1149
00:53:50,360 --> 00:53:54,520
So the idea of let's say waiting
for one of them to come unparked

1150
00:53:54,520 --> 00:53:56,960
and just saying we'll wait, wait
for this, it's a cache miss. 

1151
00:53:57,120 --> 00:53:59,200
We'll wait for this and we'll, 
we'll swing back around and 

1152
00:53:59,200 --> 00:54:02,160
we'll hit it on the next cycle 
stating, no, what we're going to

1153
00:54:02,160 --> 00:54:05,520
do is we're going to feed 1/3 of
this larger thing we need to 

1154
00:54:05,520 --> 00:54:08,160
three of them and we're going to
have them do it all in one quick

1155
00:54:08,160 --> 00:54:10,640
burst. 
And it's not really that crazy. 

1156
00:54:10,640 --> 00:54:13,440
I mean, that is something that 
especially when you look at the 

1157
00:54:13,440 --> 00:54:16,320
opposite of it with how some of 
these CPUs and their 

1158
00:54:16,320 --> 00:54:19,080
architectures are made it, it's 
not out of the order that they 

1159
00:54:19,080 --> 00:54:22,120
could do it, especially because 
we're looking at a lot of these 

1160
00:54:22,120 --> 00:54:24,640
CPUs that are all connected to 
one another already. 

1161
00:54:24,800 --> 00:54:27,880
It's just they've never been 
sort of locked down as 10. 

1162
00:54:27,880 --> 00:54:29,080
Whoops. 
Alexa, turn off. 

1163
00:54:29,160 --> 00:54:32,400
That was my alarm and that was 
my alarm indicating we are at 

1164
00:54:32,520 --> 00:54:35,200
what, one hour? 
God damn, almost one hour. 

1165
00:54:35,320 --> 00:54:37,040
But yeah, this is cool. 
You guys can check out that 

1166
00:54:37,040 --> 00:54:39,960
patent. 
Just look it up as like Intel 

1167
00:54:40,040 --> 00:54:42,800
CPU patent for Supercell or 
super CPU. 

1168
00:54:42,800 --> 00:54:44,120
I'm sorry if I can't remember 
the name. 

1169
00:54:44,120 --> 00:54:47,120
I looked it up a couple days ago
when I saw a pop up in my news 

1170
00:54:47,160 --> 00:54:49,600
and I really do like the idea of
it. 

1171
00:54:49,600 --> 00:54:52,480
And you know, it's not it 
doesn't change anything. 

1172
00:54:52,480 --> 00:54:55,360
Who knows, but I think when you 
come to the technologies for 

1173
00:54:55,440 --> 00:54:58,560
consoles, something like that 
where maybe the developer 

1174
00:54:58,560 --> 00:55:01,000
doesn't have to worry so much 
about making sure, especially 

1175
00:55:01,000 --> 00:55:04,000
with the lower level stuff that 
consoles have your lower level 

1176
00:55:04,000 --> 00:55:06,480
RAM, what have you. 
If you could lock them down, you

1177
00:55:06,480 --> 00:55:10,880
could burst some data out to 
some and then continue to do all

1178
00:55:10,880 --> 00:55:12,520
of your other multi threading 
that you're doing. 

1179
00:55:12,720 --> 00:55:15,400
That just improves the 
efficiency of the system and 

1180
00:55:15,400 --> 00:55:16,680
it's using what you already have
there. 

1181
00:55:16,680 --> 00:55:20,600
So I like the idea. 
I'd like to see NVM or NVIDIA as

1182
00:55:20,600 --> 00:55:23,200
well as AMD do that kind of 
stuff and I would assume that 

1183
00:55:23,200 --> 00:55:26,120
they will if, if it works out, 
if Intel works out, it'll 

1184
00:55:26,120 --> 00:55:28,480
probably be a generation that we
watch and we try to see what 

1185
00:55:28,480 --> 00:55:31,240
happens then that kind of stuff.
That's great to me in a way it 

1186
00:55:31,240 --> 00:55:34,200
reminds me of all these other 
interconnected systems we have 

1187
00:55:34,200 --> 00:55:36,200
now. 
Look at Rebar, I mean Rebar 

1188
00:55:36,200 --> 00:55:39,920
basically lets the video card 
see a little bit more of the RAM

1189
00:55:39,920 --> 00:55:44,400
or basically see the RAM and use
it as I guess you'd say AV RAM 

1190
00:55:44,400 --> 00:55:48,840
substitute and it's slower. 
But the way it works, it filters

1191
00:55:48,840 --> 00:55:51,080
out and uses the fastest VRAM 
1st. 

1192
00:55:51,240 --> 00:55:53,600
And we're starting to see that 
actually not 'cause as many 

1193
00:55:53,600 --> 00:55:55,360
problems as it used to. 
It used to be where if you 

1194
00:55:55,440 --> 00:55:58,040
turned on rebar, you'd be like, 
OK, listen, in one game it's 

1195
00:55:58,040 --> 00:56:01,960
going to give you 2330, maybe 
extra FPS, crazy gains. 

1196
00:56:01,960 --> 00:56:04,280
Sometimes on some of the older 
games, you'd be like, whoa, what

1197
00:56:04,280 --> 00:56:05,720
the hell? 
And then other times it would 

1198
00:56:05,720 --> 00:56:08,200
stutter like a bitch. 
It would have all kinds of 

1199
00:56:08,200 --> 00:56:10,040
problems. 
So I love this. 

1200
00:56:10,040 --> 00:56:12,880
I love when developers look at 
something to say, you know what?

1201
00:56:12,880 --> 00:56:14,680
This entire time we've been 
doing it this way. 

1202
00:56:14,800 --> 00:56:16,720
What if we just turn rebar on, 
man? 

1203
00:56:16,760 --> 00:56:19,640
What if we just let these cards 
see a little bit more of the 

1204
00:56:19,640 --> 00:56:22,400
RAM, especially as people have 
more and more RAM. 

1205
00:56:22,400 --> 00:56:24,880
Why don't we do that? 
Especially when you look that AP

1206
00:56:24,880 --> 00:56:26,440
US are already sharing RAM 
anyway. 

1207
00:56:26,560 --> 00:56:29,080
That's how an APU runs. 
They're using shared RAM with 

1208
00:56:29,080 --> 00:56:31,720
the CPU and with the system. 
So it's like we already know it 

1209
00:56:31,720 --> 00:56:33,800
can work. 
And if we just do it a certain 

1210
00:56:33,800 --> 00:56:36,480
way and we have our software 
take advantage of it, we can do 

1211
00:56:36,480 --> 00:56:37,760
some crazy stuff. 
I love it. 

1212
00:56:37,920 --> 00:56:39,240
I want to see more of this kind 
of shit. 

1213
00:56:39,360 --> 00:56:42,440
But you know, the other thing 
would be to figure out the RAM 

1214
00:56:42,440 --> 00:56:45,480
situation on the video cards. 
I would say if I had my 

1215
00:56:45,480 --> 00:56:48,520
druthers, if I had my ability to
improve anything or change 

1216
00:56:48,520 --> 00:56:52,800
anything, it's that we start to 
look at VRAM as something that's

1217
00:56:52,800 --> 00:56:56,400
hyper important and we need, we 
need to figure out a way. 

1218
00:56:56,400 --> 00:56:59,080
Because it feels to me like when
you start looking at these 

1219
00:56:59,080 --> 00:57:01,720
cards, the VRAM is being left 
behind. 

1220
00:57:01,720 --> 00:57:05,360
We're getting 24 or 32. 
But if you go back and look, if 

1221
00:57:05,360 --> 00:57:07,840
you go back and look at the 
other improvements elsewhere, 

1222
00:57:07,840 --> 00:57:11,560
you start to see massive jumps. 
And really RAM hasn't increased.

1223
00:57:11,560 --> 00:57:14,960
In fact, we see that a lot of 
video cards will have that one 

1224
00:57:15,160 --> 00:57:18,320
video card in their line that 
has really bad VRAM and it just 

1225
00:57:18,320 --> 00:57:20,640
doesn't have a lot. 
And I feel like that's a place 

1226
00:57:20,640 --> 00:57:23,400
that we're sort of missing out. 
And I would like to see 

1227
00:57:23,400 --> 00:57:26,600
companies, especially you're 
looking at that, the little mini

1228
00:57:26,600 --> 00:57:29,000
laptops and stuff like that. 
They're using all kinds of 

1229
00:57:29,000 --> 00:57:32,000
different RAM sort of plans and 
situations. 

1230
00:57:32,000 --> 00:57:36,280
And I like the idea of just 
making sure that we're prepared 

1231
00:57:36,280 --> 00:57:37,880
for games. 
When you get that game that's 

1232
00:57:37,880 --> 00:57:40,720
running 8K textures and you're 
like, OK, what are we going to 

1233
00:57:40,720 --> 00:57:42,360
do? 
Like how are we going to get 

1234
00:57:42,360 --> 00:57:45,040
these into the system? 
I don't want an 8 KTV, but I'm 

1235
00:57:45,040 --> 00:57:46,440
just saying that's where they're
going to go. 

1236
00:57:46,440 --> 00:57:48,880
Somebody's going to put it on 
their system and really make it 

1237
00:57:48,880 --> 00:57:51,160
a real selling point. 
Like they're going to, you know,

1238
00:57:51,160 --> 00:57:53,000
it'd probably be PlayStation 6, 
just known them. 

1239
00:57:53,000 --> 00:57:55,360
They'll be like, you know, it 
plays it native 8K, but we can 

1240
00:57:55,480 --> 00:57:58,680
downsample for those of you who 
haven't stepped into the future,

1241
00:57:58,720 --> 00:58:00,160
which is then going to cause 
FOMO. 

1242
00:58:00,160 --> 00:58:01,960
Everybody's going to move 
forward being like, Oh my God, 

1243
00:58:01,960 --> 00:58:05,200
we have to have 8K and that's 
just a shit ton of Rams. 

1244
00:58:05,920 --> 00:58:09,080
I mean, the idea of how big 
those textures are going to be 

1245
00:58:09,280 --> 00:58:12,720
is monumental. 
So that is what I would like to 

1246
00:58:12,720 --> 00:58:13,760
see. 
I would like to see some 

1247
00:58:13,760 --> 00:58:16,600
companies looking at the ring 
kind of system that Intel is 

1248
00:58:16,600 --> 00:58:19,160
looking at trying to take care 
of multi threading, which is 

1249
00:58:19,160 --> 00:58:22,600
basically the entire story. 
I would like these companies if 

1250
00:58:22,600 --> 00:58:26,480
I had my druthers to figure out 
a way to prove all the multi 

1251
00:58:26,480 --> 00:58:27,840
threading and take better 
advantage. 

1252
00:58:28,080 --> 00:58:30,320
Anyway, that's it for me. 
I got to get going Peace out 

1253
00:58:30,320 --> 00:58:31,960
everybody. 
If you get a chance, leave a 

1254
00:58:31,960 --> 00:58:35,360
comment, say the ring, hashtag 
the ring if you got this far. 

1255
00:58:35,520 --> 00:58:38,040
That's it for me. 
I hope you guys enjoy the rest 

1256
00:58:38,040 --> 00:58:41,000
of your week. 
We will see you Friday video 

1257
00:58:41,000 --> 00:58:42,720
coming tomorrow so keep an eye 
on it. 

1258
00:58:42,840 --> 00:58:45,120
If you haven't been getting 
videos from me, go to YouTube, 

1259
00:58:45,120 --> 00:58:48,320
unsubscribe, then hit subscribe 
again and hit the all button and

1260
00:58:48,320 --> 00:58:49,520
that should fix it. 
Peace out.

