Jump to content

Recommended Posts

Posted

Master arm simulate, tpod in auto, move it to target, tms up.

Go to mav, have it in pre, move it to target, lock it up. I get the boresight button on the MFD, hit it. But it doesn't flash white and and the mav definitely isn't boresighted.

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

  • 2 weeks later...
Posted (edited)

Was having some issues yesterday too, they bore sight fine, but the new parallax thing is throwing me for a loop.. I boresighted on ground, targeted something about 6 miles away, ( as recommended to now try to bore sight 3+nm if possible) but when up in the air and lock something with the t-pod, manual handoff, the mavericks slave, but aren’t close to the point of the t-pod at all. Probably 1/2mile offset down and to the left, every time. Is boresighting on the ground the issue as opposed to in-flight? I tried several times yesterday, even re-boresighting in the air but to no avail. I should note I was using mav-h’s.. I did not try d’s, I usually only use d’s at night. Contrary to most I really like(ed) the TV mavs, they have been good up until recently it seems with the changes to boresighting. I  will try to get a couple tracks together today, maybe someone can see something I’m doing wrong, although I’m doing everything the way I have always done in the past. 

—— never mind, It was me.. I wasn’t switching the mavs to PRE.. It definitely doesn’t work boresighting in VIS 😂 I’m a little rusty in the 16

Edited by MadKreator
  • Like 1

Intel i7 13700k, ASUS  rog strix z790A, 64gigs G.Skill Trident DDR5 @6400Mhz, Nvidia  RTX 4080FE, 4TB,  2x 2TB,  1TB Samsung NVME, 1TB Samsung SSD,   Corsair RM1000x, Corsair Titan 360 X AIO cooler, Lian Li LanCool 2, VKB Gunfighter Ultimate, VKB Custom STECS , MFG Crosswinds, Moza FFB,  Virpil Collective, Track IR5, 48” LG UltraGear OLED & HP 24” touchscreen for Helios,49” Samsung Ultrawide,  Streamdeck XL, Corsair Virtuoso RGB Headphones

Posted (edited)

pre beta the Mave boresighting doesn't work. Pre latest update it worked.

They already fixed it with the new beta. Wait for it when it goes final.

Edited by void68
Posted (edited)

So to clarify, what distance should we have to an object on the ground when doing ground boresight (GND JETT ON and SIM mode)?

I'm asking because I did a few very accurate maverick boresight on a power line post few miles away and it was not as accurate on a vehicle 5 miles away later on when I went up in the air. Or this kind offset is correct?

 

Mav boresight off cold start .trk

 

Power line post location

Screen_230220_201023.jpg

Edited by Furiz
Posted
19 minutes ago, Furiz said:

So to clarify, what distance should we have to an object on the ground when doing ground boresight (GND JETT ON and SIM mode)?

I'm asking because I did a few very accurate maverick boresight on a power line post few miles away and it was not as accurate on a vehicle 5 miles away later on when I went up in the air. Or this kind offset is correct?

 

Mav boresight off cold start .trk 228.49 kB · 0 downloads

 

Power line post location

Screen_230220_201023.jpg

 

we had to boresight our tank main gun with the sights. we usually did this at targets 1000 meters away. the closer or further away you had a target in the sight, the boresight would be off and progressively more off when you moved away from 1000 meters. so in my case with the F16, i know that one cannot get a target lock more than 8 miles and a more likely target lock is about 6-7 miles, i boresight at 6-7 miles and always try to shoot 6-7 miles. it boils down to geometry. i may be totally wrong though it seems to work for me.

  • Like 1

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted
35 minutes ago, silverdevil said:

we had to boresight our tank main gun with the sights. we usually did this at targets 1000 meters away. the closer or further away you had a target in the sight, the boresight would be off and progressively more off when you moved away from 1000 meters. so in my case with the F16, i know that one cannot get a target lock more than 8 miles and a more likely target lock is about 6-7 miles, i boresight at 6-7 miles and always try to shoot 6-7 miles. it boils down to geometry. i may be totally wrong though it seems to work for me.

Yeah, I completely understand the trigonometry,

but they said at least 1 away and you are fine, and I did my boresight on a post 2.5 miles away and still it was not accurate. So that's why I'm asking to clarify.

I think I'll do my boresight in the air on a vehicle 6+ miles away and then it should be ok.

Posted
2 minutes ago, Furiz said:

Yeah, I completely understand the trigonometry,

but they said at least 1 away and you are fine, and I did my boresight on a post 2.5 miles away and still it was not accurate. So that's why I'm asking to clarify.

I think I'll do my boresight in the air on a vehicle 6+ miles away and then it should be ok.

yes like i said. my sweet spot is 6-7 mile. 1 mile would be too close IMO. i do not know if it real world or not. i just care that it works. most f-16 pilots probably do not have a beer on the right panel cup holder either. 

  • Like 1

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

Posted (edited)
On 2/8/2023 at 8:22 PM, Gunfreak said:

Master arm simulate, tpod in auto, move it to target, tms up.

Go to mav, have it in pre, move it to target, lock it up. I get the boresight button on the MFD, hit it. But it doesn't flash white and and the mav definitely isn't boresighted.

I have the same problem, D Mavs. I tried to lock far away objects, but no joy - not on the ground.

 

EDIT: Never mind, I did not have ground jett enabled.

Edited by Reflected
Posted
On 2/20/2023 at 3:18 PM, Furiz said:

Yeah, I completely understand the trigonometry,

but they said at least 1 away and you are fine, and I did my boresight on a post 2.5 miles away and still it was not accurate. So that's why I'm asking to clarify.

I think I'll do my boresight in the air on a vehicle 6+ miles away and then it should be ok.

i ran across this video yesterday. pretty sweet. the cc shows use of air boresight.

 

AKA_SilverDevil Join AKA Wardogs Email Address My YouTube

“The MIGS came up, the MIGS were aggressive, we tangled, they lost.”

- Robin Olds - An American fighter pilot. He was a triple ace.

The only man to ever record a confirmed kill while in glide mode.

  • 2 weeks later...
Posted (edited)

I've had no problems with boresighting when TGO Hand-off mode was in MAN... I'm switching it back to AUTO only after boresighting.

Edited by smire666
Posted (edited)

I have had problem with calibrating them while airborn. Lock on to some building far away and BSGT them, but there's usually always one rack that seems to completely fail at being calibrated properly and will point somewhere way off when receiving the handoff. Sometimes it will turn all the way to the side. If I go through and try to recalibrate that rack, it will just continue to fail over and over and just not ever line up with the TGP.

I've never once had this problem before they were broken a few updates ago, but they are consistently broken now. Very easy to replicate.

Edited by FusRoPotato
Posted
2 hours ago, FusRoPotato said:

I have had problem with calibrating them while airborn. Lock on to some building far away and BSGT them, but there's usually always one rack that seems to completely fail at being calibrated properly and will point somewhere way off when receiving the handoff. Sometimes it will turn all the way to the side. If I go through and try to recalibrate that rack, it will just continue to fail over and over and just not ever line up with the TGP.

I've never once had this problem before they were broken a few updates ago, but they are consistently broken now. Very easy to replicate.

 

Seems like you didn't calibrate both pylons, you have to calibrate for each pylon, so one Mav per pylon and it is enough.

Posted (edited)
33 minutes ago, Furiz said:

Seems like you didn't calibrate both pylons, you have to calibrate for each pylon, so one Mav per pylon and it is enough.

I suppose it does seem like that if I skip reading a lot of words.

Edited by FusRoPotato
Posted
17 minutes ago, FusRoPotato said:

I suppose it does seem like that if I skip reading a lot of words.

 

You never mentioned calibrating both pylons,

3 hours ago, FusRoPotato said:

but there's usually always one rack that seems to completely fail at being calibrated properly

and this is exactly what happens when you don't calibrate both pylons.

  • Like 2
Posted (edited)
10 hours ago, Furiz said:

You never mentioned calibrating both pylons,

This is what happens when you don't calibrate both your eyes.

13 hours ago, FusRoPotato said:

 If I go through and try to recalibrate that rack, it will just continue to fail over and over and just not ever line up with the TGP.

I mean, does this not suggest anything?

Take the hint, I've been seeing these bugs after attempting to calibrate both racks. One of them usually fails and becomes far worse off than it would have been in its initially uncalibrated state.

Considering how I've also been seeing a lot of bugs with the TGP not properly snapping to its waypoints, FCR targets, and VIS points, but rather on occasion ignore SOI POIs or get stuck floating wherever, I'd say the problem with the mavericks is probably caused by some issue with a bugged TGP or POI state. Switching from one pylon to another must somehow be triggering that corruption, but my guessing ends there. There was a time these calibrated just fine and probably should have been left alone.

Edited by FusRoPotato
Posted
12 minutes ago, FusRoPotato said:

This is what happens when you don't calibrate both your eyes.

You should be nice to ppl that try to help you.

I have no issue with Mav boresight, good luck.

  • Like 3
Posted

You made a lowball assumption after a low effort read of a comment for an easy dismissal, not a very nice way to start "helping". Maybe read carefully and give the benefit of doubt before expecting appreciation, or steer away from problem reports that you haven't experienced yourself. 

  • Like 2
Posted
18 minutes ago, FusRoPotato said:

You made a lowball assumption after a low effort read of a comment for an easy dismissal, not a very nice way to start "helping". Maybe read carefully and give the benefit of doubt before expecting appreciation, or steer away from problem reports that you haven't experienced yourself. 

Relax mate, it might be user error and it‘s more often than not a valid assumption.

I dont have issues boresighting them at all, i‘d also guess you do something wrong in the whole process.

good luck

  • Like 2
Posted
9 hours ago, _SteelFalcon_ said:

Relax mate, it might be user error and it‘s more often than not a valid assumption.

If I say I attempted to recalibrate the uncalibrated rack and it continues fail calibration, then I don't know what else to say. 

9 hours ago, _SteelFalcon_ said:

I dont have issues boresighting them at all, i‘d also guess you do something wrong in the whole process.

good luck

I know about a half dozen others who have been having this issue so I'll hand you some of your own: You must not have actually interacted with Mavs once within the past few updates. It's become a common saying within our larger community that if you want to use mavs, fly the A10, as they've historically always had one major issue or another active on this aircraft. Were you aware of the issue in the prior patch? It was 100% failure to calibrate. Now it's an occasional repeat of the same issue. Don't believe me? Guess who doesn't care. 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...