1
00:00:00,500 --> 00:00:03,700
Sup everybody, this is Eric with
a CG every single time I wake up

2
00:00:03,700 --> 00:00:07,300
now and I look at news in 2020. 
I'm just like, yeah you know 

3
00:00:07,300 --> 00:00:09,600
what, checks out it really 
nothing surprises me. 

4
00:00:09,600 --> 00:00:12,800
So this morning when I woke up 
and I realized that somehow EA 

5
00:00:12,800 --> 00:00:16,300
had bought codemasters and CD, 
projekt Red and realized that 

6
00:00:16,300 --> 00:00:19,100
there were bugs in their games. 
Hey, you know what, it wasn't 

7
00:00:19,100 --> 00:00:21,500
that surprising, let's begin. 
We're going to talk about two 

8
00:00:21,500 --> 00:00:24,800
bits of data and then I'll break
into a little bit of a podcast 

9
00:00:24,800 --> 00:00:27,800
type format at the very end to 
discuss these in more detail. 

10
00:00:27,900 --> 00:00:30,400
First thing I want to talk about
1.2 Billion. 

11
00:00:30,400 --> 00:00:33,000
Now 1.2 billion, I believe 
that's what Zappos got from 

12
00:00:33,000 --> 00:00:35,000
Amazon. 
And zox got from Amazon for 

13
00:00:35,000 --> 00:00:38,400
their hardware and software. 
That's actually what AstraZeneca

14
00:00:38,400 --> 00:00:41,100
got from United States 
government for working on a 

15
00:00:41,100 --> 00:00:44,500
grant for the vaccine. 
That is also what codemasters 

16
00:00:44,500 --> 00:00:47,500
just got from EA. 
So somehow like, Nickelback 

17
00:00:47,500 --> 00:00:50,300
sneaking into the Grammys and 
getting some kind of award from 

18
00:00:50,300 --> 00:00:53,600
her more talented artist, he a 
went in there and snuck it out 

19
00:00:53,600 --> 00:00:58,100
and basically stole it from 2K. 
Now, 2K offered, I think 970 

20
00:00:58,100 --> 00:01:02,200
million dollars for this. 
And then EA snuck in offered a 

21
00:01:02,208 --> 00:01:05,099
little bit more and got it. 
You'll also remember or maybe 

22
00:01:05,099 --> 00:01:08,300
you won't that EA also about the
Developers for project cars 3. 

23
00:01:08,300 --> 00:01:10,500
The reason why you probably 
won't remember is that project 

24
00:01:10,500 --> 00:01:12,800
cars? 
Three absolutely sucked, and no 

25
00:01:12,800 --> 00:01:17,000
one pretty much cared, but EA 
now has Need for Speed, it's got

26
00:01:17,000 --> 00:01:20,400
dirt and Grid, it's got Formula 
One pretty much all the racing. 

27
00:01:20,400 --> 00:01:23,300
So if you're taking out bets for
how long, it takes her EA to 

28
00:01:23,300 --> 00:01:24,600
walk. 
One of these guys behind the 

29
00:01:24,600 --> 00:01:27,200
Woodshed and disappeared. 
The company, like, Jimmy Hoffa. 

30
00:01:27,400 --> 00:01:29,600
I'll take that bet. 
Good luck to anybody, though. 

31
00:01:29,600 --> 00:01:31,900
A Codemasters. 
And hey I wish you. 

32
00:01:31,900 --> 00:01:34,000
Well the next thing we're going 
to talk about is CD. 

33
00:01:34,000 --> 00:01:36,700
Projekt Red agrees with me, 
corpo all the way. 

34
00:01:37,200 --> 00:01:40,700
So CD, projekt Red released an 
announcement this morning about 

35
00:01:40,700 --> 00:01:43,500
the game and its current state, 
and we're going to talk about 

36
00:01:43,500 --> 00:01:46,500
that a little bit now. 
As always, don't take out any 

37
00:01:46,500 --> 00:01:49,000
aggression or issues. 
You may have on some random 

38
00:01:49,000 --> 00:01:51,700
person on Twitter, they don't 
treat you personal in any way 

39
00:01:51,700 --> 00:01:53,300
from a company standpoint. 
You shouldn't treat them 

40
00:01:53,300 --> 00:01:55,500
personally from a consumer 
standpoint. 

41
00:01:55,600 --> 00:01:57,300
They aren't always saving babies
from floods. 

42
00:01:57,300 --> 00:01:59,100
Nor are you throwing babies in 
flood? 

43
00:01:59,100 --> 00:02:02,300
So the company will say, I don't
know not a good analogy but 

44
00:02:02,400 --> 00:02:04,900
regardless of all that you also 
shouldn't attack some poor 

45
00:02:04,900 --> 00:02:07,700
random Joe who just loves the 
internet and likes their job at 

46
00:02:07,708 --> 00:02:09,500
a company. 
It just doesn't make any sense. 

47
00:02:09,500 --> 00:02:11,900
Knock it the fuck off. 
Also some people are going to be

48
00:02:11,900 --> 00:02:14,500
like but I don't have any bugs, 
that's awesome but guess what? 

49
00:02:14,600 --> 00:02:18,600
The devs themselves are 
introducing this actual 

50
00:02:18,600 --> 00:02:21,000
announcement to state. 
That they know that there's so 

51
00:02:21,000 --> 00:02:23,500
many bugs. 
It's a large enough issue that 

52
00:02:23,500 --> 00:02:25,900
they're actually going out there
and making sure people know that

53
00:02:25,900 --> 00:02:29,000
they can request refunds and 
basically telling people stick 

54
00:02:29,000 --> 00:02:30,500
with us. 
Even though Oh, that makes 

55
00:02:30,500 --> 00:02:33,900
absolutely no sense because most
of us stuck with you six years, 

56
00:02:33,900 --> 00:02:36,300
prior to its release, but we'll 
get to that in a second. 

57
00:02:36,400 --> 00:02:39,100
So, I'm going to break this down
and sort of how all this came 

58
00:02:39,100 --> 00:02:40,400
about. 
But also the process real 

59
00:02:40,400 --> 00:02:42,700
quickly in three different ways.
I'm going to talk about the 

60
00:02:42,700 --> 00:02:45,500
process itself, the product, and
the pr. 

61
00:02:45,500 --> 00:02:47,900
Now, when it comes to the 
process, as I've discussed in 

62
00:02:47,900 --> 00:02:52,400
past videos, not always having 
code is for a particular 

63
00:02:52,400 --> 00:02:54,600
platform. 
I would say, not completely 

64
00:02:54,600 --> 00:02:56,300
abnormal. 
In fact, it's mostly normal. 

65
00:02:56,300 --> 00:02:58,000
There's nothing really unique. 
Nothing. 

66
00:02:58,000 --> 00:02:59,800
Really special about that kind 
of situation. 

67
00:03:00,000 --> 00:03:02,200
But that's why most of the 
videos that I do, I State 

68
00:03:02,200 --> 00:03:04,300
something like, code wasn't 
available on this platform or 

69
00:03:04,300 --> 00:03:06,700
something like that. 
This is adjusted and sort of 

70
00:03:06,700 --> 00:03:09,800
altered, depending on the 
timeliness of the review, 

71
00:03:09,800 --> 00:03:13,700
embargo itself, how close it is.
So cyberpunk was close enough 

72
00:03:13,700 --> 00:03:15,500
that it made sense. 
There might be an issue, which 

73
00:03:15,500 --> 00:03:19,000
is one of the reasons why I 
refused that review code or the 

74
00:03:19,000 --> 00:03:21,400
streaming code that that went 
live a couple days before 

75
00:03:21,400 --> 00:03:24,200
because so many things had just 
gone completely off the rails. 

76
00:03:24,500 --> 00:03:28,800
In addition, unless you're asked
as a reviewer and you refused 

77
00:03:28,900 --> 00:03:30,800
most people who are Reviewing a 
game. 

78
00:03:30,800 --> 00:03:33,100
Won't know what platforms are 
really available? 

79
00:03:33,100 --> 00:03:36,700
They'll State what platform they
want many moons prior to that 

80
00:03:36,700 --> 00:03:39,900
many months, usually where 
you're filling, out forms and 

81
00:03:39,900 --> 00:03:42,500
stating what you want. 
So them knowing and not knowing 

82
00:03:42,500 --> 00:03:46,200
is really just investigative or 
perhaps talking to people which 

83
00:03:46,300 --> 00:03:48,100
nda's tell you not to talk to 
people. 

84
00:03:48,100 --> 00:03:51,500
But what have you? 
And I've discussed all this in 

85
00:03:51,500 --> 00:03:55,200
more depth in the Horizon zero 
Dawn video about embargo as well

86
00:03:55,200 --> 00:03:57,100
as the Friday podcast, we always
talk about it. 

87
00:03:57,100 --> 00:04:01,900
So also rest assured each. 
Any handles PR and code a 

88
00:04:01,908 --> 00:04:04,300
different way. 
Some better some worse than 

89
00:04:04,300 --> 00:04:06,100
this. 
This is not the be-all end-all 

90
00:04:06,100 --> 00:04:08,600
of situations. 
Now, I want to debunk one thing 

91
00:04:08,600 --> 00:04:10,800
or at least draw attention to it
and then sort of debunk. 

92
00:04:10,800 --> 00:04:12,800
And that's that a huge number of
people are starting this weird 

93
00:04:12,800 --> 00:04:14,800
conspiracy and I saw it my 
Discord where people were 

94
00:04:14,800 --> 00:04:18,600
saying, CD, projekt Red corded 
streamers and such on purpose, 

95
00:04:18,600 --> 00:04:20,899
to get away with this. 
That would have been done prior 

96
00:04:20,899 --> 00:04:24,400
to any of the, you know, any of 
the polishing moments because 

97
00:04:24,400 --> 00:04:27,100
you have to actually have 
content polish so they would 

98
00:04:27,100 --> 00:04:30,300
have actually created that 
content and then Paul, Wished it

99
00:04:30,300 --> 00:04:33,400
later while. 
Yes, that is a way to get a 

100
00:04:33,400 --> 00:04:35,600
large. 
Number of people sort of excited

101
00:04:35,600 --> 00:04:39,300
about your product. 
These two things are not related

102
00:04:39,300 --> 00:04:41,900
and that's totally acceptable. 
As long as that person is never 

103
00:04:41,900 --> 00:04:44,500
stating the quality of the 
content because they're in the 

104
00:04:44,500 --> 00:04:47,800
content, which would be really 
weird, especially if they had a 

105
00:04:47,800 --> 00:04:50,700
particular, a large audience, 
that's fine, those kind of 

106
00:04:50,707 --> 00:04:52,400
things. 
Some people want to show up in 

107
00:04:52,400 --> 00:04:54,300
those. 
But, you know, for example, if I

108
00:04:54,300 --> 00:04:57,500
was in something I would never 
review it, I would probably say 

109
00:04:57,500 --> 00:04:59,600
nothing else, then I'm in 
something. 

110
00:04:59,900 --> 00:05:03,200
And and just push it off because
at that point if you're giving 

111
00:05:03,200 --> 00:05:06,000
any kind of statement, this is 
awesome or this is cool or this 

112
00:05:06,000 --> 00:05:08,200
is terrible. 
I don't know why you'd say that 

113
00:05:08,600 --> 00:05:10,900
you would probably have to put 
sponsored on that. 

114
00:05:10,900 --> 00:05:12,200
Now, let's talk about the 
product. 

115
00:05:12,200 --> 00:05:14,300
So the product we're going to 
jump into this and we're going 

116
00:05:14,300 --> 00:05:16,600
to discuss. 
Why CD projekt Red release this 

117
00:05:16,800 --> 00:05:19,600
and a release, this weird PR 
statement. 

118
00:05:20,300 --> 00:05:23,400
It really is, as a game in an 
unfinished state. 

119
00:05:23,400 --> 00:05:26,700
It is the buggies game so far 
that I've ever had to review. 

120
00:05:26,700 --> 00:05:29,700
And that means it beats Unity, 
which blows my mind. 

121
00:05:29,900 --> 00:05:32,200
And, but I do want to discuss 
what a bug is. 

122
00:05:32,200 --> 00:05:35,600
So, people understand and how 
that's different from, let's say

123
00:05:35,600 --> 00:05:38,000
a stopper. 
So a bug is something that is a 

124
00:05:38,000 --> 00:05:40,700
failure of the code, this 
results in like a negative 

125
00:05:40,700 --> 00:05:44,100
player feedback loop. 
But it's not something like a 

126
00:05:44,100 --> 00:05:46,700
pathan issue. 
Not so much unless it affects 

127
00:05:46,700 --> 00:05:49,400
immersion consistently like 
Unity did. 

128
00:05:49,400 --> 00:05:51,900
But when you start getting 
quests that won't take off or 

129
00:05:51,900 --> 00:05:56,000
freezes on load screens or bugs,
that won't let you continue. 

130
00:05:56,000 --> 00:05:59,200
Those begum, a higher category 
of bug and something that I 

131
00:05:59,200 --> 00:06:00,800
definitely do. 
In the summary. 

132
00:06:01,000 --> 00:06:04,500
And that will for sure be 
informed to the gamer, as well 

133
00:06:04,500 --> 00:06:07,600
as affect the review now bug so 
far. 

134
00:06:08,000 --> 00:06:10,100
As of this morning, is crazy, be
aware. 

135
00:06:10,100 --> 00:06:13,400
These are specified by my 
channel and how I report bugs, 

136
00:06:13,700 --> 00:06:16,800
and my guidelines for the 
channel that I've had since day 

137
00:06:16,800 --> 00:06:18,900
one. 
Pretty much anybody reviewing 

138
00:06:19,200 --> 00:06:21,800
any type of game should have a 
ton of guidelines for how they 

139
00:06:21,800 --> 00:06:24,200
go about, to make sure that 
they're fair and honest, and 

140
00:06:24,200 --> 00:06:25,500
they're following particular 
rules. 

141
00:06:25,800 --> 00:06:28,400
These are mine, I'll flash them 
up on the screen, but I can tell

142
00:06:28,400 --> 00:06:31,200
you just from memory. 
I Add some crazy stuff. 

143
00:06:31,200 --> 00:06:33,500
First of all, the HDR is 
completely broken. 

144
00:06:33,500 --> 00:06:35,100
Its broken. 
It just doesn't work. 

145
00:06:35,100 --> 00:06:38,100
I've had nine ten. 
I think 10 of the small, as of 

146
00:06:38,100 --> 00:06:43,100
this morning, crashes to the 
actual desktop on PC 15, loading

147
00:06:43,100 --> 00:06:46,800
new area are errors on PC and 
console combined. 

148
00:06:46,800 --> 00:06:50,700
Meaning, when you go to a new 
spot textures just simply never 

149
00:06:50,700 --> 00:06:52,400
load no matter what I've come 
back. 

150
00:06:52,600 --> 00:06:55,200
You know, circled around done a 
an event done. 

151
00:06:55,200 --> 00:06:57,700
Some kind of battle came back, 
not there, we've also had the 

152
00:06:57,700 --> 00:07:02,000
police spawn bug or Police 
spawning, I don't know what 

153
00:07:02,000 --> 00:07:04,300
you'd call it program situation 
that occurs in there. 

154
00:07:04,300 --> 00:07:07,500
Were police can spawn in the air
that can spawn on top of 

155
00:07:07,500 --> 00:07:09,600
buildings. 
It's crazy when you get in a 

156
00:07:09,608 --> 00:07:13,200
battle that the enemies will 
just spawn everywhere in some 

157
00:07:13,600 --> 00:07:16,600
sort of really casual way in 
which they want to handle the 

158
00:07:16,600 --> 00:07:20,900
police system, so that really 
does impact immersion. 

159
00:07:20,900 --> 00:07:23,300
It may not be considered a bug 
when I do the review. 

160
00:07:23,300 --> 00:07:27,300
I'm going to look at it closer 
and about 80% of the time, NPCs 

161
00:07:27,300 --> 00:07:29,300
do nothing. 
When you're in the street, their

162
00:07:29,800 --> 00:07:32,000
It won't move for lip-syncing. 
This is something you can see on

163
00:07:32,000 --> 00:07:33,800
any stream. 
It was funny too because I 

164
00:07:33,800 --> 00:07:36,300
jumped into a bunch of streams 
many with thousands upon 

165
00:07:36,300 --> 00:07:38,400
thousands of people streaming 
and people are asking them. 

166
00:07:38,400 --> 00:07:40,100
They were like hey man how's the
game? 

167
00:07:40,100 --> 00:07:42,900
And there are no it's fine. 
And I've had no bugs and you're 

168
00:07:42,900 --> 00:07:46,800
watching as like cars are flying
into the sky or people are 

169
00:07:46,800 --> 00:07:50,500
disappearing in front of them. 
You she's like really but each 

170
00:07:50,500 --> 00:07:54,400
person looks at these things 
differently and, you know, some 

171
00:07:54,400 --> 00:07:55,900
people that's just not what 
they're doing. 

172
00:07:55,900 --> 00:07:58,000
I'm reviewing a product. 
Some people are just streaming 

173
00:07:58,000 --> 00:08:00,800
there, you know, that's not the 
That they're actually looking 

174
00:08:00,800 --> 00:08:03,200
for. 
But looking for something Hoops,

175
00:08:03,200 --> 00:08:06,000
looking for something, let's 
discuss the pr for a second. 

176
00:08:06,100 --> 00:08:08,600
Let me highlight that PR is 
handled differently by different

177
00:08:08,600 --> 00:08:10,100
companies. 
This isn't too strange. 

178
00:08:10,100 --> 00:08:11,800
There's some great companies out
there. 

179
00:08:11,800 --> 00:08:16,500
Handling, PR, some not so good. 
It's not really crazy to see how

180
00:08:16,500 --> 00:08:19,100
it's handled differently by CD, 
projekt Red than somebody else. 

181
00:08:19,400 --> 00:08:23,000
People told in an embargo to not
draw attention to bugs nor 

182
00:08:23,000 --> 00:08:25,700
repeatedly show them. 
And in some cases to inform 

183
00:08:25,700 --> 00:08:29,700
Gamers that those will be fixed 
is also not necessarily hugely. 

184
00:08:29,800 --> 00:08:33,100
Lee new, it's not some kind of 
surprising development. 

185
00:08:33,400 --> 00:08:35,799
The last few times I've 
encountered this was mostly 

186
00:08:35,799 --> 00:08:38,400
streamer and DA's because you 
have a streamer ND, a lot of 

187
00:08:38,408 --> 00:08:40,400
times in a review NDA and the 
streamer NDA. 

188
00:08:40,400 --> 00:08:43,900
Sometimes comes earlier, they'll
be like only stream 2 or 3, you 

189
00:08:43,900 --> 00:08:46,800
know levels. 
And then do this and tell people

190
00:08:46,800 --> 00:08:49,900
that those bugs that they see 
will most likely be fixed or 

191
00:08:50,100 --> 00:08:52,400
these specific bugs. 
And that's what I'll do is I'll 

192
00:08:52,400 --> 00:08:55,600
look closer to that language and
if they say these specific bugs 

193
00:08:55,600 --> 00:08:57,000
and list them. 
Hey, you know what? 

194
00:08:57,000 --> 00:08:58,700
That makes sense. 
They've seen those bugs. 

195
00:08:58,700 --> 00:09:01,800
However, and this is Something 
that sort of got me on this two 

196
00:09:01,800 --> 00:09:05,800
years ago, sometimes you'll see 
that review that NDA for 

197
00:09:05,800 --> 00:09:07,200
streamer. 
And it'll say, just tell 

198
00:09:07,200 --> 00:09:09,900
everybody, everything will be 
fixed at that point. 

199
00:09:09,900 --> 00:09:12,700
If you're signing that NDA, you 
might, as well put sponsored 

200
00:09:12,700 --> 00:09:15,200
behind everything, because that 
makes no sense. 

201
00:09:15,200 --> 00:09:19,000
No one knows every single bug. 
And it just makes no sense to 

202
00:09:19,000 --> 00:09:20,800
even say that on any kind of 
stream. 

203
00:09:20,800 --> 00:09:25,200
So, this is also something that 
I want to bring up, you always 

204
00:09:25,200 --> 00:09:29,000
see this conspiracy theory about
paid for reviews, which is I 

205
00:09:29,000 --> 00:09:31,400
really haven't. 
Run into those very much, you 

206
00:09:31,400 --> 00:09:33,700
know, there's a couple Chinese 
companies, a couple 

207
00:09:33,900 --> 00:09:36,300
International companies, that 
they'll sort of hint around 

208
00:09:36,300 --> 00:09:39,100
particular ways and sort of try 
to get you into things. 

209
00:09:39,200 --> 00:09:41,700
And I've always just refused him
and moved on, I've talked to you

210
00:09:41,700 --> 00:09:44,400
about those a couple times. 
That's really not the thing, but

211
00:09:44,400 --> 00:09:47,700
what I do run into time and 
again is this worried or 

212
00:09:47,700 --> 00:09:51,500
hesitation to report bugs as 
immersion Killers to work 

213
00:09:51,500 --> 00:09:55,700
through the code, regardless of 
those bugs and to fight through 

214
00:09:55,700 --> 00:09:58,000
something and to sort of ignore 
them, this is something that we 

215
00:09:58,000 --> 00:10:01,200
saw in AC Unity. 
We saw Cry 5S horrendous 

216
00:10:01,200 --> 00:10:04,100
spawning in AI issues and it's 
in cyberpunk. 

217
00:10:04,100 --> 00:10:08,100
It's in Halo, this is days gone 
day one, which was crazy. 

218
00:10:08,700 --> 00:10:13,300
And seeing something like this 
in CD projekt Reds announcement 

219
00:10:13,300 --> 00:10:14,900
about. 
We would appreciate if you gave 

220
00:10:14,900 --> 00:10:19,100
us a chance, you know, those 
chances were six years ago and I

221
00:10:19,100 --> 00:10:23,100
think that day one, you pay 60 
bucks or prior to that, you pay 

222
00:10:23,100 --> 00:10:25,600
60 bucks. 
It's really not a chance 

223
00:10:25,600 --> 00:10:27,600
anymore. 
This is just be sort of throwing

224
00:10:27,600 --> 00:10:29,600
away your money for a game that 
isn't complete. 

225
00:10:29,800 --> 00:10:32,900
Oh, those people who are having 
issues and I'm not going to 

226
00:10:32,900 --> 00:10:36,000
really pretend that CD, projekt 
Red isn't great with after 

227
00:10:36,000 --> 00:10:40,400
launch support and why we should
expect that there are a massive 

228
00:10:40,400 --> 00:10:43,000
number of people working at that
company, that should be 

229
00:10:43,000 --> 00:10:46,100
utilizing themselves as support 
for bugs, but that's like being 

230
00:10:46,100 --> 00:10:49,100
surprised that many planes, 
carry, many passengers. 

231
00:10:49,300 --> 00:10:52,800
You don't celebrate that and you
don't really celebrate the fact 

232
00:10:52,800 --> 00:10:56,900
that they require that they also
also said he stated that, they 

233
00:10:56,900 --> 00:11:00,900
had one patch prepped and 
another for After the holidays, 

234
00:11:00,900 --> 00:11:05,300
meaning that, if your patch 
doesn't fix these issues, Little

235
00:11:05,300 --> 00:11:07,900
Jimmy's not going to be playing 
this game for Christmas, which I

236
00:11:07,908 --> 00:11:12,900
think is really pretty sad. 
I think for gamers usually 

237
00:11:13,100 --> 00:11:15,800
expect, a relatively bug, free 
product. 

238
00:11:15,800 --> 00:11:19,100
And that brings me to my last 
Point as I was informed 

239
00:11:19,100 --> 00:11:20,900
recently. 
I've discussed with many people,

240
00:11:21,100 --> 00:11:25,000
they just don't feel prepared to
discuss bugs in some kind of 

241
00:11:25,000 --> 00:11:27,000
coverage. 
I'm not sure what to say to 

242
00:11:27,000 --> 00:11:29,600
that, but I would say get 
comfortable because these are 

243
00:11:29,700 --> 00:11:33,600
are not unique. 
The situation is not new and 

244
00:11:33,600 --> 00:11:36,900
it's been a repetitive problem 
that we've had multiple times 

245
00:11:36,900 --> 00:11:41,200
and that really disturbs me. 
So anyway, that's my 2 bits of 

246
00:11:41,200 --> 00:11:43,100
basic news. 
I'm going to jump into this in 

247
00:11:43,100 --> 00:11:46,100
podcast form a little bit more 
and talk about, I'm going to 

248
00:11:46,100 --> 00:11:50,900
talk first about codemasters 
and, you know, getting purchased

249
00:11:50,900 --> 00:11:53,700
by EA. 
So a lot of people do bring up. 

250
00:11:53,700 --> 00:11:56,000
And by the way, if you get a 
chance, subscribe, all that kind

251
00:11:56,000 --> 00:11:57,600
of stuff. 
Follow me on Spotify if you want

252
00:11:57,600 --> 00:11:59,300
to leave now. 
Hey, go ahead. 

253
00:11:59,300 --> 00:12:01,800
It'll ruin. 
I washed my watch time but if 

254
00:12:01,800 --> 00:12:04,100
you want to stick around just 
going to break these down a 

255
00:12:04,108 --> 00:12:08,400
little bit more. 
So codemasters buying or getting

256
00:12:08,400 --> 00:12:11,800
bot, is just another event where
we're seeing a lot of these 

257
00:12:11,800 --> 00:12:15,100
companies end up under the 
umbrella of EA which has had 

258
00:12:15,400 --> 00:12:18,900
what I would consider to be a 
fairly tumultuous kind of 

259
00:12:18,900 --> 00:12:22,300
history with a purchasing 
developers and a lot of people 

260
00:12:22,300 --> 00:12:24,000
will look at Microsoft and say 
the same thing. 

261
00:12:24,000 --> 00:12:25,900
And I look at Microsoft and I'm 
like, well at least a lot of 

262
00:12:25,900 --> 00:12:28,900
those companies are still there.
When you look at EA it's just a 

263
00:12:28,900 --> 00:12:31,400
graveyard. 
It's just a graveyard and 

264
00:12:31,400 --> 00:12:33,600
there's enough issues. 
It's going to be interesting to 

265
00:12:33,600 --> 00:12:37,300
see what they pull off and how 
and sort of how they want to go 

266
00:12:37,300 --> 00:12:38,800
forward. 
Because I've always felt that 

267
00:12:38,800 --> 00:12:42,600
there's a DNA for a lot of 
companies games dirt, right grid

268
00:12:42,800 --> 00:12:45,900
even Formula One, there's 
something about them and there's

269
00:12:45,900 --> 00:12:48,500
something about those games that
you can sort of go, I get it 

270
00:12:48,600 --> 00:12:50,300
right. 
Like I know who this is from 

271
00:12:50,300 --> 00:12:53,400
just like a Ubisoft game whether
you like them or dislike them. 

272
00:12:53,500 --> 00:12:56,600
A lot of times you go I sort of 
know where that's from or who 

273
00:12:56,600 --> 00:13:01,300
that's from and I want to see 
how EA Yay is going to change 

274
00:13:01,300 --> 00:13:05,100
that because it hasn't been a 
great track record for them. 

275
00:13:05,100 --> 00:13:08,900
And codemasters as a whole, I've
been pretty happy with their 

276
00:13:08,900 --> 00:13:12,100
output and pretty, I think that 
there are not necessarily super 

277
00:13:12,100 --> 00:13:13,800
high quality on all of their 
titles. 

278
00:13:13,800 --> 00:13:17,200
But quality enough on many of 
their titles that I like their 

279
00:13:17,200 --> 00:13:19,900
output and I really wouldn't 
want that to change very much 

280
00:13:19,900 --> 00:13:23,800
and I think with 2K there was a 
higher chance of them just sort 

281
00:13:23,800 --> 00:13:26,000
of being their own thing and 
moving forward. 

282
00:13:26,000 --> 00:13:28,100
Now we don't know this could all
change, right? 

283
00:13:28,100 --> 00:13:29,500
This could all change in 
suddenly. 

284
00:13:29,700 --> 00:13:33,000
Magically they're just given 
free rein and we see no changes 

285
00:13:33,000 --> 00:13:35,400
whatsoever. 
But then you have to wonder why 

286
00:13:35,400 --> 00:13:39,100
a company buys them for that 
much money for no reason to not 

287
00:13:39,100 --> 00:13:40,900
change them. 
And to not maybe take some of 

288
00:13:40,908 --> 00:13:45,000
their talent and move it around,
maybe we'll see new racing types

289
00:13:45,000 --> 00:13:47,700
introduced but I certainly don't
want to see the death of the 

290
00:13:47,700 --> 00:13:50,800
games that they have released in
the past because I pretty much 

291
00:13:50,800 --> 00:13:52,800
like most of them. 
And the next thing I want to 

292
00:13:52,800 --> 00:13:54,000
talk about more of a podcast 
form. 

293
00:13:54,000 --> 00:13:55,600
Is these reviews in this 
situation? 

294
00:13:55,600 --> 00:13:58,300
It sucks guy's. 
It sucks because I think a lot 

295
00:13:58,300 --> 00:13:59,600
of people look forward to this 
game. 

296
00:13:59,800 --> 00:14:02,800
And a lot of people are enjoying
it and I think, you know, when 

297
00:14:02,800 --> 00:14:05,200
somebody sees a video like this,
they're like, oh man, you know, 

298
00:14:05,200 --> 00:14:08,600
it's - Bubba blot it is. 
It is a negative situation and 

299
00:14:08,600 --> 00:14:10,700
the company agrees. 
It's negative, because they're 

300
00:14:10,700 --> 00:14:13,900
the ones who actually released 
the the stuff, the, the 

301
00:14:13,900 --> 00:14:15,600
announcement. 
So that's on you to go talk to 

302
00:14:15,600 --> 00:14:18,300
them, if you disagree. 
But to those people who bought 

303
00:14:18,300 --> 00:14:21,400
this game and who look forward 
for multiple years, you're 

304
00:14:21,400 --> 00:14:24,100
looking down the barrel of a 
bug, just waiting to happen. 

305
00:14:24,200 --> 00:14:26,900
And, you know, I get that some 
people don't notice those and 

306
00:14:26,900 --> 00:14:29,200
some people do and I get to some
people can ignore them. 

307
00:14:29,700 --> 00:14:31,900
One of the things I've always 
stated about bugs, that's always

308
00:14:31,900 --> 00:14:34,900
shocked me. 
Is how few people want to talk 

309
00:14:34,900 --> 00:14:37,600
about them when it comes to 
coverage of any kind of 

310
00:14:37,600 --> 00:14:40,500
Impressions, I've even covered 
them in previews, I mean, not 

311
00:14:40,500 --> 00:14:42,800
like a crash or something like 
that in a preview, if it's 

312
00:14:42,800 --> 00:14:45,700
months ahead of time, but if you
just noticing something that 

313
00:14:45,700 --> 00:14:48,900
maybe appears like, it could be 
a bug, or it could be a shallow 

314
00:14:48,900 --> 00:14:51,500
feature more shallow than 
they're admitting that kind of 

315
00:14:51,508 --> 00:14:52,800
thing. 
And then, of course, when you 

316
00:14:52,800 --> 00:14:54,000
get into reviews, it's even 
more. 

317
00:14:54,000 --> 00:14:55,800
So when you get into streaming, 
it's more. 

318
00:14:55,800 --> 00:14:58,100
So if you can, if I stream a 
game, you guys know me, if I'm 

319
00:14:58,100 --> 00:14:59,400
screaming, I'm pretty much 
reviewing it. 

320
00:14:59,800 --> 00:15:03,900
Like that, you'll hear me, 
Baton, you know, onto something 

321
00:15:03,900 --> 00:15:06,000
and bitching about something or 
loving something. 

322
00:15:06,000 --> 00:15:09,300
If I see it in a review, I 
really can't keep, you know, 

323
00:15:09,300 --> 00:15:12,100
quiet about the things that I 
like or dislike when it comes to

324
00:15:12,100 --> 00:15:14,600
those. 
But I just really hope that we 

325
00:15:14,600 --> 00:15:18,100
can get out of this CD, projekt 
Red does have good support for 

326
00:15:18,100 --> 00:15:21,400
after, you know, after time 
support I have heard people say 

327
00:15:21,400 --> 00:15:25,000
Witcher 3 was buggy as well. 
It was nowhere near. 

328
00:15:25,000 --> 00:15:27,300
I did go and check. 
I looked at some SEO stuff. 

329
00:15:27,300 --> 00:15:31,200
I looked at videos all kinds. 
Of stuff there was, it was 

330
00:15:31,200 --> 00:15:35,000
definitely buggy but it's not 
even close to the massive level 

331
00:15:35,000 --> 00:15:38,100
that we're seeing with this 
current game and as somebody, 

332
00:15:38,100 --> 00:15:41,200
who's a big cyberpunk fan, I 
can't wait to see them patch 

333
00:15:41,200 --> 00:15:44,600
this up to really get an idea of
what it's going to offer. 

334
00:15:44,600 --> 00:15:47,700
My review will be done before 
most of these patches fix 

335
00:15:47,700 --> 00:15:50,700
anything, but I definitely want 
to experience this at some 

336
00:15:50,700 --> 00:15:52,700
point. 
You know, once it's fixed up, 

337
00:15:52,700 --> 00:15:56,400
maybe once some DLC, adds some 
life to that City, and some 

338
00:15:56,400 --> 00:16:01,300
other issues that we see, it's 
just Always remember there's a 

339
00:16:01,308 --> 00:16:03,600
lot of games out there. 
Phoenix risings out there, if 

340
00:16:03,600 --> 00:16:05,800
you're if you're thinking hey 
man, I might wait till this gets

341
00:16:05,800 --> 00:16:07,600
patched up a little bit, check 
that out. 

342
00:16:07,600 --> 00:16:10,500
There's a lot of games that have
come out under the radar, call 

343
00:16:10,500 --> 00:16:13,900
of the sea and you might just 
want to look at those because 

344
00:16:14,000 --> 00:16:16,700
spending 60 bucks on something 
that may just be a technical 

345
00:16:16,700 --> 00:16:18,800
disaster for you might not be 
the best bet. 

346
00:16:18,900 --> 00:16:21,400
It's up to you, right? 
Everybody is different. 

347
00:16:21,400 --> 00:16:24,000
All I gotta say. 
Is this, hope you guys all have 

348
00:16:24,000 --> 00:16:26,300
an excellent week. 
I hate to have to report news 

349
00:16:26,300 --> 00:16:29,200
that seems overly negative, but 
this has been an overly negative

350
00:16:29,200 --> 00:16:31,700
situation. 
No, and I'm not going to cower 

351
00:16:31,700 --> 00:16:34,400
from it, regardless. 
So anyway, that's it for me. 

352
00:16:34,400 --> 00:16:36,700
If you get a chance, subscribe, 
I would love for you to go to 

353
00:16:36,700 --> 00:16:38,900
Facebook and read it in Twitter 
and all that follow me on 

354
00:16:38,900 --> 00:16:41,100
Twitter. 
Peace, out and enjoy the rest of

355
00:16:41,100 --> 00:16:41,300
your
