jdw81

Kneeboard builder 1.9.1.1 builds kneeboards for the AH-64D_BLK_II in a folder named AH-64D. As such, the kneeboards do not show up in the aircraft. I can copy the contents of the created folder into the correct folder but that is a bit of a pain. Surely, I'm not the only one with this problem. Any solutions? I have tried several search combinations without success.

Deleted this post as it was in the wrong subject.

Very similar problem here - but - I have not upgraded to Ver 63 on the headset. Unfortunately, the QuestLink software on the PC updated to Ver 63 (Meta Quest Link App Version 63.0.0.216.361 (63.0.0.216.361)) without my asking for it. I guess I'm back to TrackIR until something is done.

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.

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.

So I did some searching and I do not see anything to change the position of the IHADDS (or NVG). I can change my eye position but that is the same as moving the seat up / down / forward / backward / left / right. I had already tested those moves and none of them help with this problem. It acts as if the DCS program is projecting those overlays in a fixed position that somehow is impacted by the resolution of the VR headset.

I will look again. Thanks.

Falconeer (or anyone else), This linked post has a little better description and includes screenshots if that helps. https://forum.dcs.world/topic/342711-quest-2-vs-quest-3-field-of-view/#comment-5373844

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?

Thank you for reading. I recenter my VR view every time. My line of sight view out of the cockpit is great. The problem arises when using a helmet mounted device such as the reticle/monocle in the AH-64 or the NVGs in the F-16. I have also tried seat position (forward, back, up, down) with no impact. I need to get some screenshots I guess to better explain.

I have been pretty happy with the Quest 2 with the HMD reticle looking forward - directly in line with my sight with a level head position. When I started using a Quest 3, that sight is now looking up 10-20 degrees (guess). To sight a target, I have to tilt my head way down and look through the top of my eyes (eyebrows) to place the crosshair on a target. Is there some kind of control for that angle? I have a nearly identical issue in the F-16 with Night Vision Goggles - they are also looking high vs my level eye sight.

When using my Q2, my AH-64 sight and my F-16 NVG views are pretty much straight forward. I just got a Q3 and both of those views are pointing up by 20+ degrees vs me looking straight forward. This issue is making anything that uses an overlay nearly impossible to use. Is there a way to adjust the angle of a view overlay like a sight or NVG? I am having to crank my head up or move my chin down and look way up with my eyes to get anything to work right. I have finally found a set of parameters that maintain a decent FPS on the Q3 while delivering more clarity inside the cockpit. I still get more stutter than I like when moving at high speed on the ground (take-off / landing). Once in the air, everything is great. That said, the Q3 is very demanding on the GPU. I have a 4090 and have to be careful with settings. The YouTube videos talking about the Q3 and settings are all in the air and indeed, you can crank the settings up and get spectacular results but you will die in high speed ground movement.

Was flying again and the ATT problem was back. I was running the same mission from the same airport, etc. when it worked fine (per my previous post). This time, I made a live video of the flight plus saved the track. I am uploading the video to my YouTube account (private, with link only) at (may be a minute to complete rendering): ATT Hold AH-64 Problems.trk

Just tried to record a video and repeat the situation. Suddenly, it's working fine after several failures earlier. I guess I should just delete this post totally.