Jump to content

Netduma Fraser

Administrators
  • Posts

    85374
  • Joined

  • Days Won

    1801

Everything posted by Netduma Fraser

  1. Have no firmware updates in that time resolved it? In most cases rebooting then waiting about 4 minutes before accessing should allow it to load correctly, does that work?
  2. You won't be being punished for using the router, I would suggest: Disable GeoLatency Disable PingAssist (set it to 0,0) Enable Strict Mode Disable Fast Search Use Simple instead of Custom radius Then restart game or wait 10 minutes (in the lobby in the game). If that doesn't work, reboot PC/Console and this will help with keeping it in the radius. If it's still happening then it's something we'll find during testing and will make any necessary cloud updates to adjust it.
  3. Yeah we wouldn't use the existing remote access for that, I don't know what the plans are for it currently, there will be a time where more user requests make it in
  4. You already have access: https://forum.netduma.com/forum/144-netduma-r2-early-access/
  5. Great thanks a lot, I'll pass it onto the team!
  6. We don't control the servers the game uses we can't add any that might not be there. If there are some that are mislocated for example we can move them but ultimately the Geo-Filter shows active connections.
  7. If you disable the Geo-Filter for the PC and restart the game does it appear open then?
  8. Okay that's good, if you do the process again above does it then work?
  9. Please sign up here: https://forum.netduma.com/topic/39415-introducing-early-access/ and we can get you added
  10. Peer is an easy fix but that's good to know, thanks!
  11. You could try the above but otherwise you may need to disable the Geo-Filter for the moment while we test it and hopefully get a cloud update out during the beta period
  12. Where are you testing the NAT type exactly? When you're testing it is the console also in use at the time? If so if you use the PC first is it on open?
  13. Go up to the properly posted firmware in Early Access which is more up to date. The team are still actively looking into the issue as well.
  14. CPU is higher after the reboot so CPU doesn't seem to be a factor in it, everything looks normal there. At least we know where not to look, thank you, the team will take a look at the logs you provided before.
  15. I've responded to you via email, we can continue there if you like.
  16. That's much better, more like what we would expect to see, it'll be your setup then
  17. I've not heard anything more unfortunately and I emailed personally as well, I'll see if the team knows anything more
  18. I've given you access. If you could please not pass it out to people I'd appreciate it. The reason we have it in a new area is so we can get feedback on it to improve it. They also don't get any newer versions that way.
  19. We'll test it and put out any necessary updates hopefully within the course of the beta.
  20. It doesn't impact what servers you play on, you still use the filter to force the servers you want, then the additional ping is applied regardless of where you play.
×
×
  • Create New...