| 1 |
At
this
point
I've
only
my
own
experimentation
to
go
on*,
but
what
I've
found
is
that
(
255,
0,
0)
tends
to
macroblock
a
lot
in
h.
264
compression
when
stuff
is
moving
about,
while
something
more
like
(
255,
65,
65)
maintains
its
definition
even
as
the
scene
changes
around
it.
A
nice
orange,
such
as
(
255,
145,
30)
(
currently
enemy
#3)
is
even
better,
but
since
the
idea
is
to
have
teal
vs
red
for
1v1,
and
not
teal
vs
orange,
I
kept
that
orange
as
enemy
#3.
|
1 |
At
this
point
I've
only
my
own
experimentation
to
go
on*,
but
what
I've
found
is
that
(
255,
0,
0)
[color=FF0000]▓[/color]
tends
to
macroblock
a
lot
in
h.
264
compression
when
stuff
is
moving
about,
while
something
more
like
(
255,
65,
65)
[color=FF4141]▓[/color]
maintains
its
definition
even
as
the
scene
changes
around
it.
A
nice
orange,
such
as
(
255,
145,
30)
[color=FF911E]▓[/color]
(
currently
enemy
#3)
is
even
better,
but
since
the
idea
is
to
have
teal
vs
red
for
1v1,
and
not
teal
vs
orange,
I
kept
that
orange
as
enemy
#3.
|
| 3 |
[color=999999]*since I haven't researched all of the niggly details about how MPEG/JPEG compression algorithms rotate colours, collapse the image into 8x8 blocks containing contrast info, otherwise mess around with things, and why that seems to affect pure red worse than a mix that uses all channels[/color]
|
3 |
[color=999999]*since I haven't researched all of the niggly details about how MPEG/JPEG compression algorithms rotate colours, collapse the image into 8x8 blocks containing contrast info, otherwise mess around with things, and why that seems to affect pure red worse than a mix that uses all channels[/color]
|
Problem with team colors