Same issue, and might as well be targeting using WWI visuals. I can highlight and acquire a target, but the minute the distance closes to where you should get the white box for tracking, aiming, shooting, it just doesn't happen and I lose track of my intended target. Frankly, this is a bit ridiculous for a core component of playing this game in VR.
Product: Star Wars: Squadrons
Platform:Steam-PC
Please specify your platform model. nVidia 2080 Super, 32gb RAM, i9 9900K, 1920x1080 g-sync desktop monitor w/144MHz, HP Reverg vr headset.
What is your gamertag/PSN ID/EA Account name? Steam/Origin: OMGBigData
Are you playing in VR? Yes
Which VR Platform are you using? Steam VR- HP Windows Mixed Reality Headset (the first one that they launched not the reverb line)
Which part of the game is the issue happening in? Whenever you lock and attempt to track and target
What were you doing when the bug occurred? Step by Step detail is helpful. Playing in VR, every single time I engage and attempt to track and destroy a target
Where did this issue occur? Please include menu name or in game location. When targeting anything.
When did this happen? From the release of the game up to the present only in VR
How often does the bug occur? Every time in VR
How severe is your issue? Makes the game incredibly difficult to play given this isn't a WWI/WWII/Korea simulator; takes away from experience; incredibly frustrating knowing that I get killed due to circumstances I have no control over
What happens when the bug occurs? The white box which is supposed to appear on the target that I have locked onto, never is on the target; Instead the white box just moves around me as the I turn my head in VR; no tracking of target within ranges to use cannons; just straight naked targets
What do you expect to see? A working target tracker; eg white box and brackets
Which ship were you playing? If not applicable, just answer "no" or "none." Every ship
What components were you using? It carries into everything
Which customizations (if any) were you using? I have tried changing settings many times and it appears that they have no effect on the bug.