All Activity

Why does it take the community to point this out when they are the one's developing the game, sounds kind of unsettling to see how inexperienced this company truly is.. And we pay these people hand over fist in the misbelief that it is going towards the further development of the game, sigh..

to under stand this you need to have a basic understanding of the game engine and assets. also you need to have a little history with the development APB. Before the green pumpkins are originally only 120 in the event. in this years event there are more than 600 green pumpkins. Why does that matter. The are two (2) basic elements to pumpkins. 1 a model assent and 2 a sound node. to explain this simply we can use a ( o ) to represent the sound node around the pumpkin. So before the pumpkins were placed similar to this .. ( o ) ( o ) ( o ) ( o ) ( o ) etc... meaning there was no overlap of the sounds and if there was the game was coded to take the distance from the player and mute (slightly) the more distance sounds. Which it was able to do. In this event (2026) the pumpkins were increased from 120 to 600+ so now the effect is this ( (o o ) )( ( ( oo ) )) ( o( ) o ( )(o ) ).... etc. thus the code cannot play because there is a logic error to the sound node. So to fix the problem, simply change the number of green pumpkins back down to under 180 and they will sound off again.

you do know why the green pumpkins are broken...

the point is it is too easy to stun and it is not crims have a similar item (poison) so to play on a level field the devs made the anti-stun mod. If it is brought back then it does not matter if the enforcer is close or far. they will have to actually work for the stuns not automatically get free kills. PS. the game is based on game units and the units are not in meters. But also not in feet 12" .

Windows 11 Pro 4090 Tuf 24GB 64gig 6400 (locked at 2400, profile turned off) M.2 Samsung 990 Evo 4tb M.2 Samsung 990 Evo 4tb HDD 8tb HDD 16tb MSI 870E Carbon Wifi AMD 9900x3D Anyone have any ideas on what's going on?

Setting apps for Launcher/apb.exe as admin in propitiates -Didn't work Doing memory leak fixes -Didn't work DX Fixes -Didn't work GFAC fixes -Didn't work Default settings set in game files -Didn't work Everything Updated -Didn't work Closed all programs in background -Didn't work Deleted AppDatas -Didn't work No over clocks of any type (gpu, amp/xmp, cpu) still reset anyway -Didn't work Game repair -Didn't work New install of game (deleting apb reg, appcashe, and so on - so it's a clean install) -Didn't work Hard Drive scan to see if it's failing -GOOD C++ repair and installed (tried both) -Didn't work .Net frame work repaired/installed (did both) -Didn't work Memory test to see if ram is failing -GOOD Windows scan to see if it's Corrupted -GOOD ran the repair anyway -Didn't work Restarted after every step/repair/re-install. -Didn't work Throwing crap at the wall and seeing what sticks -Didn't work

sfc /scannow - DISM /Online /Cleanup-Image /RestoreHealth Didn't work.

23:51:22 - Log: Exception handler starts. 23:51:22 - Log: Main thread is suspended. 23:51:22 - Log: UE3 memory allocator is unlocked. 23:51:22 - Log: Memory freed for exception handler. 23:51:22 - Log: ErrorCode : 0xC0000005 23:51:22 - Log: ErrorLocation : 0xC0000005 23:51:22 - Log: Create minidump. Found in the dump, working on fix. It's APB_Audio: cAudioEngine.

https://imgur.com/a/UWgr9Vz Launching from steam or ExE. No error pops up. 23:51:22 - Log: Log file open, 25/10/26 19:51:22, PID 6400. 23:51:22 - hosting: BugReport.exe -url "http://apb.crashreport.gamersfirst.com" -type "crash" -reporter "Client" -summary "General protection fault: " -showbugreference -log "D:\Steam\steamapps\common\APB Reloaded\APBGame\Logs\2026.10.25-19.51.20-6400.log" -file "D:\Steam\steamapps\common\APB Reloaded\Binaries\..\APBGame\Logs\2026.10.25-19.51.20-6400_Catcher.dmp" -dxdiag -errorcode "0xC0000005" -user 23:51:22 - Exit: Executing UObject::StaticShutdownAfterError 23:51:22 - DevNet: Closing connection Default__NetConnection due to shutdownaftererror 23:51:22 - DevNet: Closing connection Default__ChildConnection due to shutdownaftererror 23:51:22 - DevNet: Closing connection Default__TcpipConnection due to shutdownaftererror 23:51:22 - Exit: Executing UWindowsClient::ShutdownAfterError 23:51:22 - Exit: Executing UWindowsClient::ShutdownAfterError 23:51:22 - Log: Exception: Starting StaticShutdownAfterError()... 23:51:22 - Exit: Exiting. 23:51:24 - APB_Steam: EOS shutdown completed 23:51:24 - Log: Log file closed, 25/10/26 19:51:24 GFAC initilization started! GFAC DLL module succesfully found! GFAC Initialize function found! GFAC Initializion completed! GFAC DLL file found! GFAC Finalize function found! GFAC Finalization completed! [ELEVATION] CheckElevation() called! [ELEVATION] CheckElevation: IsProcessElevated() = 1 [ELEVATION] CheckElevation: IsRunAsAdmin() = 1 [ELEVATION] CheckElevation: passed -> returning 0 [ELEVATION] RequestPrivilege() called! Priv: 20 [ELEVATION] CheckElevation() called! [ELEVATION] CheckElevation: IsProcessElevated() = 1 [ELEVATION] CheckElevation: IsRunAsAdmin() = 1 [ELEVATION] CheckElevation: passed -> returning 0 Finalize routine started! Error: 0 InitRet: 1 [FINAL] Finalization completed!

What even is this discussion and why are people saying stabba is 'good' again. Lol. People will literally teamkill you or yell at you for just trying to playstyle. That's not some random effect, that's a statement.

Stabba is stupid easy to use. Theres a high chance you can stun someone even in CQC. The n9 only needs 3 shots and yo ucan stun someone with it at the same range as a base ntec with both guns. Direct hits with stun opgl or stun nades will result in being instantly stun. You can also go for the classic perc and pig to stun people quickly if you do it correctly. No one who mains crim enjoys fighting LTL weapons, And they hate LTL hackers even more. Since i almost forgot the ltl pistol can also stun quickly it's basically an FBW with stuns. the HB version is a nightmare to face. Also mods do not really help. kev makes it easier to stun you. fragile means one of there friends will just osok you with an HVR flak can stop instant stuns from nades but they spam them so much it's going to barely help. compound all of this with LTL slowing you down and making it hard to see/hear means your almost always going to lose the fight. Crims needs anti stun equipment

Do you mean meters, not feet? 60 feet is only 18.3 meters. The Stabba CCG damage drops off at 50 meters and reached minimum damage at 60 meters.. The Stabba NL9 has a max range of 50 meters.

Ya sounds like a hack, guns that outrange their design, fire faster than the one you have, kill almost instantly. I figure the anticheat has been off since the last event at least in na. I got more proof of that in this event when i saw numerous players in out of bounds areas, so I knew the ac was off. Yes I call them special people too, cuz they get away with everything. They're not even shadow banning. The only discipline they seem to be good at is taking anyone not special out of discord. thus they are very bias toward legit players.

good point

You do realize thats someone using a bot in order to get an unfair advantage right? A stabba normally doesnt 2 tap someone especially at range and how this games spechul hitreg goes if someone has perfect aim or a weapon is acting differently then they have an aimbot. The game registers bots without issue while those who are legit have no hitreg at all.

You guys gave this event only 2 weeks when the population is dead. You maby get an hr or 2 a day to actually play the event otherwise nobody is playing it. This event should of started afew weeks ago and ran all oct long. You then brought about green pumpkins when nobody liked chasing the ones we had to begin with, its tedious and not very fun. Then you make it 600 pumpkins in order to get the skin. Who thought this would be a good idea?

That requires doing the work to click extra buttons tho

The anti-stun item for crims. It was pulled because too many enfs were complaining that they could not stun crims. But now days the ""special" enfs are using a lvl1 stabba to snipe crims at 50+ feet then throw a grenade 50 or 60 ft to kill the stunned crim. What worse is they are using a base stabba to stun crims in less than 2 sec. Bring back the anti-stun equipment to give players a chance to make it to 4 sec. (or even take cover)

Frosi said they are aware of it they gonna fix it. without the sound its much harder to farm and longer

Cant you just type in chat?

Yes I am also Not hearing them, which is the best thing because they are annoying especially in mission area's. I thought LO removed the sounds, as opposed to it being a glitch. Not just the pumpkin laugh its that bass background sound that bothers your battle senses in combat, or is so much louder than the environment you need to adjust your volume.

Subject: APB Reloaded BSOD Report – Potential GFAC Anti-Cheat Driver Issue (0x139) Hello APB Reloaded Support Team, I am reporting a Blue Screen of Death (BSOD) issue that occurs while playing APB Reloaded on Steam. After analyzing the Windows minidump using WinDbg, I found that the GFAC anti-cheat driver appears in the crash stack. I would appreciate it if your technical team could investigate this issue. 1. System Configuration CPU: AMD Ryzen 7 7800X3D Motherboard: GIGABYTE B850M AORUS ELITE WIFI6E GPU: GIGABYTE GeForce RTX 5090 Power Supply: ASUS ROG Thor 1200W Memory: 16 GB DDR5-6000 CL28 (1 × 16 GB) Memory Profile: AMD EXPO enabled Operating System: Windows (exact edition and build available upon request) Game Platform: Steam 2. BSOD Details The system encounters a BSOD and automatically restarts while playing APB Reloaded. Other games generally run normally, and the issue appears to be primarily associated with APB Reloaded. WinDbg analysis returned the following information: Bugcheck Code: 0x139 – KERNEL_SECURITY_CHECK_FAILURE Parameter 1: 0xA – GUARD_ICALL_CHECK_FAILURE Process Name: APB.exe Failure Bucket: 0x139_a_GUARD_ICALL_CHECK_FAILURE_win32kfull!GreProtectSpriteContent Windows Module: win32kfull.sys Driver in the Crash Stack: GFAC_Sys_x64.sys, at offset +0x49aa The crash stack contains the GFAC driver and a Windows graphics-related kernel function. This raises the possibility of a driver compatibility or interaction issue, although the available minidump does not conclusively establish the root cause. 3. GFAC Driver Information Driver File: GFAC_Sys_x64.sys File Path: C:\Program Files\GFAC\GFAC_Sys_x64.sys Installed Version: 0.2.3 build 1 File Timestamp: July 8, 2026 Digital Signature: Valid; signer identified as Little Orbit Inc. Updater Status: The updater reported that the installed files passed integrity checks and that no update was required. The GFAC service was observed in the STOPPED state during a diagnostic check after reboot. Its state at the time of the crash is unknown. 4. Troubleshooting Findings Other games on the same PC generally run normally. The crash dump identifies APB.exe as the active process. The failure is classified as GUARD_ICALL_CHECK_FAILURE. The GFAC driver appears in the crash stack. The available file-integrity checks did not report a problem with the GFAC driver files. The current evidence does not prove that GFAC is the definitive cause, but it provides a specific lead for further investigation. 5. Request for Technical Investigation Could your technical team please investigate the following? Whether this BSOD pattern is a known issue involving GFAC. Whether GFAC version 0.2.3 build 1 has any known compatibility issues with current Windows versions. Whether the GFAC driver could be involved in the failure path containing win32kfull!GreProtectSpriteContent. Whether a newer driver version, official workaround, or additional diagnostic procedure is available. Crash Dump: C:\Windows\Minidump\101926-15062-01.dmp I can provide the original minidump and additional diagnostic information if required. Thank you for your time and assistance. I look forward to your response. Best regards

Actually a lot of the players are now using "nice try team" or "good try team". Which is a way of acknowledging to your team players, that are pointing out the cheats, that all you can do is accept that the Cheaters are a part of the game. So they have a choice, try or chose not to try. But if you chose not to try, then why play. The best way to consider fighting cheaters is to liken it playing a P&P game and your DM is annoyed so throws your party into a random boss fight. At that point all you can do is try. (an prey to the goddess of luck)/

is anyone else not hearing the pumpkins? I ran across several by sight but never heard a red or green one.

Every single page is unlocked. you can make anything you can think of. also includes all emotes