Hi,
I’ve owned the game for a about 5 months. About 2-3 times a night I will have the game straight freeze on me for about 4-5 seconds. Sometimes I will get booted for no reason. I’m assuming the freezing and booting is a connectivity issue, but I don’t have problems with other games. Thoughts?
Thanks.
I haven’t lost connection in a while, been booted or had the game crash.
Your connectivity issues might depend on where you live, and your internet.
Have you tried hard resetting Your Xbox? That might help with the crashing
Hope this helps
> 2533274808396058;1:
> Hi,
>
> I’ve owned the game for a about 5 months. About 2-3 times a night I will have the game straight freeze on me for about 4-5 seconds. Sometimes I will get booted for no reason. I’m assuming the freezing and booting is a connectivity issue, but I don’t have problems with other games. Thoughts?
>
> Thanks.
Probably a lag spike. Happens a lot in warzone. Especially when someone quits
4 or 5 seconds are very long spikes. Most are usually only half that though.
Make sure you are wired with an open NAT. For me the game was unstable on wifi. I did get kicked out of a match today, but so did everyone else, leaving me to believe it was an xbox server issue, but I went back in no problem.
> 2533274875982754;4:
> Make sure you are wired with an open NAT. For me the game was unstable on wifi. I did get kicked out of a match today, but so did everyone else, leaving me to believe it was an xbox server issue, but I went back in no problem.
NAT doesn’t matter when using dedicated servers.
Honesty OP, this seem to be a Halo 5 thing most of the time. That’s the problem when you pretty much have an online game only. I had ZERO issues up until the monitors bounty update (Had Halo 5 since day 1 btw) Only thing that changed on my end was I now have an Xbox One S. Ever since that update I get random disconnects a good amount and the odd freezing. I’ve done everything possible to fix things but after talking to MS and even some 343I people, I’ve come to the conclusion that it’s a Halo 5 thing. MS and company agree with me even. Just make sure you do everything on your ends too.
> 2533274815533909;5:
> > 2533274875982754;4:
> > Make sure you are wired with an open NAT. For me the game was unstable on wifi. I did get kicked out of a match today, but so did everyone else, leaving me to believe it was an xbox server issue, but I went back in no problem.
>
> NAT doesn’t matter when using dedicated servers.
>
> Honesty OP, this seem to be a Halo 5 thing most of the time. That’s the problem when you pretty much have an online game only. I had ZERO issues up until the monitors bounty update (Had Halo 5 since day 1 btw) Only thing that changed on my end was I now have an Xbox One S. Ever since that update I get random disconnects a good amount and the odd freezing. I’ve done everything possible to fix things but after talking to MS and even some 343I people, I’ve come to the conclusion that it’s a Halo 5 thing. MS and company agree with me even. Just make sure you do everything on your ends too.
To minimize random disconnects. Go wired with an open nat. Don’t claim something doesn’t work that works.
> 2533274815533909;5:
> NAT doesn’t matter when using dedicated servers.
NAT always matters.
Moderate and strict NAT add additional latency because the router needs to do more work (just to dumb it down and make it simple).
On top of that comes the fact that most home routers have a very small memory allocation to host guess what - routing tables. So if you have many devices on your network and several people are using them concurrently chances are there is not enough memory for all those requests and the router gets busy just rewriting those tables all the time. Now guess what - that adds latency or in other words lag.
> 2533274875982754;6:
> > 2533274815533909;5:
> > > 2533274875982754;4:
> > > Make sure you are wired with an open NAT. For me the game was unstable on wifi. I did get kicked out of a match today, but so did everyone else, leaving me to believe it was an xbox server issue, but I went back in no problem.
> >
> > NAT doesn’t matter when using dedicated servers.
> >
> > Honesty OP, this seem to be a Halo 5 thing most of the time. That’s the problem when you pretty much have an online game only. I had ZERO issues up until the monitors bounty update (Had Halo 5 since day 1 btw) Only thing that changed on my end was I now have an Xbox One S. Ever since that update I get random disconnects a good amount and the odd freezing. I’ve done everything possible to fix things but after talking to MS and even some 343I people, I’ve come to the conclusion that it’s a Halo 5 thing. MS and company agree with me even. Just make sure you do everything on your ends too.
>
> To minimize random disconnects. Go wired with an open nat. Don’t claim something doesn’t work that works.
> 2533274798332734;7:
> > 2533274815533909;5:
> > NAT doesn’t matter when using dedicated servers.
>
> NAT always matters.
> Moderate and strict NAT add additional latency because the router needs to do more work (just to dumb it down and make it simple).
> On top of that comes the fact that most home routers have a very small memory allocation to host guess what - routing tables. So if you have many devices on your network and several people are using them concurrently chances are there is not enough memory for all those requests and the router gets busy just rewriting those tables all the time. Now guess what - that adds latency or in other words lag.
Ok you guys need to learn networking. NAT matters when connecting peer to peer, it’s true, but not with dedicated servers… oh and guess what, halo 5 uses dedicated servers. NAT has nothing to do with lag, nothing!!! Ping affects lag the most one could argue. An open NAT just allows your machine to “talk” or “see” other machines better. Your NAT status, does NOT, affect ping, upload or download speeds. Having a moderate or strict Nat just restrict you with who you can connect with, THAT’S ALL… But if you connecting to a dedicated server that doesn’t apply because your not connecting peer to peer, your connecting to a central server or client as some people call it. If you really want to know between the two, read this article, it explains it decently…
http://www.techrepublic.com/article/understanding-the-differences-between-client-server-and-peer-to-peer-networks/If you want to experiment put your router in a strict or moderate setting do speed tests, ping tests etc then do it with open. It’ll all be similar. Get someone else to make their router strict and both of you try playing something that’s not on dedicated servers you won’t be able to connect to each other. But if you both play something on dedicated servers you will.
So long story short, if you can get an open NAT great. It’ll help you with connecting and hosting things that aren’t on a dedicated servers aka peer to peer and THAT’S IT!!
As next time before you start calling someone out, go talk to someone who does networking for a living or Google some information first. If you really want to get into super technical stuff I’d be happy to do it but unless you do networking for living, I doubt you’ll understand.
> 2533274815533909;8:
> As next time before you start calling someone out, go talk to someone who does networking for a living or Google some information first. If you really want to get into super technical stuff I’d be happy to do it but unless you do networking for living, I doubt you’ll understand.
Well said but if I may suggest using BING insteal of google and it may enlighten you.
While the NAT type doesn’t influence the core up/download speed or anything like that it has an affect on the load on your router.
The reason for that is simply that with open NAT the router has the least work to do because it sends ALL incoming requests/responds right to your Xbox while in moderate or strict NAT the router will reject data.
Here is how this works:
Xbox connects to the router. The Xbox uses a random port (lets say 15343).
The router now connects to the internet also using a random port on its end (lets say 25343).
These ports are helping the device/server/service they are trying to reach to better identify them and send the proper data back to them.
Now with open NAT every data from anyone on the internet that reaches our router on port 25343 will be directly sent to that Xbox using port 15343.
With moderate NAT the router will only forward data from the original host to which the request was made and will reject any other host (a host in this case for example is www.waypoint.com so if the initial request was to www.waypoint.com and now www.microsoft.com would send data back that would be rejected).
With strict NAT the router will take an even closer look at the incoming data and will reject everything that doesn’t come not only from the original host but it also has to come from the very same port the initial request was sent to (so if a request was sent to www.waypoint.com on port 80 and now www.waypoint.com sends a response from its own port 443 that router with strict NAT will reject that data).
Now a cheap router doesn’t have a very powerful CPU and performing all those rejections puts more load on the router’s CPU than simply forwarding all that data to the Xbox.
From a security point open NAT actually is more of a security nightmare but that is a different story.