Can offset of helmet mounted sight customized?

[Usagi]

In KA-50 you can do that by options / special settings page but how with A-10C II?

Currently sight is too low to my taste and requires awkward neck angles when trying to point something with Track-IR.

I have found that by editing SnapViews.lua you can change that but unfortunately it changes the whole view. If you shift helmet mounted sight more up, you have to tilt head more downwards when looking at cockpit. Not good.

Any other options?

[Hive]

Unfortunately I have no solution, but I totally agree with you that it should be higher or customizable as in the KA-50. The HMCS crosshair should not be centered to the monitor, because that is not the pilot's eye level in the normal cockpit view/position when looking straight forward. The pilot looks at the HUD's top, not at the instruments. No matter what the camera perspective in the simulation is, we as players look at the upper third of the monitor, not the middle. It think it would feel most natural when the HMCS crosshair was in the middle of the HUD when TrackIR is centered and you are in the default position.

I tried to visualize the straight line of sight (green) and what position the pilot would have where the crosshair is now (red):

Or this way - line of sight (green) and line of HMCS (red) - both lines should more or less match I think:

Edited November 23, 2023 by Hive

[ASAP]

In the real aircraft the pilots have to boresight the HMCS after turning the system on. In the monocle they have a big X and they have to match it up over a circle on the HUD and TMS forward short. If they implemented a system like that in the SIM it coulc solve a lot of these errors and tell the system exactly where the users eyes are.

[GrEaSeLiTeNiN]

On 11/24/2023 at 9:00 AM, ASAP said:

In the real aircraft the pilots have to boresight the HMCS after turning the system on. In the monocle they have a big X and they have to match it up over a circle on the HUD and TMS forward short. If they implemented a system like that in the SIM it could solve a lot of these errors and tell the system exactly where the users eyes are.

Is this why we have this but it's not implemented?

[ASAP]

6 hours ago, GrEaSeLiTeNiN said:

Is this why we have this but it's not implemented?

Yes but there's more than that even...

There are a couple of functions being shown on this table that are not simulated with the HMCS. TMS FWD SHORT is used in the initial boresight. Everything referencing the "Occl Pt"  is referring to a different setting. It's short for occlusion pattern. There are multiple default occlusion patterns (For instance: can't see the monocle just when it's pointed at the HUD, can't see the monocle when it's looking inside the aircraft). You can also build a custom occlusion pattern using the HMCS MFCD page (accessed through the STAT page) and the TMS commands shown there. So basically if I wanted my HMCS to not display when I'm looking at the front panel, but I DO want it to display still when I'm looking through the side panels, down at my crotch, and through the HUD, you could built an occlusion pattern for that.

The HMCS come with a TON of options in real life and pilots have a lot of control over what you can/can't see in the monocle and how it displays, to include having some stuff always display even in an occlusion zone. It also comes with multiple profiles that can change in flight. so you can have one set of options for medium altitude stuff, and then when you drop into the low altitude environment you can switch profiles to something more suited for that.

there's multiple pages of options accessed through the "Status" page of the MCFD.  Like most aspects of the jet, there is an overwhelming level of customize-ability. Also like most things, the entire A-10 community has a set of standards for how they use it. That means that by default all the options are set one way, generally those standards are decided by the weapons officers based on tested/proven techniques and best practices. Pilots can change those options to whatever works better for them, but the standard setup is sort of a one-size-fits-the-99%. 

So you can think of what we have in DCS as the "standard" setup which works pretty well. 

[GrEaSeLiTeNiN]

21 minutes ago, ASAP said:

Yes but there's more than that even...

There are a couple of functions being shown on this table that are not simulated with the HMCS. TMS FWD SHORT is used in the initial boresight. Everything referencing the "Occl Pt"  is referring to a different setting. It's short for occlusion pattern. There are multiple default occlusion patterns (For instance: can't see the monocle just when it's pointed at the HUD, can't see the monocle when it's looking inside the aircraft). You can also build a custom occlusion pattern using the HMCS MFCD page (accessed through the STAT page) and the TMS commands shown there. So basically if I wanted my HMCS to not display when I'm looking at the front panel, but I DO want it to display still when I'm looking through the side panels, down at my crotch, and through the HUD, you could built an occlusion pattern for that.

The HMCS come with a TON of options in real life and pilots have a lot of control over what you can/can't see in the monocle and how it displays, to include having some stuff always display even in an occlusion zone. It also comes with multiple profiles that can change in flight. so you can have one set of options for medium altitude stuff, and then when you drop into the low altitude environment you can switch profiles to something more suited for that.

there's multiple pages of options accessed through the "Status" page of the MCFD.  Like most aspects of the jet, there is an overwhelming level of customize-ability. Also like most things, the entire A-10 community has a set of standards for how they use it. That means that by default all the options are set one way, generally those standards are decided by the weapons officers based on tested/proven techniques and best practices. Pilots can change those options to whatever works better for them, but the standard setup is sort of a one-size-fits-the-99%. 

So you can think of what we have in DCS as the "standard" setup which works pretty well. 

Thanks for the detailed info and insight. I guess these commands aren't really necessary for the sim given the 'standard' setups are already there, except perhaps for the Track IR part B/S part.