Netduma Liam

We don't have the servers whitelisted, I just though we might've done because you had strict mode disabled. It looks as though server is essential for gameplay, as if it's an authentication server perhaps. If you manually allow that server, do you then just consistently play on that server? What ping are you getting?

When you add the console to Geo-filter, could you please make sure you're selecting the 'Choose manually' option when prompted?

OK apparently it's not whitelisted, so there shouldn't be any issues. If you go to the three-line menu in the Geo-filter map, do you have strict mode disabled? If so, please enable it. Then you'll only get connected to servers within your polygon.

That's very odd, so when crossplay is enabled, you're then seeing a blocked icon on the map for these peers? Could you remind me what platform you're playing on please?

Looks like it's whitelisted in DumaOS, I'll pass the ID on to the team and see if there's a reason for this.

So you're able to block the servers in DumaOS when you have crossplay disabled? That's bizarre, are they definitely the same servers? Can you compare the IDs?

Thank you, I've passed this onto the App dev and will let you know once I've heard more.

Je ne sais pas encore avec certitude, cela dépend vraiment du temps qu'il faut pour passer les tests. Si c'est assez rapide alors oui peut-être !

It would probably be best to yeah, just to make sure you don't get connected to it again in the next game.

The servers you're seeing in the server browser aren't located in your radius, so they're getting blocked. What are you now seeing on the Geo-filter map when you search for a game regularly?

It's something we can do without needing to release a new firmware, so hopefully soon. The team member who looks after this will be back in the office this week so he should be able to update it then, provided it doesn't require any developer input.

We're still working on improving how Geo-filter and Ping Heatmap work with Battlefield. What about Geo-filter doesn't seem to be working for you? How do you currently have it configured?

So it didn't let you in to the game right? It booted you back to menu? I think that's the current behaviour we've found in our testing too. We're looking into the possibility of makes Geo-filter's blocking a little more gentle so games don't react in this way, but I don't have an ETA as to when we might be able to make those changes.

What was going on in-game when you took this video? It shows it as being blocked so you shouldn't have gotten into a game, though I don't have Battlefield yet so I haven't tested it myself. Are you using a VPN at all? It's weird that it'd try connect you to a server so far away.

Can you share a screeenshot of your Geo-filter setup? It should be working nicely so perhaps we need to optimise your config a little more.

3.0 n'est pas en version bêta sur le R1, il est entièrement publié. Nous publierons bientôt une autre mise à jour avec les derniers changements.

Cela arrivera une fois que nous aurons publié le firmware R2, après quoi nous porterons les mêmes modifications mais quelques modifications spécifiques à R1 sur le R1 et publierons un firmware pour cela.

Sure! Assuming we can capture it OK, it should be on Ping Heatmap later today.

OK, thanks for letting us know, we've got a new firmware coming out very soon for the R2 so that should definitely help with the problem!

OK, glad to hear it was able to get through the boot process properly then. I believe it's more a case of residual power draining rather than heat, although it's never a bad idea to give it a little more ventilation! Let us know if you run into any other problems with it.

OK, thank you. Could you please try Fraser's last suggestion and see if that helps?

I can certainly understand your frustration, we understand that screenshotting your config isn't a feasible solution, more just a suggestion to help a user in the meantime. I'll also raise the problem with the team again to bring it to the forefront, I'll get someone to replicate it and investigate why it occurs from a backend perspective.

You can save device information and restore that on the R2, there isn't currently a way to save and restore network configuration however. I've responded to your post in the other topic, though if you'd like to troubleshoot the issues you're having it may be best to open a new topic.

To clarify, are you experiencing this on an R2 or on an XR500? What firmware version are you currently running?

Not sure, we found a bug while testing it so the devs are currently working on fixing that now. Once that's done we'll re-test it. After that, it'll go out to beta testers first before we can fully release it.