oh ubisoft... im not buying this crap. | Forums

[Sam_vimes_]

Anyone sharing consoles on the same router? You mentioned your brothers?

no, we all live separately

[AI BLUEFOX]

no, we all live separately

OK, only thing I can suggest is putting consoles in the DMZ if you haven't already. The game is using a P2P connection (common to all Ubisoft games) and running in the DMZ is about the only guaranteed way to connect reliably. Even then, there are some issues if you have more than one console in the same house as most routers can only handle one device with an Open NAT - even if the game tells you the NAT is open, the console may tell you something else.

[ChaosFuture]

So, your absolutely certain its the servers and not you? I've never had any issues with Coop.

Read through the forums. A lot of people are not able to play this game despite hours of at home trial and error. i had the same issues in the closed beta as i am having now.
i left my comments hoping they would be resolved (especially something that is so broke) and now here we are at open beta with the same issues. Ubisoft has not given themselves time to create a fix.
Devs in another post i read last night, saying they are "working on a fix and will be releasing it next week". Who the F*** is playing this game next week???

Regrettably I did not learn my lesson from the Division and Siege. Both are games that had issues, and still to this day have opening day issues present 1 year later.

The for Honor Beta Closed and Open Betas were the same as this.

I wish i could have the game refunded as of today, but will give them the benefit of the doubt to have this game working for everyone on launch day.

[Sam_vimes_]

Read through the forums. A lot of people are not able to play this game despite hours of at home trial and error. i had the same issues in the closed beta as i am having now.
i left my comments hoping they would be resolved (especially something that is so broke) and now here we are at open beta with the same issues. Ubisoft has not given themselves time to create a fix.
Devs in another post i read last night, saying they are "working on a fix and will be releasing it next week". Who the F*** is playing this game next week???

Regrettably I did not learn my lesson from the Division and Siege. Both are games that had issues, and still to this day have opening day issues present 1 year later.

The for Honor Beta Closed and Open Betas were the same as this.

I wish i could have the game refunded as of today, but will give them the benefit of the doubt to have this game working for everyone on launch day.

im glad someone actually understands. you get all these idiots saying "its fine for me" or "i have no problems" yeah great... if you havent had the issues i do you clearly arent helping by stating as much.

then again, like i said in a previous post the fan boys take criticism personally.... almost as if ive personally insulted their mother.

OK, only thing I can suggest is putting consoles in the DMZ if you haven't already. The game is using a P2P connection (common to all Ubisoft games) and running in the DMZ is about the only guaranteed way to connect reliably. Even then, there are some issues if you have more than one console in the same house as most routers can only handle one device with an Open NAT - even if the game tells you the NAT is open, the console may tell you something else.

ive had my ps4 in the dmz and it doesnt help. after port forwarding for siege i tried the dmz and nothing worked. I tried the same for wild lands as it looks like a cool game but its the same old problems.

As i said my brothers also have the same problems and considering its this close to release, it looks as though its going to be the same story as siege.

[AI BLUEFOX]

@mberry, don't open ports and run in the DMZ at the same time if you are doing that.

What NAT states is the game reporting for you and your buddies?