Jump to content

Netduma Fraser

Administrators
  • Posts

    83915
  • Joined

  • Days Won

    1727

Everything posted by Netduma Fraser

  1. I've given you Early Access which should work better: https://forum.netduma.com/forum/151-netduma-r3-early-access/ If on point 1 you're still seeing servers on the Geo-Filter etc then you can ignore that but it should be resolved on early access firmware. You won't be able to stabilize or even ping every server so that can happen. We're working on a new ping method that may improve this.
  2. I don't think the command was right as it should return a different message, double check you're getting the whole command. What did you see when you tried it on the app exactly? What is the model of the modem/router the R3 is connected to?
  3. Added
  4. Right click the page, then go to Inspect (Element), on the window that appears click on the Console tab. Then paste and enter this command: await duma.RPCHandler.PostRPC({rapp: "com.netdumasoftware.config", method: "get_time_zone", params: []}) see if that allows you to get past the Setup Wizard.
  5. Open it in an incognito window and see if you can continue, if not try another browser, otherwise download the DumaOS app on your phone and try to continue that way
  6. Thanks for letting us know, we can certainly look into it
  7. It's hard to say, I think they would use relay servers regardless but I suppose it is possible - if you play without filtering enabled but so you can still see the servers, do you notice the same thing?
  8. Have you tried the latest Early Access firmware? It should be largely resolved with that one. To disable fully go into SmartBOOST - Menu - Settings > Toggle Enabled off
  9. The only things I can think of that could be causing it are: The devices aren't directly connected, instead they're connected through a switch, extender etc The device name you think it is, is no longer correct - for example if you've changed the connection method it may appear as a different device. Check the IP on the device itself and then check the device you think it is on the Device Manager, do they match? If they do then I think go ahead with the reinstall of the firmware.
  10. Added
  11. I've given you Early Access, please try the firmware there and see if it works better please https://forum.netduma.com/forum/151-netduma-r3-early-access/
  12. Just to clarify, you're allowing the area of Japan which seems to handle the relay and than allows you to then force the server you want to play on to wherever you want?
  13. I think you'll need to be on the beta firmware, please re-upgrade and check again
  14. Added https://forum.netduma.com/forum/144-netduma-r2-early-access/
  15. Added https://forum.netduma.com/forum/144-netduma-r2-early-access/
  16. Keep scrolling down and the button should become viewable
  17. Good to hear, do let us know any feedback you may have.
  18. There isn't anything there to indicate why it may not be working, could you add another device to the VPN and see if you notice the same thing?
  19. Go to https://forum.netduma.com/forum/151-netduma-r3-early-access/ and check the pinned topic for the firmware
  20. Click Advanced on that screenshot there and skip through until you get to the interface. Then reboot your modem, wait 2 minutes, then reboot the R3, wait 4 minutes and see if you have internet.
  21. Added
  22. Zippy is the resident Halo player here so he speaks wisely. If you're going to use the Geo-Filter then you'd have to use Geo-Latency, it's just not likely to work otherwise given their changes.
  23. The V2 is the same as the V1, there was a CPU shortage so they had to make a new one with a comparable CPU, that's the only difference. There aren't any conspiracies going on, if I knew why it took so long I would say. When I have more information I will provide it.
  24. No there isn't, exitlag changes your routing to the game server, this isn't something we can do - you're essentially using a VPN
×
×
  • Create New...