-
Posts
4 -
Joined
-
Last visited
Reputation Activity
-
_Volkan_ reacted to Chaiyoabc in The reason behind 'Shoot First Die First' (Data inside)
https://docs.google.com/spreadsheets/d/1XjlB4026XlExVHldj8OQC-F5WRnAjT6d3lX9j0VS2MU/edit#gid=0
Turned out your setting could have already been well-optimized
All the setting you have done.
Adjust bandwidth percentage > Still shoot first die first
Adjust MTU > Still shoot first die first
Do deep Traffic Prioritization > Still shoot first die first
and many more that we have been doing for years.
Me and my friends decide to do the research. and we have finally come up with interesting insights. And after we did this, I got nuke and my KD went from 2.7 to 2.92 in 5 Days!!
My setting is pretty much standard, just same as most of you guys, but the magic is as following:
SOME SERVERS ARE NOT GOOD FOR YOU !!
Me and my friends are tracking good servers based on ip address. and block those IPs that don't perform well
So we started to track every IP adresses we have been playing using Mikrotik router
We give score based on KD. And we know that player skills are various, so we don't give score and decide right away if this IP is good until we come across to play this ip again. We test it for 3 times and mostly scores are close. This indicates that this IP is actually performing well. Then we average score latest 3 matches that we play on 1 single ip
Red highlights are the poor performing servers. And we block these IP using Mikrotik router to make sure we don't matchmake to these servers again.
Side note: This could affect SBMM too because lower server selection = low effect of SBMM
My best recommendations for those who can sniff the ip. I suggest you guys to build your own list of data
If you are in europe, start from Spain servers. I heard they are the best. avoid France and london servers.
My info:
My ISP: AIS Fibre
Speed: 1000/1000
Setup: Mikrotik RB4011 combo with Netduma
Server Location: Singapore
VPN: Yes
VPN Location: South Africa
I hope this helps !
-
_Volkan_ reacted to kinel in WZ2/MW2 Change Region
That source port is wrong 100%source 1_65535 destination 3074 udp this is wrong its meant to be
Here the right way source 3074_3074 destination 1_65535 udp
If anyone intrestedd here are the ports the game is using
Source3074 to 3074 destination 35000to 50000 upd
Source1 to 65535 destination 443 to 443 tcp
50000 to 65535 destination 3074 to 3074 tcp
Herees the new one and is a main port in use source1 to 65535 destination 80 to 80 tcp
-
_Volkan_ got a reaction from Netduma Fraser in QOS Error: Device not found
v3.2.453 version. Thank you Liam, it worked after factory reset.
-
_Volkan_ reacted to Netduma Liam in QOS Error: Device not found
Which firmware version did you upgrade to specifically?
Since upgrading, can you please now factory reset the R2 to ensure you're starting from a clean slate? There's likely been some big changes from the firmware you were on to the one you're one now, so a reset is required to clear out any old low-level code that could be left over from previous firwmare.
-
_Volkan_ reacted to RobBob in WZ2/MW2 Change Region
This is how I have it. I don’t know if they’re all needed though.
-
_Volkan_ reacted to Netduma Fraser in WZ2/MW2 Change Region
You do so in the Traffic Prioritization section on the QoS page, not on Port Forwarding
-
_Volkan_ reacted to Netduma Fraser in MW2 Shoot First Die first? how to fix this?
Deep Packet Inspection, basically it analyzes the packets and can determine right now MW2 is being played, based on the settings done on the router I will prioritize all these packets and nothing else. So instead of using ports to prioritize for example which can be problematic if there is other applications/services using the same packets on the device e.g. you're playing a game on PC and downloading a torrent it only prioritizes the game/service and nothing else. We've always used DPI but it's a lot better now.
-
_Volkan_ reacted to Netduma Liam in MW2 Shoot First Die first? how to fix this?
For those wondering about DPI, as long as you have an R2 and you're on version 3.2.453 or newer, just resync your cloud manually from the three-line menu in Device Manager and you'll get the new DPI update. Give it a test and let us know how it goes!
-
_Volkan_ reacted to Infoseye in MW2 Shoot First Die first? how to fix this?
The results are amazing....went from 3 to 4 kills to double digit kills.im beginning to enjoy the game finally.
My settings.
Geo filter: Polygon Mode drew a square around the dedicated server around my location.
Filter mode : On
Ping assist 0
QoS: Congestion set to never
Bandwidth allocation for ps5 I used 1mb download and 0.33 upload.
Turned off WiFi,( because I'm hardwired)
Turned off Upnp
Then I reserved my PS5 IP address.
Just a short clip of the bullet hit registration is crips feels like am playing on a LAN tournament, never experienced it this good before.
-
_Volkan_ reacted to Netduma Liam in MW2 Shoot First Die first? how to fix this?
@alex.devine @johnnytran Have you guys tested out my suggestion above? The key part being adding the custom rule to Traffic Prio, I think it should help you.
As you mention, we are also working on a update to help DumaOS detect the new CoD's traffic much more fluently, that should improve matters.
-
_Volkan_ reacted to Netduma Liam in MW2 Shoot First Die first? how to fix this?
This one's likely all about QoS.
My initial suggestion here for you:
Make sure ALL devices on your network are connected through your R2 Make sure your bandwidth speeds are set correctly in QoS (Click the three-line menu in Congestion Control -> Set Bandwidth Speeds) Set Congestion Control sliders to about 70% each, to start with. Set Congestion Control to Auto-enable Disable ALL rules in Traffic Prioritisation Manually add a new rule to Traffic Prio, select the device you're playing on, then select 'Games Console' as the service. Go ahead and play some games and see how it feels.
If you're still having issues, post a screenshot of how QoS and Geo-filter are currently setup.
-
_Volkan_ reacted to Netduma Fraser in Problemas con los servidores de MW2
Make sure you have Ping Assist set to 0 and it will always stay within your polygon/radius