Forum Discussion

Re: Target indicator does not point to target

Looks like this issue is finally considered one of the "known" issues, but unfortunately, it's been labelled as a  "HP Reverb/VIVE" specific issue. https://answers.ea.com/t5/Technical-Issues/SW-Squadrons-Known-Issues-amp-Announcements/m-p/9526030#M22 I have the issue on my Valve Index and I have no tape or whatever on my headset. As far as I know my proximity sensor is working just fine, but I have no solution for this issue.

4 Replies

  • @vaerkay @Tineras I actually play on the Index (and SteamVR), although (as I mentioned in my original post) the reason my sensor wasn't working was simply because I had spaced my headset too far away from my face, which may not be applicable to you. I assume you've both tried something like sticking your finger in front of the sensor while you're playing in the practice arena? Targeting the frigate is a good way to see if it's working or not.

  • @SR_Jay788 @achreios @vaerkay @Tineras 

    Aaaaaaand.... then it didn't work tonight.

    Took me a half hour to make it work again. I don't remember the exact steps I took -- and why should I, EA?

    Yesterday I had done the "thumb-on-sensor test" with just the Steam VR pop-up -- making it think my head was there and then not. The game worked. This makes me think that it's tied to SteamVR's implementation of presence sensing.

    Today, once I somehow got it to work again, I did the test in game and took a clumsy video. You can see the grid lines appear and disappear. Once it succeeds it seems to work between sessions -- until it doesn't the next day because I forgot my steps?

    Again, I wish I had a nice scientific procedure, but my brain is mush.

    FIX PLEASE!

    -JC

  • Okay... I had it BACKWARDS.

    For *me* tape was not the answer. My extra padding was already making the sensor think I always had my headset on. So every time I started a session I would always see that floating warning and keyboard enter "Win + Y to use the desktop instead..." -- maybe reverting to manual and telling my system that my headset was ALWAYS not on my face. Possibly turning off the sensor entirely -- or at least whenever Squadrons boots, it reads "sensor off" and Squadrons NEVER registers it as on again.. So...

    I moved my extra padding up out of the way very slightly (which in the video below you can see also has a white sweat-soaking stick-on on top).

    I have sensor SET TO AUTO.

    I start WMR and then DO NOTHING with my keyboard. I DO NOT see the floating warning.

    Before even starting Steam or Squadrons I can confirm that everything is working properly and automatically with the Thumb Test --  the big bar with "Win + Y to use the desktop..." appears and disappears with the thumb. THIS IS KEY and if it's working you're basically done.

    (Also, in this state I can completely turn off WMR and it will automatically turn back on when I put my headset on -- a behavior I never did before.)

    Then:

    I put my headset on.

    Start Steam and Steam VR.

    Start and play Squadrons.

    I've tested this both through desktop shortcuts and inside VR with controllers.

    EA needs to unhook any and all behavior from presence sensors.

    -JC 

    @EA_Tom @SRJay78 @achreios @vaerkay @Tineras 

  • Sorry, I have no idea why my videos are so tiny. Clicking on the right edge at least brings up bigger picture-in-picture mode.

    -JC

Featured Places