G_or_Gazz

Hi, there is a moderator who has done extensive testing for Destiny. His name is Chive. This link will take you to his profile page and if you click on 'Topics' you will get a great guide. http://forum.netduma.../1066-chive972/ Destinys matchmaking uses servers in the actual matchmaking process, the connections are peer-to-peer based. It gets a little complex as certain players host specific aspects of the gameplay. This can make it lag for some, whilst being good for others. Personally, I don't see the benefit of setting ranges for Destiny, others think that they have some success. When you look at how the servers matchmake, then you would probably deduce that setting range is going to have little if any effect. Your best bet is to follow Chive's guide and then have nights where you change one setting to see how it effects your "instance". All in all, the Duma will ensure you have the best connection you can get, then its praying that you see few players hosting mechanics aspects during your play sessions. Destiny 2 revises the issue of mechanics with bad hosts, simply by hosting the mechanics on their servers. The actual connections will remain peer-to-peer. This should bring greater balance to the crucible. Good Luck

Hi, there is a moderator who has done extensive testing for Destiny. His name is Chive. This link will take you to his profile page and if you click on 'Topics' you will get a great guide. http://forum.netduma.com/user/1066-chive972/ Destinys matchmaking uses servers in the actual matchmaking process, the connections are peer-to-peer based. It gets a little complex as certain players host specific aspects of the gameplay. This can make it lag for some, whilst being good for others. Personally, I don't see the benefit of setting ranges for Destiny, others think that they have some success. When you look at how the servers matchmake, then you would probably deduce that setting range is going to have little if any effect. Your best bet is to follow Chive's guide and then have nights where you change one setting to see how it effects your "instance". All in all, the Duma will ensure you have the best connection you can get, then its praying that you see few players hosting mechanics aspects during your play sessions. Destiny 2 revises the issue of mechanics with bad hosts, simply by hosting the mechanics on their servers. The actual connections will remain peer-to-peer. This should bring greater balance to the crucible. Good Luck

if a user manual is under construction, then usability must be almost. if not already complete that leaves the fun stuff, which must be user implementation

https://www.reddit.com/r/DestinyTheGame/comments/6g3laj/how_networking_works_in_destiny_1_and_how_it_will/?st=J3PXFXZP&sh=b2788987 If you can get your head around this, it explains the current Destiny lag scenario, along with predictions for Destiny 2 changes.

Do you switch the superhub to modem mode? Run a factory reset on the netduma, enter the new bandwidth, enable cookies, sliders at 100% and retest. If you need to switch the superhub back to router services, 192.168.100.1 is the address it normally gains in modem mode.

Geoip will work but only when P2P is host based, and when others are not trying to gatecrash via a vpn service. Location and ping are directly related. There are two normal factors that significantly influence the latency of a consumer device (like a cable modem, dsl modem or dial-up modem). The latency of the connecting device. For a cable modem, this can normally be between 5 and 40 ms. For a DSL modem this is normally 10 to 70ms. For a cellular link, this can be from 200 to 600 ms. For a T1, this is normally 0 to 10 ms. The distance the data is traveling. Data travels at (very roughly) 120,000 miles (or 192,000 kilometers) per second, or 120 miles (192 km) per ms (millisecond) over a network connection. With traceroute, we have to send the data there and back again, so roughly 1 ms of latency is added for every 60 miles (96km, although with the level of accuracy we're using here, we should say '100km') of distance between you and the target. Connecting to a web site across 1500 miles (2400 km) of distance is going to add at least 25 ms to the latency. Normally, it's more like 75 after the data zig-zags around a bit and goes through numerous routers. Packet loss is generally line quality, which will be internal or upto the local cabinet. Matchmaking in Destiny is like flying your spacecraft to their servers, where they assess your connection, match your skill and then try to geoip you themselves. Traffic at the start of the process is low, resulting in bad matchmaking in that sector. Then when the game starts and traffic increases, opponents connections are pot luck. Before I switched to an R1 I ran several different "custom" router firmwares. DD-WRT graphs spring to mind where connections would increase to 5mb bandwidth shortly before you see which map you are on. They would generally then settle at 1mb, with respawn jumping bandwidth back upto 1.5mb. This in my opinion is one of the main reasons why connections can be so varied after the matchmaking phase. From the bits I read on here, packet loss for an R1 user will improve again in the next OS. Which again will be a slight improvement, I just don't see how a mesh can work well for this type of application (Destiny PVP), when there are so many variables. The salt is in Bungie's own words for D2, they are trying to balance good and bad connections. The reasoning behind this is fair enough, some can not get high speeds, never mind line quality. In the UK, openreach and VM are pressing forwards with upgrades and expansion. We, as one of two companies supplying them both are manufacturing just under 1000 street cabinets per month alone. The cost of a BT twin door cab is around £30k on the street. They are throwing money at it. None of this is relevant when it appears to be red bar galore in the crucible. Until people want a fair fight, the biggest problem will remain as artificially manufacturing poor connections, unknowingly or purposely, in the homes of players. Needless to say, as I already have, with increased population for at least 9 months and hopefully for at least 18 months, everyone should see less lag in D2 and the probability of an R1 assisting your game, is high. The best pm you can send a lagger then, a web link to a pair of ethernet homeplugs???

Physics going to the the cloud should bring more consistency to RoF/RPM lag issues, which should mean everyone can run away faster. High impact slow firing yet fast hitting scouts for example, shouldn't hit you like an auto rifle. Destiny's mesh would work brilliant in a LAN setup... To begin D2 will be less laggy, its after 18 months that the revised cloud system will prove its worth, or not. If your R1 is set up correct, it should always reduce how bad a lobby of laggers you end up with, everything has its limits though. If there is only laggers playing, you will see lag but the new cloud physics should prevent them visibly benefiting from it, (just cloaked perks then...). You could supply powerline adapters with a game, yet there are some that wouldn't use them to try to gain an advantage. You can't beat a cheat but you can limit how much they effect you with an R1, usually 4's in itself will help stability in PvP.

I haven't found game time in about 4 weeks, so I don't know the current state of PvP. What I can tell you is that there is very little point using the geo filter on anything but max range, (especially in ToO), in the current and future Destiny games. To simplify the reasoning behind this, you are never connected to everyone. Bungie have always implemented a mesh in Destiny. When I first wired in my netduma, I was confident it made a difference to local games. In reality population in Destiny would most likely have been higher than nowadays. The best way to compare, turn geo-filter on, set to max range for a couple of games, watch where your players are. After a few games set to 1k range or whatever you use and watch again. So why use a netduma. The overall reasoning is CBMM, no matter how low they put this against SBMM, your prime focus need to be on having the best so you are LESS likely to be MM with the "laggers". With Destiny 2 the aim is to make the PvP game 100% global. In theory this will be more beneficial after two years and a dwindling population base. With Destiny currently and probably for the last 12 months, I feel laggers came to the game on wind of bad connections rule... You may have your own opinions or idea's regarding my text, I do not work for Bungie or Neduma but supply ISP's with hardware like BT type 7 street boxes, VM street cabs, to internal server gear. My knowledge is far from expert, yet found from logical chains. Last weeks Bungie news points you to look, if you look to find. Run the range test, think about how a mesh works, read up on page 7 of the document found http://www.gdcvault.com/play/1022247/Shared-World-Shooter-Destiny-s Add all this up and hoping for consistent in a game 2.5 years old, is futile. Similar to life, enjoy the good games, limit the damage in the bad games. Good Luck Guardians