Jump to content

Crusader

+MODDER
  • Posts

    4,161
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by Crusader

  1. Said to be leaked footage of the incident. Also there https://news.sky.com/story/amp/leaked-footage-shows-moment-british-f35-jet-crashes-into-mediterranean-during-hms-queen-elizabeth-carrier-take-off-12482611
  2. Even easier if it works with just the SystemType. As long as the added object (missile) doesn't need a yaw angle.
  3. Yes, by making the object to be added a missile/rocket which is never launched. The GO (Jeep in your case) needs a WeaponSystem section with a missile launcher. Can be a bit ini-editing intensive until it looks right, but its possible.. see my WIP pic of a Quad .50 on the TW CargoShip mast (still unfinished) For positioning, example from my wip for the directions WeaponPosition=0.0,40.0,23.0 // ------- ------------ = L/R, F/B, U/D from GO center
  4. There was an avalanche of patches/updates during the heydays of SF2. What worked in a certain way with one game version became nonfunctional with the next version. Its possible that before SF2I (which brought the F-16A) RCS "worked" with low negative values. And it changed subsequently. Older posts from years back are or can be connected to a certain game version. not to mention that individual users often did not update to the latest version because of personal preferences or "new bug avoidance"
  5. You are on the right track. Its a bit of confusion/confounding of the [AircraftData] section with the AircraftShortName= This line is only used for in-game text display purposes, not connected to the RWR and The "aircrafts" data ini, e.g. MiG-29M_data.ini which contains the [DetectSystem] section with the important RadarFamilyName= entry And this (example) RadarFamilyName=MiG-29M designation is what goes into the first part of the list in the .lst file, calling the appropriate texture MiG-29M=RWR_MiG-29M.tga If the RadarFamilyName= line is missing, simply add it. Several older mods dont have it or it has been overlooked during upgrade/conversion from SF1 to SF2 This explanation should be more exact
  6. Do not use negative RCS values. More here:
  7. The MiGs data inis must have the RadarFamilyName= entry in the DetectSystem section. This name is referred to in the RWR .LST files for calling the threat symbol tga file. A missing entry in the data ini or .LST or a typo/different names result in no symbol shown. By default, the threat tga files go into the Flight folder. If they are put into a "RWR" subfolder, then the RWR .LST file need the correct path entered, e.g. "....=RWR/MiG-31.tga"
  8. Real aircraft: The range covered by the scale tape (the V 196 type HUD is an electro-mechanical unit) goes from 0 to 2000 feet. It is intended for low altitude navigation, approach and the air to ground mode. If the radar altitude is above 2000 feet the scale readout would be not visible anymore. We cant do that in SF, we have to make do with the scale being "stuck" at 2000 feet :( :)
  9. A note on lights/lamps/etc: While nice eye-catching details, they wont be like that on vehicles in a tactical/combat setting or operation. Every vehicle has covers (made of fabric, usually) for all the lamps/lights, the rearview mirrors are folded down or removed. These things are "wrong" from a tactical point of view on many of the SF-world GO's/vehicles.
  10. Hello Lex, yes, the latest release is up to date regarding the function of the HUD symbols/readouts. Altitude scale is limited to maximal 2000 feet and the "horizon" (the small center --- --- symbol) functions as a extended reference for the attitude reticle (aka pitch ladder). Crusader Mirage F1 Team
  11. Stary's "Tree mod" (+ a few extras) for Africa East (AE) terrain by Deuces (iirc)
  12. From last Saturday's (a week ago) virtual airshow, the part/interview with AERGES about the Spanish F1 for DCS
  13. https://www.checksix-fr.com/bibliotheque/index.php?page=detail&ID=4591 Main archive page on C6: https://www.checksix-fr.com/bibliotheque/index.php In "Categorie", select S. F. Project 1 or WOE/WOV In "Type": Avion / Cockpit / Texture etc.
  14. You came up short on proper armament huh
  15. Quoting the size-offending text a few times is kinda.. snowball-effect ya know
  16. AIM-9L series AIM-9L, 1978+ USAF and export, all-aspect seeker, still poor vs IR flares, SEAM-capable AIM-9L-1, 1978+ USN variant of 9L AIM-9L(EUR), ~1981+ Euro-Consortium produced 9L, wide NATO service AIM-9L/I, ~1988 (perhaps a bit earlier) EUR Improved IRCCM, several NATO users, final version for Lw AIM-9L/I-1, ~1993 (guessed, possibly later) EUR Improved again IRCCM, said to be the equivalent of US 9M-8/9 (1995), some NATO users (Italy) AIM-9JULI, ~1993 upgrade for SR116 motor 9J/N/P missiles which replaces the old GCU with the 9L/I GCU (JULI = Juliet(series) Upgrade to Lima Improved) Known users: Spain... AIM-9L Genetic, ~1984-86 (guessed) possibly UK IRCCM mod, similar to what they've done to their 9G SWIFT To be continued...
  17. Brrrrrrrrrrrrrrrrrt !!! With radar, range 2000 ft / 600 m
  18. Sparrow F / F / P, intentions... AIM-7F, 1976+ improved with new 2-stage motor and seeker. There were several sub-variants (perhaps optional SF mod) AIM-7M, 1982+ new monopulse-seeker variant AIM-7M-F1, ~1984+ further upgrades to the autopilot software / ECCM AIM-7M-H, 1987+ again software upgrade, better ECCM and other improvements AIM-7P, 1994, USN (later export, e.g. Spain) low-altitude and ECCM improvements AIM-7P-2, 1998, USN, last fielded version, low-altitude and ECCM improvements To be continued...
×
×
  • Create New...

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..