fixed internally oap1 and oap2

[Viciam1]

Hi guys,

Are the offset aim points broken? They don't seem to work?

Also...are there 2 ways of setting them? 1: from the TGP and 2: from the destination page?

Thank you. They don't work well for me. I set them but they look else where. Used to work for me.

[Moonshine]

dont know why this is tagged as "missing trackfile" this issue is now sufficiently reported..

Edited May 23, 2023 by Moonshine

[twistking]

4 hours ago, Viciam1 said:

Used to work for me.

From my experience they never worked. The jet would always designate the current TGP POA for weapon release, even if TGP was in OA and the actual target (TGT) was offset.

[Moonshine]

it did work prior to the ominous christmas last minute update in 2022.. since then they are broken again

Edited May 23, 2023 by Moonshine

[Viciam1]

thats so lame.

[twistking]

21 hours ago, Moonshine said:

it did work prior to the ominous christmas last minute update in 2022.. since then they are broken again

 

ok. must have missed that.

[RogueRunner]

seems a few of these are on the 'back burner' as it were, the GBU alignment one also seems not to get attention

[Moonshine]

yeah its a bit sad currently. for most sensors and functions, while they do work lets say 75%, often you need to rely on some weird workaround to get desired results, making the viper that by design would be highly optimized for pilot use, a very tedious plane in its current state in DCS. OA1 and OA2 are completely unuseable since 6 months now

 

Edited May 26, 2023 by Moonshine

[VarZat]

I agree with you @Moonshine.

I hope to see some big bugs getting squashed soon

[Viciam1]

3 hours ago, RogueRunner said:

seems a few of these are on the 'back burner' as it were, the GBU alignment one also seems not to get attention

Yeh i haven't used the gbu jdams for a few months now. So badly want to. They are lame ducks

[Viciam1]

Proper lame duck bruv.

[GrEaSeLiTeNiN]

TGP OA1 OA2 still messed up for me. Often I can get TGT and OA1 but not OA2.

[Moonshine]

yeah they are still broken. been listed as fixed in two separate patches yet the issue remains. for both OAs, the symbology appears to be below ground. the higher you set the elevation data in the DED, the more "below ground" they appear. as if the values are in the negative.

dont know why this thread has the "missing trackfile" tag still...

Edited August 28, 2023 by Moonshine

[_SteelFalcon_]

@BIGNEWY is there any news about this? It‘s been a while and despite being listed twice as fixed in OB patches (2.8.6.41066 and 2.8.3.37556) it still is bugged.

The feature symbology is useless like this at the moment.

tracks should be sufficient in this report

 

[Shrike88]

On 8/28/2023 at 3:33 AM, _SteelFalcon_ said:

@BIGNEWY is there any news about this? It‘s been a while and despite being listed twice as fixed in OB patches (2.8.6.41066 and 2.8.3.37556) it still is bugged.

The feature symbology is useless like this at the moment.

tracks should be sufficient in this report

 

Agreed.  Hopefully fixed and some closure.  Last mini update was June.  Seems much of the Air to Ground section / MC stuff has been sidelined.

On 5/26/2023 at 11:29 AM, VarZat said:

I agree with you @Moonshine.

I hope to see some big bugs getting squashed soon

Well thats May.  Still nothing - Bump

[BIGNEWY]

A tweak for this issue is coming in a future patch. 

thank you