Default774

You are on the Caucasus mission, try the PG refuelling mission, forgot to mention that

I think this issue is related to what version the mission was created in. Trying any of the instant action missions results in ground not being visible on GM radar, only road/buildings. Gain rocker does not affect terrain visibility on old missions. Following image was captured in a freshly created mission: Following screenshot was captured in the aerial refuelling instant action mission and has no terrain visible. agr_FRESHMISSION.trk agr_INSTANTACTION.trk

https://streamable.com/xwyrws With heavy winds set in the mission, meaning large waves, the armed speed boat does not react to the waves properly and will "sink" beneath the water surface. speedboat.trk

You have a point on 4&5 possibly being outside of the capabilities of the missile, but would expect the missile to not make a random left/right turn and start twitching (Which is the reason I included them). Aside from that, even if the missile cannot kinematically hit the target or the target is outside of the seeker limits, the target is flying at a constant speed/altitude, so I don't think it would be unreasonable to assume the INS would still guide the missile onto the rough track of the target.

To be honest I am not sure why this is needed. The radar cursor soft locking onto the target already happens in the OB build (as is shown in the expected trk) so I assume the radar cursor doing this is intentional, the problem lies in that it doesn't work properly when you lock the target at certain ranges/scale settings. If you want evidence that the radar cursor is actually not supposed to lag behind the target or not track it at all under these specific conditions, then it unfortunately ends here as I don't have any evidence to suggest that is the case. I haven't been able to find any reference that the cursor is supposed to follow the bugged target in the first place (MLU manuals do not mention this behaviour occurring at all), so that might be worth a look at if the cursor following the target isn't actually intentional.

When fired in very steep lookdown conditions the missile has a chance to not guide onto the target properly and will not hit the target. The target is flying straight and level and not defending. 120_ns.acmi 120_ns_2.acmi 120_ns.trk 120_ns_2.trk

The AIM-120 does not guide properly under HOBS conditions. The missile will overcorrect the target and never acquire the target. HOBS shots in the vertical axis cause the missile to make an unusual turn to either the left or the right. 120_hobs_2.trk 120_hobs_3.trk 120_hobs_4.trk 120_hobs_5.trk 120_hobs_2.acmi 120_hobs_3.acmi 120_hobs_4.acmi 120_hobs_5.acmi

As shown in the 16_rws_expected track, the expected behaviour of the cursor after commanding a SAM lock on a target is that the cursor snaps to target, allowing you to command an STT lock on your target without having to reposition your cursor over the target. The radar screen when in SAM will automatically reduce radar scale when the locked target comes within a certain range, however, this transition of radar scale causes problems with the aforementioned behaviour of the cursor locking to the locked target. When a SAM lock is commanded on a target that is near or within the range where the radar scale will automatically scale down, the cursor will either not lock to the target at all, or lag behind. This lag means you can no longer TMS UP to command an STT lock on target without repositioning the cursor. In some circumstances, especially in closer ranges, the cursor might not lock onto the target on the radar cursor at all. This behaviour gets more apparent the closer the target is. 16_rws_expected.trk 16_rws_snap_1.trk 16_rws_snap_2.trk

Certain assets from the WW2 asset pack are visible in the encyclopaedia without actually owning the asset pack. These entries are selectable and cause a black screen when selected. The following list contains all the assets I have found to have this issue, this might not be an exhaustive list. Vehicles V-1 Launch ramp SL Flakscheinwerfer 37 Mashchinensatz 33 Gen Weapons V-1 null

The AIM-120 exhibits twitching when fired directly 90deg into the sky. The twitching gets progressively worse the higher/slower the missile gets. maddog_90deg.trk

The train was manually placed in the mission editor

The GMT radar mode is currently not able to detect a moving train. A moving train should be no different than a regular moving ground vehicle/convoy in terms of radar signature. I think this is an oversight. train.trk

The AI F-117 has no damage model and is invincible. f117.trk f117.acmi

The HQ7 is almost completely incapable of hitting targets at the moment. They get defeated by flying straight and level at a constant speed. All AI set to maximum skill hq7_crotale_single.acmi hq7_crotale.acmi hq7_Crotale_single.trk hq7_Crotale.trk

The moskva stops giving out RWR warnings as soon as it fires entirely. Search still gives nails on rwr, but as soon as you get fired upon by the sams the RWR becomes completely clean. moskva_rwr.trk

The C802AK AShM will guide onto, and kill, helicopters when set on small RCS. This works in all submodes, DIR, COO and LOS. Seeing as the C802 is an anti ship missile, I dont think this is intentional behaviour. I have not been able to get it to guide onto fixed wing aircraft yet, but I imagine it may be possible. c802AK_helicopter.acmi c802AK_helicopter.trk

The C802AK antiship missile exhibits some weird behaviour when they dont acquire their target. The missile will pitch up and gain speed. It will easily reach 40000ft and Mach 4+. I don't think this is intentional behaviour. null c802.trk c802.acmi

The patch notes list the following for the F-16: Fixed: AIM-120 AMRAAM would still receive telemetry even if radar is off. After testing the patch this does not seem the case, and behaviour is the same as pre-patch. Did the fix not make it into the patch/get merged? fcr_off_1.acmi fcr_off_1.trk

Issue still occurs on 2.8.0.32066

After testing on the Hornet with both the litening and ATFLIR, both TGPs give exactly the same results as the litening on the F-16. Definitely seems like a core issue related to all targeting pods. Hornet_LITENING_TGP.trk Hornet_ATFLIR_TGP.trk

I think you are misunderstanding what my track shows. The target in my track is manoeuvring. If you were to perform the same shot in my track and either don't turn the FCR power off, or make the radar lose track normally, the missile will miss. As I mentioned in my earlier post, my target is set to make a turn halfway through the midcourse phase. By the time I am cold to the target the turn hasn't been made yet, so how is my plane supposed to know that the target has made said turn? My radar can't see him, so how does my plane still know his position? If it was simply extrapolating, it would extrapolate the target at it's last known trajectory, which is it going straight. The missile would then get midcourse guidance information which is completely incorrect, and proceed to go active looking for a target that isn't there(the target has made a left turn). The DCS 120 has extremely tight parameters for acquiring a target on INS, even a 10-20kt difference of speed after the missile is on INS means the missile doesn't acquire the target, so it's not coincidentally acquiring it at the edge of the seeker FoV either(you would be able to tell, the DCS AIM-120 snaps like crazy when it acquires a target when on INS). The seeker of the missile doesn't come into the equation at all here, as it hasn't even turned on yet. The DCS aim-120 doesn't have HUSKY/HPRF, so that's not it either. What is actually happening is that when you turn the FCR power off, it doesn't actually drop the track in time. When you lose track normally by for example going out of gimbal limits, it takes exactly 8 seconds before the track is dropped. The FCR switch only drops the track after about 60 seconds. The HUD symbology doesn't update, but none of that matters, as in the backend my plane still has a live track of the targeted aircraft, without actually having any possible way of knowing this. This in practise means that you can fire a missile and have the missile get completely perfect midcourse guidance updates, despite my plane having no possible means to know what the targeted plane is actually doing, the radar is completely powered off after all. Hopefully this explanation is more clear, but it seems the issue is already reported/fixed internally. I can attach more tracks later if it's still needed.

Clouds dont affect the targeting pod at all. It will point track through clouds just fine, see clouds.trk WHOT/BHOT/TV selection does not affect point track range, see noclouds_30k_swap.trk. this mission also now has no clouds set. clouds.trk noclouds_30k_swap.trk

@BIGNEWY While your assessment that the steerpoint diamond is over the target is correct, there is without a doubt an issue with the FCR power switch and the radar holding tracks. By turning off the FCR power the plane will magically keep track of where the targeted jet is without needing radar illumination for roughly 60 seconds. This means you can fire a missile, turn the FCR power off, and then do whatever you want. The missile will get magic midcourse guidance from the jet even if you turn cold. The HUD indications will not change, but this doesn't matter, the jet still knows where the target is in the background. As demonstrated in the trackfile, I fire a missile, turn the FCR power off and then turn cold, the target is no longer being illuminated by my radar. Yet, my missile, almost 180 degrees behind me, is receiving midcourse guidance updates. The target aircraft is set to make a slight left turn about halfway through the midcourse stage of the missile. If the missile was in INS or receiving false midcourse guidance info, the missile would go for empty air and miss. However, the missile keeps guiding perfectly, as if I was supporting it all the way conventionally. Additionally, I fire an AIM-120 about 180 degrees off bore when I am fully cold, you can see the missile attempt to do a complete 180 trying to get to the target. magic_midcourse.trk magic_midcourse.acmi

The A-A TGP will not point track targets further than an arbitrary range no matter how good your contrast is at the moment. This arbitrary range value where your TGP suddenly is able to lock point track the air target is based on your altitude, for some reason. The lower you are, the less range your TGP point track has on air targets, the higher you are, the more range your TGP point track has. This makes very little sense to me. The ranges you are able to point track at per altitude in feet are as follows, roughly: 50K - ~36nm 40K - ~30nm 30k - ~25nm 20k - ~20nm 10k - ~15nm This seems like a completely arbitrary 5nm increase in point track range per 10,000ft of altitude. Again, contrast, target visibility and TGP resolution do not come into the equation at all, just altitude. Even different aircraft do not make a difference, a tu-160 has exactly the same point track range as an F-16. Furthermore, the litening seems to have no issue at all point tracking anything within the 40nm render range of the targeting pod, as long as you're in A-G mode and trying to point track the ground. This definitely doesn't seem correct, I'm not sure how altitude would come into the equation at all when determining point track range. Tracks attached below, all tests performed with absolutely no background clutter behind the target and good contrast. airtoairtgp_cap_10k.trk airtoairtgp_cap_20k.trk airtoairtgp_cap_30k.trk airtoairtgp_cap_40k.trk airtoairtgp_cap_50k.trk

The TGP in air-to-air mode is extremely jittery and barely usable except when flying perfectly straight and level with the target flying directly towards you. You seem to get better results when using STT instead of RWS SAM/TWS, but not by much. Point tracking the target partially fixes this jitter, but this is hardcapped to <25nm for some reason. Comparing it to footage of the SNIPER XR(Not the same targeting pod, I know! This is the only footage of targeting pods in air-to-air mode I could find) the real tracking seems much smoother No point track https://streamable.com/d6cpmx Point track https://streamable.com/qv1mv2 airtoairtgp_jitter.trk airtoairtgp_jitter_pttrack.trk