Jump to content

Recommended Posts

Posted (edited)
1 hour ago, Raven (Elysian Angel) said:

It depends on which headset you use. On my Varjo Aero it renders perfectly, but it's a headset with a rather large physical "nose gap" that some people find annoying. So the problem is the rather large physical differences between different headsets, making a "one size fits all" solution for visors challenging.
This will affect any module that uses a JHMCS (the upcoming F-15C as well for example), as you need the visor for the symbology. When flying MiG-29 users who don't like the visor can simply flip it up (or rather, not flip it down as it's up by default) and they don't lose anything.

Absolutely correct! I use a Quest 3 and have no issue with the visor but the where the center of any JHMCS is too high for me. With the amount of possible different combinations of headsets, single and multiple monitors and particular user settings and resolutions out there, a "one size" kind of approach will never "fit all". 

Of course, that same combinations of hardware and software setting make the generalization of comments like "it doesn't work well for VR" (just an example, since I fly only in VR) absurd. What doesn't work well from one user might be perfect for others. Options about configuring these features is what we all need. 

It is definitely a challenge for the dev team.

Edited by Draken35
  • Like 1
Posted
6 hours ago, Lange_666 said:

It's a lot closer to reality now in VR instead of the 2D version where it's more on/off.
A lot of people want their sim to be as close to reality as it can get until they are annoyed by something and then all of a sudden it's not so needed any more. 

It can be as real as you want it: if YOU want it, enable the option. For others with headsets where the gap is glaringly visible, give them the option to fill in that gap, and remove the top "mask".

Just like how there's an option for:

  • Disabling super carrier deck crew
  • Enabling HMD rendering for both eyes
  • Using a non FFB device with non-FCS jets
  • Setting custom curves on axes

I could go on, but you get the point. Gameplay/hardware issues should supercede "reality". Nobody is after your slice of the pie. Some don't even like pie.

 

5 hours ago, Draken35 said:

Absolutely correct! I use a Quest 3 and have no issue with the visor...

I'm not too knowledgeable with headsets, but it seems that this issue depends on binocular overlap: if it's too low, you won't even see that nose gap

Posted (edited)
On 10/31/2025 at 11:05 AM, niru27 said:

I'm not too knowledgeable with headsets, but it seems that this issue depends on binocular overlap: if it's too low, you won't even see that nose gap

As a funny aside, it also depends on where you're looking.  Your FOV is significantly affected by where you're looking, your pupil translates almost a centimeter when looking left vs right.  Fairly significant when the lens is almost up against your eyeball.  In my headset, I can see the gap clearly when looking straight ahead, but if I look at it with either eye, it's suddenly outside my FOV and I couldn't see it, which made me think I was imagining it initially 😅

Edited by jaylw314
Posted

I completely agree that a toggle would be useful. I don't see it specifically mentioned, but the AH-64 Apache already has precisely this capability with an "IHADSS monocle visible" toggle box--it could be just like that.

  • Like 1
Posted
21 hours ago, jaylw314 said:

I can see the gap clearly when looking straight ahead, but if I look at it with either eye, it's suddenly outside my FOV and I couldn't see it, which made me think I was imagining it initially 😅

Haha I had the same experience 

  • Like 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...