Object Markers in VR since latest patch

[Khelz]

Hi there,

 

Since the last patch, I'm having an issue with object markers on planes in VR. Basically, depending on how I turn my head (Rift-S), and specifically when I turn my head to the right while having a plane in front of me, the HUD marking for that plane is disappearing; like if there was some invisible layer masking the plane marker.

 

I do have a powerful rig (2080ti, 9700k, Me2 SSD, 32Gb Ram, etc.) and I'm playing windowed, if that information can help.

[Essex477Neilpeel1959]

On 10/8/2019 at 12:37 AM, Khelz said:

Hi there,

 

Since the last patch, I'm having an issue with object markers on planes in VR. Basically, depending on how I turn my head (Rift-S), and specifically when I turn my head to the right while having a plane in front of me, the HUD marking for that plane is disappearing; like if there was some invisible layer masking the plane marker.

 

I do have a powerful rig (2080ti, 9700k, Me2 SSD, 32Gb Ram, etc.) and I'm playing windowed, if that information can help.

 

I'm having exactly the same problem.

[Khelz]

Would be nice if we could have an official reply on that issue because it's really annoying when you play with the HUD.

[greasegunDivebomb]

I have the exact same issue with the HUD and its round invisible clear circle to the left and below the cross hairs for targeting. This is affecting all planes and missions of BOS, can not aim at aircraft or ground targets in that invisible spot around the aiming cross hairs.To a point I can not see the ground targets without aiming help ? above 300 meters, they are too small and cannot make them out. My rig is a G force GTX 760, Driver 436.30, Intel Core i5-3550, CPU 3.30 GHz, 7.97 GB Ram, 1920x1080, 60 Hz. Ground targets are hard to destroy!!  

[CSW_Tommy544]

I also have the same problem. There was a new feature added to the game, I think in the last patch, where a frame of your aircraft cockpit should block the object markers. The idea is that you can only see the markers when you really have a clear sight to the object. It seems like the cockpit frame doesn't align properly and now the markers disappear even though you can see the object.

[Major_T]

This problem is still persisting!! I had used my VR on the first day I got it and had no problems... Loaded the same career mode now has this misalignment, makes it almost impossible to see targets clearly!!! Any fixes for this? Really need the help asap!!

[-DED-Rapidus]

First, write down which VR helmet you are using, and second, we need to reproduce the problem exactly. in order for you to send us a problem that occurs in your VR helmet, you need to record a track with the problem in your VR helmet and attach it as an archive to your message.

[sniperton]

17 hours ago, -DED-Rapidus said:

First, write down which VR helmet you are using, and second, we need to reproduce the problem exactly. in order for you to send us a problem that occurs in your VR helmet, you need to record a track with the problem in your VR helmet and attach it as an archive to your message.

FYI I seem to have this problem even without VR.

I'll record it, but you can test it yourself.

 

Test conditions:

- Moscow map, autumn

- any icon mod where icons are reduced to the object marker (no text)

- dive on a ground unit whose marker you can see

- bank your plane while diving: the marker is likely to fade away as you bank

 

I guess the problem is that markers are always above the object according to the viewer's position (and not relative to the ground).

When you bank, the marker position rotates according to head position and gets behind nearby houses/trees.

 

[-DED-Rapidus]

On 1/29/2020 at 3:34 PM, sniperton said:

- any icon mod where icons are reduced to the object marker (no text)

I have a task to test with regular means, without modification, by installing modifications you agree to the conditions that may arise when modifying the game.

Without modifications, everything works as intended by the developers.

[naigovan]

I've encountered this issue by lowering Dynamic resolution factor to 0.8. Issue was fixed when I've set it back to 1.0