[WAD+TWEAK] Not within Boresight limits

[wyskass]

I've been getting this limit to firing in many cases where I'm flying directly at a target at nearly the same altitude, and needing to fire but just unable and then having to deal with their missile.
And it's not just for a second, but in this case for a long time where I have to make a defensive move. I retreated a bit, reset targeting and still blocked. I can't shoot at all.

boresight.jpg (161.11 KiB) Viewed 1075 times

boresight_save.zip

(547.11 KiB) Downloaded 7 times

[KnightHawk75]

Can't see anything obvious as to why it there is a bore-sight issue there (illumination problem maybe but not boresight), /me scratches head.

[CHM]

I've been getting this limit to firing in many cases where I'm flying directly at a target at nearly the same altitude, and needing to fire but just unable and then having to deal with their missile.

You're not alone in suffering from this bug. I recall that this was a problem in a previous version of CMO, before being fixed. My game build is 1147.45.

[thewood1]

My guess at this is that it is an issue with specific optical weapons. The previous report was some Russian weapons. Those got fixed. I suspect there are more than those weapons with the issue. Just a wild guess.

[Easy301]

I've been getting this limit to firing in many cases where I'm flying directly at a target at nearly the same altitude, and needing to fire but just unable and then having to deal with their missile.

You're not alone in suffering from this bug. I recall that this was a problem in a previous version of CMO, before being fixed. My game build is 1147.45.

I'm getting the exact same issue. I didn't post or comment initially as I was new to the game and thought maybe the problem was with something I wasn't seeing.

After getting a firm grasp on the basics and having completed dozens of scenarios, I've seen this issue a few times so far, and I'm confident at this point it's not happening due to a unit management issue on my end.

Clear skies, altitude set correctly, unit flying directly at target will cause me to have the same boresight error that's been posted above.

It doesn't happen all the time but it's happened with enough consistency to where I worry I'm going to see it whenever I open up the manual weapons allocation window on an applicable air unit.

[wyskass]

Again..
Aircraft id: B CapF 10A 2 - directly at an F15. Not within boresight limits.

boresight2.jpg (104.52 KiB) Viewed 809 times

Head on, no ability to fire. Already avoided 2 missiles, now still not being able to fire getting 2 more fired at me.
Are we to expect a coin toss and sometimes just having a broken airplane which is to be lost?
This is really making me want to stop playing. Before it was F16 missiles not factoring distance, making me lose every engagement, which still happens. I just keep expecting something random to be broken at any time.

Any response to this?

BCapA10A2-BoresightProblem.zip

(1.25 MiB) Downloaded 4 times

[wyskass]

My guess at this is that it is an issue with specific optical weapons. The previous report was some Russian weapons. Those got fixed. I suspect there are more than those weapons with the issue. Just a wild guess.

This case is with PL-12. The previous case was with AIM-120.

[thewood1]

There might have been issues with the 120 before, but there was an issue with some russian optically guided missiles a couple months ago that were fixed. I think they were weapon-specific.

[thewood1]

I just played a single run through and this is what I observed...

1) Raptor 3 has no radar on.
2) I think its detecting the Mig-29 through a B-1's relay of an optical track from 68nm away.
3) It looks like the B-1 has changed course and is no longer able to feed detailed track info.
4) So the bore sight message might be coming from the optical track on the B-1 and not able to provide tracking for a CEC launch.
5) If I turn on Raptor 3's radar, it fires with no issues.

Again, this is one run through. I might be misreading it and will take a more detailed look after work.

Just checked and the B-1 in the scenario has an AIM-120 link, but with a very limited range. I suspect this also plays a role in the issue. Whether its working as it should, I don't know. But the interaction between the AIM-120s, the F-22s, and the B-1s is playing some kind of role here.

[wyskass]

Thanks for checking.
I wonder if the interaction you describe wouldn't be explained by a different message though.
The other block from launch is the targeting message. I forget the specific words, but it's due to not getting a good fix. Which can be fixed by turning on radar or getting a fix from another aircraft with CEC. I've seen this message in those cases and it makes sense what to do.

In these cases, the radar was on, and the target was well within range and altitude.

[thewood1]

I think whats happening is because Raptor 3 isn't using its radar, its looking for lock information from another unit. Its either going to be Raptor 2 or Bone Front. Since Raptor 2 isn't radiating either, its looking for Bone Front. But at the time, Bone Front it pointing away. If I swing Bone Front around to point at the Mig, the fire control message goes from boresight issues to the fact that Raptor 3 needs to self illuminate to get a firing solution.

So the issue isn't the boresight for Raptor 3, its that it can't get a firing solution from itself or any CEC-related other unit. The message could be a clearer or even something different, but my logic knew right way that with Raptor 3's radar off, it would be looking for another unit to track the target and guide the 120s.

[thewood1]

If I eliminate the B1s, I get this message. If I turn on Raptor 3's radar, it gets a solid fix after the OODA loop expires.

Screenshot 2022-05-03 131144.jpg (229.45 KiB) Viewed 710 times

[Deserere]

I've been getting this limit to firing in many cases where I'm flying directly at a target at nearly the same altitude, and needing to fire but just unable and then having to deal with their missile.
And it's not just for a second, but in this case for a long time where I have to make a defensive move. I retreated a bit, reset targeting and still blocked. I can't shoot at all.

boresight.jpg

boresight_save.zip

Hi wyskass, thanks for posting this issue.
In the example that you attached the F-22 Raptor is at higher altitude compared to the target MiG Fulcrum. Even if the altitude is not much the pitch of the F22 is very steep (44 degrees). This cause the target MiG to be out of boresight limit.

a more detailed user feedback is now present in the Weapon Allocation window. That let the users know if the issue is related to vertical boresight (with a note to check the observer's pitch) or horizontal boresight.
It will be in the next update release

Let me know if any other boresight issue persists