Search the Community

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?

ogre got dumpstered due to the old days were a single IR 3 ogre could wipe a room of ten people with one mag. it would also ruin cars passing by them should they have wound up there weapon Truth is that with any gun wether it is balanced or not LO will step in tank it till it's a about as effective as a under charged .22 with a 3 inch barrel and then leave it as such for the next millennia

I just checked the night time in asylum and its so fucking bad. It's not even that it's night time, but you literally set it to the worst time of the night. The one that has the worst amount of fog and fps impact. 00:00 AM. It would have been better if you set it to 22:00-23:00 which has more fog but the fog is not broken (dark areas are not too dark and bright areas do not have "faded" ig filter AND it has smaller fps impact). Or you could have set it to 23:40 which still has just enough fog to cover up the visible rendering in the distance but still very clean look (similiar to no fog but better). I literally added value for each time of the day so people can set it easier and you just decide to lock it and not only that, but lock it to the worst time of the night. And apparently the reason you did it is because you like the night ambience in asylum, lmao. Yep, don't even ask the community for major changes like this, you like it? Fuck it, it's all that matters. Hopefully this horrible change will be reverted in the next patch.

Hello, everyone, Our standard weekly maintenance for PC and Console will be held this Wednesday (03/22) starting at 9AM (UTC). Expected duration of this maintenance will be 2 to 4 hours. As a part of maintenance, we will be removing the St. Patrick's login reward as we prepare for the next big event! Stay tuned for more information on it in the meantime. And, as always, thank you for your patience during the maintenance process. We will be back up and running in no time P.S: This thread has been cross-posted from Game Updates

Hello, everyone, Our standard weekly maintenance for PC and Console will be held this Wednesday (03/22) starting at 9AM (UTC). Expected duration of this maintenance will be 2 to 4 hours. As a part of maintenance, we will be removing the St. Patrick's login reward as we prepare for the next big event! Stay tuned for more information on it in the meantime. And, as always, thank you for your patience during the maintenance process. We will be back up and running in no time

I gave m_bUseDiskCache=False a little go and the game was stuttering excessively and ran badly, this is under Fedora 37. I can confirm it was working as the AssetCache was empty throughout playing around on social and FC. Might give it a go in Ubuntu 22.04 LTS or 22.10 see if works any better. Update 22/03/23 Tried m_bUseDiskCache=False in Ubuntu 22.10 and it introduces frequent stutters but not as bad as Fedora 37. Therefore in my experience it's not an option I would use.

But our Loaf friend is talking about cheats / cheaters vs genuine players. There is no doubt, a cheater could easily out gun with the FBW and kill quicker than a genuine player using the ntec (or other such as an SMG) in CQC. How Loaf has expressed this and worded the post may not convey the actual suggestion. Loaf is frustrated that in all this time cheaters and cheating is still a big problem today and suggests it is hurting the playerbase / and is one of the biggest contributing factors to the games decline and should be the number 1 priority. I'm not sure what to say about this, do you see what you have done? You imply our Loaf friend has made an assumption about players and yet you do the very same thing based on their forum account. Loaf also mentions the word "decade" in the original post and so I would assume he / she has been around much longer. Loaf, there are posts about the changes to the game (see the A/Q thread ) https://www.gamersfirst.com/apb/news/2022/12/22/2022-AMA-RECAP In short nothing will change yet as the game engine and code needs to be updated first. Essentially what will happen is the game will remain identical but all the coding behind it will be modernised. This transition will then allow for and make it easier to change the game content and improve it but in the mean time most of the issues that exist will remain.

Currently, the district "Missions-Waterfront-2-US-East" is not located in US east. It is located in US west or Europe. The district server IP address's (205.220.229.82) geolocation is in California. The second to last hop (89.149.128.174) has multiple locations. Some sites show California, others show Germany. District latency shows about 71ms. I am located on the east coast. My normal latency is about 20ms to east servers. I'm using this site to lookup IP addresses: https://www.iplocation.net/ip-lookup Traceroute taken from the in game /latencytest command. I removed IPs from first two hops for privacy reasons. Time,Entry type,Hop,IP Address,Latency,Status,Message 25/02/2023 22:14:10,CLIENT_FRAMETIME,,,0,,Outlier Stats:,10,1 25/02/2023 22:14:10,SERVER_FRAMETIME,,,33,,Outlier Stats:,39,1 25/02/2023 22:14:10,DISTRICT_SERVER,,,74,,Packet loss:,0,CCU:,50,47 25/02/2023 22:14:10,PACKET_RECEIVED, ,0,11013, 25/02/2023 22:14:10,PACKET_RECEIVED,1, ,4,11013, 25/02/2023 22:14:10,PACKET_RECEIVED,2,100.41.3.250,14,11013, 25/02/2023 22:14:10,PACKET_RECEIVED,4,152.193.0.114,10,11013, 25/02/2023 22:14:10,PACKET_RECEIVED,5,89.149.128.174,71,11013, 25/02/2023 22:14:10,PACKET_RECEIVED,7,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,8,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,9,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,10,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,11,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,12,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,13,205.220.229.82,71,0, 25/02/2023 22:14:10,PACKET_RECEIVED,14,205.220.229.82,71,0, 25/02/2023 22:14:11,CLIENT_FRAMETIME,,,0,,Outlier Stats:,11,1 25/02/2023 22:14:11,SERVER_FRAMETIME,,,33,,Outlier Stats:,39,1 25/02/2023 22:14:11,DISTRICT_SERVER,,,74,,Packet loss:,0,CCU:,50,47

Hello, After this update crashes on RTX cards are back. On 64-bit update I did not have any of those issues and could run the game for hours without issues. I am running 3080 Ti, 64 GB RAM, Ryzen 9 5950X, Windows 10. Resizable BAR enabled. I run game in borderless window, 1440p, all maxed settings, smoothing disabled. My GPU drivers are up to date (528.49). Did not tinker with fps caps, all set to default (Min Smoothed 22, Max Smoothed 100, Max Client 128) Tried running game on other systems: 3080 10 GB, 32 GB RAM, Ryzen 7 5800X, Windows 10. Resizable BAR enabled. Borderless, 1440p, maxed settings, smoothing disabled. GPU drivers 528.49 3060 6 GB (Laptop 130W), 32 GB RAM, Ryzen 7 5800H, Windows 10, Resizable BAR enabled. Borderless, 1080p, maxed settings, smoothing disabled. GPU drivers 528.49 Best luck I had was on laptop with 3060, it seemed to crash only after roughly half an hour, the other 2 systems crash/run out of memory in just a few minutes. The issue can be reproduced by respawning, just like the initial issue prior to 64 bit update. Did not try running RBAR disabled.

so i donwloaded the game after some years from steam and ----- - i can launch the game - i can log in into my acc - i can get into my character list but no matter what character i choose.... i get kick out you have ben disconected from the server unexpectedly - i repaired , same problem - uninstalled and clean steam download cookies - re installed but i get the same problem same thing happend to 1.3 otw beta client and also the client updated from gamefirst page i reminds me of that punkbuster problems we used to have back in the old days i know that now, apb uses batleEye, yet i dont know if its actually installed or not I manage to made a tracert to jericho ... that i got it from here https://support.gamersfirst.com/hc/en-us/articles/360003329912-My-Latency-is-really-high- C:\Windows\system32>tracert 138.128.136.106 Traza a la dirección hosted-by.i3d.net [138.128.136.106] sobre un máximo de 30 saltos: 1 1 ms 2 ms 1 ms 10.0.0.1 2 3 ms 7 ms 3 ms 10.22.29.1 3 3 ms 3 ms * 10.16.12.1 4 25 ms 21 ms 22 ms 10.40.100.62 5 21 ms 23 ms 21 ms ae9.2027.edge1.eze2.as7195.net [200.25.50.212] 6 21 ms 23 ms 21 ms ae110.0.edge2.eze2.as7195.net [200.25.51.195] 7 48 ms 53 ms 62 ms ae0.12.edge1.gru1.as7195.net [200.25.51.157] 8 52 ms 58 ms 49 ms ae1.0.edge5.gru1.as7195.net [200.25.51.39] 9 173 ms 173 ms 172 ms ae2.0.edge1.nyc1.as7195.net [200.25.51.143] 10 185 ms 182 ms 194 ms 100ge.eqx-ashburn.misi3d.com [206.126.237.210] 11 184 ms 184 ms 184 ms usatl1-rt002i.i3d.net [109.200.219.36] 12 185 ms 185 ms 185 ms usatl1-rt001i.i3d.net [109.200.219.8] 13 * 2222 ms * usdal1-rt002i.i3d.net [109.200.219.35] 14 * * * Tiempo de espera agotado para esta solicitud. 15 * * * Tiempo de espera agotado para esta solicitud. 16 * * * Tiempo de espera agotado para esta solicitud. 17 * * * Tiempo de espera agotado para esta solicitud. 18 * * * Tiempo de espera agotado para esta solicitud. 19 * * * Tiempo de espera agotado para esta solicitud. 20 * * * Tiempo de espera agotado para esta solicitud. 21 * * * Tiempo de espera agotado para esta solicitud. 22 * * * Tiempo de espera agotado para esta solicitud. 23 * * * Tiempo de espera agotado para esta solicitud. 24 * * * Tiempo de espera agotado para esta solicitud. 25 * * * Tiempo de espera agotado para esta solicitud. 26 * * * Tiempo de espera agotado para esta solicitud. 27 * * * Tiempo de espera agotado para esta solicitud. 28 * * * Tiempo de espera agotado para esta solicitud. 29 * * * Tiempo de espera agotado para esta solicitud. 30 * * * Tiempo de espera agotado para esta solicitud. Traza completa. Any suggestion is well recieved

Good chance Console-servers are handled by Sony and Microsoft, so upgrading them should be more straightforward. But for PC-servers, some upgrades/changes can surely prove to be beneficial due to servers having similar trends to client-demand (core-clock rather than multi-thread). Current APB servers are confirmed to be single-threaded: "The clear winner here is the SoftLayer 1270v3 at 3.9Ghz (TURBO). That's a bit surprising, since technically it's the "smallest" of the three processors types (AWS C3 is a E5-2680v2 with 10 cores at 2.8Ghz, and the SoftLayer E5-2690v2 is an 8 core 3.0Ghz processor) and by far the cheapest. However, Unreal eats processor clock for breakfast, and does not properly use multiple cores for its processing tasks. So the smaller processor actually wins out. For the 1270v3 even with each district at full 100 capacity, frame rate remained close to 30 FPS, and dropped only very occasionally to 25 FPS. This is higher than the current servers’ frame rate of 25 FPS under the best conditions (down to 18 FPS at 80 capacity), and actually better than the US based Overkill servers which run closer to 22 FPS under the same 100-player load!" Which makes sense because servers receive information from clients, so there have to be some similarities. Because of this, there is also a good-chance cheaper servers were used because having more threads at the moment doesn't matter. Luckily though, multi-threaded CPUs are now very affordable for servers compared to the past. I remember it to be more lively (till players block-roads on purpose with green planet trucks)

how to fix this error crash? C:\PROGRAM FILES (X86)\GAMERSFIRST\APB RELOADED\APBGame\Logs\2022.12.19-19.55.03-2036.log C:\PROGRAM FILES (X86)\GAMERSFIRST\APB RELOADED\APBGame\Logs\2022.12.19-19.55.03-2036.dmp C:\PROGRAM FILES (X86)\GAMERSFIRST\APB RELOADED\Binaries\dxdiag.txt General protection fault! Script call stack: Function APBUserInterface.cUIDataStore_Chat|OnPlayerProfileChanged History: 11:57:10 - Log: Log file closed, 19/12/22 19:57:10

hello! xbox user here! the idea that the game (as far as console goes) has been abandoned or at least pushed a aside due to financial crisis or problems unfixable by such a small company is nothing new. we’ve learned to accept it. however for us players who’ve invested 5000+ hours into the game, it’s disappointing. as of 10/10/22 we have been unable to login, due to “maintenance” however a new question has come up in the Xbox community. Have you guys pulled the plug? With thousands of dollars invested, years of gameplay and friendships made throughout the game I feel as though it’s a bit unfair to be left in the dark as far as server status and updates. yes, we know updates are not coming anytime soon if not ever, and yes we know it’d be simpler to just switch to pc. However, even with the major complications with the game we still play. If you have in fact indefinitely shut down Xbox servers, we’d appreciate a post or any kind of information regarding the topic, if not, when can we expect to log in again? Every players situation is different..so switching platforms may be out of the question. the community created through the game, even though it’s small, it’s kind of like family. I guess the main question is: is APB Reloaded- Xbox One still a reality? Or should we uninstall?

If anyone can please provide some insight to what my crash log means? I am playing sometimes not even 1 mission long and I get this random crash with the General Protection Fault title. I think this is a different issue then most have experienced with RTX crashes as I have not seen anyone post a log like mine. Before I post the log below, here are my specs: i7 12700k Z390P DDR5 Motherboard RGB DominatorDDR5 5600mhz RAM EVGA RTX 3080ti M.2 SSD 1TB 1000WATT PSU APB CURRENT CRASH LOG: 04:12:30 - Log: Log file open, 15/07/22 00:12:30, PID 22928. 04:12:30 - hosting: BugReport.exe -url "http://apb.crashreport.gamersfirst.com" -type "crash" -reporter "Client" -summary "General protection fault: " -showbugreference -log "C:\Program Files (x86)\Steam\steamapps\common\APB Reloaded\APBGame\Logs\2022.07.14-23.56.50-22928.log" -file "C:\Program Files (x86)\Steam\steamapps\common\APB Reloaded\Binaries\..\APBGame\Logs\2022.07.14-23.56.50-22928.dmp" -dxdiag -errorcode "0x11226385" -user 04:12:30 - Exit: Executing UObject::StaticShutdownAfterError 04:12:30 - DevNet: Closing connection Default__NetConnection due to shutdownaftererror 04:12:30 - DevNet: Closing connection Default__ChildConnection due to shutdownaftererror 04:12:30 - DevNet: Closing connection Default__TcpipConnection due to shutdownaftererror 04:12:30 - Exit: Executing UWindowsClient::ShutdownAfterError 04:12:30 - Exit: Executing UWindowsClient::ShutdownAfterError 04:12:30 - Exit: Executing UWindowsClient::ShutdownAfterError 04:12:30 - DevNet: Closing connection TcpipConnection_0 due to shutdownaftererror 04:12:30 - NetComeGo: Close TcpNetDriver_0 TcpipConnection_0 205.220.227.71:12609 15/07/22 00:12:30 04:12:30 - Log: Closing CONTROL channel! 04:12:30 - ScriptLog: (cHostingGC2DS_0) cHostingGC2DS::OnDisconnect() 04:12:30 - ScriptLog: (cHostingClient_0) ClientState kCLIENT_STATE_DISTRICT_EXIT_IN_PROGRESS 04:12:30 - Log: Exception: Starting StaticShutdownAfterError()... 04:12:30 - Exit: Exiting. 04:12:30 - Log: Log file closed, 15/07/22 00:12:30 If anyone can tell me whats going on here so I can stop these crashes, as I am already playing on Minimal settings and even running the game in compatibility mode for older windows versions to help optimize as best as possible. I have also checked my Event Viewer, and nothing is happening during the time of the crash.

Ive submitted a ticket, but I have NO idea how long that will take to get a response from so I thought Id try here too. Ive played this game for over a decade and have never had any issues. No lag, no crashing, nothing. I recently upgraded my Graphics card, and My 2nd monitor. Since then every time I log in to play I crash at LEAST once and its always in the middle of a mission This is what the error box says when I crash: m_VertexBuffer->Lock(m_nNextVertexData, Size, &pData, VertexLockFlags) failed at Src\D3D9DrawPrimitiveUPWrapper.cpp:293 with error D3DERR_DEVICELOST History: 01:48:39 - Log: Log file closed, 27/06/22 21:48:39 All drivers are up to date, I tried limiting the framerate on the game in the nvidia control panel - Still crash tried turning off the second monitor - Still crash ive messed with every graphics setting in game - still crash Tonight Ive crashed 4 times in a row in less than an hour and im losing my mind here. Anyone have any insight into what that error is? here are my specs: Intel i7-6700K 8 CPUs at 4.0 GHz 32 gig ddr 2400 ram NVIDIA GeForce GTX 1660 SUPER 1TB ssd help?

Hello everyone! This Wednesday (06/22), 9 AM UTC, we will have our standard weekly maintenance. It is expected to last between 4 and 6 hours. As always, this also includes regular console maintenance. Thank you for your patience during this period! P.S: The thread has been cross-posted from Game Updates.