can not reproduce VR: HMD / HIADSS Symbology too high

[corbu1]

vor 2 Stunden schrieb RuskyV:

Are you holding or tapping the buttons? I use an encoder so it send a press command every click. Make sure you are simply not holding the button down, instead click multiple times.

@RuskyV

ok, tried it a second time……and yes it works!!! Great, so always give things a second chance is the lesson I learned. It‘s a bit fiddling as you really need to press the buttons a lot but it works!

I always had too big symbols shown overlapping the monocles frame with my vive pro 2. Now I can adjust it to fit.

really interesting I never noticed when these key bindings were introduced in the control settings….wonder who else di not know or were I‘m the only one.

Thanks again for pointing on these….really helped me a lot!

[RuskyV]

Your welcome mate, glad I could help.

one thing to remember though do your adjustments before you boresight the HMD. 

[derfritz]

I suggest you use the search option and put in the following:
DAP 
this will bring up all mappable axis, but you can find them all under Display Adjust Panel.
 

Thank you, this helps! Still want a slider do adjust HMD position though tbh

[RuskyV]

Stick it in the wish list maybe as an idea to add as an axis? 

 

[Whirley]

I tried seating the Reverb G2 differently on my face and it is actually way better now.

The Display Adjust Panel option did not work well for me as not all symbology is moved and it messed with the FLIR alignment. Not using the Display Adjust Panel now as the view is much better with differently seated Reverb G2.

[daemon1808]

...that a lot of the issues in VR (related to people having issues with HIADSS symbology positioning, vision-obscuring monocle, etc) seems to be related to where the player's "virtual" head is placed in relation with the monocle, HIADSS symbology and pilot helmet. And that position depends on the VR headset.

I have acquired a new VR headset recently (Pico Neo 3) that will replace my old Lenovo Explorer, and I have found that what I see is completely different from one to the other.

Using the LE I had problems with HIADSS symbology (it's too high, so the upper part is blurry and I have to tilt my head to center it on the targets, as you can see in the thread below), but the pilot helmet and balaclava do not impede my vision.

Using the PN3 the HIADSS symbology HIADSS symbology is vertical centered (not blurry and I don't have to tilt my head to center it on the targets), but I can see a centimeter of the borders of the helmet (loosing peripheral vision), the monocle is away from my "virtual face" and the HIADSS symbology seems bigger than the monocle itself.

What is more anoying, when I activate the balaclava in Apache's options, I can see the balaclava a couple of centimeters away from my "virtual face" reducing drastically my field of view.

As screenshots in VR are useless, below you have a simple diagram of what I see with both VR headsets (with and without balaclava)

My "analisys" of the problem is that using the LE my "virtual head" is placed nearer to the monocle and a bit low. And in the PN3 my "virtual head" is farther from the monocle and centered in the vertical axis.

So, in the LE, the helmed does not impede my vision, the monocle seems "bigger" and the HIADSS symbology is above my eyes. And in the NP3 the helmed impede my vision, the monocle seems "smaller" and the HIADSS symbology is centered.

I understand that developing an option in the menu to change the position of the "virtual head" of the player could be tricky but, should it be possible to have a lua file to offset this possition? This way players can tweak the offset x, y and z (in relation with the helmet/HIADDS) by themselves depending on the VR headset.

I have tried to change values in the apache's views.lua but, although the virtual head position is change, the helmet/monocle position moves with the head. Same happens with the keybindings that allows the player to reposition himself in the cokpit (the helmet/monocle moves too)

@BIGNEWYfinally it is not a problem of some of us placing the VR headset wrong. Could you tell this to the development team please?

At last I understand those people that complained about the monocle impeding the vision. Now, I have to remove the HIADSS (and the rest of the helmet) in the apache's options because is "so small" that the borders are placed just where I need a clear line of sight, plus the helmet killing my peripheral vision (where with the Lenovo explorer the monocle is big enough to do not impede my vision with its borders, and the helmet is not seen)

 

 

 

nullnull

Edited December 21, 2022 by daemon1808

[BIGNEWY]

thanks I will share this with the team 

[jdw81]

Please see the attached files for a side-by-side comparison of the Quest 2 and 3. In both files, the Q2 is the left screenshot and the Q3 is the right. My concern is the relative position of the NVG or reticle. Screenshots were using Oculus Mirror (thus the "window out of focus" message - referring to the mouse/active window, not a picture focus). The screenshots are using my right eye. I recentered my VR view before screenshots. The screenshots only capture the active area of the VR headset. My view inside the cockpit (in terms of zoom) is not as different as these comparisons show but the relative position of the NVG and IHADDS overlays is as I see it.

In the F-16 NVG comparison, you see the higher relative position of the NVG. You also see a bit different view of both cockpits. The Q3 is more zoomed in even though I did not do anything. I assume this is the result of the higher resolution of the Q3. Regardless, I have to point my eyes up considerably more in the Q3 to put the center of the NVG into the center of my view.

In the AH64D comparison, I have turned of the monocle outline - otherwise a large portion on the right side of the capture is helmet. Again, I see the same general effect of a more zoomed in view in the Q3. You see the IHADSS information is much higher in the Q3. The relative position of the information in the Q2 is much more comfortable and natural than the Q3. To aim the guns (example) in the Q3, I have to tilt my head down "a lot" to put the crosshair on the target. The crosshair is accurate (boresighted) - just uncomfortable to move my head down even when I'm flying level.

Is there anything that can adjust the relative position of these overlay type displays to be moved?

[jdw81]

Working with customer support, I think we have a work-around. I have several view adjustments binded to mouse or joystick. These include VR Recenter (in UI menu) and seat forward, back, up, down (4 seat binds). When I get in the cockpit, I tilt my head back - looking virtually overhead - and then hit the VR Recenter. When I look back down, I then adjust my seat position to match my preference. The AH-64D IHADDS and F-16 NVGs are now more in line with my sight looking forward. I tested the sighting of the IHADDS and it is still accurate despite all of these major adjustments to the view. Bottom line, I can live with this.

[Draken35]

On 1/30/2024 at 5:12 PM, jdw81 said:

Working with customer support, I think we have a work-around. I have several view adjustments binded to mouse or joystick. These include VR Recenter (in UI menu) and seat forward, back, up, down (4 seat binds). When I get in the cockpit, I tilt my head back - looking virtually overhead - and then hit the VR Recenter. When I look back down, I then adjust my seat position to match my preference. The AH-64D IHADDS and F-16 NVGs are now more in line with my sight looking forward. I tested the sighting of the IHADDS and it is still accurate despite all of these major adjustments to the view. Bottom line, I can live with this.

Can you clarify which seat bindings are you talking about please?

[Kirill A. Pavlov]

 

I also encountered this problem on Oculus Quest 3. The XR Neck Saver utility solves this problem.

[DD_Crash]

Thanks, I will try that out.

[Fear-Factor]

I have the AH64D since few days and now i am running into a problem which is probably connected to this topic.

I am using a Reverb G2 and during coldstart i need to do the EGI alligement.
And now when i allign the yellow circles so the IHDASS rectile do not match the centre of the circles.
To be honest i dont know what do i need to do because ive triec to centre the rectile and ignore the circles but doesnt matter what i do the automatic startup procedure do not continue.
And before you ask, yes i confirm the boresight adjustment on thr right MFD.

So how i can centre the IHDASS properly in VR?

[derfritz]

5 minutes ago, Fear-Factor said:

I have the AH64D since few days and now i am running into a problem which is probably connected to this topic.

I am using a Reverb G2 and during coldstart i need to do the EGI alligement.
And now when i allign the yellow circles so the IHDASS rectile do not match the centre of the circles.
To be honest i dont know what do i need to do because ive triec to centre the rectile and ignore the circles but doesnt matter what i do the automatic startup procedure do not continue.
And before you ask, yes i confirm the boresight adjustment on thr right MFD.

So how i can centre the IHDASS properly in VR?

I don't think this is connected to this issue. Also I did not understand what the problem is. The yellow circles have to be centered in the scope and your IHADSS center cross has to be on the middle dot. But probably create a different topic, this one is not about boresighting the IHADSS.

[Fear-Factor]

Topic is about IHDASS misalligement.
So when the IHDASS is misalligned in VR so do it not affect the boresight adjusment procedure?
I think the IHDASS recticle has to match the yellow circles or do i need only to centre the circles in the scope?

 

[derfritz]

1 minute ago, Fear-Factor said:

Topic is about IHDASS misalligement.
So when the IHDASS is misalligned in VR so do it not affect the boresight adjusment procedure?
I think the IHDASS recticle has to match the yellow circles or do i need only to centre the circles in the scope?

 

This topic is not about EGI alignment at all, it is also not about how to boresight the IHADSS. This is about the IHADSS showing too high for some specific VR setups, nothing to do with the startup, or the procedures of the module itself. I still do not understand exactly what your issue is, but I strongly recommend you to watch a startup video and see how they boresight the IHADSS and follow along. The reticle has to be on the center yellow dot, and all the yellow circles should be at the same distance from each other and not outside the scope.
 

 

[Fear-Factor]

I saw that video already thats why i was not sure.
Anyway, ive got now an information from another source and its ok now.
Thanks for help so far.

[DD_Crash]

That IHDASS is a lot smaller than mine using a Quest3. What setting could cause that?

[RealDCSpilot]

It's not recorded in VR, this is the 2D IHADSS used with TrackIR. The IHADSS in VR is rendered differently. In 2D it's just a simple overlay.

Edited May 27, 2024 by RealDCSpilot

[DD_Crash]

It would help if ED would make the IHADSS resizeable even if it isnt in real life. Think of this request as a quality of life issue

Edited May 27, 2024 by DD_Crash

[Kirill A. Pavlov]

in this thread, look at the second to last message:

if you want to improve it, then set it to 1.2 - 1.5

[DD_Crash]

Thanks for that

[derfritz]

@BIGNEWY
Sorry to ping you, but is there any news on this topic? Even with new hardware (Reverb G2 to Pimax Crystal) the issue persists, the IHADDS is just too far up. Same thing with all other HMDs in Hornet Viper and Kiowa. I think this is just due to my specific setup, so way to change HMD position would be highly appreciated.

[andrei_akatsyeu]

I have the same issue with NVG/JHMCS on F/A-18C when i use Quest 3. NVG position is too high. I tried to recenter VR and change it position, but nothing helps. On 2D monitor the position is ok.

[hind75]

Same happens to me, I'm using crystal lite.

and also F-16,F-18 JHMCS