BeerHunter

For any other Fortnite R2 Gamers The best way (IMHO) to use the Geo-Filter for Fortnite is to 1. Set your required GF radius (Be realistic anything under 50ms is perfectly fine) 2. Have DumaOS open on a device next to you as you search for a game in Fortnite. 3. When Fortnite says its preparing to move to Server / Lobby, look at the DumaOS it will now show you (white icon) what server your going to 4. You then have a about 3-7 seconds to cancel the search before Fortnite moves you to that lobby 5. Restart search (Xbox Press B then Y), it's not ideal but it's so much smoother than the DING Beacon service error, DING Beason Service error loop

Just for info, if you are playing on XBOX and get this issue in the future, it's not a router issue, the XBOX quick resume for Fortnite doesn't work in a lot of scenarios, so will just hang on that screen. The fix is easy, 1. Press the X (middle) button on the controller. 2. The Game/ App side menu appears with Fortnite at the top, goto the fortnite (game icon) 3. Press the menu button (3 lines) and select Quit 4. Start Fortnite again 5 Game should load perfectly fine now

Hey Morph, I feel your pain, I almost had the exact same issue as you on my XBOX X playing Fortnite I'm using the R2 over Wifi, only the XBOX is connected to the R2 Good Internet bandwidth 1000mb d/l etc Using the R2 via a TP-Link Router (Deco M4) - Zero LAG spikes on the TP-Link, constant spikes via the R2 Play Fortnite on the R2, intermittent Lag spikes make the game absolutely unplayable I play from the UK but more often than not land on German servers (25ms -35ms) I get lag spikes on the London server with 9ms latency, i get spike lags on any server, no matter the latency, switch to the TP-Link lag spikes disappear, switch back to the R2 and like a bad smell the Lag spikes come back! Frustrating as hell. Tried everything you did, but nothing worked until this... My steps from TP-Link (deco M4) to R2 1. Factory reset the R2 and start with a clean install 2. Upgrade to the latest R2 firmware. 3. On my TP-Link router, I reserved the address of the connected R2 router (this assigns internal static IP address) 4. In the TP-Link I have assigned the R2 as High priority (locate client in the TP-Link UI, should be a toggle for High Priority) 4. GOTO to the Advanced -> NAT Forwarding -> Port Forwarding section on your TP-Link and forward the following ports for the R2 Ports required for XBOX Port 88 (UDP) Port 3074 (UDP and TCP) Port 53 (UDP and TCP) Port 80 (TCP) Port 500 (UDP) Port 3544 (UDP) Port 4500 (UDP) If you have the same UI on your TP-Link then its should be something like Service Type = Custom Service Name = Port 88 (UDP) - this is example for port 88 Internal IP - Select the IP of the R2 that you reserved early Internal Port = 88 External Port = 88 Protocol = UDP Repeat for all Ports listed above - Double check at the end that all ports have been correctly forwarded to the correct reserved IP using the stated protocols TCP, UDP or TCP & UDP Restart your devices Xbox / PS5 & R2 (i didn't bother restarting the TP-Link) Hopefully like me, you should now see zero lag spikes on the R2 Best of luck buddy

Cheers buddy, some good suggestions. The duma is so flaky at times (admittedly much better with the latest firmware) but when it works, its beautiful.

This is me 100%, don't want/need bot lobbies, I like going up against good players. I don't mind being out gunned, what I hate about this COD and most of the previous ones, is the fact that certain players will have a generous milli-second advantage on you and they are basically invincible unless you hide in a bush and shoot them in their back. Ruins the flow of a game for me.

Thanks, good advice in there, appreciate the effort. I'm honestly not looking for easy lobbies, i actually prefer going up against better players, as they are more rewarding when you win, I have no interest in any K/D figures TBH. What I was looking to test was the lag compensation and whether I could tinker the match-making for a fairer distribution of lag-comp on the lobby. I don't mind being out gunned, but there are many times where a player seems to be a second ahead of me, it feels like, gun fights with these players are predetermined already on their screen, you see them first, start shooting, get shit on. A lot of the time its just down to a better opponent but there are times where the gun fights don't seem fair at all, regardless of opponents skill level. Tonight I played a lobby and was decent against everybody but one player who finished at the bottom of his team, he killed me easily everytime, once he killed me and it spawned me around the corner, waited for him to appear ADS ready and he still killed me. From his gameplay he was fairly new to COD, no jumping, no ADSing around corners etc but the lag comp made him invincible to me. I got the most skills/score of both teams, did well against the others teams best players but the guy at the bottom felt like he was a full second ahead of me. Its the one thing i truly dislike about COD games, it's just so much more apparent. I live in the NorthWest of England, so wanted to tinker to see if the Geo-Filter ease could the lag-comp, I reckon there are locations that maybe are in the sweet spot where they don't have much lag-comp applied and have more consistent match-ups.

FYI, If I set home via the home button it seems to work as expected, however it doesn't work for me via the set home manually button. Maybe a bug. Update: it seemed to have worked for 2 matches, I think Microsoft have updated their code to override the netduma, the xbox is wired to the duma but it might as well be wired to my own router, if the geo-filter doesn't work its a waste of money IMO

To test the duma geo locater with MWII I have my Xbox-X wired into the duma, I have set the geo-location to the middle of the atlantic, 250 mile radius and added the Xbox in filtered mode, still finds games, takes zero notice of the duma settings, its like it not even there TBH. Although it could be fishermen with via their phones 4g hotspot. Anyone else experienced this?

This was the behaviour I was expecting from the Geo location function but on this MWII game it does not work for me. I put home as US mid-west and start a game and i'm connected to Keele UK. What gives? Do also need to VPN from a mid west server? Like the original poster, i'm interested in testing lag comp and how it changes but geo filter is not working as expected. Any ideas?