Sindonesia Posted October 4, 2015 Posted October 4, 2015 I just started playing Destiny again and I have followed all the Destiny setup guides. My problem is every crucible match I get in is incredibly laggy. Is there something everyone is doing outside of the Netduma wiki instructions? It's unplayable at the moment. Thanks for any help.
jarra87 Posted October 5, 2015 Posted October 5, 2015 go watch triple wrecks video he will show u , as he is a massive cruicble player
Administrators Netduma Fraser Posted October 5, 2015 Administrators Posted October 5, 2015 What exactly are the settings you're using? PA 0, strict off etc?
Chive972 Posted October 5, 2015 Posted October 5, 2015 I just started playing Destiny again and I have followed all the Destiny setup guides. My problem is every crucible match I get in is incredibly laggy. Is there something everyone is doing outside of the Netduma wiki instructions? It's unplayable at the moment. Thanks for any help. You can follow those instructions: 1) On the geo-filter: you can put 500km and 0ms on Ping assist 2) Disable Upnp and add those ports in port forwarding: 3) Make sure that you have a static IP on the router and the same configuration on the PS4
Ace_Uk1000 Posted October 5, 2015 Posted October 5, 2015 When I play crucble with strict on i'm getting grey padlocks appearing. Anyone know what these mean?
PharmDawgg Posted October 5, 2015 Posted October 5, 2015 Great padlocks usually mean dedicated servers are being blocked. http://wiki.netduma.com/doku.php?id=geo-filter_symbols
Ace_Uk1000 Posted October 5, 2015 Posted October 5, 2015 Thanks. So why are theses servers being blocked by my duma then?
PharmDawgg Posted October 5, 2015 Posted October 5, 2015 They are either being blocked because you have strict mode on and they are outside of your Geofilter range or that they do not meet the qualifications of your Ping assist value. http://wiki.netduma.com/doku.php?id=destiny_crucible&s[]=strict As a sidenote some servers may be mislocated.
Sindonesia Posted October 5, 2015 Author Posted October 5, 2015 What exactly are the settings you're using? PA 0, strict off etc?Strict offPA 0 Geo Filter 625 miles Peer ping ticked Just as the instructions state, it just laggy for some reason.
Chive972 Posted October 5, 2015 Posted October 5, 2015 They are either being blocked because you have strict mode on and they are outside of your Geofilter range or that they do not meet the qualifications of your Ping assist value. http://wiki.netduma.com/doku.php?id=destiny_crucible&s[]=strict As a sidenote some servers may be mislocated. Do you think that if you put your PA to 80ms with strict mode, it will work?
PharmDawgg Posted October 5, 2015 Posted October 5, 2015 You could try. But from what the Netduma admins are saying is Ping Assist does not work with Destiny because there is no single host. The way the game is set up everyone is seen as a host.
Administrators Netduma Fraser Posted October 5, 2015 Administrators Posted October 5, 2015 Strict off PA 0 Geo Filter 625 miles Peer ping ticked Just as the instructions state, it just laggy for some reason. You can try strict on, this will get better games but you may experience booting. Your distance is a little small, I'd say a couple hundred extra miles with strict off should work
Sindonesia Posted October 5, 2015 Author Posted October 5, 2015 No luck, I bumped it up to 1200 miles and turned strict on. I live in the middle of the U.S., so that pretty much covers the entire U.S., no need for strict than.
Sindonesia Posted October 5, 2015 Author Posted October 5, 2015 You can follow those instructions: 1) On the geo-filter: you can put 500km and 0ms on Ping assist 2) Disable Upnp and add those ports in port forwarding: 3) Make sure that you have a static IP on the router and the same configuration on the PS4 Thanks, trying this now.
Administrators Netduma Fraser Posted October 5, 2015 Administrators Posted October 5, 2015 Let us know how you get on, I would recommend strict off though, you can also try moving your home location around as well
Sindonesia Posted October 6, 2015 Author Posted October 6, 2015 Port forwarding is working so far. I have geofilter 1200, PA 0 and Strict off. I'm currently using the 1.03.5h, I don't know why upnp isn't as effective.
Administrators Netduma Fraser Posted October 6, 2015 Administrators Posted October 6, 2015 Port forwarding is working so far. I have geofilter 1200, PA 0 and Strict off. I'm currently using the 1.03.5h, I don't know why upnp isn't as effective. Great to hear that! It should open all the ports you need but glad to know thats the fix
Spartanogc Posted October 6, 2015 Posted October 6, 2015 I did the port forwarding as suggested but cant log into destiny, I get the marionberry error. Any suggestions
Chive972 Posted October 6, 2015 Posted October 6, 2015 1) Put static IP for your console on the netduma 2) Set the port forwarding rules for that IP 3) Untick the upnp option 4) Reboot the netduma 5) Put the same IP directly on you console 6) Launch Destiny 7) Wreck everyone in the crucible
Chive972 Posted October 6, 2015 Posted October 6, 2015 Port forwarding is working so far. I have geofilter 1200, PA 0 and Strict off. I'm currently using the 1.03.5h, I don't know why upnp isn't as effective. I've got the same problem when i've got my netduma. Upnp won't open all the ports for that game but i don't think it's a problem on the router.
Administrators Netduma Fraser Posted October 6, 2015 Administrators Posted October 6, 2015 I did the port forwarding as suggested but cant log into destiny, I get the marionberry error. Any suggestions Destiny advise the following for this error: Log off of Destiny Turn off your PlayStation or Xbox console Power-cycle your networking hardware (router, modem, etc.) by turning each item off, then waiting 30 seconds before turning them back on one by one, beginning with your modem Once your home network is back up, turn on your PlayStation or Xbox console and relaunch Destiny
Sindonesia Posted October 6, 2015 Author Posted October 6, 2015 1) Put static IP for your console on the netduma 2) Set the port forwarding rules for that IP 3) Untick the upnp option 4) Reboot the netduma 5) Put the same IP directly on you console 6) Launch Destiny 7) Wreck everyone in the crucible Thanks again, this is working great. I haven't done this since I bought the Netduma because it wasn't needed on COD:AW but for some reason Destiny doesn't like upnp on my network.
Chive972 Posted October 6, 2015 Posted October 6, 2015 Thanks again, this is working great. I haven't done this since I bought the Netduma because it wasn't needed on COD:AW but for some reason Destiny doesn't like upnp on my network. Take a look on Advance Warfare: it may improve the hit detection
Recommended Posts
Archived
This topic is now archived and is closed to further replies.