List of (imo) high priority bugs/issues

[J20Stronk]

.trk #1 AG Radar Bugs:

 

1-1. The first trackfile shows various bugs with the AG radar.

 

For starters using the keybinds for antenna elevation up and down will change the number for desired antenna elevation, but the antenna itself will not move to the entered elevation.

 

You must switch to AA radar and then change back to AG radar to gimbal the antenna after setting the elevation.

 

I believe the antenna will move in AG mode if you have antenna elevation bound to an axis, but I have no axis on my HOTAS to test. :(

 

1-2. This track also shows how upon unlocking a surface target from SSTT (or GMTT/FTT), display range will always reset to 40nm.

 

This will happen also happen when using S2 depress to unlock a target, and will also restore the radar mode to the second-to-last radar mode;

 

ie MAP -> GMTT -> SEA1 Lock -> S2 Depress -> Mode returns to GMTT or MAP and Range to 40nm.

 

If the target unlocks by going out of gimbal range or on it's own due to the notch filter bug (bug I know has been fixed internally.), then mode does not reset but display range does, back to 40nm.

 

1-3. AG radar contact will briefly display in AA radar modes, and can also be locked onto and engaged if you are quick enough.

 

SD-10s will home onto the surface target unless there is an aircraft nearby, then they'll chase it instead. (<- not shown in .trk)

 

 

 

.trk #2 AA datalink contacts and CM-802AKG oddities

 

2-1. There is a small window of time where a contact will disappear from HSD upon being detected by radar.

 

Though my track does not show the worst case, there are times especially in populated MP or SP missions where an AA contact will not reappear on HSD until the contact has faded entirely from the RDR screen.

 

2-2.The first half of the track show how contacts locked in STT do not update position on HSD at all, provided that the aforementioned disappearance bug does not occur.

 

They appear static on HSD in the exact same location where first locked in STT.

 

Once unlocked and detected by other means or ownship radar if bug from above does not occur, they will teleport to their new position on HSD.

 

Changes in the target's heading are still repeated on the HSD contact however, even though it is not shown in the track.

 

2-3. CM-802AKG will not update the SPI on the HUD if you have selected PP mode, nor will it highlight the first RP point on the HUD or HSD. The AKG missile will still follow the selected PP or RP route, but range and target diamond on the HUD will always point to the selected SPI (usually selected waypoint on UFC).

 

Also, the HSD now seems to indicate that the max launch range is 20nm in a similar way as the LS6/GB6, by using a perpendicular line and dotted line to SPI in PP and TOO modes. of course the AKG has much greater range, and you can fire it beyond the indicated 20 limit.

 

I think it's actually showing Min launch range, in which case, wouldn't it be better to have a large blue circle as the indicator for that just like the LS6/GB6? to avoid confusion.

 

 

3. Selecting Non-IAM AG weapons remove the waypoint indicator from the HSD.

 

This is probably behavior from the real aircraft, but I figure I should still report it and be wrong than live with it and never have it looked at.

 

The only way to have the selected waypoint/SPI show up on the HSD in AG mode is to have an INS/GPS guided weapon with PP capabilities selected like the C-802AK/G, GB-6 or LS-6 bombs. Selecting any other weapon removes the waypoint/SPI indicator from the HSD, making it difficult to find target location or SPI where AG radar/ TGP is designating.

 

4. Most lighting knobs still behave like buttons and do not dim lighting.

 

Self explanatory. In the track I show which lighting knobs behave more like on/off switches (Landing Gear, OXY Blink), and others that just do not work (AAP Brightness).

 

Also the Speed-Brake, Drogue-Chute, TE-Flaps and Front Panel Indication (Trim, selected FCS mode, NWS) lighting is way too dim during the day.

I believe the intensity is supposed to be controlled by the Day/Night switch and brightness knob on the Warnings and Advisories Panel (which do work, but only for this panel).

 

 

 

Thanks for coming to my TED Talk. Keep up the good work Deka! :thumbup:

1 JF AG Radar Bugs.trk

2 JF DL AA detect delay and AKG bugs.trk

4 JF binary light knobs and dim status lights.trk

Edited April 13, 2020 by J20Stronk

[Kumabit]

Emmm also the AA radar curser has wrong elevation indications, the indicated scan elevation is not what the radar is actually scaning. For example, if a target is at 20,000 feet, I need to adjust the radar elevation to let the curser indicating I am looking at 30-45(30,000 feet to 45,000 feet) to find the target.

 

Also, the elevation angle of each scan bar is too small. This has been a bug during the first release but got fixed in the 2nd or the 3th patch. However, it comes back now.

[foxwxl]

Emmm also the AA radar curser has wrong elevation indications, the indicated scan elevation is not what the radar is actually scaning. For example, if a target is at 20,000 feet, I need to adjust the radar elevation to let the curser indicating I am looking at 30-45(30,000 feet to 45,000 feet) to find the target.

 

Also, the elevation angle of each scan bar is too small. This has been a bug during the first release but got fixed in the 2nd or the 3th patch. However, it comes back now.

 

Already fixed and waiting to roll out with next update.

[foxwxl]

DL threat list and datalink system is still WIP, and is subject to change(very likely) when our coder is available.

[L0op8ack]

I think he post too quickly,

 

better wait 2 more days and check again after the coming update.

[shaHeen-1]

AG can never be above AA:radar+datalink. AA is number 1 priority.

[LastRifleRound]

AG can never be above AA:radar+datalink. AA is number 1 priority.

 

But I like AG....

[shaHeen-1]

But not more than the datalink surely? Datalink is what let's you get close enough to toss those gb6. As you may see amraams have ranges of up to 80nm now. Goodluck with your AG2 load out when you only have a 5 sec warning.

[LastRifleRound]

But not more than the datalink surely? Datalink is what let's you get close enough to toss those gb6. As you may see amraams have ranges of up to 80nm now. Goodluck with your AG2 load out when you only have a 5 sec warning.

 

Why pick? Shouldn't we have both a functioning datalink AND AG radar? I think that's what was advertised for the final build any way.

 

Also why are you flying strike without CAP? And how do you think we get on target in Harriers and Viggens? By datalinking and lobbing fox 3's when there's things that need bombing?

 

It's just a false binary in my opinion. It's all good. Deka's going to get it all done at some point.

[shaHeen-1]

I thought we were discussing priorities. If this is pointless then why comment? Cap may or may not save you. Datalink almost certainly will. Who said anything about firing fox3s?

[LastRifleRound]

I thought we were discussing priorities. If this is pointless then why comment? Cap may or may not save you. Datalink almost certainly will. Who said anything about firing fox3s?

 

Never said it was pointless, just pointing out it's pure opinion and I have a different opinion driven by a different set of anecdotal factors. I'd like to see AG done. DL is good enough after the bug fix goes through that's already in the change log in my opinion.

 

I think whether something has a point or not there's nothing wrong with posting it on a forum. What the hell else can we do these days anyway, so I welcome the discussion. Just thought I'd weigh in with my .02