BlatMan

They're probably getting just enough bonus score from completing and defending objectives to prevent them for losing threat. There are some missions where they get 0 score, which means it doesn't count against their threat. I don't get the bonus for defending objectives since I'm usually away from the objective spawn camping, I mean tactically watching for spawns.

All I know is there's too much of a skill imbalance because threat doesn't come close to matching your overall skill level. I'm not sure how to fix that without rewriting the threat system. A few of my friends are currently borderline gold threat but often they play like new bronze players. Their callouts are more than 5 seconds behind the action. They'll say 2 players are rushing me, but I've already killed both players and finished reloading with extended mag. I don't get it, how are they not bronze?

The only griefing I've experienced recently are clans having other members, who are not in the mission, block doors with their vehicles and move objectives so you can't finish them.

You can send all the clips you want from the cheater's own twitch and youtube. Nothing ever happens to the cheaters. Support get mad and break character when you update an existing ticket with more evidence from recent streams. It also doesn't help that the in game GMs are old players and not real GMs.

Teammates can damage your vehicle in the event. See what I mean by unplayable?

Air bag suspension update looking fire.

4x4 Fresno You know what. F it, 4x4 Green Planet garbage truck.

To add to the above, you have to compensate for server latency. On east with 20ms I can consistently switch while throwing the grenade, but on west half the time the grenade does not throw. I've also never need my mouse wheel to do it.

Just means the game will be unplayable for 2 weeks.

It's roughly the same. Some bugs were created while others were fixed. Weapon balance is still not right but not that bad either. If you have most of the customization unlocked it's relaxing to just join social and mess with your character.

Technically one does exist but the hitbox doesn't scale with it. Also, using the Always Sprint config breaks the animation.

I'm fine with the timed out of bounds system. They need to remove the instant kill areas, and it should not be active when out of mission.

I prefer to purchase functional hardware. I seem to be in the minority these days.

Case and point, MACKxBOLAN is somehow silver.

It would only be 5 seconds if it was the old main manu.

Honestly, that would probably be the best thing to keep new players coming. Kinda hard to get someone interested in playing when the first thing they see is a loading screen, followed by a low budget Bollywood knockoff of Michael Bay with a fog horn at 100% volume.

To add to that, let players manually choose which side of the vehicle to exit from. I hate it when there's plenty of room to exit the vehicle but the game thinks it's blocked so it shoves me in the passenger seat for 2 seconds, then another 2 seconds to get out, then I blow up.

Old Tommy gun recoil with muzzle break and high mag. It was OP if you had a tall enough mouse pad.

It's the upper section between the two parking garages.

Little Orbit isn't responsible for someone spending thousands of dollars on a barely functional free to play game.

DMR-SD: Pull down mouse a little. DRM-AV: Pull down mouse a lot,

Ghetto fix it by adding a timer that starts when you stop pressing a movement key. After X seconds set your movement to 0.

PR1 and PR2 have the same recoil. PR1 has less bloom, but that's not an issue when shooting vehicles.

Also occurs with a Logitech MX518. It gets worse as you increase DPI while keeping your sensitivity to the same ratio. This mouse uses a different sensor, has wider DPI range, and use onboard memory instead of software for it's settings. That should eliminate any mouse related issues. For example: 800DPI, 10.8 sensitivity, 0.35 marksmans mode, issue occurs but not obvious. I can't consistently reproduce it. 800 * 10.8 * 0.35 = 3024 6400DPI, 1.35 sensitivity, 0.35 marksmans mode, issue is very noticeable. I can slowly move the mouse across my desk without turning the camera. 6400 * 1.35 * 0.35 = 3024 Remember this mouse fix thread? https://forums.gamersfirst.com/topic/364-mouse-accelerationdampening-fix/ Baseinput.ini: Bindings=(Name="MouseX",Command="Count bXAxis | Axis aMouseX Speed=2.0") Bindings=(Name="MouseY",Command="Count bYAxis | Axis aMouseY Speed=2.0") Those settings double the number of counts the game sees from your mouse. I tried messing with it and noticed that setting to say 0.5, 0.25, etc, makes the issue occur even at player tracking speed, while 2.0 made it harder to do. This explains why some people feel like their mouse is more responsive with that fix. Regardless, this problem needs to be resolved. There's lots players who play other games with extremely low DPI, as in using 20" of desk space to turn 180 degrees or less. These players will not be able to play APB reloaded. How have I not noticed this issue since 2012? It's most likely due to using a higher sensitivity than most "pro" players. (800DPI, 10.8 sense, 0.35 mm) and using a 1680x1050 75hz display. I now play with a 2560x1440 144hz display. Every now and then I notice a slight pause or a pixel jump. I thought my +10 year old mouse was diying, or 800DPI is not high enough to pixel perfect aim at 10.8 sense. I tried changing it and noticed the camera stopped moving.

APB's camera does not respond when using very low sensitivity. I've tested it with different DPI settings. 400 DPI requires faster mouse movement to make the camera start rotating, 3200 DPI requires slower mouse movement. At 400 DPI, I can move the mouse across my desk and not turn the camera. This is only affecting APB Reloaded. Steps to reproduce: 1. Set sensitivity to 0.5 or lower. 2. Very slowly move mouse to rotate camera. Results: The camera does not rotate. Expected Results: The camera should always rotate. Other Information: List of changes that have no affect: - Graphics settings (min/max, fullscreen/windowed, etc). - Windows cursor speed. - USB poling rate. - Putting mouse on dedicated PCIe USB 2.0 controller. Other Sensitivity settings that cause this issue (DPI, Sensitivity, Marksmans mode sensitivity). - 1600, 5.44, 0.2 - 3200, 2.71, 0.35 Hardware: CPU: Xeon W3680 @ 4.25GHz RAM: 12GB DDR3 2133Mhz Triple Channel GPU: GTX 1080 8GB Mouse; Logitech G400