can not reproduce VR: HIADSS Symbology too high

[MRTX]

Like I mentioned before, just make the IHADSS adjustable and all of these problems would go away over night.

[Rosebud47]

After trying out some tools to solve my issue with the offset of the IHADSS symbology to the left in the Reverb G2, like trying out Necksafer, Stereo setting on/off, resetting the VR setup with WindowsMixedReality Tool and trying to adjust the settings with the DCS integrated OpenXR tool ( to initialize with the autoexec.bat ), nothing seems to help.

The problem is not only that the IHADSS symbology is offset, but also the rockets and gun-shots are offset accordingly, means I focus on a target and the rockets ( properly targeted ) and gun-shots are offset to the right from the IHADSS according to the IHADSS offset to the left from the LOS or head tracker or virtual cockpit. 

I don´t know ... but meanhwhile I believe, that there is not ED to blame for the issue I have, but the Reverb G2 respectively the Windows Mixed Reality VR headsets, like the DCS integrated OpenXR tool to adjust the settings per eye indicate an offset as well, what I don´t understand neither.

But still it is valid to point ED to the issues many have with IHADSS, as a function to adjust the IHADSS cosmetically might bring the solution for many, as in my case the rocket and gunshots seems to point correctly, it´s just the IHADSS which is offset from the aiming and impacting point of rockets and rounds.

[Loadie]

I have a Quest 3 and this is a massive problem for me! I’ve tried literally everything to adjust the headset itself, nothing has worked. It actually hurts my neck when I adjust the headset so I can sort of see the heading tape. 
 

please DCS adjust the ability for users to move the HDU itself, just like in real life! That monocle can be adjusted for each persons head.

[Toge]

I have the same issue with Q3. Reverb G2 was spot on for me, but two other headsets were not. Also, on Q3, the whole monocle is too far forward, so the tube/lens blocks a lot of the lower right view.

[Loadie]

On 12/17/2024 at 9:58 PM, Toge said:

I have the same issue with Q3. Reverb G2 was spot on for me, but two other headsets were not. Also, on Q3, the whole monocle is too far forward, so the tube/lens blocks a lot of the lower right view.

There has to be some setting in the Q3 that can fix this issue! Now when I use George AI, the AI pop ups are vertical vice horizontal. I’ve got a ticket submitted with ED; however, I can’t even take a screen shot in the Q3. When I hit the oculus button and pull the trigger, all I get is the DCS folder pop up and it asks me to readjust the view or do you want to quit DCS. I can’t even take a video of this as the second I remove the headset the eye pieces shut off. I’m so confused now!

[Shaman]

I have just gotten to fly DCS in Quest 3... I think I know what the problem is.

I think the reason is we tend to lean back on our seats (I have ACES II replica) due to seat construction, also the weight of VR headset makes us raise our chin compared to where our head would be without them. The HMD is perfectly centered on screen and this is why ED devs can't replicate this issue.

HMD vertical adjustment should be a special option for every module, not only Ka-50 2 and Ka-50 III.

[Rosebud47]

Am 26.12.2024 um 12:38 schrieb Shaman:

HMD vertical adjustment should be a special option for every module, not only Ka-50 2 and Ka-50 III.

 That's a good point and an option to have for the Apache monocle.

With my Reverb G2 the offset of IHADSS symbology for sure has to do with VR-headset itself. It was very much visible as I recently jumped in to a cockpit of another sim, which name starts with an "I" and ends with "l2-Sturmovik"; the left eye view was completely distorted. So, the solution found to this, was in windows settings/ mixed reality --> headsetdisplay--> there is a pull-down-menu, which gives the option to "let windows decide", "best visual quality" or "best performance". Switching to "best visual quality" solved the problem in IL-2 for me, but still there is some offset of the LOS from the heading tape to the left in the Apache. Didn't noticed it before, but the slightly offset is also present for me in the HMCS of the Viper, which doesn't bother. The internet said, when the USB port of the Reverb G2 was changed, windows switches back to "let windows decide", which causes some problems in the Reverb G2.

Using the gun in the Apache with the IHADSS works fine and with precision meanwhile, so this VR-headset offset issue doesn't bother me in the Apache neither. 

For sure, the option for vertical / horizontal adjustment would be great to have, as an individual adjustment of the IHADSS for the VR-headset in use. 

[Draken35]

On 12/26/2024 at 6:38 AM, Shaman said:

I have just gotten to fly DCS in Quest 3... I think I know what the problem is.

I think the reason is we tend to lean back on our seats (I have ACES II replica) due to seat construction, also the weight of VR headset makes us raise our chin compared to where our head would be without them. The HMD is perfectly centered on screen and this is why ED devs can't replicate this issue.

HMD vertical adjustment should be a special option for every module, not only Ka-50 2 and Ka-50 III.

While there might be something to this, I think it is headset related. I have a Sim Fab chair and a Quest 2 and a 3. The center of mass of the Q2 is farther away from the face than the Q3, causing it to feel heavier but, the IHADSS (and Viper/Hornet HMDs) are centered in my LOS in the Q2 but not in the Q3.

Edited December 27, 2024 by Draken35

[loadie150]

I have a ticket in on this issue, sadly, I don't think ED is going to do anything for us. It sucks, I love the Apache but with this issue, I might have to put it away for a while! I've literally tried everything manually I could, lowering the VR headset on my head, tilting the facepiece, everything I do results in the same issue. AS Pilot the George AT sits so high I can barely read it. I can't see the top of the the circle on the AI popup either.  

[BIGNEWY]

The problem is we are not able to reproduce the issue you are seeing. I will ask QA to take another look however. 

thank you 

[jaguar56]

Just purchased the Apache module yesterday and use Q2.  The offset was the first thing I noticed.  So, I started a search on how to adjust it and found it was not possible.  The Apache module is very deep and complex.  And the IHADSS is a central function.  With it being off it makes it that much more difficult to learn.  

Based on what I am reading in all the threads, every VR user is just enough different to throw this off.  The user and headset that ED tests with got lucky and is right on track.  But it seems at least 50% of us are not.  

Put me down as voting for the ability to adjust it.  If it has been done in other modules it is clearly not asking for something impossible.  These are expensive modules.  It is not right that people can't use it properly due to this issue.  Please stop fighting it and just make the adjustment possible.

[ShuRugal]

On 1/15/2025 at 1:30 PM, BIGNEWY said:

The problem is we are not able to reproduce the issue you are seeing. I will ask QA to take another look however. 

thank you 

That would most likely be because your faces are not the same shape as the faces of those of us having this problem.  Short of getting plastic surgery, i don't see how you COULD reproduce an issue stemming from the fact that HMDs fit on people's faces differently.

[bak3dp0t4to]

This does not seem to be a matter of HMD fit. I did not have this issue when I was still using my Oculus CV1 and it's only started since upgrading to the Q3. People in BSVR and PiMax seem to have mixed results as well, however as BigNewy has said over and over and over and over, he does not have the problem on his Reverb G2.

So, what that means is that just because you don't have the problem, it doesn't mean others don't. Different resolutions in different displays will all need to be rendered accordingly; a one-size-fits-all does not work here. The display needs to be adjustable by the user. For me to get the HMD in the F-16 aligned so it doesn't show when I'm looking straight ahead I have to move my headset forward until the forehead pad is resting below my eyebrows. You cannot tell me that that is the proper way to wear this headset.

This has been an issue for years now and it keeps getting blown off.

[ShuRugal]

On 1/15/2025 at 1:30 PM, BIGNEWY said:

The problem is we are not able to reproduce the issue you are seeing.

Unless you all are getting plastic surgery to change the shape of your face to the shapes of those of us who are having the problem, i would expect that you can't reproduce the problem.

[BIGNEWY]

I am using a PIMAX Crystal currently and I still don't see an issue, I will ask internally again for others to try and reproduce. 

 

[Firebird1955]

I must agree that the George AI circle is far too high in my line of sight as well in VR.  I am using a Valve Index and it is placed above the compass line in the  IHADSS to the point that I cannot see it clearly (same thing everyone was talking about in 2022 thread).  Since it is fixed to the placement in the VR location, moving your head just moves the circle with the IHADSS movement.  Also the target list once "deslaved" is far down at the bottom of the IHADSS.  Hard to believe that this issue has been going for over 3 years.  Not sure what the issue is to make it player adjustable (I am sure programming has something to do with it), but it seems with the variety of users, flexibility would be key to success here.  Just my humble opinion

 

Edited May 13 by Firebird1955

[Raven (Elysian Angel)]

21 hours ago, Firebird1955 said:

the George AI circle is far too high in my line of sight as well in VR.

Yes it is: to look at it i have to roll up my irises so much my eyes hurt.

I fail to see why it’s so hard to make a Special Option that allows users to adjust the default position. If Heatblur can do it, so can ED…

Edited May 14 by Raven (Elysian Angel)
Typo

[Draken35]

On 5/13/2025 at 9:38 AM, BIGNEWY said:

I am using a PIMAX Crystal currently and I still don't see an issue, I will ask internally again for others to try and reproduce. 

 

I think the real issue is how the head set sits on the individual faces and not really in the modules code. The Quest 3 "center of vision"  sits a bit high on my face with the OEM face interrace and in comfortable position. This is only evident when a Helmet Mounted Display is used (Apache, Hornet, Viper and Blackshark). With the Blackshark it can be fixed via special options easily but with the others, my only solution is to push the headset down and crush my nose, which is  very uncomfortable of course.  The Quest 2, on the other hand, sits perfectly on my face.

Since this is "hardware" (our faces) related, I suspect that you will have a hard time reproducing it if your current team members cannot already experience it. The best and only solution, IMHO, will be to add special options to the modules to allow to adjust the HMD device like the Ka-50 does.

[Dangerzone]

On 1/16/2025 at 5:30 AM, BIGNEWY said:

The problem is we are not able to reproduce the issue you are seeing. I will ask QA to take another look however. 

thank you 

Hi BN,

Just a thought - Instead of treating this as a bug in DCS - would it be possible to approach it from the perspective of a feature request instead? (Ability to move the IHADSS's position like the recital can be in the KA-50)?

This way - replication of the issue that users are experiencing wouldn't be a requirement/obstacle to overcome in order to provide a solution. Just adding that option as a feature for the AH-64 in the same way as the KA-50 would go a long way to solving a 3 year now issue for people (plus add a new feature in even for those not having an immediate issue with it)?

Cheers

DZ

[BIGNEWY]

3 hours ago, Dangerzone said:

Hi BN,

Just a thought - Instead of treating this as a bug in DCS - would it be possible to approach it from the perspective of a feature request instead? (Ability to move the IHADSS's position like the recital can be in the KA-50)?

This way - replication of the issue that users are experiencing wouldn't be a requirement/obstacle to overcome in order to provide a solution. Just adding that option as a feature for the AH-64 in the same way as the KA-50 would go a long way to solving a 3 year now issue for people (plus add a new feature in even for those not having an immediate issue with it)?

Cheers

DZ

Yes I will ask the team about making it adjustable. 

thanks