ANTI- CHEAT Error: (7) (1053)
EA Javelin Anticheat encountered an error. Please restart your PC.: C:\Program Files\EA\AC\EAAntiCheat.GameService.exe ( 7 ) ( 1053 ) Session ID: hy03VSDkurDxjI/gts3KSyskC8B6YttaIUpDJT4UZamSXGw0 Previous Session ID: n/a Previous Service Session ID: n/a Secure Boot: YES BIOS: UEFI Reinstalled Game: YES Uninstalled/ Reinstalled ANTICHEAT: YES Crashes after the Starting EA Javalin AntiCheat: Please help
Updated AFK - wayyyyyyy to quick
Hey EA, The AKF (away from keyboard) is too quick. There was nothing wrong with it before. It was fine as it was. I have timed it and it looks like it only 1:40 seconds before you get booted. They doesnt give me any time to grab my coffee that I left in the kitchen. Answer a knock at the front door. Lets me go take a wee - without me losing my current 20+ mins of game play. Common EA - This is real life. People need to do a few other things sometimes that takes more than 1 minute 40 seconds. Why on earth do you keep changing stuff that doesn’t need changing. You need to start asking for VOTES from the gamers to justify some of the changes your are making. Its messing up the game play. Kind Regards, Kenny Balharry.
Unnecessary Scope Change - SSDS 6.00X
Hey, Whats happened to the SSDS 6.00X. It was awesome as it was. It was clean crisp sharp- perfect. Until today. Why? Why on earth have you added a thicker red / black lines. Its terrible. There was nothing wrong with it. You guys should at least start VOTING to make changes and let players decide. You keep changing things that are not broken and don’t fix the items that are broken. Kind Regards, Kenny BalharryDeployment of the Deployable Cover.
Can we get a fix in for the deployment of the Deployable Cover - that 99% of the time will not even deploy on flat surface because of a spec of dust? The amount of seconds and deaths thatI have received whilst trying to find a suitable location for it - on a floor that is completely flat with nothing on it. You should be able to put it pretty much anywhere - on a flat surface or on bricks or certain corners. On rubble. Its very finicky to deploy. Your moving up / down / left / right waiting for the red colour to change and by then the enemy have seen you and killed you... Kind Regards, Kenny Balharry
Deep Six event / update bugs
Noticed some new, um, features after today's update. The distance meter (or whatever this thing is called) disappeared from the interface. I mean the one where you can choose between 100 to 500 meters on DRMs and sniper rifles. Sorry, don't know the English word for it. It still works, but it's not in the interface anymore. I spawned in IFV that was abandoned by its driver (my squadmate was the gunner). So I spawned as the driver, and the interface was totally broken: all the seats were shown as empty, and I had half of my soldier's loadout and half of someone else's in the right corner, instead of IFV's loadout icon. The Battle Pass points from the weekly challenges I earned today didn't count in my progression until I manually chose "activate path" and reloaded the game (by the way, remove this motherducking pop-up window with BF pro reminder; it's extremely annoying, and because of that I'M NOT BUING IT). Maybe it's fixed, but I can't know since it's not friday. Last two weeks, when I tried to join any of the Friday Night Battlefield servers from the main menu, the game would send me back to main menu after the attempt of loading the map.
When do the bot soldiers head out to sea?
It has been a long time since maps like Tsururifu and Wake Island were implemented, yet I have never seen bot soldiers on them, and the game still requires 32 players to start a match. I seem to recall that the first update of Season 4 improved how bot soldiers behave in water, so I had assumed there might be some underlying issue. However, when I went to the Wake Island map in Portal for an FNB mission, I encountered bot soldiers. I had hoped they would be added to the official servers in the next update, but there was no mention of it in the patch notes—even though others had reported the same issue before me. I don't recall seeing any message from the Community Manager about it; I wonder when this will finally be fixed?