Search the Community

I am on the East Coast of US ,, and have faithfully been connecting to "West Coast" servers, ever since the reprisal of APB after the extended outage in February. Typically the latency is around 80ms, which is doable. Tonight, 180-210 ,,,, Something is not working... Please investigate. Update: Ran a Speed Test, wanted to spot check my internet.. 660 Mbps (down) 22 (up)

Hi everyone, I missed the end of Friday CS stats for last week. Here they are. STATS for 5/2/2025: Oldest ticket: April 22 Total Tickets in the system: 353 Unassigned Tickets: 60 Assigned Unsolved Tickets: 293 Pending Tickets: 146 (awaiting player response) Thanks, Matt

Part 7: 1) APB: Reloaded P2W way - p.7 How i hate getting cold(shit Spring season)  2025 04 17 21 01 2) APB: Reloaded P2W way - p.7.2 Waterfront is still unbalanced shit  2025 04 17 21 32 Part 8: 1) APB: Reloaded P2W way - p.8 Today i'll finally left Waterfront shit district  2025 04 18 21 59 2) APB: Reloaded P2W way - p.8.2 It took me 3 hours to max Chiro from 7.5 to 10 lvl 2025 04 18 22 22

P2W, start of the way, part 1: APB: Reloaded - P2W way - p.1 First steps & maxing starter contacts 2025 04 11 22 03 Finally started to play with donate! Feels relaxing after F2P, like you compeletely different gameplay when you can rely more on your self Let's see how P2W will perform against F2P!

Fourth video: APB: Reloaded - F2P way - p.4: first time in waterfront! 2025 03 22 23 43 First time in the Waterfront, i didn't wanted to go there, because i hate this district's level design even more than anything in this game Surprisingly, LO did a great job with some attempt to rebalance some points of the map by adding objects in which you can hide yourself This district is still crap, but at least it's not that bad as it was in G1's primetime, still, there are a lot of work for this one, and if deleting and replacing it with new district isn't a thing, i'd deleted this Marina ship at the north of the map and also closed a lot of roofs, which are still the main pain of this map As for the today's missions, well, it's not that bad, as in 11% winrate video

3rd video: APB: Reloaded - F2P way - p.3: 11.11% winrate is 2025 03 21 22 21 Fun video, of course the situation isn't that bad, i just had a lot of missions that i had backuped right at the final minute and of course it's instalose, - that's another thing with APB, that's very bad: you can wait a good 3 minutes for mission, while guys in their mission can't receive any backup I also got tilted in this video, but pulled my self together and last mission was fine

Second video: APB: Reloaded - F2P way - p.2: crap points - this is our everything 2025 03 20 22 40 Another bad thing with APB's balance is points system, map-design isn't passed the test of time and that's pretty terrible, how some points are just inacceble if you aren't fast enough to complete them(and that's the case with new character, because you can't finish targets fast, because you don't have any equipment)

And here's the first video of F2P way! APB: Reloaded - F2P way - p.1.2: first games and facing the golds 2025 03 19 22 58 First of all: i was surprised by whooping 55.56% of winrate, which is insane for new player The second thing: i don't know if role with just playing missions for JT will be left in the game, but right now it's one of the best way to boost new players' start, for example, you can buy some stuff for 2k JTs early in the game and that's cool I wonder, if someday LO will merge G1C with JTs because right now, this system with IGC, donate and half-donate-half-IGC currencies is crap and creates a lot of confusion INB4: yep, playing without mods or perks is pretty hard, especially after long break

Hello everyone, Our standard weekly maintenance will be held this Wednesday (01/22) starting at 9 AM UTC. The game should be back up and running in 6 to 8 hours. Patchnotes This weeks patch features more game balance as well as some changes in interaction priorities. Balance VBR 'Enchantress' Minimum Damage % increased from 30% to 45%. Dev note: This is a slight increase to its 2 shot range (2 meters) but makes it so it is a little better at poking outside of its effective range, allowing it to kill in 5 shots within 100m. DOW Shotgun RaySpreadAt10m reduced from 80 to 70. NFAS-12 RaySpreadAt10m reduced from 150 to 110. NFAS-12 'True Ogre' RaySpreadAt10m reduced from 150 to 110. Low-Yield Fragmentation Grenade Max damage radius increased from 2 meters to 3.5 meters. Maximum Stamina Damage increased from 295 to 365. Maximum Hard Damage increased from 375.95 to 434.66. Dev note: A lot has changed since the Low-Yield meta that we addressed many years ago so we feel like we can now bring those grenades back up in power without causing another meta that is dominated by this grenade type. Bishada Rapier & Kissaki Weight increased from 1.5 to 2.5. Chassis Torque Factor lowered from 0.08 to 0.04. Suspension Stiffness increased from 60 to 100. Health Increased from 1150 to 1300. Dev note: The Bishada has been pretty easy to push around or even flip due to its low weight. We have increased its weight and adjusted the amount its chassis moves as well as its suspension to be able to support the increase in weight. Our goal with this change is to keep the Bishada handle roughly the same as before so please let us know if you encounter any sort of strange behavior in the way the vehicle drives after this change. Patriot V20 Jericho & Nightrider Health Increased from 1150 to 1300. Charge Mikro & Raptor - Packer Vaquero & Toreador Max Speed increased from 20.5m/s to 21.8m/s Gameplay Interaction Priorities Interacting with the Cargo/Trunk of a vehicle no longer takes priority over entering the vehicle, instead it now prioritizes the action the player is looking at. Dev note: This is an experimental change to make the interaction system more intuitive as well as fixing many cases in which a player carrying a medium item would want to enter a car but would instead put the item they were holding into the trunk of the vehicle, this issue was particularly common on smaller vehicles such as the Charge Mikro or Packer Vaquero. Decreased the priority of breaking into vehicles to avoid cases in which players prioritize breaking into vehicles over picking up task items next to it. Decreased the priority of opening gift boxes to prevent item cheesing. Miscellaneous changes The following two weapons are now skinable: CSG-20 "Country Gent" Colby RSA "Hunter" Thank you for your patience during this period.

"We all need to have faith in the anti-cheat, because it's just #1. You know, it's a competitive game. Anything that affects those matches has to be our top priority" (c) MattScott, Dec 2024 AMA (@ 00:05:35) Order of priority: - More Anti-Cheat work - More Matchmaking work (they're moving to "instancing" / "phasing") - A little bit of mission work (@ 00:43:20) - PvE (tutorial district, won't happen before Easter) district ("Redhill will better suited for new district" @ 00:49:17) - examples: mission against bots, common enemy, technological elements,... - Next big patch will include 2 new contacts (around Easter), cross-world matchmaking & "some more content behind those contacts" & "other things we're working on" They'll edit contacts which are in-files already and re-release them "way, way cooler" (@ 00:48:30) The two new contacts won't be Redhill and they're Matt's favourite contacts in the game "which are thrown away and underutilized" Small tidbits: Game will come to Epic Games Store "soon" (@ 00:06:13) CQC will get looked at "soon" (@ 00:11:00) Car "teleport" will get nerfed by adding a delay, it's "on their list" (@ 00:12:02) Clan system & player (monthly) leaderboards talk (@ 00:16:50) Private district talk (@ 00:19:00) NA-East server talk (@ 00:29:35) "New district & some other stuff" will happen afterwards - post Easter (inventory, more than 100 layers, music studio was mentioned as post-easter as well, "possibly even post that patch") (@ 00:57:15) EMP was created for RIOT and will release for the next big patch. (@ 00:55:30) A new login screen is "very low priority" "Hairstyles are tricky...and a bit lower on the list" (@ 01:02:43) Plans to make a "Disable Garbage Collection" option in settings. "The more modern way technique is gonna be doing it in another thread" (@ 01:09:00) High frame-rate slide issue is "an artifact of framerate and animation timing" and it's "fixable but sorta low on the priority right now" (@ 01:12:50) HUD glitch is "sky-high priority and is on their radar" (@01:13:25) Mouse-sensitivity issue - is completely unknown to them (don't expect anything from it) (@01:14:04) More vehicle mods will be coming, according to Frosi Spawn points are "high on their priority" and work was started on it but got sidelined for anti-cheat (@01:18:20) Melee weapons won't happen. (@01:22:32) Login rewards & gifting system mentioned but not elaborated on. (@ 01:32:00) Personal comments: The fact the sliding bug & GC being something which are low priority is... very sad, considering the statement at the top. Not to mention the fact that they're completely unaware of the mouse sensitivity issues this game has. (IT NEEDS A SEPARATE THREAD AS WELL) EMP Grenades will break the game, both in balancing & in it's performance impact on the client. Just look at the Flare Gun, the particles are mega FPS bombs. Very similar to last AMA in the end...

In any mission district (FIN or WF) the time for wait a single mission is "forever" . yesterday = 22 minutes ,full district. NO mission today 1st attempt = 15 minutes, full, no missions today 2nd = 30 minutes, full, no missions there ahd been also players that were waiting more than 50 minutes.

Hello everyone, Our standard weekly maintenance will be held this Wednesday (11/20) starting at 9 AM UTC. The game should be back up and running in 6 to 10 hours. Patchnotes This weeks update ships a couple of balance changes as well as tweaks to certain time of days to decrease the brightness of the Skybox during those times. Skybox changes We have decreased the sun-light intensity during the following time of days to avoid cases in which the Sun could make the Skybox extremely bright. 5 AM 6 AM 9 AM 5 PM Weapon Balance STAR 556 'LCR' Health Damage per shot increased from 200 to 210. STAR 556 Health Damage per shot increased from 175 to 180. Reload time reduced from 2.8 to 2.4. Colby SNR Health Damage per shot increased from 334 to 370. Sprint delay decreased from 0.73s to 0.53s. Norsemen Accuracy at 10m improved from 33 to 32. Slightly reduced vertical and horizontal recoil. COBR-A Recovery delay decreased from 0.225s to 0.18s. FAR Maximum bloom reduced by 6%. ISSR-C 'Kingdom' Minimum damage range increased from 15m to 25m. Raptor 45 Reserve Ammo increased from 132 to 176. Joker SR-15 Carbine Accuracy at 10m improved from 24 to 22. RHD LS1 'Corsair' Reload time reduced from 0.7s to 0.5s. N-TEC 5 / Scoped N-TEC 5 / N-TEC 7 Jump modifier reduced from 30 to 18. Dev Note: In one of Little Orbit's earlier balancing efforts, we significantly reduced the accuracy of all N-TEC variants when jumping. This adjustment effectively addressed the overuse and effectiveness of jump shooting with the N-TEC, but it also made jumping with these weapons feel lackluster, even in close-range situations where it should remain a viable option. With this patch, we're bringing the jump modifier of all N-TEC variants back in line with other Assault Rifles, while still maintaining a noticeable drawback to account for the weapon's long-range capabilities. This adjustment is intended to be a modest improvement rather than a major buff. Combined with the other changes made to the N-TEC 5 over the years, this should ensure the weapon remains balanced and far from the dominant force it once was when jump shooting was overly effective. We'll closely monitor the N-TEC 5's performance following this change to ensure it doesn't overshadow other Assault Rifles, particularly those designed to excel at close range. Further adjustments will be made if necessary. Thank you for your patience during this period.

I tried launching APB on Debian and to my surprise it works with SARD anti-cheat. No launch arguments needed. It seems to run about the same as it did with EAC. System Specs: CPU: Xeon W3680 RAM: 24GB DDR3 GPU: Nvidia GTX 1080 Operating System: Debian 12 (Bookworm) Kernel Version: 6.1.0-22-amd64 Compatibility tool: GE-Proton 9-10

Hello everyone, Our standard weekly maintenance will be held this Wednesday (05/22) starting at 9 AM UTC. The game should be back up and running in 4 to 6 hours. Thank you for your patience during this period.

Hello everyone, Our standard weekly maintenance will be held this Wednesday (05/22) starting at 9 AM UTC. The game should be back up and running in 4 to 6 hours. Thank you for your patience during this period.

Hello everyone, Just a quick heads-up: We've got an emergency maintenance rolling out in 40 minutes. It'll last about an hour. Hotfix will include: All VIP missions will be temporarily disabled until further notice. Sorry for the short notice and any hassle this causes.

Hello everyone, Our standard weekly maintenance will be held this Wednesday (11/22) starting at 9 AM UTC. As this maintenance will include backend, we expect it to be longer. The game should be back up and running in 4 to 6 hours. Thank you for your patience during this period.

Hello everyone, Our standard weekly maintenance will be held this Wednesday (11/22) starting at 9 AM UTC. As this maintenance will include backend, we expect it to be longer. The game should be back up and running in 6 to 10 hours. Thank you for your patience during this period.

Hello everyone, Our standard weekly maintenance will be held this Wednesday (11/22) starting at 9 AM UTC. As this maintenance will include backend, we expect it to be longer. The game should be back up and running in 6 to 10 hours. Thank you for your patience during this period.

Edit: Tested each US East district server. IP address, port, and latency are taken from the /latencytest report. I only ran it for a few minutes. I restarted APB and rejoined Waterfront-1-US-East. The IP address is the same between Financial-1-US-East and Waterfront-1-US-East. There is only one Waterfront US-East and 1 Waterfront US-West, but there are two Financial US-East and two Financial US-West. Automatic district spin up is not working. Fight Club-Ambigton Towers-1-US-East: IP Address / Port: 205.220.227.73:12595 Latency: 31ms to 39ms Fight Club-Baylon Shipping Storage-1-US-East: IP Address / Port: 205.220.227.77:10467 Latency: 31ms to 39ms Missions-Financial-1-US-East: IP Address / Port: 205.220.227.75:10555 Latency: 23ms to 70ms Missions-Financial-2-US-East: IP Address / Port: 205.220.227.71:10563 Latency: 31ms to 39ms Missions-Waterfront-1-US-East: IP Address / Port: 205.220.227.75:12793 Latency: 265ms to 273ms Extra info. Here's my Original Post: It's even worse after maintenance. Did you fire up the servers in China? There's something wrong with your anti-DDoS provider, Path Network Inc, or your servers are starting in the wrong physical location. I don't see any incidents opened: https://status.path.net/history District: Missions-Waterfront-1-US-East IP Address: 205.220.227.75:12778 In-game Latency: 230ms LatencyTest District_Server Latency: 260ms-280ms /latencytest latency: Line 5: 30/08/2023 22:12:22,DISTRICT_SERVER,,,268,,Packet loss:,0,CCU:,19,22 Line 16: 30/08/2023 22:12:23,DISTRICT_SERVER,,,268,,Packet loss:,0,CCU:,19,22 Line 26: 30/08/2023 22:12:24,DISTRICT_SERVER,,,265,,Packet loss:,0,CCU:,19,22 Windows Trace Route (removed IP from first hop): Tracing route to 205.220.227.75 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms XXX.XXX.XX.X 2 2 ms 6 ms 6 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 6 ms 7 ms 7 ms B4325.NWRKNJ-LCR-22.verizon-gni.net [100.41.3.252] 4 * * * Request timed out. 5 14 ms 11 ms 12 ms customer.alter.net [152.193.0.114] 6 13 ms 12 ms 12 ms ae10.cr3-nyc3.ip4.gtt.net [89.149.140.182] 7 * * * Request timed out. 8 14 ms 11 ms 11 ms 205.220.227.75 Trace complete.

The connection to US East is screwed up internally. This is obviously not routing to a US East location. Did you start the district server in the wrong datacenter? Regardless, that doesn't explain the +70ms variance and these random +200ms latency spikes. District: Missions-Financial-1-US-East IP Address: 205.220.229.40 In-game Latency: 30ms to 90ms Edit. Added Cloudflare traceroute to prove it's not an ISP issue. Obviously traceroutes don't show the whole picture, but they do show that both my ISP and Cloudflare WARP VPN are functionally the same. Both route to gtt.net on the west coast and then to 205.220.229.40. Cloudflare Trace Route: 1 9 ms 12 ms 11 ms 104.28.0.0 2 9 ms 11 ms 12 ms 104.29.106.1 3 20 ms 17 ms 8 ms 162.158.156.2 4 11 ms 11 ms 12 ms ae5.cr2-nyc4.ip4.gtt.net [208.116.240.225] 5 69 ms 70 ms 85 ms ae12.cr4-lax1.ip4.gtt.net [89.149.128.174] 6 * * * Request timed out. 7 72 ms 70 ms 69 ms 205.220.229.40 Home Trace Route: 2 4 ms <1 ms 5 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 11 ms 7 ms 7 ms B4325.NWRKNJ-LCR-22.verizon-gni.net [100.41.3.252] 4 * * * Request timed out. 5 12 ms 13 ms 11 ms customer.alter.net [152.193.0.114] 6 63 ms 64 ms 62 ms ae12.cr4-lax1.ip4.gtt.net [89.149.128.174] 7 * * * Request timed out. 8 63 ms 63 ms 64 ms 205.220.229.40 /latencytest District_Server: Line 5: 26/08/2023 18:59:09,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,25 Line 17: 26/08/2023 18:59:10,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,25 Line 26: 26/08/2023 18:59:11,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 29: 26/08/2023 18:59:12,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 38: 26/08/2023 18:59:13,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 43: 26/08/2023 18:59:14,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 46: 26/08/2023 18:59:15,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,25 Line 55: 26/08/2023 18:59:16,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,25 Line 60: 26/08/2023 18:59:17,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 63: 26/08/2023 18:59:18,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 72: 26/08/2023 18:59:19,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 77: 26/08/2023 18:59:20,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 80: 26/08/2023 18:59:21,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,25 Line 89: 26/08/2023 18:59:22,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 94: 26/08/2023 18:59:23,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 99: 26/08/2023 18:59:24,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 106: 26/08/2023 18:59:25,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 111: 26/08/2023 18:59:26,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 115: 26/08/2023 18:59:27,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 123: 26/08/2023 18:59:28,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 128: 26/08/2023 18:59:29,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 132: 26/08/2023 18:59:30,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 140: 26/08/2023 18:59:31,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 145: 26/08/2023 18:59:32,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,26 Line 152: 26/08/2023 18:59:33,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 157: 26/08/2023 18:59:34,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 162: 26/08/2023 18:59:35,DISTRICT_SERVER,,,253,,Packet loss:,0,CCU:,25,26 Line 169: 26/08/2023 18:59:36,DISTRICT_SERVER,,,253,,Packet loss:,0,CCU:,25,26 Line 174: 26/08/2023 18:59:37,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 179: 26/08/2023 18:59:38,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 186: 26/08/2023 18:59:39,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 191: 26/08/2023 18:59:40,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 196: 26/08/2023 18:59:41,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 203: 26/08/2023 18:59:42,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,26 Line 208: 26/08/2023 18:59:43,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 213: 26/08/2023 18:59:44,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 220: 26/08/2023 18:59:45,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 225: 26/08/2023 18:59:46,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,26 Line 230: 26/08/2023 18:59:47,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 237: 26/08/2023 18:59:48,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 242: 26/08/2023 18:59:49,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 247: 26/08/2023 18:59:50,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 253: 26/08/2023 18:59:51,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 259: 26/08/2023 18:59:52,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 264: 26/08/2023 18:59:53,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 271: 26/08/2023 18:59:54,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 276: 26/08/2023 18:59:55,DISTRICT_SERVER,,,66,,Packet loss:,0,CCU:,25,27 Line 281: 26/08/2023 18:59:56,DISTRICT_SERVER,,,66,,Packet loss:,0,CCU:,25,27 Line 288: 26/08/2023 18:59:57,DISTRICT_SERVER,,,62,,Packet loss:,0,CCU:,25,27 Line 293: 26/08/2023 18:59:58,DISTRICT_SERVER,,,62,,Packet loss:,0,CCU:,25,27 Line 298: 26/08/2023 18:59:59,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 305: 26/08/2023 19:00:00,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 310: 26/08/2023 19:00:01,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 315: 26/08/2023 19:00:02,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 322: 26/08/2023 19:00:03,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,27 Line 327: 26/08/2023 19:00:04,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,27 Line 332: 26/08/2023 19:00:05,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,27 Line 338: 26/08/2023 19:00:06,DISTRICT_SERVER,,,93,,Packet loss:,0,CCU:,25,27 Line 344: 26/08/2023 19:00:07,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 349: 26/08/2023 19:00:08,DISTRICT_SERVER,,,101,,Packet loss:,0,CCU:,25,27 Line 356: 26/08/2023 19:00:09,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 Line 361: 26/08/2023 19:00:10,DISTRICT_SERVER,,,70,,Packet loss:,0,CCU:,25,27 ... Ping to 205.220.229.40 from PC, APB client during /latencytest: Reply from 205.220.229.40: bytes=32 time=66ms TTL=118 Reply from 205.220.229.40: bytes=32 time=74ms TTL=118 Reply from 205.220.229.40: bytes=32 time=60ms TTL=118 Reply from 205.220.229.40: bytes=32 time=64ms TTL=118 Reply from 205.220.229.40: bytes=32 time=60ms TTL=118 Reply from 205.220.229.40: bytes=32 time=62ms TTL=118 Reply from 205.220.229.40: bytes=32 time=66ms TTL=118 Reply from 205.220.229.40: bytes=32 time=62ms TTL=118 Reply from 205.220.229.40: bytes=32 time=65ms TTL=118 Reply from 205.220.229.40: bytes=32 time=66ms TTL=118 Reply from 205.220.229.40: bytes=32 time=66ms TTL=118 Reply from 205.220.229.40: bytes=32 time=61ms TTL=118 Ping to 205.220.229.40 from router during /latencytest: Min: 59ms Max: 75ms Avg: 63ms.

Fav's gonna be Colby Commander and RSA mainly for looks and sounds. I'm fond of the Huntress for looks and performance not so much sounds, it sounds like a beefy .22 I like the Cobra for looks n sound but its been Neryked I like the BIG shotgun forgot the name but its Slow, but its looks and shooting are more like what a 12 gauge should be but the disgusting part is the csg 20 gauge has more range and material damage/cars than the big 10 gauge. Now your subguns suck, they aren't precise, have this 'pattern akin to a shot gun, with exception for the Troublemaker.

New clothes 1) Plate carrier 2) Flak vest (Pasgt vest) 3) Kevlar helmet cover and SWDG goggles (Pasgt-H cover) 4) Tactical helmet 5) Gen 3 Combat shirt 6) Military shirt ACU 7) A.L.I.C.E. system (Suspenders, pistol belt, stanag pouch case, field first aid, water canteen 1qt, ) 8 ) Old military style field jacket (M65) 9) Police/Military style shirt 10) Service uniform 11) Military/Combat boots/Jungle boots panama sole 12) Riot helmet/ PASGT-H Glass 13) Old ww2 style helmet (US M1 Helmet) 14) Eastern Bloc style helmet 15) 8 point cap (usmc cap) 16) LAPD style hat (non 8 point hat) 17) Campaign hat 18) Gen 3 style tactical pants 19) Police/military style belts 20) Scientist lab coat 21) Double-breasted suit 80s 90s 22) Hawaii/Aloha/50s shirt 23) Coat/Detective/Military trench 24) Soviet overcoat 25) Karate suit 26) Hev style armor 27) Ushanka 28) Firefighter hat 29) Builder/Safety hat 30) Modern ACH Mich 200 helmet 31) Karakul hat/ Papaq hat (Papakha) 32) Medical mask 33) Aerodrome cap (peaky styled hat) 34) M17A1 Gas mask 35) 80s style glasses 36) 2000s style sunglasses 37) Mr Smith sunglasses 38) Oakley tactical sunglasses 39) Fuzzy puzz glasses

Something is screwed up between Path's nodes (ddos mitigation provider) and US-West servers. The majority of my shots do not register on players while aimed directly at them. Meanwhile, I got a few hits and then a kill when I smacked my keyboard with my mouse and fired a burst over 5 meters away from a player. None of those shots should have hit, but the server thought they did. District: Missions-Waterfront-1-US-West (205.220.229.52) In-game Latency: 60ms In-game packet loss: 0.00 latencytest district latency: 99-107ms CMD Ping to district IP Address: 67ms Traceroute to district IP Address: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 1 ms 6 ms 5 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 6 ms 7 ms 7 ms B4325.NWRKNJ-LCR-22.verizon-gni.net [100.41.3.252] 4 * * * Request timed out. 5 6 ms 11 ms 11 ms &#10.0.193.152.in-addr.arpa [152.193.0.114] 6 69 ms 78 ms 66 ms ae12.cr4-lax1.ip4.gtt.net [89.149.128.174] 7 * * * Request timed out. 8 68 ms 64 ms 66 ms 205.220.229.52 Near perfect score for bufferbloat on Waveform: https://www.waveform.com/tools/bufferbloat?test-id=94f035ba-0819-4a2a-8c33-a4ba92ef8ec9 Where is the extra 30-40ms coming from in the /latencytest result for the district server? It's not much latency, but it's showing a problem. The server shouldn't be located that far from the node, considering the USA coverage Path has. Is traffic being routed to the wrong locations internally? I checked the packets with Wireshark. I don't see any packets arriving or leaving my network out of order, that's if the IP.ID is accurate. I cannot check if there's packet loss from client to server. The in game packet loss counter only counts packet loss from server to client. EDIT: Tested EU Server. There's a different problem on EU. My latency randomly goes from about 90ms up to over 300ms, and stays there for a while. However, despite the significant latency spikes, the hit registration is overall better. Most shots hit. The few that miss are edge cases where the bloom was a little high, or the player was about to get behind cover. District: Missions-Financial-2-EU-West (205.220.228.181) In-game Latency: 90ms average. 200ms spikes. In-game packet loss: 0.00 Latencytest district latency: 135ms CMD Ping to district IP Address: 95ms to 317ms Traceroute to district IP Address: Tracing route to 205.220.228.181 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 28 ms 17 ms 4 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 13 ms 7 ms 15 ms B4325.NWRKNJ-LCR-21.verizon-gni.net [100.41.3.250] 4 * * * Request timed out. 5 8 ms 12 ms 11 ms &#10.0.193.152.in-addr.arpa [152.193.0.114] 6 85 ms 93 ms 82 ms ae11.cr6-ams1.ip4.gtt.net [213.200.117.178] 7 * * * Request timed out. 8 145 ms 148 ms 147 ms 205.220.228.181 Trace complete. Tracing route to 205.220.228.181 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 15 ms 12 ms 10 ms lo0-100.CMDNNJ-VFTTP-325.verizon-gni.net [72.82.234.1] 3 11 ms 7 ms 15 ms B4325.NWRKNJ-LCR-21.verizon-gni.net [100.41.3.250] 4 * * * Request timed out. 5 8 ms 40 ms 20 ms &#10.0.193.152.in-addr.arpa [152.193.0.114] 6 115 ms 93 ms 100 ms ae11.cr6-ams1.ip4.gtt.net [213.200.117.178] 7 * * * Request timed out. 8 85 ms 86 ms 95 ms 205.220.228.181 Trace complete. I'm leaning on there being a problem with Path Network Inc. APB is configured improperly for their service, or their service sucks major donkey dong.

what does it mean? i tried to read this sentence many times but don't understand anyway vaquero now can drive 22 m/s or what?