Jump to content

drPhibes

Members
  • Posts

    1057
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by drPhibes

  1. Bad example, since the AKPWS has more aerodynamic drag than a regular Hydra...
  2. The "chartOffsetX =" parameter moves the ILS coverage sector illustration so that the sectors for opposite runway ends don't overlap. It makes things a bit tidier in the F10 map / ME, but it doesn't affect the simulated signals in any way. Note that it's only really relevant for the localizer, since the GP coverage sector isn't shown.
  3. Then the answer is simple: you can't. Every time you update DCS it'll be re-downloaded.
  4. Here's a small behind the scenes peek into how I make new beacons. I made a spreadsheet which simplifies the process a lot, so it basically boils down to a bit of Google Earth and mission editor work: 1. Find an airport that should have ILS, but doesn't in DCS. For the PG map this is quite easy since I have been involved in ILS deliveries to most of the airports in question. An other method is to just check the AIPs for the airports (which is needed anyways, in order to get the correct frequncy and ident, unless you have this info from other sources). 2. Google earth surveying: I find the location of the localizer (LOC) and glide path (GP) antennas and reference their position to the thresholds and centerline of the runway. Google earth coordinates aren't necessarily 1:1 with DCS, so this is the best way I have found of semi-accurately placing the beacons. The positions are noted in collumn B and D in the spreadsheet. 3. I check AIP AD 2.19 to find the LOC frequency and IDs of the navaids. DCS handles the LOC/GP frequency pairing, so there's no need to check the GP freq. in Annex 10. The results are noted in collumn F/G. 4. Collumn H is just a note of where the GP is located in relation to the runway. 5. Collumn I-O: DCS mission editor surveying. I find the points specified in col. B/D in the mission editor, and note down the coordinates in both X/Y metric (I/J) and decimal degrees (L/M), and the elevation in meters (K). N is the runway heading in degrees, referenced to true north, and it ranges from -180° to +180°. So N, E, S and W would be 0, 90, 180, -90. The reason why there are both metric X/Y and lat/lon coordinates is that one defines the placement of the navaid, and one defines the placement of the mission editor/F10 map symbology. Collumn O defines an offset in the localizer coverage symbology, so that it emanates from the opposite runway end. 6. Beacon ID (col. P) is taken from the beacons.lua entries for the airport in question. If no navaids exist at the airport, just chose the next available number. Beacon number (col. Q) is the next available beacon number for the given beacon ID. DisplayName is just used in the LUA to keep stuff organized. When I finish filling out these various parameters, I go on to sheet 2 of the spreadsheet, where I generate the lua code using 'concat', pre-defined strings and the values from sheet 1:
  5. Move the contents of the \DCS World\Mods\terrains\Caucasus\ folder to somewhere else, and create a symlink to the new location.
  6. AFAIK DCS world is written in C++, not C#.
  7. Unfortunately I haven't kept this mod up to date, so it may not represent the current status of the PG map that well. I have been tinkering a bit with it, adding regular ILS to a few airfields which ED has omitted; Ras Al Kaimah and/or Al Ain(can't remember which one, if not both), and Al Bateen. Al Bateen is a bit of an odd case since ED has added the 3d model for the localizer array, but the placement is wrong (rotated 180°), and no entry for the airport is present in the beacon file. It seems a bit half baked ATM. Eventually I'll update the public mod with these changes (and new ICLS beacons where needed), and then go on to the Syria map.
  8. Works fine here: Check your wind settings. You need a headwind of approximately 7kts for the faulty runway direction logic (core DCS feature, not map related) to switch the ILS over from 05 to 23.
  9. Two north of Damascus (near the presidential palace): 33° 29' 59.66"N 36° 12' 49.07"E 33° 30' 34.08"N 36° 13' 42.39"E Post it on google docs instead of the user files. That makes it a lot easier to maintain and keep up to date.
  10. \DCS World\Mods\aircraft\Flaming Cliffs\Missions\Single\Su-27 - Syria - Unwanted Guest.miz
  11. Generally, you'll never see ILS operational on two opposing runway directions at the same time. For all CAT II/III systems, an interlock preventing this is mandatory (ICAO Annex 10, 3.1.2.7), and it is recommended for CAT I. The wind speed threshold for switching runway directions in DCS is somewhere around 5-7 kts IIRC.
  12. Check your wind settings in the mission editor. Try a headwind of 7-10 kts .
  13. ED should definitely include more SMBs, subject matter believers, in their team....
  14. Updates are usually launched afternoon-ish CET, so probably in 5-7 hours.
  15. Al Kibar is 80km east of Raqqa. And it doesn't really matter if it's outside the high detail area as long as we can place static buildings wherever we want to.
  16. I personally don't care that much about Cyprus, but it's nice to see that the map extends far enough to the east to include the location of the DPRK-built reactor at Al Kibar (35° 42.467'N 39° 50.008'E).
  17. The large grain silo next to the warehouse that exploded is visible at 18:56-19:06 in Wags' Bekaa valley video.
  18. Just paste f0LOzujZPZc inside the [ youtube] tags, not the complete URL.
  19. Yep. Nobody other than the RAF and USAF has managed to kill as many Luftwaffe pilots as the F-104.
  20. There are two heliports near Marj al-Sultan. With Deir Salman being the neighbouring village to the south-east, the heliport to the south-east of MaS might be the one. But that's more of an educated guess than anything else. 33°29'14.12"N 36°28'29.83"E
  21. My guess would be that it's a terrain engine limitation. Sea seems to cover the entire map, with terrain placed over it (seen frequently when loading MP missions).
  22. drPhibes

    Nukes

    15 and 21 kiloton bombs leveled Hiroshima and Nagasaki. A test (Halfbeak) of the an early B61 warhead in 1966 had an estimated yield of over 350 kilotons.
  23. And regarding the OP's suggestion: unless high G straining can be measured in blood alcohol content, a brethalyzer is the wrong tool. Tight pants covered with strain gauges will do a much better job.
  24. That sounds like an excuse I'd use if someone asked me to help out with beach balls, ballons and whatnot.
×
×
  • Create New...