Jump to content

Recommended Posts


RadarSearchCW=FALSE

This means that the radar does not search in Continuous Wave (CW) mode.

RadarTrackCW=FALSE

This means that the radar does not track in Continuous Wave (CW) mode.

Further, the radar is most likely a Pulse Doppler (PD) set or a simple range only radar. This means that a jammer designed to interfere with a CW radar may not work as the fundamental operating principles of CW and PD radar are different and jammers useful against one type are generally not useful against the other. Later jammers may have settings that allow them to be effective against both types.

Are there any other lines with the words "Search" or "Track" in them?

  • Like 3

Share this post


Link to post
Share on other sites
On 28.10.2022 at 1:36 AM, Righteous26 said:

RadarSearchCW=FALSE

This means that the radar does not search in Continuous Wave (CW) mode.

RadarTrackCW=FALSE

This means that the radar does not track in Continuous Wave (CW) mode.

Further, the radar is most likely a Pulse Doppler (PD) set or a simple range only radar. This means that a jammer designed to interfere with a CW radar may not work as the fundamental operating principles of CW and PD radar are different and jammers useful against one type are generally not useful against the other. Later jammers may have settings that allow them to be effective against both types.

Are there any other lines with the words "Search" or "Track" in them?

RadarMissileGuidanceCW=TRUE

 

RadarSearchTime=0.4

 

RadarTrackTime=0.8

Share this post


Link to post
Share on other sites
24 minutes ago, Righteous26 said:

Which missile is this?

These lines look like data for an Air Intercept (AI) radar.

Its for an S400 Air Defense defence system

Edited by AcariaPlainum

Share this post


Link to post
Share on other sites

The radar in question is a PD Active Electronically Scanned Array (AESA) or PD Passive Electronically Scanned Array (PESA). SF2 does not simulate these sorts of radars very well as it was intended for radars that use only one antenna and are mechanically scanned and AESA/PESA radars have hundreds of small antennae and are electronically scanned.

RadarMissileGuidanceCW=TRUE

This means that the radar can provide CW illumination to guide a missile to the target. The missile is likely a Semi-Active Homing Missile (SAHM). However, some missiles may require guidance to the target before switching to their own internal guidance (e.g. AMRAAM, Phoenix) but SP2 does not simulate this properly because you get a launch warning on your RWR and this likely would not be the case especially when facing an AESA/PESA radar.

RadarSearchTime=0.4

This is the time required for the radar to complete one scan of its search sector at any given range. This means it updates contact positions every 0.4 seconds.

RadarTrackTime=0.8

This is the time required for the radar to switch from search to track mode when acquiring a target. This will take 0.8 seconds in this case. The radar likely has to track the target before the computer will fire a missile.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Similar Content

    • By JamesWilson
      Hi everyone,
      I'm trying to recreate the 1st Gulf of Sidra Incident with my F-14A Tomcats and my Su-22M3 Fitters, doing it extremely historically accurate, paying attention to every little detail.
      So far i've done everything, and it's almost identical to the real one, but there's ONE issue i can't figure out, let me explain:
      During the morning of the 19th of August 1981 two F-14A Tomcats intercepted two Libyan Su-22M3 Fitters in the Gulf of Sidra.
      The Fitters were equipped with two AA-2 "Atoll".
      Just before the merge, while nose-to-nose, one of the two Fitters fired a missile to one of the two Tomcats, but being the missile a very old and primitive heatseeker, it started tracked and going for the Tomcat, but as soon as the F-14 made a slight break, the Atoll lost its track.
      The PROBLEM IS:
      There's no way i can make the Fitters shoot the missiles before merging, if only the AA-2, or any other equippable missile was all-aspect or radar guided just like the R-23, i think it would work.
      I tried having a head-on merge with two Mig-23 Floggers equipped with radar guided R-23s and they shot at me before merging.
      I tried all other available missiles and nothing changed, some didn't show either.
      I tried copying and pasting the Data file from the Aim-7 to the R-60 Data file, and nothing changed.
      I tried changing the loadout file to R-23, but the Fitters show up without any weapon since there's no R-23 option in loadout for Su-23M3s, so i think it's not possible to have them (and would be historically inaccurate too).
      I tried changing enemy difficulty from Normal to Hard, but nothing changes still.
      The only thing the Fitters do is shooting their guns just before the merge, but no missiles are fired when nose-to-nose.
      Is there a way to fix this? A way i can make my Fitters fire at least one of their missiles when we're nose-to-nose, just like when i got nose-to-nose against Floggers equipped with R-23s?
      Is it a problem with the enemy AI? Or with the missiles? Or maybe even with the Su-22M3 Fitter i'm using?
      Thank you very much for helping me
    • By JPMoney
      I’m flying an F-16I Sufa mod for Strike Fighters 2 Israel. I’ve modified the loadout ini file in an attempt to change the missile types and positions on the pylons. I’m having a consistent issue with the outer pylons (not the wingtip mounts, but the furthest pylons from the fuselage under the wings). I want these to carry one AMRAAM each, and as far as I can tell I have modified the loadout ini, the related missile object inis, and aircraft ini to be able to accommodate this. However, when I go to a single mission in-game and access the loadout screen, those outer pylons are always empty (no missiles). When I go to add missiles manually to these pylons, all AMRAAM types only are available in “4s” and not “2s.” So in other words it’s trying to mount 2 AMRAAMs on each pylon, which shouldn’t be possible (realistically), as these are set up for single missiles only. The F-16I ini file does have a relatively complex series of pylon rules, but I believe I have it set up to be able to mount AMRAAMs on these pylons, and I can’t find any setting in any file that would allow me to indicate there should only be the option to mount one missile per pylon in the loadout screen in game. I suspect a setting related to this “4 missiles” issue is preventing my loadout ini file from operating correctly and defaulting my vipers to have AMRAAMs on those pylons. 
       
      Any thoughts on a setting I am missing here?
    • By toot
      As much as I like the stock F-14A, The roll rate on it is just awful. The only way I manage to get a proper fast roll is by pointing my elevators down and then rolling, which is really annoying when you're trying to gun someone down. Does anyone have any fix available for the data.ini on it? Would highly appreciate that. Thanks!
    • By 76.IAP-Blackbird
      Dear Friends,

      Today is a big day. IL-2 Sturmovik team is glad to report that after almost three years of development Battle of Normandy is out of Early Access and is officially released - 5.001 update is out!

      «You are about to embark upon the Great Crusade, toward which we have striven these many months. The eyes of the world are upon you. The hopes and prayers of liberty-loving people everywhere march with you.» Gen. Dwight D. Eisenhower.



      The official release also means that in addition to Battle of Normandy Premium Edition in our webstore there’s now Standard Edition without two Collector Planes - German jet bomber Arado Ar 234 and British fighter Spitfire Mk.XIV (they can be bought individually). On Steam the new module and its accompanying Collector Planes will appear in the coming weeks - please stay tuned while we work out the details. As usual, Battle of Normandy owners who have linked IL-2 and Steam accounts can access all the new content in the Steam version already.
       



      These years weren’t easy, but they were very interesting. During the development we have created many new technologies and approaches, did a lot of historical research, implemented new solutions. The last aircraft for Battle of Normandy were released in Early Access in August and today we add the last pieces - the map of the Northern France and Southern England, Pilot Career mode, Quick Mission Builder and Advanced Quick Mission Generator support for the new map.





      We have told about the Career mode and the new map in our recent Dev Blogs, but must point out again that they set the new record in terms of the work involved. New mission types, new airfield types, new airfields appearing on the map after D-Day - bringing their total amount to 100 airfields with historically accurate layouts! New objects created specially for the module - ships, ground vehicles, buildings, coastal defenses, V-1 buzzbombs and their launch positions, dozens of new aircraft paint schemes, etc.




      Battle of Normandy contains 10 player controllable aircraft (8 in the Standard Edition):
      - Hawker Typhoon Mk.Ib – British fighter/bomber,
      - North American P-51B-5 Mustang – American long range fighter,
      - Republic P-47D-22 Thunderbolt – American fighter/bomber,
      - Messerschmitt Bf 109 G-6 Late – late version of the German fighter,
      - Focke-Wulf Fw 190 A-6 Würger - German fighter,
      - De Havilland Mosquito F.B. Mk.VI ser.2 – British twin engine fighter-bomber,
      - Messerschmitt Me 410 A-1 Hornisse – German twin engine fighter-bomber,
      - Junkers Ju 88 C-6 – German twin engine heavy fighter,
      - Supermarine Spitfire Mk.XIV – British fighter (Collector Plane included in the Premium Edition),
      - Arado Ar 234 B-2 Blitz – German twin engine jet bomber and recon aircraft (Collector Plane included in the Premium Edition).













      Each aircraft includes a slew of historically correct modifications - unlike other games where each modification would be counted as a separate aircraft model, in Great Battles you can freely select and combine them. For instance, Me-410 A-1 mentioned above has modifications that, when selected, make it a whole model lineup:
      1. Me-410 A-1/U2,
      2. Me-410 A-1/U4,
      3. Me-410 B,
      4. Me-410 B-2,
      5. Me-410 B-2/U1,
      6. Me-410 B-2/U2,
      7. Me-410 B-2/U4,
      8. Me-410 B-2/U4 field mod with four MG 151 guns.



      In addition to the all above, update 5.001 contains the results of the big work on the damage model improvements which are of course are applicable to all the modules as usual - as you can see in the long list below, it required many changes in various parts of the sim. The testing and tuning of these changes by beta-testers from the community took a lot of time. We think this is the big step forward for Great Battles series and hope you’ll enjoy it. 

      There are many other fixes and improvements - for instance, the mission loading time has been reduced dramatically, several times less on some PC configurations! The pilot and tank crew AI got better, etc.:

      Main Features
      1. All Battle of Normandy owners have access to Northern France and Southern England map in two variations (before and after the D-Day). As usual, in multiplayer mode the map can be accessed by all Great Battles players.
      2. All Battle of Normandy owners have access to the mid-1944 Career mode (3 countries, 5 phases, 17 frontline states, 225 historical squadrons, 103 of them joinable by the player, many new mission types).
      3. All Battle of Normandy owners have access to QMB and AQMG game modes on the new map for a quick action, also with many new mission types.
      4. Numerous new aircraft paint schemes added, including different invasion stripes for various time periods of 1944.
      5. PzKpfw IV Ausf.H. tank added (AI controlled).
      6. Flakpanzer IV «Möbelwagen» SPAA added (AI controlled).
      7. Gleaves-class destroyer added (AI controlled).
      8. The loading speed of all missions on all Great Battles maps has been improved significantly.

      Damage Model Improvements
      9. Aircraft DM: RHA equivalent of the aircraft skin has been reduced nearly three times to the previous (wrong) values.
      10. Aircraft DM: an issue that made aircraft skin damage too severe for larger bombers and some fighters has been fixed.
      11. Aircraft DM: like the previously released change for larger caliber ammo, now all projectiles in the game loose integrity and stability after penetrating a significant armor thickness which affects their remaining ability to penetrate armor.
      12. Aircraft DM: the relative speed of the target is correctly accounted for projectile penetrations calculations.
      13. Aircraft DM: AP bullets and shells make slightly bigger holes in the airframe and aircraft skin.
      14. Aircraft DM: powerful HE rounds explosions cause more damage to the airframe, aircraft skin and components.
      15. Aircraft DM: small HE bullets cause less damage to aircraft skin.
      16. Aircraft DM: it is now possible to damage radiators and fuel tanks when firing 7.62-7.92 rounds from more than 350 m distance.
      17. Aircraft DM: bullets are less likely to ricochet from aircraft skin at low angles.
      18. Aircraft DM: Bf 109 radiator collision model has been improved (previously its wrong shape could cause most smaller caliber bullets to ricochet when fired directly from behind).
      19. Aircraft DM: the loss of the bullets energy hitting Bf 109 F-4 engine has been corrected.
      20. Aircraft DM: an issue that caused bullets hitting Spitfire Mk.XIV MGs and guns to not lose energy has been fixed.
      21. Aircraft DM: engine fire probability from bullet hits has been somewhat increased for WWI-era piston engines and jet engines.
      22. Aircraft DM: engine fire probability from bullet hits has been reduced for WWII-era piston engines.
      23. Aircraft DM: fuel tank fire probability from bullet hits has been reduced.
      24. Aircraft DM: fuel tank fire and explosion probability from HE ammo hits has been reduced, now it depends on the HE power more.
      25. Aircraft DM: it’s now harder to put out the fires by side-slip movement.
      26. Aircraft DM: the several years old ‘crew health cheat’ (they required four point-blank 7.62 bullets in the torso or two in the head to be killed) has been removed. Now their ability to sustain damage is much more close to reality.
      27. Crew DM: a random error that could cause a death from mild G-loads has been found and fixed, thus improving survivability rate during emergency landings.
      28. Ballistics: ricochet tendency has been reduced somewhat.
      29. Right wing MGs on P-51B can be correctly damaged.
      30. P-51B and D fighters wings (middle-upper parts) can be correctly damaged.

      Me 410 Improvements
      31. Me 410A-1: weapon panel placards corrected for WB 151 and MG 131 modifications.
      32. Me 410A-1: missing rods from bomb doors to the forward window added.
      33. Me 410 A-1: speed and timer gauges in the pilot’s cockpit corrected.
      34. Me 410 A-1: altitude and speed gauges in the gunner’s cockpit corrected.
      35. Me 410 A-1: bomb holders for 250 kg bombs and for SB 1000/410 look corrected.
      36. Me 410 A-1: radiator fenders indicators light up when the cockpit light is turned on.
      37. Me 410 A-1: the rear landing gear state affects air drag.
      38. Me 410 A-1: technochat message warning about the gun overheating restored for the gunner.
      39. Me 410 A-1: now the gunner can use the entire horizontal range of the guns for aiming.
      40. Me-410 A-1: radiators can be correctly damaged by AP projectiles, resulting in coolant leaks.
      41. Me 410A-1 intercept missions added to AQMG game mode.

      Tank Crew Improvements
      42. M4A2, KV-1s, Pz.IV.G, Pz.V.D, Pz.VI.H1 hatches close when the turret blocks them.
      43. The damage of the gun barrels base on Pz.III, Pz.IV and Pz.VI is calculated correctly when it is hit by fragments.
      44. In multiplayer a guest gunner (who connected to someone else tank) won’t constantly hear the turret turning mechanism noise.
      45. In multiplayer a tank owner won’t hear the gun or MG reloading sound when another player connected to his tank to the gunner or MG gunner station.
      46. In multiplayer turning aircraft or tank turrets controlled by another player emit correct turning  sounds.

      AI Improvements
      47. AI controlled bombers keep formation a bit better during climb.
      48. AI pilots will attempt to return to base in the event of an oil or coolant leak.
      49. Me 410 pilots will correctly drop bombs in a deep dive.
      50. Mosquito, Ju 88 C6 and Me 410 pilots will correctly drop underwing bombs.
      51. Twin and 4x guns in AI controlled vehicles won’t judder during aiming.

      Other Improvements
      52. Dropping an 1650 pounds bomb from Handley Page O/400 bomber won’t display an error.
      53. A visual artifact in front of the right engine of Handley Page O/400 bomber has been removed.
      54. An issue that caused guns and MGs to ‘float’ above certain breastwork has been fixed.
      55. ‘No jamming’ difficulty option works correctly for aircraft turrets.
      56. Me 410 is correctly counted in stats.
      57. Visual bomb explosion effects has been corrected for cases when a bomb ricochets and goes off above the ground.
      58. Proximity and CheckZone triggers in missions won’t erroneously count non-spawned and inactive objects.
      59. External camera works correctly after flying beyond the map borders.
      60. An issue that could lower the muzzle speed of an overheated MG before causing additional scattering of the fired bullets has been fixed.
      61. Both P-47 have their idle engine RPM corrected (it was a bit too high potentially causing moving with brakes applied.
       
    • By Righteous26
      I have two different packs that include the MIM-23B HAWK missile in them. There are significant differences in the _data.ini files between the two versions. I have included parts of the _data.ini files below. It seems the GKABS missile is much better across the board based on the numbers. Is there any way to rectify this or can the _data.ini files be used interchangeably?
      MIM-23B (GKABS HAWK 1.0.3)                                        HAWK B (SF2 SAMS Pack)

      GuidanceType=12                                                                  GuidanceType=12
      Accuracy=80                                                                           Accuracy=70
      MaxTurnRate=15.000000                                                      MaxTurnRate=15.000000
      MaxLaunchG=6.000000                                                         MaxLaunchG=3.000000
      LockonChance=85                                                                  LockonChance=80
      LaunchReliability=95                                                             LaunchReliability=85
      ArmingTime=0.400000                                                          ArmingTime=2.000000
      SeekerFOV=120.000000                                                        SeekerFOV=60.000000
      SeekerGimbleLimit=180.000000                                           SeekerGimbleLimit=135.000000
      SeekerTrackRate=13.000000                                                 SeekerTrackRate=13.000000
      SeekerRange=55000.000000                                                  SeekerRange=40000.000000
      //
      MinLaunchRange=1500.000000                                            MinLaunchRange=1500.000000
      MaxLaunchRange=39357.337000                                          MaxLaunchRange=40000.00000
      Duration=60.000000                                                               Duration=183.000000
      CounterCountermeasure=50.000000                                      CounterCountermeasure=40.000000
      NoiseRejection=60.000000                                                    NoiseRejection=40.000000
      CapabilityFlags=0x10000003                                                 CapabilityFlags=0x10000000
      //
      BoosterDuration=5.000000                                                    BoosterDuration=5.000000
      BoosterAccel=30.000000                                                       BoosterAccel=16.722000
      //
      SustainerDuration=21.000000                                                SustainerDuration=21.000000
      SustainerAccel=10.000000                                                     SustainerAccel=1.429000

       
       
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..