Frosi

As of 64Bit release the bug is no longer affecting actual role progression, its simply a visual bug now so before you bash them for doing nothing you should probably actually look to understand the bug you seem to be so passionate about

First of all, this is an entirely visual bug the Sniper and Munitions Specialist roles will very likely not be bugged anymore after the Easter event is over, however, there will still be some roles that remain bugged as they were already bugged prior to the Easter Patch, this is on their Radar but right now the focus is on getting EAC going.

LMFAO

It'd help if you posted your PC specs and when this issue started happening. Outside of that have you tried to close background applications? I have heard of a case recently where razer synapse would make a users fps dip down to 10-20 from 80+ by just moving their mouse.

They're aware of it but haven't had any sort of good leads on the issue, if anyone starts to realize some sort of pattern related to the crashes it'd be best to let them know.

I haven't noticed a difference whatsoever when it comes to the 4x4.

It does not and its only for the regular Vegas, not the 4x4.

Very wrong, macros are strictly forbidden as per APB's EULA Also I want to let OP know that macros can not make weapons shoot faster than the rate of fire enforced by the server and that very experienced players can get pretty damn close to shooting at the max rate of fire on semi auto guns even without macros. In the end its a hard thing to detect but still very much against the rules and EAC / FairFight in the future should hopefully help detecting them faster.

I think Daarin is making a couple of good points and is pointing out some obvious flaws that LO will have to take into account especially when it comes to phasing. I don't think LO wants to take away from the current social experience APB has right now, it would feel bad seeing ppl just disappear as they're moved to a different district, however, Matt has also already stated that the new system could simply sort players into a district with players of similar MMR which would then mean they could stay on said district to get missions much like segregation worked in the past but working like a rubberband where matchmaking gets stricter and more accurate the more players are in the pool where as threat segregation simply made the game unplayable at off-peak times for a lot of players, especially on NA. It'd help if you were to mention the things you feel iffy about. Obviously that'd have to be fixed first, so would any sort of performance degradation coming from swapping districts, although in my experience it tends to be less when swapping between the same type of district rather than going from WF to Fin.

I'm not quite sure this is correct, I believe Epic dropped 32Bit support ENTIRELY when they moved to their new "Free to use" format for EAC cause this format now REQUIRES Epic Online Services (EOS) integration which is what Epic is currently working on.

APBDB has all the top speed values for the cars in meters per second.

When you made a new character the character was granted every mod in the game at every level with no rank restriction.

Unfortunate but the bug was rather major so it had to be fixed ahead of the weekend.

They are doing some emergency maintenance to fix a major bug / exploit introduced in the patch on Wednesday, estimated downtime is around 1 hour.

There's no simple solution to the issues players are facing right now, you either have 5 playable mission districts (on EU) which keeps the game playable at all times but has matchmaking issues or you turn threat segregation back on which then makes NA less playable at all times for Gold players as well as reintroducing the issue of dethreating which then causes frustrations for the players playing against dethreaters getting a boring missions as well as the players on the dethreaters team since they are now getting actively griefed and are playing a mission one man down. I don't know if there are any plans to bring back threat segregation but I can see why they would not want to bring it back and create extra work which would then delay the actual solution for matchmaking issues which is Phasing, something Matt has talked about a lot and is now possible thanks to the 64Bit update. Phasing for those that aren't familiar with it allows for cross-district matchmaking meaning that all financial instances are connected and the system may now match players from Financial 1 against players on Financial 3, one of the groups will then seamlessly (no loading screen) be phased over to the district of their opponents where the match will take place. Right now the matchmaking system is simply crippled by the fact that there's only 50 players to match against, some of which may be afk or not ready, ram raiding, in an existing mission, too high of a threat to be considered for an even match, in a group bigger / smaller than your current group etc. There's SO many factors that play into matchmaking that if they were enforced any stricter than they currently are players would find themselves not getting opp at all or at least waiting for opp a long time, because Phasing expands the pool beyond 50 players they can then work on a system that enforces stricter matchmaking rules the more players are online meaning that around peak times you shouldn't feel like you're constantly getting put into poorly match made missions which should then hopefully also make it so players don't feel like they're forced to dethreat just to increase the likely hood of getting "fair" missions. APB is over a decade old, some systems simply don't work as initially intended anymore as well as the top players exceeding levels of skill RTW / G1 never thought possible and therefore didn't account for, I don't enjoy playing against silvers either but for the time being even if its not the best experience it is simply down to the fact that the game is in dire need of updates to its core systems and LO can now actually get those updates into the game and I would expect Matt to talk more about the things they have planned in his upcoming roadmap which he will hopefully post soon.

Every account should be brought up to the current max that long time players have on their characters, however, G1 stated multiple times in the past that the inventory capacity could not be increased any further due to engine limitations, it'd be interesting to know if that has changed now that 64Bit is out.

Matt has stated that the community wants them and he's fine with them being used as long as they aren't editing files like shader files to add them to the game because most gaming monitors nowadays let you add one, they can't stop you from taping something in the middle of your monitor etc. So yes, using programs like Hudsight is permitted and is EXTREMELY unlikely to be what got OP banned.

Very nice guide, I hope this helps people that use Linux / Steam deck and want to play, consider publishing it on steam too if you haven't. Also smh my head not using a steam skin

They are going to replace the current anti cheat "BattlEye" which has had mixed results but was the only option for the time being with "Easy Anti-Cheat" in the hopefully very near future. Easy Anti-Cheat has worked very well for APB in the past with just its client side solution, however, this time around we'll be getting both Client and Server side components to the Anti-cheat which should make it even better. From what I know the timing of EAC is however out of their hand right now as they're waiting on Epic to finish their integration of the anti-cheat, once that is done it should be good to go and will be added to the game.

If its an empty district it'll do that, the /fps menu is simply not reliable on lesser populated districts and hasn't been in a long long time. NA has also experienced atleast 1 major crash in the last 48 hours and Matt stated that they're looking into whats happening on the LO discord so it is possible that something may be going on with the servers themselves or possibly another round of DDoS attacks causing issues.

I agree, its very clear that some cheats have gotten updated to support 64Bit already but that's why EAC is coming in the hopefully very near future, when is out of LO's hands right now as they're apparently waiting on Epics part of the integration but I'm sure LO is well aware that the sooner they get EAC going the sooner they can start actually tackling the cheating issue APB is having. Cheaters will always be a thing tho, its just a matter of how fast you can detect their cheat and ban their accounts, its basically impossible to keep them out entirely, even if they got banned in the past.

They want to make it an actual option ingame but for now their plan was to get 1.30 out but also include the ability to uncap for those that really want to, same goes for sliding and the ghost bloom stuff that happen on higher fps values so it'd make sense to fix those things and make it an ingame option in the same patch.

You can do it yourself now, to do so go to your APB install directory and navigate to Engine\Config and open the file called "BaseEngine.ini" in there search for "MaxClientFrameRate=128" to whatever you want the cap to be up to 500 and then start the game with the APB.exe found in the Binaries folder and make sure you have "Smooth Frame rate" and "Vysnc" turned off ingame.

As of this patch you will be able to increase your clients FPS cap by yourself, to do so head over to your APB install directory and go to Engine\Config and open the file called "BaseEngine.ini". In there you want to scroll down or search for "MaxClientFrameRate=128" and set the value at the end to whatever you want your cap to be, to restore the current behavior if you have a 144Hz monitor set the value to 145 although you may now also exceed said cap up to 500. !!!You will have to start the game with the APB.exe located in the Binaries folder to keep the changes set in BaseEngine.ini!!! Raising your FPS cap above 145 will make existing issues related to running above 128 fps worse although sliding will only happen if your fps is too stable aka running at cap. There's an issue related to high framerates that makes your crosshair open and show an inaccurate accuracy value, this is however a purely visual bug and does not actually affect accuracy. If you want to keep using your existing BaseEngine.ini from last patch as part of a config it is advised to add the new "MaxClientFrameRate=" line yourself just under the "MaxSmoothedFrameRate=" line in the .ini, make sure to add a value as well!

There's little interest in testing these things so its usually best to just do it on one server regardless of ping just to have everyone on one server, things would likely be unplayable / testable if there were 2 servers cause it'd be like 10 ppl on one server and 10-20 on the other.