witness_me

UBOATS meant lock warning (i.e. constant illumination / tracking) - a radar warning receiver on it's own can't detect missile launches unless it picks up on the electromagnetic radiation for the missile guidance (fox1 or 3 etc - nowdays it's more common for the rwr to be part of a larger integrated defensive subsystem, including missile warning systems etc) you can pick up the guidance signal if you're lucky - not sure if that's modelled in DCS. I'm not disputing that instant launch warnings are probably a bug not sure if i'm following - a radar in TWS still illuminates a target with emr, so the target should get some kind of rwr warning for the threat if the rwr is not from the stone age - tws is just a type of 'multitasking' where the radar splits a percentage of it's time making sure the target is where it's expected to be, based on algorithms predicting it's location using previous vectors stored in memory, and looking out for other targets. Also i think we're agreeing that the rwr can only know about a missile headed your way if it picks up relevant EMR (e.g. sarh or guidance signalling etc)

i would expect rwr warnings for a tws track too though, unless i misunderstood what you're saying? the rwr should produce warnings when it detects emr - it should produce a tone if it's tracked using tws (e.g. square or sine-ish waveform), a tracking warning if the aircraft is continuously illuminated, a missile launch if it picks up the radar signalling to an amraam datalink etc

hi, just wanted to say i don't experience this anymore since the last patch, when i egress at high G or when i do a roll & dive etc thanks so much for fixing! feel free to delete the post for clean-up purposes etc

you mean this reported bug? :P https://forums.eagle.ru/showthread.php?t=259790 i wonder how many duplicates there are :P just wanted to say, i don't get this problem anymore - the elevation seems alright, however, i noticed that sometimes you can't find a target no matter what, unless you switch to a/g mode and then go a/a again i recorded a video with a bunch of problems with the air to air radar (most importantly, sometimes the radar will drop a track when i roll, sometimes all it takes is a 50-60 degree roll, sometimes it happens at 90-100 degrees), you can see the targetting problem here: - in the video i'm swapping between the f1 view and the f10 map so you can see i'm pointing at the correct direction/elevation etc my "fix" is to quickly swap from a/a to a/g and back, after i'm done with an engagement, in order to reset it

there's no doubt in my mind that a top tier radar manufacturer from china would be able to come up with a similar or better radar than the griffo s (or a radar with similar specs from any western manufacturer) at a lower price, i think that much is a given - if PAF went with lower specs it would either be because they wanted to produce it domestically/there was some IP transfer or they were looking at drivign the cost even lower or maybe they just use different air to air tactics? p.s. please take a look at my youtube video and let me know if you get the same problems - it's driving me nuts, i can't do air to air since the last patch :P

it does, go to a2g master mode, then slew it to some direction (say 10 degrees lower than boresight) and it'll remain pointing to that direction (and you'll be able to see the ground zooming past you in the tgp view) if you're asking why doesn't it continuously change angles so that it can follow what you slewed it at initially, then it's because there's something missing from being able to specify a point in 3d space: distance. You have a vector to a desired point, but the computer doesn't know how far along that axis the point you want to track is, so it can't calculate how fast it needs to rotate the tgp gimbal in order to follow it. If you're in a car that's moving at 50mph and you're looking at something on the side half a mile away, you'll be moving your eyes much faster than if you're looking at something that's initially in the same vector but 5 miles away. The computer in this case doesn't know how far the object you want to track is, so it can't follow it (basically it's focused at a point at infinity, as it can't laze&range)

just a guess - i can't log on to the game at the moment, did you disable the zeroizer?

the grifo i linked does +- 60 degrees on both axis - i linked it here just because it seemed to me that in the early days of the project the spec was for a different setup but they (PAF) altered their specs later on (different tactics? cost? who knows) the 2nd photo is from an early f15, the other one is from another airplane/it's there just as another example of what they used to do back in the day (the 1st one is still in use) no worries, i didn't get such an impression, all good here :) we're all just trying to figure stuff out :beer:

your airplane has gps/ins and it's computer can calculate it's location in 3d space and it's vector of movement (using accelerometers, measuring angular velocity with gyros, it can measure air speed etc), it can also calculate the location of a waypoint in 3d space, relative to own position (necessary for navigation cues etc) and/or provide an angle to the tgp to point at

@Pikey - if you're referring to a problem similar to the one i was reporting here: https://forums.eagle.ru/showthread.php?t=259790 -- I think it's now fixed @Aeria - first of all my comment about the radars with 2dof in the last 20yrs was a brainfart - it was late and all that :) I meant, the latest radars with a rectangular scan area (before advances in electronics made possible the increase in the number of modules / being able to have a square or square-ish scan area), before they were all obsoleted by aesa's (a good couple of decades ago or so), were using 3dof gimbals to overcome issues with the scan area becoming very narrow when an airplane is banked and/or for noise related reasons etc - chronologically this is more of a 70's / 80's issue rather than 20 years ago e.g. and - the f15 was using the same arrangement so the 30 degrees limitation on the vertical wasn't so much of a problem unless someone would do a barrel roll :P the jeff was to use this originally i think: https://www.leonardocompany.com/documents/20142/3149726/GRIFO_S_Fire_Control_Radar_LQ_mm07799_.pdf?t=1538987501858 maybe PAF didn't want to pay for a larger antenna for whatever reason :S I have no idea :S I know very little about the company that makes the radar and/or the history behind the jeff and about how "non western" airforces use their aircrafts/tactics involved etc, maybe somehow it's a non issue for them? As far as the game is concerned though, the radar is behaving erratically: - sometimes if i roll more than 50 degrees, i might lose a track, even if i'm pointing straight at the target (wtf!?) - sometimes the radar tracks 60 degrees on the vertical, sometimes it doesn't - there's all sorts of visual glitches (i can swap modes and that takes care of them) - it's not losing tracks when it should do - picking a target is all over the place, sometimes i click on an old return and the radar locks on to a target 20 degrees apart !? I'm not sure if it's my computer, if it's a general issue but nobody's doing any a2a and people haven't noticed, if the radar has some weird specs regarding rates of changes in attitude and/or angle when tracking etc i recorded all sorts of issues with the help of a mate: i'll try to raise a bug report, but considering that this post took me almost half an hour to type, i'll probably get to it sometime in the week :)

I'm pretty new to DCS, so not sure if this is how the game implements things etc - that being said you shouldn't be getting a warning in your RWR for an amraam or sd-10 launch, regardless of the presence of a track or not. I always thought the msl lch cue was from the MWS :confused: The rwr is able to detect emr from radars and can give you a warning for changes in the tracking mode or a missile launch based on the changes in the signature of the radiation detected. There would be changes between TWS and DTT or STT (as the signature of the emitter changes and also the frequency of "beam hits" / energy etc) or if a sarh missile is lauched, as again there will be changes to the signature. However there wouldn't be any changes to the radar signature when launching a missile that gets its updates through a datalink like the amraam unless you have some equipment that can detect the datalink signal etc (there are advanced rwr's out there that use fuzzy logic and have a very large database of systems/frequency hopping/energy patterns etc, but i very much doubt our jeff has any of that)

make sure you're in air to ground master mode

yeah if you have the same limits up/down with left/right then you can still maneuver at least, unfortunately the jeff has 30 degrees on the vertical and 60 on the horizontal afaik sorry i wasn't talking about aesa's, i shouuld have clarified that my comment didn't make much sense if taken literally - i doubt anyone is still making this type of radars these days - they're not in use for some time now. The airplanes you mention are pretty old - i guess i was expecting a modern fighter to fly in a certain way, but maybe that wasn't a concern for the manufacturer etc or they simply didn't want to pay for this capability the "problem" i'm having is that if the radar scan zone is a rectangle and you can't rotate your antenna then when the airplane rolls the limits change (horizontal limits are now vertical and vice versa), not allowing you to perform some types of manoeuvres. It's getting pretty late for me i'll try to post some drawing tomorrow and hopefully explain this better - thanks for trying to help though!

doh - sorry didn't realize you were talking about the actual mfcd resolution :doh:

no issues here (i'm exporting the tgp view though - not sure if that plays a role?)