Jump to content

drPhibes

Members
  • Posts

    1054
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by drPhibes

  1. I'll have to tread lightly here due to the "no politics" policy on the forums, but anything that could refer to Taiwan as an independent nation is a no-go if you want to sell your product in a certain Asian country. There is a 21.000 line long list of words and phrases that are censored (presumably from the MP chat) in \DCS World\Data\censor.lua, many of which are related to Taiwan. TL;DR: don't hold your breath.
  2. Yep. The "chartOffsetX = xyz" parameter in beacons.lua simply moves the showm sector xyz meters along the axis of the radaited signal. The beacons are located in the correct location (and radiate in the correct direction).
  3. The short answer is no. The longer answer: Many/most runways with ILS in both directions are equipped with an interlock that prevents both systems from radiating at the same time. This is a requirement for CAT III (specified in ICAO Annex 10), and it is recommended for CAT I/II systems. If the ILS for both directions use the same frequency, the opposing beacons will interfere with each other, and cannot operate at the same time. The way the coverage sector of the Localizers shown in DCS is a bit misleading, as it indicates that the beacons radiate away from the runway (and thus the opposing beacons), but this is not the case IRL (see the pic below for an illustration). Simultaneous operation on the same frequency will cause erronious monitor readings on the opposing beacon, and the actual signal in space will be corrupted by the interference. /drPhibes Hardware engineer in the R&D dept. of the largest ILS manufacturer on the international market.
  4. Not really. TACAN is compatible with DME (TACAN is a DME system with the bearing waveform modulated onto the ranging pulses), but no part of a VOR is compatible with TACAN.
  5. It's also what ghosts do to you if you open the ark of the covenant, at least according to Lucas/Spielberg.
  6. 95 worked quite well (especially after the OSR2 service pack), but the first release of 98 was more of the "if it compiles, ship it" variety.
  7. A few of them: SU-22(or 17?): cancelled YF-23: cancelled Mitsubishi F-2: cancelled F-16: probably never really a project, just a few stolen renders with the author's signature/watermark removed F-84: cancelled KC-130T: cancelled TL;DR: don't get your hopes up.
  8. Don't hold your breath. His track record is not particularly good (to put it mildly). He has announced, and then cancelled, too many projects to count.
  9. I stand partially corrected. There seems to be intermittent coverage behind the localizer array at LCA. This shouldn't be the case. Back course approaches aren't a thing in this area of operations. The error reported by the OP is unrelated to this. The entry for the GP in the beacons.lua is rotated 88,955947° clockwise with regard to the LOC, and the 3d model of the M-array GP mast is also rotated approximately 90° CW: { display_name = _(''); beaconId = 'airfield47_0'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'ILC'; frequency = 110300000.000000; position = { -8990.810547, 7.217739, -210314.343750 }; direction = 48.171958; positionGeo = { latitude = 34.860647, longitude = 33.608001 }; sceneObjects = {'t:336825842'}; chartOffsetX = 3620.000000; }; { display_name = _(''); beaconId = 'airfield47_2'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'ILC'; frequency = 110300000.000000; position = { -6839.587402, 5.000005, -208096.250000 }; direction = 137.127905; positionGeo = { latitude = 34.881032, longitude = 33.630902 }; sceneObjects = {'t:750780863'}; };
  10. Feel free to believe whatever you like, but in this case you're wrong.
  11. Modern ILS systems do not have a usable back course signal, and back course approaches are not approved for operational use in many parts of the world, including the EU. The log-periodic antennas used by all major ILS manufacturers on the international market are highly directional, and have a front-to-back ratio of around 14dB. No usable signal radiates from the back of the antenna array.
  12. There is a leaked development version circulating online, but this is probably not the place to be discussing such things, as per rule 1.8...
  13. drPhibes

    Arctic Map

    Exactly! Case in point: the northernmost part of mainland Norway is approximately as far from the geographic north pole as Houston TX is form the Canadian Border.
  14. He believed that the submarine launched F-15 video was real... Perhaps google can find him a good optometrist?
  15. A new preview video popped up in my youtube notifications:
  16. This is probably the dumbest request since "Wah, people won't let me join as a RIO in their F14. I demand that Heatblur fix this..." a few years ago.
  17. Have you checked the wind settings in the mission editor?
  18. There's a bug in the active runway logic, so the ILS isn't synchronized with the active runway given by ATC at low wind speeds. Set up a headwind of ~7kts and see if that helps.
  19. What do you base that on? Out of the 17 IRIAF tactical airbases listed on wikipedia, 10 of them have ILS for at least one runway according to the Iranian AIP.
  20. There is no ILS at Lar IRL, so that's probably why it has been removed. See section 2.19: https://ais.airport.ir/documents/452631/63756645/OISL.PDF
  21. RCS is just a static value defined defined for each aircraft. AI values are defined in \DCS World\Scripts\Database\PlaneConst.lua / HelicopterConst.lua, and playable module values are typically defined in the \CoreMods\aircraft\[module_name]\[module_name].lua (e.g. \CoreMods\aircraft\FA-18C\FA-18C.lua).
  22. You obviously didn't scroll down to the end of the article...
  23. You're absolutely right. I didn't know about that one. https://www.google.com/maps/@35.1539127,33.2654197,192m/data=!3m1!1e3
  24. The rest of the map is set in a relatively recent era, so a pre-1974 version of Nicosia airport doesn't make much sense. Shackleton? Are you sure you're noe thinking of the two at Paphos?
×
×
  • Create New...