Maverick806

Until it's fixed, you can use custom snap views to get around the issue. Here are some decent settings for 2D and VR. (The 2D isn't perfect as it blocks the Steering Engaged light) The custom Snap View file can be found here: "C:\Users\<USER.NAME>\Saved Games\DCS\Config\View\SnapViews.lua" Look for items 13 (2D) and 14 (VR) under A-10C [13] = {--default view viewAngle = 80.000000,--FOV hAngle = 0.000000, vAngle = -17.000000, x_trans = 0.257000, y_trans = -0.027000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 1, }, [14] = {--default view - VR viewAngle = 75.000000,--FOV hAngle = 0.000000, vAngle = 0.000000, x_trans = 0.157000, y_trans = -0.034000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 1, },

Those photos you included are taken from sitting much farther back in the cockpit. You can move the in game view back to match however not all information in the HUD will be visible as it’s designed to be viewed with both eyes rather than 1 camera.

Auto won’t work until you’ve started moving. I don’t know if that’s realistic or a bug, but you should be able to box it once you’ve taxied to the runway

https://forums.eagle.ru/showpost.php?p=3803475&postcount=131

This thread was 17 months old before being resurrected. The issue was likely fixed a while back

HSI > DATA > A/C > OSB15? (bottom right option) to switch from decimal minutes to decimal seconds

Alternatively, you can adjust the default view so you aren’t looking down. Assuming you have head tracking, the only real problem is that NVGs are’t centered

Added Screenshot

Did you set INS to NAV or IFA IFA does not work currently. It didn’t cause this issue when this video was made

If you're using HACQ/LHAQ like Bore-Sight mode, both modes seem to keep the previous targets azimuth instead of re-centering preventing you from acquiring a second target Steps to reproduce: 1. Enable HMD and select a weapon 2. Looking forward at the HUD, press Sensor Select FWD to enter HACQ and lock your first target 3. Steer to another target 4. Press Sensor Select FWD again to try to lock the second target. 5. The Scan Line doesn't move from the old target and the new targets in your HUD will not lock Note: The issue can be resolved by either: a) Looking outside of the HUD, or b) Pressing NWS/Undesignate and re-entering HACQ Edit: Using 2.5.5.32533. HACQ_Bug.trk

Already Reported here https://forums.eagle.ru/showthread.php?t=242503

I'm also experiencing freezing on NTTR in the Hornet If the mission starts in the air and the aircraft is set to player: it freezes in the loading screen If the mission starts in the air and the aircraft is set to client: it freezes once I take control If the mission starts on the ground cold and dark: it freezes shortly after starting my right engine (a few seconds after Betty calls Flight Controls Flight Controls) I've tried repairing my game as well as deleting FXO and Metashaders2 folders under Saved Games\DCS

Any chance the back of your plane is hanging over the edge of the deck where you’re starting up?

From the patch notes: “Only a contact determined as hostile (red, chevron), will have a diamond TD marker on the HUD.” I believe you need to interrogate the target aircraft in order get the diamond now

Also: If you actually have AIM-9M's they'll show up as 9L on the JHMCS

I've been seeing this myself lately so I did a little testing with AGM-65Ds. What I noticed was: -When you're carrying 2+ per station on an LUA-88 the next rounds are already slaved to the previous target like I was used to. -When you're carrying 1 per station on an LUA-117 the second Maverick is bore-sighted instead of pointing where your first round was fired. Is this expected behavior or a bug?

Parking stalls G01-G25 also seem to have aircraft pointing away from the base on Google Earth as well

I've noticed a few times that if you land your airplane / rearm and refuel, your wingman will not use a runway when attempting to take off again.Once you're airborne again, your AI will attempt to take off by going full throttle in your direction. I've seen this happen 3 or 4 times in DCS A10c and DCS World. In every case there was one or more fireballs