investigating IHADSS symbology at night

[Dr Zaius]

Not sure if this is working as it should but I've realised that when flying at night using the PNVS the symbology that's applied through the IHADDS is what you would normally see using your own eyes i.e. at eye level. Shouldn't the symbology be applied via the PNVS sensor which is actually further forward and slightly lower than whats normally seen during the day? I ask as the velocity vector often looks like it'll clear obstacles but you if you don’t factor this in you’re gonna crash, I know this problem really only highlights itself on a pitch back night but it's still a little on the dangerous side - I wonder has this feature been implemented correctly?

Edited March 28, 2022 by Dr Zaius

[NineLine]

Can you include a short track?

[Dr Zaius]

11 hours ago, NineLine said:

Can you include a short track?

Attached as requested @NineLine, its hard to explain what's going on exactly but the 2 screenshots may help, the first shows level flight but to the PNVS the velocity vector looks to be above the horizon, the 2nd picture results with me crashing in a firery ball of death despite the velocity vector suggesting that I'm above the (FLIR) horizon.

 

IHADDS.trk

 

[NineLine]

Thanks very much for the track, I will investigate.

[Dr Zaius]

For the record it doesn't do it all time, it's almost as if that the sight goes out of sync somehow - I've tried to suss out exectly what thorws it off but as I say it's difficult trying to work out what's going on, sorry I couldn't be more specific.

Edited March 29, 2022 by Dr Zaius

[NineLine]

Ok, I think I see what you mean, when I try the track on internal versions it looks better though, so lets do this, I will leave this report open, then when the update is released, try it again and see what you think, if you still see an issue send me another track and I will look into it further, again, thanks for the report!

[Dr Zaius]

1 hour ago, NineLine said:

Ok, I think I see what you mean, when I try the track on internal versions it looks better though, so lets do this, I will leave this report open, then when the update is released, try it again and see what you think, if you still see an issue send me another track and I will look into it further, again, thanks for the report!

No worries, until then

[Dr Zaius]

The error was mine @NineLine, I have the boresight polarity switch (both functions) binded on my throttle and realised that it only go's out of sync when I hit the boresight button, bit of an odd feature given the lengthy process of boresighting via the lense you stare into at start up, seems odd that there's a button that quickly overrides this - perhaps the system is prone to going out of sync and that's the quick fix solution?

To confirm re-boresighting fixes the issue and all looks to be working as it should.