BUSHES, PRONING IN AND NEAR THEM: MAJOR ISSUES

This has been an issue since about Season 1 or possibly even prior:

>> When playing as any infantry if you prone in almost all bushes you are pushed out as soon as you move or even sometimes before you move or if something nudges you. <<

^^THIS IS TERRIBLE^^    ^^IF IT WAS INTENDED, IT IS EVEN WORSE^^

When proning you already have reduced movement so the following can happen with bushes:

-thrown out quickly into the open

-unable to crawl backwards into them, especially right after you've been pushed out, rendering you stuck

-unable to crawl into forwards or at all

-if near a rock or rocky terrain or 2 bushes, the game attempts to adjust your prone or possibly move out of both of them, causing 2 actual forces to apply to your infantry player, causing you to to be placed in a forced limbo between the 2, often moving you to the top of said terrain (exposed, no cover) or have greatly reduced movement.

-if on the side of a bush, you can use the bushes to prone-surf. Even if people do this intentionally it is NOT GOOD. (wall+prone surfing has been in Battlefield since atleast Battlefield 4 and honestly, it needs to be removed from this game. If people are prone and their legs should block their turn to avoid clipping, then their legs should simply block their turn any further in the unfair direction. It makes sense because it's realistic. You can't prone in a tight space and expect to have freedom of movement. There is no reason players should gain movement speed. There should be no worry of getting stuck because if fixed as I described there'd be no way to get stuck, even in an awkward situation, there's always crouch, but even that is affected by bad terrain as well)

-some rocks and terrain alone cause the same repositioning issues as bushes as described above making movement in, near, ontop and around them terrible whilst proning, but even whilst crouching or trying to climb them.

All of the above IS actually game breaking. The only reason I never brought this up earlier is because proning/laying down for cover or to reduce profile is a standard in the military and should be reflected in military shooters so I thought "surely, even the developers see this and will address it. It's such a core issue of the game, blaring problem". But I was wrong. I've done basic searches for "bushes" and "proning" and it's not coming up. Maybe I missed it. Regardless, as of no more than an hour ago, it is still a problem in the game.

Obviously it only affects proning or trying to get in and or out of prone and prone-like states (for example, downed or sometimes coming out of Sundance's wingsuit) so for the run and gun style of most novice or rushed gamers it may have gone unnoticed. Others have seen it and probably just accepted it as is, thinking that they just wont prone in bushes to solve the problem.

Call it what you will: camouflage usage, cover, concealment, hiding, stealth, covert, "camping"; it's all a part of the game. If I can't be seen using a basic fair tactic, that's the opponent's problem.

Could this whole glitch have arisen due to people not being able to easily revive people in bushes or wreckages/near walls so the developers addressed that by having people automatically pushed out of bushes when they are downed? Regardless, making a new problem with a fix is just more work on their plates.

I'll keep checking to see how many others have the same issue on these forums or other communities

(Unrelated game breaking major issue: "mouse" and "aiming" lag issues:

It seems mouse (or even analog controller) input can be completely frozen or lagged out by random vehicles using specific skins at a myriad of distances: Especially aircraft (jets mostly) and some AAs. This issue is sporadic and may not even be related entirely to skins or vehicles but any object/texture. The effects are as described or sometimes massive framerate drops occur. This issue is one of the issues that many have also said makes the game "unplayably choppy" or "broken". They question how DICE and other development teams involved let this slip by but it is understandably hard to catch. It could be a PC thing, but regardless, it is definitely not a "just my computer" thing. Alot of people quit this game over this specific issue. It just happened to me yet again and I stopped playing just to come here and talk about it. My theory is that the game is hunting for specific texture info which hasn't been loaded either due to rushed loads or bad texture organization and then, mid gameplay, instead of just skipping this and putting a placeholder there, it actually causes the screen to stop moving left/right or up/down due to obfuscation/out of view loading techniques used by game engines to reduce the impact on what the videocard / GPU need to work on.

The issue can manifest as jerky aiming inputs, laggy aiming inputs, frozen/unresponsive aiming inputs, (yet the mouse polls fine if you alt tab for example). You all need to work on your LOD management and the core engine behind all of this. It is unacceptable and despite all the improvements to the game, a sluggish/laggy/choppy entirely unsmooth experience will cause many people to question if you developers even have the right priorities in mind at all when you develop games. This stuff, all of this stuff above should not be slipping by. These are the things that we would prefer cause a game to not be release until fixed.)

You've all done a great job with this game, but there's still a lot of work to be done and stuff like all of the above, you can't be waiting for feedback to notice. Internal teams should be catching this. I know it sounds like alot of work but if the focus was on a smooth experience overall from start to finish, this never would've been a problem in the first place. We can't just be testing games on the most powerful in house developer rigs either, hence closed betas."Game looks great but how does it play?"

Thanks for reading. Peace