Head 2 Head Alpha

[superballs]

I'm using the "B" build.

I'm on c but on my nexus on WiFi gets the error. If I use my phone as a hotspot its all good.

 

[netizen]

I'm on c but on my nexus on WiFi gets the error. If I use my phone as a hotspot its all good.

The C Build seems to throw more connection errors, in my experience. It does work, but if you start getting NAT errors, close TPA then restart it to regain connection I find.

 

[superballs]

I noticed that.

I dropped the NAT on my router and have less issues.

Do we know what ports we need to open to make this work?

 

[netizen]

I noticed that.

I dropped the NAT on my router and have less issues.

Do we know what ports we need to open to make this work?

I haven't dropped my NAT or opened any ports and the B build is connecting just fine

 

[superballs]

hmm might install that build

 

[Dylan_h]

I'm using the b build and I'm running into the Nat punchthrough 1 to 2 whenever I try to join the cue both on WiFi and 3g.

 

[jaredmorgs]

Thanks netizen...Unfortunately, I'm getting the "NAT Punchthrough 1 to 2" over my 4GLTE network.

id=14 and id=15

I tried to connect three separate times...restarting the app before each try. I'm still using the "B" build.

EDIT : Tried a fourth time...no dice. id=16

Worked over WiFi on my Galaxy S4 earlier, but doesn't seem to work over 4GLTE using the same device.

I deleted version C, that one does not work for some reason, B version is the debug compiled version of C so it may be laggy in some places. I will start to look into what might be causing that but for now please use B

Ryan thought this might be an issue. He was having all sorts of issues getting 4G connections working.

 

[Ryan Routon]

i was able to get it to work on my 4G, but you may have some kind of firewall. I would have to run some more tests.

 

[Ryan Routon]

has anyone else had issues with 4g connections? I just tested it again and the B version appears to work with my phone w/ 4G. If you are having issues please report the id=# that way I can take a look at the database.

 

[Heretic]

tl;dr ryan dude need pass these thing to the ios team, stewie get in there

 

[switch3flip]

I'm available to play for the next 6 hours. I'm on regular phone internet connection, not wifi or 4g. No problems logging in to que, lets hope playing works out good

 

[switch3flip]

I'll be checking this thread, if anyone will be logging on let me know what time to log in to tpa.

 

[debuggiest]

Cool idea. I think it would be more authentic to see the other player's game, but it's a start at multiplayer. Thanks Ryan!

I'll putz around in the queue and see if anyone's on.

 

[debuggiest]

B build...

On wifi... NAT punchthrough 1 to 2 (id=32)

edit:

On 3G... NAT punchthrough 1 to 2 (id=34)

edit2: id 36/37/38/39/41 as well.

 

[switch3flip]

Ok I will try now also and in 15min.

 

[switch3flip]

Was in que but got NAT message repeatedly with id= 38, 39 and 40.

 

[debuggiest]

Was in que but got NAT message repeatedly with id= 38, 39 and 40.

38 and 39 was me too, were you on wifi or 3G/4G?

 

[switch3flip]

38 and 39 was me too, were you on wifi or 3G/4G?

I was on 3g. I'm at work, don't have wifi here out of security reasons.

 

[xAzatothx]

Got bored of waiting in the queue

 

[netizen]

With it being a proof of concept you need to line up players on chat or via some other means for the time being. The queue will connect the next player to come in with no current ability to select you opponents. It's a bit of a let down if you don't already have some opponents on deck