Jump to content

Search the Community

Showing results for tags 'hit rego'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News & Community
    • News & Announcements
    • Feature Ideas & Improvements for DumaOS
    • Community Discussion
  • Support
    • Knowledge Base
    • Latest Firmwares
    • DumaOS on NETGEAR Nighthawk Support
    • DumaOS on Netduma R1 Support (Open Beta)
    • Original Netduma R1 Firmware Support
    • Call of Duty Support
    • New Games for the Geo-Filter
  • Duma Army Lounge
    • Gamer Talk
    • TechnoBabble
    • Off Topic
  • International Language Forums
    • NETDUMA Deutsch
    • NETDUMA Español
    • NETDUMA Français
  • 1 on 1 Support
    • Request 1 on 1

Marker Groups

  • Members

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location


Interests


DumaOS Routers Owned


Website URL


Skype


Twitter


Discord


Steam


PlayStation Network


Xbox Live


Nintendo Switch


Battle.net


Gamer Type


Favourite Genres


Connection Speed

Found 2 results

  1. Sometimes I feel like the netduma is useless. You emptying a clip only to get turn on a get two shot. When you check the kill cam only two hit reg only two bullets connect out of 30. Always getting connected to 80 plus ping servers. I am just fed up
  2. This thread (and others) is created to assist those who are having chronic hit rego and lag movement issues in which the game is simply not enjoyable. It was determined that there are port ranges that need to be placed in traffic prioritization that are not listed by the games developers. The point to this is that by prioritizing those ports one would have better hit registration and overall better fluidity in the game(s) you play. The information provided to you is not a final on the research presented so far. Furthermore, testing is ongoing. It take this community as a whole to help gather more data/input to determine what works and what doesn't. Please keep that in mind when reading this thread. Thanks Ok here is a list of ports you want to test for Traffic Prioritization as discussed in this thread: 1. Reboot modem. Next reboot your router (if you don't have any double nat issues if you do go to step 2, 1st). 2. Make sure you don't have double NAT (google how to check). However you can do either a tracert or check your router to see if you are using a private or public ip. If private more then likely you have double nat. In order to compensate for double nat you will need to use your modem to place your router in DMZ (google how to). Afterwards you may need to reboot your modem then your router again in order for it to take effect. 3. For your XR router make sure you Disable DumaOS Classified Games. 4. Uncheck Shared Excess for both download and upload from Bandwidth Allocation. Make sure that your Down/Up Bandwidth is correct. Do a speed test with just your modem to verify. 5. Delete all existing rules if you haven't added these before. 6. Set Anti-Buffer Bloat settings to both 100 and set it to never. (for me even on "Never" I'm still capped to ABB slider for up/down). Test this to see if you notice any improvement. If not re-enable it. R1 users may want to keep ABB. For me, having tested this in several matches I am now "on time" with the server and on par with other players. No more .5 seconds behind other players. 7. Make sure that the port for your console is actually in Upnp. Take note of it (it's usually 5 digit number). Make sure that port corresponds with your console and not some other device. It has been suggested to tie in that rule along within Traffic Prioritization to 3074-3075. Like this: Source: (port to your console) -> Destination: 3074-3075 and vise versa for your other rule. Results have been inconclusive and more testing is needed to determine if there is any impact doing so. I've read that tying in your console port to the actual port ranges as well in both source and destination and destination to source. But again, further research is needed to determine if this actually works or not. 8. Adjust Bandwidth Allocation as needed. 9. Set the following rules for Traffic Prioritization For UDP. It takes trial/error on your part between those games that use udp vs those that require tcp. Source 3074-3075 -> Destination 3100-3500 Source 3100 - 3500 -> Destination 3074 - 3075 This is not needed for the actual game itself (it seems). You are prioritizing data about your stats more so then anything else. I've noticed at the end of the round that my rank up wouldn't animate (filling up the circle). It would be instantaneous. Albeit I was also prioritizing 2000-7000 udp as well. This was/is unnecessary. Thanks @blackfirehawk for the tip. Source 3074-3075 -> Destination 30000-45000 Source 30000-45000 -> Destination 3074-3075 Once added reboot the Router (to assure that the settings stick). Using the 1st set of rules. And make sure that the port for your console shows up in Upnp. If you don't use Upnp you may want to enable it, disable port forwarding (or delete the rules for them) reboot the router find your port for your console. Then add that port to port forwarding once you know what it is and disable upnp if you perfer port forwarding. Thanks to @kinel, @GHOST-1-EC and others for the research. Example (Best k/d yet for me): Disclaimer: This is not a "tweak" to help you get an edge on other players. Nor will this help improve an already great hit rego experience. If you are already consistently coming in 1st through 4th place in matches these settings may be of little benefit for you. These settings are "suggested" as a base line and may require further research (IE: Wireshark, etc) on your part to get the optimal port ranges suited for your geo-location, etc. EDIT 12/21/19: It appears that after a few updates things get borked with Modern Warfare (and BO4). I found out that in order to get better fluidity in my movement I had to reinstall the game after about 2-3 updates. The ranges above does indeed work 3074-3075 30000-45000 (in 5000-8000 increments). And for me, keeping ABB to never using 75% of my download speed (lowering it more with bandwidth allocation) seems to really bring the game up to par. I've found nothing else that would allow me to be ahead of everyone else in movement, etc so far. If anything else comes up I would update.
×
×
  • Create New...