I'm not sure if this is a Supercarrier or F-18 bug, but over the last few weeks I have noticed that the ICLS has been having an issue with localizer accuracy, specifically during Case III operations. As shown in the attached video, the localizer jumps between 2 reference points, one of which is accurate, and the other seems to be loosely based off the ships BRC (9 degrees offset from where it should be.). At times it works as intended, sometimes it is only showing the inaccurate localizer, and it occasionally jumps between the two rapidly. It seems to be exclusive to Case III as I have never noticed the issue during a Case I recovery. (but I will concede I may have not noticed it during Case I as I'm paying far less attention to the ICLS localizer.) Additionally, the glide slope seems to be unaffected, it continues to be just as accurate as it has always been.
The attached video is recorded from mission 12 of the Raven One Dominant Fury campaign, but I have ran into this issue on multiple homemade missions as well. Single player, and Multiplayer.
I'm running the most recent OB version with multi threading on the date of post, with an AMD 5900X, EVGA 3080TI FTW3, 64gb DDR4.
2023-05-15 22-40-43.mkv 2023-05-15 22-33-13.mkv
I'm not sure if this is a Supercarrier or F-18 bug, but over the last few weeks I have noticed that the ICLS has been having an issue with localizer accuracy, specifically during Case III operations. As shown in the attached video, the localizer jumps between 2 reference points, one of which is accurate, and the other seems to be loosely based off the ships BRC (9 degrees offset from where it should be.). At times it works as intended, sometimes it is only showing the inaccurate localizer, and it occasionally jumps between the two rapidly. It seems to be exclusive to Case III as I have never noticed the issue during a Case I recovery. (but I will concede I may have not noticed it during Case I as I'm paying far less attention to the ICLS localizer.) Additionally, the glide slope seems to be unaffected, it continues to be just as accurate as it has always been. The attached video is recorded from mission 12 of the Raven One Dominant Fury campaign, but I have ran into this issue on multiple homemade missions as well. Single player, and Multiplayer. I'm running the most recent OB version with multi threading on the date of post, with an AMD 5900X, EVGA 3080TI FTW3, 64gb DDR4. 2023-05-15 22-40-43.mkv 2023-05-15 22-33-13.mkv
