Jump to content

Destiny Crucible


Recommended Posts

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.

Link to comment
Share on other sites

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:

1444044294-ports.png

 

3) Make sure that you have a static IP on the router and the same configuration on the PS4

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

What exactly are the settings you're using? PA 0, strict off etc?

Strict off

PA 0

Geo Filter 625 miles

Peer ping ticked

Just as the instructions state, it just laggy for some reason.

Link to comment
Share on other sites

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?

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • Administrators

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

Link to comment
Share on other sites

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:

1444044294-ports.png

 

3) Make sure that you have a static IP on the router and the same configuration on the PS4

Thanks, trying this now.

Link to comment
Share on other sites

  • Administrators

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 :)

Link to comment
Share on other sites

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  :D

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

  • Administrators

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:

  1. Log off of Destiny
  2. Turn off your PlayStation or Xbox console
  3. 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
  4. Once your home network is back up, turn on your PlayStation or Xbox console and relaunch Destiny
Link to comment
Share on other sites

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 :D

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.
Link to comment
Share on other sites

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

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...