BlatMan

They gave up on the new engine. We didn't even get the updated districts. TBF, Matt didn't know the extent of Reloaded's laziness. Reloaded claimed they couldn't update the existing engine to 64 bit, yet LO was able to do that as a last resort in a relatively short timeframe after announcing it. Matt just needs to listen to his gut instead of waiting till it's almost too late. Matchmaking still sucks, but in a different way. They broke it to where I was unable to get missions. I recently tried it again. I don't wait as long, but the missions are not balanced in the slightest. Escalation isn't balanced. It favors groups over individuals, like the old backup system. Using that button is an automatic win for the defending team, unless it's final stage. Then it's kinda fun to use. I still can't unlock symbols on my lower rank characters without deliberately losing missions. Joker tickets override the contact random rewards. There's still nothing in game indicating which contacts unlock what, and a lot of items are hidden until you unlock them, like one of the wristwatches. It's a terrible experience for new players, not counting matchmaking itself.

Currently,the .45 AP is 5 shots up to about 36M, and goes to 15 shots at 45M. https://apbdb.com/items/Weapon_Pistol_Colby45AP The .45 AP used to be 5 shots up to about 43M, and 15 shots at about 65M. https://web.archive.org/web/20220523194242/https://apbdb.com/items/Weapon_Pistol_Colby45AP https://web.archive.org/web/20131019011659/http://apbdb.com/items/Weapon_Pistol_Colby45AP/ It was nerfed by Little Orbit. I don't feel like looking at the patch notes to get the exact date.

It used to be more accurate and had better jump shooting accuracy. It was overall better than the other SMGs, but it had a lot of recoil so not many people used it. They need to revert those changes.

They used the abbreviations "AI" and "ML" because those are the in words. Technically, most modern anti-cheat uses some form of machine learning to detect cheating, so they're not lying. They don't care about those AI chips. If they did, they wouldn't go through so many hoops to get them. They'd just import them from the neighbors.

They nerfed the .45 from 40M to 30M, and accidentally set the minimum damage to 35M but decided to leave it. The FBW is in a decent state currently. It doesn't compete against primary weapons, but is versatile. If the FR0G had more range, it would be better than the FBW in most situations. I can't say without using it with those stats. It does bloom a bit more than the FBW. OBIR starts missing some bullets at 80-90M. It's not out shooting any high velocity rifle at 90M. Obeya had it's damage and range nerfed. I can't say if it's a good or a bad change. I stopped using the SLR variant due to the crackling audio bug. N-ISSR-B is meh at best. The range reduction with the silencer puts it in a spot where it's not really good at anything. Sorta the jack of all trades. The jump shot is useful for tagging people behind cover. Everything is unbalanced if someone has an aimbot.

The Obeya Rifle. They nerfed it's range by -5 meters, and reduced the over damage, which indirectly affects it's damage at range.

The .45 was overnerfed. The FBW was so "balanced" that they made it the starting primary because no one used the Snub. Then they nerfed the Snub's draw time, the only useful thing about it. The FR0G, well all secondaries, need the -1 round negative removed from the silencer mod. But no, we get an OBIR nerf to make the new legendary have a niche. It's the same as when Reloaded nerfed the Scout's jump shot, to sell the N-ISSR-B with it's jump shoot capabilities.

Also, why nerf the OBIR? It's not like it's used much as is.

I have a few questions about the SARD Anti-Cheat compatibility. - Does SARD work with Proton on Linux? It says it's compatible with Steam, but I can't find any other info on their website. - Does it allow other rendering methods, like DXVK on Windows 10? - Can SARD run on Windows 7? It doesn't need to be supported, just wondering if there's any artificial software locks. APB runs horribly on Windows 10. I have two PCs with CPUs that were manufactured 14 years apart. On both PCs, APB slowly loses framerate the longer you play, but only when running on Windows 10. This was not a problem on Windows 7, and it's not a problem currently on various Linux distributions. It's only Windows 10. It's the same on the latest Enterprise and the various LTS versions.

Nanichi is a GM. Trust me, you don't want GMs having ban power, especially since the current set of GMs are volunteers who are APB veterans. It's impossible to not show favoritism when you've been part of the community that long.

Where is the support history? I don't have any tickets open at the moment, but I would like to know for future tickets.

LO's too incompetent to pull that off. Most likely it's accounts being farmed for other games.

No. They updated the current engine to support 64 bit, and shutdown the console version. They also updated EAC to Epic Online Services, which means no more Windows 7 support. It's not a complete upgrade. Most of the code is the same. Character movement bugs out when the framerate is over 128fps. Memory management seems to have 32 bit limits. The game runs poorly when there's too much memory assigned to it, and it stutters when AMD's Smart Access Memory is enabled. Input lag is higher on Windows 10. Don't expect it to feel snappy like it did on XP and 7.

You don't even get a copy of the ticket sent to your email. Who knows if the ticket even went through correctly.

It should be made account wide, both for you and the person you're ignoring. I hate having to add 10+ names, for each of my characters, to block 1 person.

There might be an issue on your end, but this game has had hitreg problems for years. The main thing to check is if your ammo goes down after you shoot. If it doesn't go down, this is called a "Ghost shot". Usually it happens when you click too perfectly with the weapon's rate of fire. The server thinks you shot too soon and doesn't count the shot. If it's happening when shooting slower, then it might be upload packet loss. There's no way to check for this in-game. Packet loss will show 0.0, even when 99% of your uploaded packets are being dropped. Due to the weird hit detection, sometimes you can compensate by aiming ahead or behind the player. I've gotten plenty of kills by intentionally shooting into the edge of a wall a player was about to run behind, rather than aiming at the player. Same with those yellow dumper bin things. Sometimes you can shoot through the top corners. You'll see bullets hitting the dumper, but you'll get hitmarkers on the player. Also, it might be a new issue with their service provider. I was playing last week and noticed hit registration was acting weird. For a few minutes, none of my shots would could, but the oppositions shots all counted. Then in the next mission stage, all of my shots count, and I rarely took damage from the opposition. Never experienced this before. It's usually the same, good or bad, until the server restarts or I switch to a different district.

I am experiencing game freezes or stuttering when bullets hit vehicles, only vehicles, with AMD Smart Access Memory enabled. I cannot find another object that causes stuttering when it gets hit by a bullet. Disabling Smart Access Memory seems to fix the stuttering issue, but there is still a significant framerate decrease. For example, standing next to a dump truck and hip firing an Agrotech ACES at it causes about a 20% loss in fps, but aiming down sight, while shooting the same dump truck, causes up to an 80% loss in fps. This performance loss is about the same on 2560x1440 and 1024x768 resolution, and the same between max and minimum graphics settings. Steps to reproduce: - Install an AMD RX 6600 and the latest AMD GPU drivers. Current version 24.6.1 - Enable Smart Access Memory in the Adrenalin application. - Restart PC. - Launch APB Reloaded. - Join a district. - Equip a high rate of fire weapon, like an Agrotech ACES. - Stand next a vehicle and hip fire at it with your high rate of fire weapon. Notice the game stutters. System Specs: CPU: AMD 5700X3D RAM: 32GB (2x16GB) DDR4 3600 14-14-14 GPU: AMD RX 6600 Suggested Fix: If possible, add a graphics option to remove or reduce the bullet impact particle effects. There's two options called "m_bShowServerHits" and "m_bDebugHitMarkers". Enabling these in the past disabled the bullet particle impacts, and replaced them with red dots. I would look at these features to figure out how to turn off the bullet impacts without affecting other particles.

Whatever it's locking onto, it's sure ain't the opposition.

I don't blame you. I have reported a few blatant cheaters, with evidence from their own youtube and twitch channels. They eventually got banned. Then Little Orbit decides to unban them. Why waste more time reporting if they're going to get their accounts back?

Have both of you been smoking with Mack lately?

Most of those changes were after the retail release. There's plenty of retail boxes floating around. The important parts can be extracted, like the old districts and weapon stats. G1 shipped the whole stat file with the retail version for years. LO have access to all of it if they feel like looking for 5 seconds, but like you said they can't get out of a wet cardboard box. It took them a year to release an "almost finished" vehicle, but it was still in the concept stage of development.

You can try lowering the USB poling rate on your mouse, but it will increase input lag and turning the camera might not looks as smooth. On my old PC, I have to turn off HPET, both in Windows and the BIOS, or I get massive fps drops when moving the mouse. Quoted Floid from the Steam community: https://steamcommunity.com/app/1527950/discussions/0/6222330214313935470/

And it's not hard to add notes to bans that confirm cheating from the cheaters perspective, like the few I've reported. I bet they screwed up their ticket database when migrating to zendesk, and gave up because the only person who probably knows their old system was fired.

That mission wouldn't be so bad if the truck didn't respawn. Imagine if you had to repair the truck instead, but it can only be repaired moving below a certain speed. . Give everyone a blow torch. Instead of exploding, it catches on fire and quickly damages anyone inside it, to prevent people from hiding in it. Maybe only give points while the vehicle is moving.

Since EAC won't be used, and Battleye most likely won't make a return, does this mean we can use DXVK (DirectX to Vulcan translator) and play on Windows 7?