Heavy's Blaster Upgrade Bug
Product: Star Wars Battlefront II
Platform:Sony Playstation 4
What is your issue related to? General
Summarize your bug The improved zoom modification for the heavy's first unlocked blaster is bugged. Sometimes the crosshair/scoping animation is completely missing, it's not zooming any further than default zoom even when it is present. Only work around is to pull out then put away the sentry gun. After doing this, every time you respawn, your crosshair will return, but the zoom is not improved in any way from default.
What is your gamertag/PSN ID/EA Account name? PSN: Steelshanks EA: JOKHAHHURELIPPEN
How often does the bug occur? Every time (100%)
Can you tell us the date (MM/DD/YYYY) that you saw the bug? 03/22/2019
What time did you see the bug? (HH:MM AM/PM) 01:40 AM
In what game mode did the bug occur? Galactic Assault
What is your time zone? EST (IET) - GMT - 5:30
Steps: How can we find the bug ourselves? Load into a Galactic Conquest match. Select Heavy role. Change blaster from default (top) to the second (one below default). Select the 2nd attachment, the improved zoom. Spawn into game. Confirm attachment is working normally by zooming. Die by enemy. Respawn (teammate or default). Check if attachment is working normally by zooming (which should not be functioning.)
What happens when the bug occurs? The crosshair, as well as the cosmetic border for the "scope" will be missing. The default crosshair will also be missing. It will be as though you were a camera that is zooming, with no aiming point to indicate where your shots are going to go. You can still fire and use eyesight to adjust kinda like using shots as tracers, but due to the volume of fire, this is an ineffective strategy for a heavy engaging at medium or longer ranges.
What do you expect to see? Being a programming student, I expect to see the development team isolate why the scope is not "repainting" upon respawn, but only on first spawn. In java, this would probably be because either a pack() or a repaint() wasn't being triggered on the respawn(). I'm sure you're doing a different coding language,but logically I'm betting that the problem is similar. Also, I've noted that this problem has been reported before, multiple times, spanning over a year. I find it extremely disheartening that a bug that only occurs after a respawn, which indicates which section you probably should be looking at, has taken over a year to solve. I'm willing to bet its because you haven't actually put forth any effort on it. So I expect to see progress. I know you're probably not making a ton of money on Battlefront 2, but leaving it bugged is the same as never completing the project. Seriously not trying to be rude, but even students have deadlines. We're also taught that most deadlines for bug fixes are measured in days to weeks, not years. How is someone not fired over this?
Please select your region North America
AMD or Nvidia Model Number PS4 so don't think this applies.
Not sure what information you expect me to add here that wasn't contained above. Perhaps while you're fixing the bug I'm reporting, you could also make your form a little more informative as to what this section is for.
