Feature removed from Patch Notes

[hawk4me]

The early version of the patch notes this morning said that there is an option to automatically boresight HMCS and Mavericks even when cold starting. Was this option removed for a particular reason? It seems to me that having it as an option would be a good thing to add since yes it is correct procedure to boresight them at cold start this process has been so buggy since it was released that working around it maybe the best idea for now. Just my 2 cents.

[NaOH1]

It was removed? Now I know why I can't find the option no matter how hard I look.

[AdrianL]

See 

 

[hawk4me]

6 minutes ago, NaOH1 said:

It was removed? Now I know why I can't find the option no matter how hard I look.

That's what it looks like is it was removed. It could have been mistyped and the current iteration is what they meant. But it said in bold type that this is an option so it doesn't look like a mistake.

3 minutes ago, AdrianL said:

See 

 

I know this is what it says now. But when patch notes came out it said that Maverick boresighting could be done automatically in hot/cold start. This is an option it was written plain as day. It's ok if it was removed just personal curiosity at this point.

[Furiz]

Most likely internal miscommunication, they edited the post.

[BIGNEWY]

Log was incorrect and was edited to

• Added Maverick and HMCS Auto-Boresight, automatic for hot starts. Cold starts require manual boresight.

[RyanR]

Phew. I thought I was nuts for seeing this before... and then it changed. Thanks for setting the record straight!

-Ryan

[hawk4me]

Indeed, Thx BigNewy. I figured as much but just thought it was strange to change the wording so much. Can you elaborate on the behavior though cause it's always been boresighted in the air or from a hot start. This change doesn't mean much if i understand it correctly.

Edited May 22, 2024 by hawk4me

[Chaos_Out]

8 minutes ago, hawk4me said:

Indeed, Thx BigNewy. I figured as much but just thought it was strange to change the wording so much. Can you elaborate on the behavior though cause it's always been boresighted in the air or from a hot start. This change doesn't mean much if i understand it correctly.

 

It used to be boresighted in the air or from hot start, but changed some time back to that they weren't.  I don't know exactly when, but as someone who used to setup my missions specifically in air or hot start with mavs already loaded to skip needing to boresight, I noticed after coming back from a break that they were no longer boresighted.  I gladly welcome back this option.

[hawk4me]

Huh, well color me stupid i figured they were still boresighted in the air.

 

[NineLine]

Before, only Mav was bore sighted with airborne start. Now, both are bore sighed if started in air, runway, or hot on ramp.

[DD_fruitbat]

30 minutes ago, NineLine said:

Before, only Mav was bore sighted with airborne start. Now, both are bore sighed if started in air, runway, or hot on ramp.

If you spawn into a hot jet that doesn't have mavs loaded and then load them on the jet, would they need manually boresighting then?

[NaOH1]

I hope this isn't hijacking the thread. Apologies if so.

In the Hornet, if I locked with the T-Pod, the Mav seeker was exactly on the target. I'm sure I'm bore sighting correctly but with the Viper, if I lock the T-Pod on a target, it puts the Mav seeker "close" to the target and I still need to adjust before firing. When targets are close together, I hit the wrong target about 1/3 of the time.

Just confirming if this is what you need to do in the Viper or if I'm missing something and need to go back to the manual and tutorials.

[Moonshine]

20 minutes ago, NaOH1 said:

I hope this isn't hijacking the thread. Apologies if so.

In the Hornet, if I locked with the T-Pod, the Mav seeker was exactly on the target. I'm sure I'm bore sighting correctly but with the Viper, if I lock the T-Pod on a target, it puts the Mav seeker "close" to the target and I still need to adjust before firing. When targets are close together, I hit the wrong target about 1/3 of the time.

Just confirming if this is what you need to do in the Viper or if I'm missing something and need to go back to the manual and tutorials.

it is what you need to do. boresighting is done at a certain distance, so anything above that distance and anything below that distance will look slightly off. only at the exact distance you boresighted will the mav and the tgp perfectly match. which is relatively hard to get right that perfectly.
if anything, the very perfect boresight (without ever boresighting beforehand) of other modules seem to be a bit of "wizardry"

[NaOH1]

I’ve never had it explained that way. That makes sense that parallax affects the aim.

[Chaos_Out]

Hey, @NineLine and @BIGNEWY.  I did a quick test (quick as in can't provide a track yet until I get more free time tonight), and have more bugs type stuff I'm gonna write up later, but just did a quick flight test and wanted to let you know the boresighting of the mavs seems off and not "zero'ed" in a way to be used in combat without tinkering.  What I mean is that every time I'm actually in range to use the mavs, I typically have to move the mav left to lock onto the object that the TGP is locked onto, typically within 10nm of the target, AKA even with the auto boresight, paralax is still a thing.  So another way to put the question is, what distance are the mavs boresighted at?  Is this expected use, for us to still have to manually adjust the maverick even after an "auto boresight" was done via hotstart, air, etc.