ESEA Invite: ATTACK OF THE YOMIES!!! Double Header

#31

x3

-1 Frags – +

wow i hope it will happend
need that tf2 stream injection

#32

corsa

-1 Frags – +

google.com usually works cj

#33

desca

11 Frags – +

http://www.reddit.com/r/GlobalOffensive/comments/36o0c9/boycott_esea/

#34

aim-

-6 Frags – +

descahttp://www.reddit.com/r/GlobalOffensive/comments/36o0c9/boycott_esea/

and u wont play another tf2 match in ur life

[quote=desca]http://www.reddit.com/r/GlobalOffensive/comments/36o0c9/boycott_esea/[/quote]
and u wont play another tf2 match in ur life

#35

CJ-

3 Frags – +

Posting this here since this is what caused the 1st match to not get played (the second needed a manual admin reschedule which couldn't be done due to the esea site being down).

I was getting Error #112:

http://i.imgur.com/FsegOav.png

Apparently the issue relates to having a virtual machine on your computer (whatever hypervisorlaunchtype affects). Open cmd prompt with admin and type "bcdedit /set hypervisorlaunchtype off", then restart and it should work. (ESEAthread for reference)

Anyways, it's still pretty weird that this issue has come up only with their most recent client-always-on thing. I'm pretty sure that this setting actually prevents you from running certain virtual machines on certain computers (I THINK that I had this setting on because of some Android emulator that I tried to use at some point, which refused to work unless this Hyper-V setting was changed). It might just be ESEA trying to prevent cheating through virtual machines. Whatever.

Posting this here since this is what caused the 1st match to not get played (the second needed a manual admin reschedule which couldn't be done due to the esea site being down).

I was getting Error #112: [img]http://i.imgur.com/FsegOav.png[/img]

Apparently the issue relates to having a virtual machine on your computer (whatever hypervisorlaunchtype affects). Open cmd prompt with admin and type "bcdedit /set hypervisorlaunchtype off", then restart and it should work. [url=http://webcache.googleusercontent.com/search?q=cache:hduZg3twCtUJ:play.esea.net/index.php%253Fs%253Dforums%2526d%253Dtopic%2526id%253D662994+&cd=4&hl=en&ct=clnk&gl=us](ESEAthread for reference)[/url]

Anyways, it's still pretty weird that this issue has come up only with their most recent client-always-on thing. I'm pretty sure that this setting actually prevents you from running certain virtual machines on certain computers (I THINK that I had this setting on because of some Android emulator that I tried to use at some point, which refused to work unless this Hyper-V setting was changed). It might just be ESEA trying to prevent cheating through virtual machines. Whatever.

#36

CHERRY

0 Frags – +

Soo, was the second match played in the end?

#37

Dasmem

0 Frags – +

CHERRYSoo, was the second match played in the end?

Nope

[quote=CHERRY]Soo, was the second match played in the end?[/quote]
Nope

#38

CHERRY

0 Frags – +

DasmemCHERRYSoo, was the second match played in the end?Nope

Damn it DDoSers. Maybe if ESEA was up it'd be easier to settle this up.
Why would anyone care about privacy if it stops you from playing computer games.

[quote=Dasmem][quote=CHERRY]Soo, was the second match played in the end?[/quote]
Nope[/quote]
Damn it DDoSers. Maybe if ESEA was up it'd be easier to settle this up.
Why would anyone care about privacy if it stops you from playing computer games.

#39

owl

1 Frags – +

I don't think you can blame esea for getting ddosed. Some reddit retard is to blame there.

#40

CHERRY

3 Frags – +

owlI don't think you can blame esea for getting ddosed. Some reddit retard is to blame there.CHERRYDamn it DDoSers

[quote=owl]I don't think you can blame esea for getting ddosed. Some reddit retard is to blame there.[/quote]
[quote=CHERRY]Damn it DDoSers[/quote]

#41

CHERRY

0 Frags – +

https://saloon.tf/match/386/