Administrators Netduma Fraser Posted August 10, 2016 Administrators Posted August 10, 2016 Can anyone with this issue please do the following: Ensure everything is appearing as it should by adhering to this guide: http://support.netduma.com/en/support/solutions/articles/16000022408-why-can-t-i-see-anything-on-the-geo-filter- Ensure auto & bleeding edge cloud is enabled & apply. Apply even if they are already selected - this will flush the cloud. If you have strict off look at the map when you get one of these errors, do you see anything being blocked? If so please click it and get the ID and then let me know what it is please. If the Geo-filter is disabled and it still occurs then it cannot be the router as it won't be blocking anything. ------- @ninja I'll reply in your personal thread
mike Posted August 10, 2016 Posted August 10, 2016 i have had to max out the distance on the radar thing to log on , heres the info if thats any use ID: d8cd39046a77e5ea Distance: 6587km
frustrated Posted August 10, 2016 Posted August 10, 2016 Yep ive now had thhe error, couldnt even get to character page and error code marionberry... So untick geo all ok, but forum on bungies shows a big issue on there side again...
mike Posted August 10, 2016 Posted August 10, 2016 it seems they fixed an error that i hadnt seen reports about to actually create the error they fixed what sort of idiocy is that ?
frustrated Posted August 10, 2016 Posted August 10, 2016 Tell ya Mike dont no why we play this game sometimes, joke really.
mike Posted August 10, 2016 Posted August 10, 2016 if it wernt for the fact im stuck in neverwinter i would leave destiny and play neverwinter lol
ChrisCohen Posted August 10, 2016 Author Posted August 10, 2016 Its pretty infuriating having to disable geo-filter every time I log in and then re-enable it once I'm connected.
antithesis Posted August 10, 2016 Posted August 10, 2016 This is easy to fix. Enable "Show Dormant Hosts" in the geo-filter settings, then watch the map when you boot the game. It looks like Destiny is now pinging an authentication server in the USA. Simply increase the size of the geo-filter to cover the USA while logging in, then scale it back to your regular size. Titanfall on XB1 does the same thing, which is why I suspected this would work.
mike Posted August 10, 2016 Posted August 10, 2016 some good ideas popping up here and thanks gamers , but tbh we shouldnt have to do this bungLe did an update it created an error for i think 3 ppl (joke/sarcasm) and they removed it and went back to an earlier build and created a bigger problem (no suprise there) for a larger player base , and bungle say its our network/isp/router/wrong coloured dog/wrong leaves on the line/wrong type of snow/wrong type of sun/theres a Y in the day/vowel in the month but its deffo not bungles fault .............
ChrisCohen Posted August 11, 2016 Author Posted August 11, 2016 This is easy to fix. Enable "Show Dormant Hosts" in the geo-filter settings, then watch the map when you boot the game. It looks like Destiny is now pinging an authentication server in the USA. Simply increase the size of the geo-filter to cover the USA while logging in, then scale it back to your regular size. Titanfall on XB1 does the same thing, which is why I suspected this would work. I spotted this. I tried making that server an allowed host outside of my geofilter and it hasn't worked which leads me to believe it might be more than just that, causing the error. Surely if I've told my duma to always allow that server then it doesn't matter whether my geofilter is on or not?
frustrated Posted August 11, 2016 Posted August 11, 2016 It's a bungie issue,supose we have to ride the storm again,ridiclous really.
Chive972 Posted August 11, 2016 Posted August 11, 2016 I spotted this. I tried making that server an allowed host outside of my geofilter and it hasn't worked which leads me to believe it might be more than just that, causing the error. Surely if I've told my duma to always allow that server then it doesn't matter whether my geofilter is on or not? That's a very good discovery. If you can, wrote the ID here and Fraser will be able to add this server in the cloud.
antithesis Posted August 11, 2016 Posted August 11, 2016 That's a very good discovery. If you can, wrote the ID here and Fraser will be able to add this server in the cloud. d7cd39046a76e5ea
wils1337 Posted August 11, 2016 Posted August 11, 2016 Another Australian having the same issue.If I power cycle my modem I can log in. But if I log out of Destiny I get Marion Berry again and have to restart modem again.GEO off or on made no differenceI followed Bungo's guide to fix it and no better.
SmallCaps Posted August 11, 2016 Posted August 11, 2016 Same for me when playing Destiny a couple of days now. Marionberry and then kicked out. Set "filter by distance" to 9500 km and it will work again.
frustrated Posted August 11, 2016 Posted August 11, 2016 I played rumble today with Geo on OK,i started the game with Geo off,but once in the game worked on with geo on.
antithesis Posted August 11, 2016 Posted August 11, 2016 Another Australian having the same issue. If I power cycle my modem I can log in. But if I log out of Destiny I get Marion Berry again and have to restart modem again. GEO off or on made no difference I followed Bungo's guide to fix it and no better. I'm in Oz too. Just drag the geo-map all the way out to global to let the game ping the US server. Once logged in, drag it back down to your preferred scope.
Administrators Netduma Fraser Posted August 11, 2016 Administrators Posted August 11, 2016 Hey guys, make sure you have all ports forwarded for the game as shown here: https://www.bungie.net/en/Help/Troubleshoot?oid=13610 Also with the ID's given I've done a test cloud. Please un tick bleeding & auto cloud in settings > miscellaneous and manually choose these: 20 14 25 Keep in mind it may take up to 4 hours for the cloud to propagate. Try with Geo-filter enabled/disabled and let me know how you get on.
Mantrid Posted August 11, 2016 Posted August 11, 2016 I allowed host with id: d7cd39046a76e5ae through my geofilter and now I can load Destiny with the geofilter enabled and I don't get the error
frustrated Posted August 11, 2016 Posted August 11, 2016 Will do but never port forwarded before,seems odd..anyway will do on the auto cloud etc
frustrated Posted August 11, 2016 Posted August 11, 2016 I also added a server in central Usa d8cd39046a77e5ea and now works with geo on.
Administrators Netduma Fraser Posted August 11, 2016 Administrators Posted August 11, 2016 That's great to hear! Make sure to remove it from your allow list as it is white listed in the test cloud
ChrisCohen Posted August 11, 2016 Author Posted August 11, 2016 Hey everyone, is there a way to manually add that host of the server as an allowed address, by inputting the mac address?
ChrisCohen Posted August 11, 2016 Author Posted August 11, 2016 Hey guys, make sure you have all ports forwarded for the game as shown here: https://www.bungie.net/en/Help/Troubleshoot?oid=13610 Also with the ID's given I've done a test cloud. Please un tick bleeding & auto cloud in settings > miscellaneous and manually choose these: 20 14 25 Keep in mind it may take up to 4 hours for the cloud to propagate. Try with Geo-filter enabled/disabled and let me know how you get on. I've just done this so I'll give it a whirl in the morning and see what happens. Thanks!
Recommended Posts
Archived
This topic is now archived and is closed to further replies.