

drPhibes
Members-
Posts
1161 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by drPhibes
-
A few tips: * Extend the airbrake. This gives you much finer control of your speed, so it's easier to stay connected to the tanker. * When approacing the tanker, use the radar in gun-mode (master arm off) for accurate distance and approach speed info in the HUD. * Practice. A lot!
-
It's still there, but it's only available if you set the country to Spain. Open the description.lua in \DCS World\CoreMods\aircraft\Yak-52\Liveries\Yak-52\Pobeda\ and change the "countries"-line to -- countries = {"SPN"} to make it available for all countries. -- is the lua syntax for commenting out a line.
-
-
Actually, the way the AWLS is implemented in the sim is based on regular ILS and not ICLS. The channels are defined in \DCS World\Mods\aircraft\AV8BNA\Cockpit\Scripts\RadioNav\AN_ARN128_config.lua Using ICLS channels would be the correct way of doing things, but this option was probably not available when the Harrier was released.
-
There is no TACAN at Kerman, only VOR+DME. 57 is the DME channel.
-
TL;DR. No. https://forums.eagle.ru/showthread.php?t=204693&page=2
-
The fix was included in yesterday's update, so my mod described earlier is no longer necessary. https://forums.eagle.ru/showthread.php?t=217594
-
ILS for Kutaisi RWY 26 added, and the frequency for 08 is corrected (Edit: oops. A small typo. It should be 110.1, not .7).
-
It's on my to-do list. Currently my plans are: 1. Add the missing ILS at Kutaisi RWY 25 (26 in the game) 2. Add ICLS to all runways with regular ILS 3. Maybe add ILS+ICLS to all PRMG runways in the Russian part of the map.
-
Fixed internally (as the thread topic says), but it is easily fixable right now for impatient people who don't mind messing around with the HUD lua files (needless to say, this is not compatible with the integrity check, so save a backup of your file): In \DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\Pages\HUD_common.lua scroll down to line 384-387 to find the horizontal and vertical bar info. addPlaceholder("ILS_Vert_Root" and (...)"ILS_Hor_Root" define the starting coordinate of the lines ("51"), and addStrokeLine("ILS_Vert" and (...)("ILS_Hor" etc define the length of the lines (102). Multiplying all instances of 51 and 102 with 2 gives lines twice as long, in the correct position.
-
If the NATOPS manual illustrations are to scale, the ICLS steering bars should be 1.25x the width of the velocity vector and 0,66x the width of the pitch ladder:
-
-
Thanks for the feedback. Everything looks OK here, with the only visible change in the mission editor being the added TACANs at the GP sites: Original beacons.lua: Mod:
-
In case anyone missed it, my complete(-ish) beaon mod for the PG map is available here: https://forums.eagle.ru/showthread.php?t=217594
-
You're right. In-game, .75 is rounded up to .80, while the ME shows the correct frequency. Disregard my previous post.
-
-
I have made a mod for the Persian Gulf map, with ICLS beacons for all runways equipped with regular ILS, TACANS co-located with all GP(GS) beacons for DME distance to the touchdown point, and with all VORs converted to VORTACs. So now you can practice your low visibility landings in the F/A-18C. https://github.com/adler357/DCS-PG Feel free to report any errors in this thread.
-
Reducing the Y-axis saturation to around 50% for the TDC axis controls usually helps a lot.
-
Ok, first you'll have to fire up your favorite text editor (Notepad++ in my case), and find the beacons.lua for the terrain where you want to add the beacon. The file are located in \DCS World\Mods\terrains\[terrain name] Note: this procedure only works when adding ICLS beacons to runways which already have regular ILS. If doing it from scratch, you'll need to find all coordinates etc. manually. Find the airport where you want to add the beacon (in my case, Bandar Abbas). Make a note of the beacon ID (Bandar Abbas: beaconId = 'airfield2_[x]'), and scroll down to the two ILS beacons. { display_name = _(''); beaconId = 'airfield2_2'; type = BEACON_TYPE_ILS_LOCALIZER; callsign = 'IBND'; frequency = 109900000.000000; position = { 113693.234375, 5.776140, 13155.006836 }; direction = 28.001016; positionGeo = { latitude = 27.198926, longitude = 56.367930 }; sceneObjects = {'t:197885952'}; chartOffsetX = 4544.000000; }; { display_name = _(''); beaconId = 'airfield2_3'; type = BEACON_TYPE_ILS_GLIDESLOPE; callsign = 'IBND'; frequency = 109900000.000000; position = { 116974.781250, 5.880138, 14981.854492 }; direction = 26.337865; positionGeo = { latitude = 27.228633, longitude = 56.386212 }; sceneObjects = {'t:-1265303495'}; }; Copy the text (to a new file, or just insert it after the last beacon for the selected airport), and increment the minor number of the beaconIDs to the next available numbers. For Bandar Abbas that would be beaconId = 'airfield2_4'; (LOC) and 5 (GS). Replace the "ILS" in the beacon type with "ICLS": type = BEACON_TYPE_ICLS_LOCALIZER; and type = BEACON_TYPE_ICLS_GLIDESLOPE;Frequncies/channels: Find a channel/frequency from the list below, and replace the old ILS frequency with the new ICLS freq. The same frequency is used for both LOC and GS. Add a line below the frequency with the corresponding channel number. Channel: Frequency: 1 15415000000 2 15445000000 3 15475000000 4 15505000000 5 15535000000 6 15565000000 7 15595000000 8 15625000000 9 15655000000 10 15685000000 11 15415000000 12 15445000000 13 15475000000 14 15505000000 15 15535000000 16 15565000000 17 15595000000 18 15625000000 19 15655000000 20 15685000000 or just run the following through your favorite lua interpreter: for channel =1, 20, 1 do x= 15415000000 + 30000000 * ((channel - 1) % 10) print(channel, '\t', x, '\n') end For those who prefer to copy and paste, here is my test setup (with all changes from default in bold): -- ICLS test: { display_name = _(''); beaconId = 'airfield2_[b]4[/b]'; type = BEACON_TYPE_I[b]C[/b]LS_LOCALIZER; callsign = '[b]TST[/b]'; frequency = [b]15415000000[/b].000000; [b]channel = 1;[/b] position = { 113693.234375, 5.776140, 13155.006836 }; direction = 28.001016; positionGeo = { latitude = 27.198926, longitude = 56.367930 }; sceneObjects = {'t:197885952'}; chartOffsetX = 4544.000000; }; { display_name = _(''); beaconId = 'airfield2_[b]5[/b]'; type = BEACON_TYPE_I[b]C[/b]LS_GLIDESLOPE; callsign = '[b]TST[/b]'; frequency = [b]15415000000[/b].000000; [b]channel = 1;[/b] position = { 116974.781250, 5.880138, 14981.854492 }; direction = 26.337865; positionGeo = { latitude = 27.228633, longitude = 56.386212 }; sceneObjects = {'t:-1265303495'}; }; -- end of test Note: I have only tested channel 1 at Bandar Abbas so far. YMMV. Make sure you set the wind direction in the ME so that the ICLS equipped runway is active.
-
Adding ground based ICLS beacons is easy (as demonstrated below), so I see no reason why ED wouldn't do that after more inportant features are added. If anyone is interested, I can post a short "how to"-guide (NOTE: Not IC compatible).
-
Fairchild Dornier (the successor of Fairchild Republic) went bankrupt many years before DCS existed, so that sounds unlikely.
-
There is no such feature in the F/A-18C (and according to the NATOPS manual, the same goes for the 18E). The phosphor screen that the HUD symbology is projected from is monochromatic (single color). Different shades of green in raster scan mode (when displaying FLIR on the HUD) are generated by varying the intensity of the electron beam in the CRT.
-
Probably for the same reason why you can't control your dishwasher with the TV remote. Unless the RWR is part of a highly integrated avionics suite, there is no way for it to know where the control surfaces are pointing.
-
While the cockpit labels say ILS, only the ICLS is available in this specific model of the F/A-18C. So when this functionality is added, you still won't be able to tune it to civilian ILS frequencies. Hopefully ED will add land-based ICLS beacons (like they did with the TILS for the AJS37) when the Hornet is ready for it.