JNelson

It's possible that the change to when the module are loading is contributing to the change being seen here. Here is a snippet from my log file on 2.9.15, seems like the modules are contributing about 140 seconds, whereas previously their loading would only be on demand (when loading into specific module).

The circle is related to the launch/activity warning system and is only present for C/D band threat at current, although when we add active missile radars it will likely also trigger with these threads if correlated correctly.

Are you still seeing this post patch on the 4th?

Hey, you guys are correct, this appears to be a bug in the doppler gate setting.

It appears the SA-8 has two search beams. If you are curious yourself you can take a look at the database that was constructed for the RWR in the base game files. It's called rhaw.lua If you are seeing the track radar on all the time it could be a bug, however it's not always obvious whether a unit is tracking something or not.

VA-45 was known for carrying sidewinders on outer pylons and there are images. It was their standard loadout, 2 outer sidewinders, 2 tanks and sometimes MK-82 on centre, there is even an interview from a pilot who used to fly them mentioning they carried them on intercepts. It has been discussed at length in the A-4E Discord feel free to read the arguments made by everyone. AIM-9J can be mounted on the A-4E there is nothing preventing it, it's there for people to use if it fits with their goals. If you do not want to use it then you can restrict it through the mission editor.

The RWR specifically indicates PRF changes, in DCS this will indicate a change from search to lock or vice versa, specifically the new guy audio as mentioned in my previous comment. The activity light shows if there is a SAM producing launch related signals, if the RWR thinks these are for you, then it will also give you a launch warning.

The SA-8 has three different emitters. Two for search and one for track. There will not be an audible difference between lock and launch. It is generally highly specific to the system how guidance is handled. For example in the F-4E the APQ-120 is always emitting it's guidance signal. Therefore there is no change between lock and launch. The ALR-46 was designed with the C and D band command guidance SAMs in mind.

Are you sure both these are exactly the same radar settings because the clutter you indicate is just the normal altitude line presentation.

Hey everyone just to clear up some confusion here. Unfortunately Zabuzard was slightly incorrect here. The ALR-46 has a separate set of electronics for detecting C and D band guidance commands that which are commonly found on soviet SAM systems. These signals can be detected and correlated with a threat to give you a launch warning, or warn if there is launch related activity. The RWR can also indicate PRF (Pulse Repetition Frequency) changes which occur during search/tracking changes. These will be indicated by the new guy audio which plays 3 short beeps at the PRF of the emitter. A diamond is also shown around the new guy producing the new guy audio. Currently the new guy audio is bugged and not displaying the diamond and the audio being played is wrong, these will be fixed in patches soon. Lastly the RWR can categorise known active missile threats, these will be displayed and trigger a launch warning - currently this feature is in testing but not in the public version. Thanks, Hopefully that is clearer.

Hi each emitter is characterised by certain things that can be measured, like prf, prf jitter, carrier frequency, power etc. These are then used to match against a table of contacts to identify the emitter type, the limit in the ALR-46 is 64 entries per table. The limited nature of this table means some radars are left out of this table usually because they are not a threat. In DCS units still do track their target with their radar despite not "locking", clearest example of this is the fan song radar which will track the target before actually "locking" the target. So the model accounts for this to allow a more accurate depiction of what is actually happening. Another possibility is that you are in a sidelobe for the radar as it tracks something else. As for the handoff audio, each tone is generated based on the radar characteristics, the audio is not raw per say but based on the measured characteristics of the emitter, including things like PRF and PRF modulation which results in a unique sound. There is currently a bug, this audio should be played as the new guy indication but instead a fixed tone is being played this will be resolved in the next patch so you will correctly hear the sound of the target as the new guy along with the diamond going to the new guy for a brief period. Hopefully that helps.

Hi this is clearly a bug do you mind recording another video but with the radar screen visible please? Thanks.

Yea this is a bug should be fixed next update.

Can you please post the mission and the crash log if able? Thanks!

The doppler gate is being set to what the radar is currently outputting so it will not correctly settle until the radar has.

I think potentially the issue you are running into is the TU-160 and TU-95 have the capability to jam. If you see something like the image attached then that would be my guess.

This is a bug thanks guys.

This depends on a few things it's the guaranteed time for the doppler gate to settle. You can sometimes get away with launching it earlier but it largely depends on the doppler gate setting and the closure velocity.

Handoff plays the captured pulse train information continuously, unfortunately the raw audio produced by the SAM sweep patterns and change in amplitude unfortunately cannot be heard.

I knew the M2K did something with RCS, but it's interesting we have converged on essentially the same solution. In the F-4E implementation the relation between RCS and the amount each side presented to the radar is not linear so as to give a shape closer to that of the general trend of RCS diagrams. There are factors for, side, top, bottom, and front and back which multiply the base RCS based on the amount of each side presented to the radar (as mentioned before not linear though).

Target orientation (how much of the nose/tail, top/bottom, or left/right are presented to the radar) will significantly alter the resulting RCS of a contact in our model. Just to clear something up, the conical scanning is simulated, so there is no "transferring the lock away", rather the antenna is pulled towards the maximum of the total signal (in the conical scan on average), including all kinds of clutter/noise (jamming, chaff, ground clutter and targets). As for chaff the problem is more complicated, currently in DCS chaff objects are very short lived, so building volumetric chaff clouds is not possible (with correct synchronization) or worth the cost at this time, we have asked ED for a more useful data-structure with regards to this which is being looked into for the future. The primary concern relating to the above is the track being disturbed by an aircraft dropping something which a huge RCS very quickly. To combat this the chaff takes some time to bloom and gradually comes up to it's full RCS (as it would IRL) as specified by DCS.

You can hit cage on the throttle, to break the lock and go back to caged mode, you can then re-enter CAA again with the nosewheel steering button.

Some of this thread appears deleted, but I can only assume you are referring to my quick test where I verify the "max demonstrated" figure mentioned in a DOD hearing. As you will note in that comment I added the tacview so you can replicate the test at your own leisure.

Yes unfortunately a change that was a part of the overall fixes did not make it into this patch. As a result the loft will be lower, the original loft however will be restored in the future patches.

The ALR-45, APR-36, and APR-25 are all similar family and the ALR-45 will be done for the early tomcat. The ALR-46 will be the RWR on release for the F-4E. As Cobra says we would like to do an APR-36 but no promises at this time. Sorry for any confusion.