Jump to content

MS increased once the router was installed


pyroass
 Share

Recommended Posts

As the title says, after installing the router and configuring it, the ms in EA FC 24 doubled. What can I do in this case?
Also, I noticed that in the game I have a ping of approximately 60ms and if I connect in the app, the ping shows 24. 
Even if we go by what the app says, I noticed that the gamplay is slowed down and not as smooth as before.

Also, even if I block a server it still connects me there. Example picture below.

image.thumb.png.903f80dbb490ff4a7df0fe06ef4dfe7b.png

Link to comment
Share on other sites

Likely due to steady ping being enabled, there are multiple posts on this topic and there is a video on their YouTube about it. I would recommend running pingplotter using your old router and the r3 though and ping your actual ip address on the test, on my old routers I get a base ping of like 0.4-0.6ms then on the r3 constantly spikes up to 4-5ms.

Link to comment
Share on other sites

2 hours ago, pyroass said:

I did the pingplotter. Look at the result. 

image.thumb.png.e51f056c3b6d82d254519f254a4f23cb.png 

Are you able to test your other router to compare the difference? That’s about like mine but a straight line no fluctuations on other routers.

Link to comment
Share on other sites

Update1: SmartBoost is not doing anything good and it's  not prioritize anything even if i put only my PS5 on it. 
Update2: If i disable steady ping, seems that the ping in game is lower, around 10ms. The problem there is fluctuationg a lot. as an example in a match i have from 28 to 70. 
Is not any beta version that it's trying to fix those problems?it's a disaster what's happening at the moment with latency in games using R3.

Link to comment
Share on other sites

Ok that’s great. Let’s ignore the packet loss at the moment, it’s not carried through and you would notice that to be honest.

yes it shows jitter and an increase in latency at times. As long as there was no internal clients sending out it shows a slight jump here and there. It’s not huge but it’s there. 

Hopefully the devs can resolve this once back from the holiday period

Link to comment
Share on other sites

  • Administrators

For those with the seemingly higher pings when using the R3 please do the following, ideally testing with PingPlotter and offering a plot from your ISP modem as a comparison:

  1. Ensure the upstream/ISP modem/router the R3 is connected to is setup with the R3 in its DMZ or in modem/bridge mode.
  2. Ensure ALL devices are connected to the R3 or at the very least that there are no devices connected/using internet on the upstream router when testing
  3. If you have multiple ethernet cables test using different cables connecting the R3 to the modem/the R3 to your device
  4. Disable IPv6 in LAN/WAN
  5. Please state if you are using PPPoE, VLAN or DHCP identifiers
  6. Use a different DNS such as 1.1.1.1 / 1.0.0.1
  7. As a test make an Internet rule to the device and allow ALL traffic then test, is there a difference? (Settings > Internet Rules)
  8. As a test put the PC in the DMZ (briefly for the test then remove), then do a test, is there a difference?
  9. Remove all prioritizations from SmartBOOST including activities/devices
  10. If the above doesn't help disable SmartBOOST entirely from the 3 dots menu top right of the page :r3menu > Settings then test
  11. Disable Steady Ping on the Geo-Filter page in case it is affecting traffic outside the Geo-Filter - also ensure no devices are added there
  12. Disable Adblocker
  13. Ensure you have your correct speeds entered in Speed Test > Advanced
  14. With SmartBOOST enabled, adjust Congestion Control in Ping Optimizer > Advanced and have it set to Always On and ensure speed test bypass is disabled
  15. Ensure you're doing this test over a wired connection - NOT WiFi
  16. Ensure in WAN/LAN Settings that the speeds of the ports are at 1Gbps
  17. Remove any port forwarding/DMZ/static routes you may have set
  18. Test at different times of the day i.e. during peak time (results may be worse) and during non peak times (should be better)

Once you've covered everything on this list please let us know the results. This should give us a good indicator of what the problem may be if it's covered in the list or whether it's something more on the backend. The team can then have a look. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...