cannot reproduce and missing track file Gun misaligned for me since patch

[tn_prvteye]

Firing the cannon as the Pilot, the rounds seem to be hitting WAY below where I'm aiming.  Is there a new step in the start-up I'm missing?  I Boresight the IHADSS.   Are there new limitations or anything that's changed?

[Denwagg]

Same for me. If I Create a mission takeoff from parking hot, gun is aligned properly. If I change that same mission to on the ramp and startup manually boresight IHASS, gun is way out of alignment. Not a ranging issue way off to the right

Syria - Gazentep_AH-64D.miz

Will upload track file tomorrow

Edited July 25, 2022 by Denwagg
Add

[JSpidey]

Make sure when you're boresighting you're putting the LOS reticle inside the BRU as well as making the yellow circles concentric like so. Also remember that you don't have the benefits of the target state estimator in the pilot seat and you can't get a laser range to the target so you'll need to make sure your manual range is set appropriately

Edited July 25, 2022 by JSpidey

[tn_prvteye]

Thanks.  I do that every start-up, but still shoots way down.  I'm in VR, so maybe there's something there?  I'll try a hot-start and see if I get the same issue, as well.

[JSpidey]

1 hour ago, tn_prvteye said:

Thanks.  I do that every start-up, but still shoots way down.  I'm in VR, so maybe there's something there?  I'll try a hot-start and see if I get the same issue, as well.

What's the distance of the target and what's your manual range set to. Some people have problems boresighting with IHADSS set to both eyes so that could also be causing an offset with boresighting.

Edited July 25, 2022 by JSpidey

[tn_prvteye]

Not firing at a target...I've been just testing it.  I don't have the IHADSS set to both...just right eye.  It's odd....before patch I had no problems.  It wasn't laser accurate, but it put rounds at least in the general direction.  I'll see if I can get a pic tonight.

[sirrah]

That's strange. I just tested, but no issues here.

Using VR (IHADSS set to right eye only) and also on latest OB

 

Fwiw; I added a track file (accelerated time for INS alignment). My first shots were high, because I forgot to set range to AUTO, but after that, it's accurate (well, the gun is, I am not so much )

Hope you figure out what's wrong

IHADSS alignment and gun use.trk

[Floyd1212]

If you go external view is the gun even tracking with your head? 

[tn_prvteye]

Just tried from Hotstart and it works as usual.  I went back through the start-up checklist...don't seem to be missing anything.  Did a new procedure get added that I'm missing?

[Raptor9]

The IHADSS boresight procedure hasn't changed since release. Without a track it is hard to troubleshoot if there is anything you are doing wrong, such as performing the procedure incorrectly or using an erroneous range setting.

Also, I recommend trying it outside of VR. If you follow the same steps outside of VR and there is no issue, then it may be a problem with your VR setup.

[dburne]

14 hours ago, Floyd1212 said:

If you go external view is the gun even tracking with your head? 

I don't think currently the external view shows the gun tracking with head for whatever reason.

[Hiob]

1 minute ago, dburne said:

I don't think currently the external view shows the gun tracking with head for whatever reason.

If you think about it for a moment - how could it. When in external view, your mouseview/trackIR-view controls the external camera and not the internal camera aka the pilots head.

That is, of course, in single player. In Multiplayer you should see the gun move, given that one pilot is still in the aircraft and has control of the gun.

[dburne]

10 minutes ago, Hiob said:

If you think about it for a moment - how could it. When in external view, your mouseview/trackIR-view controls the external camera and not the internal camera aka the pilots head.

That is, of course, in single player. In Multiplayer you should see the gun move, given that one pilot is still in the aircraft and has control of the gun.

True but then one can still manipulate the flight stick, one can still fire the gun or launch a missile - so why not show the head moving with gun?

Edited July 26, 2022 by dburne

[Hiob]

2 minutes ago, dburne said:

True but then one can still manipulate the flight stick, one can still fire the gun or launch a missile - so why not show the head moving with gun?

 

Because the inputs, that control the camera (and therefore the headposition and therefore the gun) are redirected to the external camera. The trigger and other inputs are not.

[Floyd1212]

Sorry, I had just done this as the PLT while my CPG was looking around, and it didn't occur to me that you can't perform this test by yourself.

You could, however, look out the left window from in the cockpit, then go external to check, then look out the right window in cockpit, then go external to check.  It was really just a suggestion as a sanity check to make sure the gun wasn't still fixed forward.

[StrongHarm]

I noticed something significant since the patch that may be related.  I'm using Pimax 8kx in wide.  When I switch to CPG I have to recenter the VR headset before I boresight.  When I go back to Pilot I have to recenter again.  It seems that the "ratio of head position" (for lack of better terms) is different in the front and back seat.  I've also had better luck when I use the Steam based "recenter seated position" upon entering the cockpit.  Not sure if any of this is related.. just fyi.

[sirrah]

7 hours ago, StrongHarm said:

I noticed something significant since the patch that may be related.  I'm using Pimax 8kx in wide.  When I switch to CPG I have to recenter the VR headset before I boresight.  When I go back to Pilot I have to recenter again.  It seems that the "ratio of head position" (for lack of better terms) is different in the front and back seat.  I've also had better luck when I use the Steam based "recenter seated position" upon entering the cockpit.  Not sure if any of this is related.. just fyi.

CP/G default head position has always been way too much to the left (centered to the TADS, which is left of the cockpit/seat centerline). So in order to properly boresight in VR, you either have to move your head right and slightly lower, or manipulate with the VR recenter function to get in the center of your seat.

 

This has always been the case since release, at least for me and many others (reported many times).

 

I think though that what the OP describes, looks like a more severe problem that most of us can't seem to reproduce.

[corbu1]

Using VR…..didn‘t notice changes in the IHADSS boresight process.

The gun works for me as in the previous OB‘s…..aiming is for me is it was already before. I didn‘t notice any issues with the AWS.

[StrongHarm]

7 hours ago, sirrah said:

CP/G default head position has always been way too much to the left (centered to the TADS, which is left of the cockpit/seat centerline). So in order to properly boresight in VR, you either have to move your head right and slightly lower, or manipulate with the VR recenter function to get in the center of your seat.

This has always been the case since release, at least for me and many others (reported many times).

I think though that what the OP describes, looks like a more severe problem that most of us can't seem to reproduce.

CPG ***height*** changed for me since the last patch, but Pilot height didn't.  i.e. height from pilot dash to virtual eye level has a different ratio than CPG dash to virtual eye level.  Of course there was already a lateral discrepancy there... I'm saying (I thought clearly) that I see something different now.  Adding a calibration step has fixed this exact issue for me... so I took the time to contribute to the OP to see if it might help.  It seems you took your time to dismiss my post so the OP wouldn't have to.  That's very kind of you.  I almost forgot why I avoid this forum.

Also, OP, I use NVS and look at a doorway in front of the bird to validate my calibration while I'm doing it.  Fixed it right up for me.  Your milage may vary... as sirrah so kindly pointed out. 

/OUT

[sirrah]

6 minutes ago, StrongHarm said:

CPG ***height*** changed for me since the last patch, but Pilot height didn't.  i.e. height from pilot dash to virtual eye level has a different ratio than CPG dash to virtual eye level.  Of course there was already a lateral discrepancy there... I'm saying (I thought clearly) that I see something different now.  Adding a calibration step has fixed this exact issue for me... so I took the time to contribute to the OP to see if it might help.  It seems you took your time to dismiss my post so the OP wouldn't have to.  That's very kind of you.  I almost forgot why I avoid this forum.

Also, OP, I use NVS and look at a doorway in front of the bird to validate my calibration while I'm doing it.  Fixed it right up for me.  Your milage may vary... as sirrah so kindly pointed out. 

/OUT

Perhaps I don't understand you correctly because I'm not native English, but did I step on your toes here? If I did, that honestly wasn't my intention 

As you were talking about the CP/G seat, having to recenter VR before being able to boresight, I thought my reply and letting you know that CP/G boresight has issues for many of us VR users, might help or be reassuring for you. Sorry if it didn't.

 

Fwiw, back on topic:

I did a few more Apache cold starts today on latest OB version (both PLT and CPG station), including IHADSS boresight and didn't have any gun inaccuracy issues. So still all working on my end.

[cthulhu68]

I was having this issue as well, after update, with shooting way low/short with gun and rockets although I dont use VR. I had also noticed that my reticule now seemed larger than the ball when bore sighting and like Strongarm mentioned seat height or view seemed off. I deleted my snapviews for AH-64D and now the reticle is back to the right size and weapons accuracy is much better.  

[Nealius]

On 7/26/2022 at 12:59 AM, JSpidey said:

Make sure when you're boresighting you're putting the LOS reticle inside the BRU as well as making the yellow circles concentric like so.

I'm doing this every startup in VR and, when checking with FLIR, alignment is always 1-2m off (usually up and left) despite being aligned in the BRU.