Gamebreaking Visual Bug

by Greenvana14
Reply

Original Post

Gamebreaking Visual Bug

★ Novice

Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number Intel(R) HD Family Graphics
Enter RAM memory size in GB 8 GB
What is your gamertag/PSN ID/EA Account name? greenvana14
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Which Legend were you playing (if applicable)? All of them
Which Legends were your squad mates using (if applicable)? All of them
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Left Side
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Playing normally
Did your squad mates also experience the issue? No
How many matches had you played in a row before the issue occurred? 0
When did this happen? (dd.mm.yy hh:mm) 09/02/2019
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? You cant turn to some direction or you will face a visual bug that makes blurry your screen, plays the hero selection on top of the game and trips your sight.
What should be happening instead? You should play and see normally
Steps: How can we find the bug ourselves? Check my video and you will understand

Check this video to see the bug

Message 1 of 4 (213 Views)

Re: Gamebreaking Visual Bug

[ Edited ]
★★★ Newbie

why are there so many fortnite tryhards it makes tha game not fun for us not tryhards because we arent [Inappropriate comment removed - Admin.]

Message 2 of 4 (206 Views)

Re: Gamebreaking Visual Bug

★ Novice

This is not an opinion post and we dont care about your game preferences, i dont play fortnite and dont know what does that game has to do with my issue so plz stop

Message 3 of 4 (203 Views)

Re: Gamebreaking Visual Bug

★ Novice

its fixed, it was the driver of my graphics card

Message 4 of 4 (159 Views)