western_JPN

By today's 2.9.8 .1107 update patch, Akrotiri can handle historical A330 MRTT (KC-30A) or A330-200 spec aircraft (58.82 m Length X 60.3 m Wingspan) ramp-starting and taxing. Slots 01-02, A1-A4, B1-B2, E1, E3, F5, F6 are allowed in Mission Editor. Aleppo's slot 15 is also (and only) available for historical A330 MRTT size, today. Other airbases / airports still don't allow A330 MRTT ; Incirlik , Damascus , Beirut , Larnaca , Paphos --- No. With historical A330-300 variant spec (63.67 m Length X 60.3 m Wingspan) , ME says "No free airport" even in the latest patch. When you want to use Civil Aircraft Mod's A330 (-300) on Syria map, you have to decrease A_330.lua's length value to 58.82 .

By today's update patch 2.9.8 .1107 , Syria map becomes to have B-52H and Tu-160's "spawn-and-taxi" abilities about Akrotiri, Aleppo, Marka. (Marka was renamed from Amman in the terrain module.) Those changes are welcome. I don't know they are all of this terrain area airports / airbases with the ability in historical? Incirlik or Damascus and ....

I finished mine. New Syria map in ME.

Thanks again, Minsky. Sharing your paintkit enables me to add A330 liveries --- I need some more days to publish those works. --- published on 06/Oct./2024 : https://www.digitalcombatsimulator.com/en/files/3340910/

Not only CH-47F ---- AH-64D + UH-1H + Mi-8 and Mi-24P cannot ramp start, too. Only possible by SA342 and OH-58D from current flyable halos. How about merging slots 05 and 06 into one big slot and also 07 and 08 into one for flyable helicopters ?

ED's An-26 Russian military transport is almost in same size and shape to DHC-8 Q300 or Fokker F27. (ATR 42 is also similar size besides different main gears' structure.) When someone will make and publish a skin template of An-26, we will be able to draw its fake skins of DHC-8 / Fokker F27 / ATR operators.

Hi, OnReTech. I cannot reproduce the reported thing on Ben-Gurion by my own missions. KC-135, KC-135MPRS, KC-130, S-3 Tanker and IL-78 spawn there normally and begin to engine startup, taxi and takeoff OK. It looks no bug to track.

I don't find such problem on Sharm El Sheikh. In placing aircrafts there by Mission Editor, F-15E or F-16CM can be placed on all 45 parking slots. Yak-40 is available 06-21, 34-45. C-130 can be set except 01-05 / 10-13 / 22-33. C-17 / KC-135 / E-3 are available 06-09, 14-21, 34-38.

Hi, prccowboy. Both E-7a and P-8's nose wheel rotating direction look inverted. It's hard to find , only watched by very low taxing speed.

ah ... I misunderstood which runway was referred. Beirut's RW 17 doesn't equip approach lights in historical. There lighting is not bug. For better solution by Ugra Media, reworking about Tower AI setup not to use RW 17 for landing.

Umm ... In my testing, Beirut's all three runways' lights are all night kept ON. Some turning OFF situation may exist I don't know ?

Creech Air Force Base's Runway Threshold lights of RW 13 are placed in wrong direction. Green lights should face to runway's outside, Red lights should face to runway's inside. Current their directions are 90 deg. rotated.

Ben-Gurion's Runway Lights turning On/Off logic at night is bugged about RW 08,12,26,30. Tested in version 2.9.7 .59074 released on 14/Aug/2024. (RW 03 and 21 are correct). Same behaviors about both Take-off or Landing cases. Activated RW xx | Lights On RW yy 08 | 30 12 | 26 26 | 12 30 | 08 Test missions' archive is also attached below. yak40_aiTOnight_bengurion20240912.zip

Hi. In my research of DCS contents, your experience might come from the bug of C-101 instead of Syria map. C-101's basic spec data is written in DCS/CoreMods/aircraft/C-101/C-101.lua file. In that file, wing span entry looks confused. It has these two lines --- wing_span = 14, WingSpan = 10.60, DCS uses the entry "wing_span" to decide parking ramp availability, not "WingSpan". So, this entry brings that C-101 needs 14 meters width for airbase ramps and taxiways. (F-16C is 9.45 meters, F/A-18C is 11.43 meters in example ... ) When AvioDev will change wing_span value into 10.60 , Syria's H4 base will be available for C-101 without Syria terrain's editing.

I post a new topic about Ben-Gurion ILS not working bug here --- There I share F-16C test missions ATC activates 5x different runways with wind blowing settings. RW 08 and 21's ILS are working. When the mission has no wind blowing, RW 21 is activated and ILS will be working. RW 12 / 26 / 30's ILS are not working in my tests.

I post another topic about ILS working or not about Ben-Gurion. See here --- F-16C test missions with wind directions' settings to activate a specific runway are packed and attached there. You can use ILS about RW 08 and 21 in current DCS version.

I fly F-16C to land Ben-Gurion with ILS for each runways activated with wind direction settings. Test missions are packed and attached. Mission names show "Wind blows to" directions in DCS-ME-Weather menu; alternative to runway numbers. Ben-Gurion equips ILS for five runway directions 08 / 12 / 21 / 26 / 30. RW 08 and 21's ILS are working. (RW 21 is no-wind default) Other RW 12 / 26 / 30 are not , even ATC answers those runways are active by radio messages to me. f16c_ils_bengurion_20240825.zip

How about increasing "LOD Switch Factor" value from default 1.0 to more like 1.5 / 1.8 / 2.0 in System Options ?

My own missions enable me F-16CM ILS at Bodø by both runways 07 / 25. Bodø RW 25's Localizer is offset 10 or 11 degrees to the right. We have to turn 10 degrees left in final approach time. f16c_land_BodoILS07_kola_20240811.miz f16c_land_BodoILS25_kola_20240811.miz

Ouch ! Should I delete this topic to avoid confusion ?

In 2.9.7 .59074 update patch published on 14th/Aug./2024 , some ILS locations are not centered to the runways. Some of them are already reported in Sinai's 1st release time and not changed yet, I post the current summary here. I don't talk about frequency or vector. Only about location in this topic. Ben-Gurion , RW 08 --- too Left Move 15 meters to the south. Ben-Gurion , RW 21 --- too Right Move 15 meters to the east. Ben-Gurion , RW 30 --- too Left Move 36 meters to the east. Cairo International , RW 05 L --- too Right Move 12 meters to the north. Cairo International , RW 23 R -- too Left Move 21 meters to the west. Hatzor , RW 05 --- too Left Move 31 meters to the east. Yellow blast pad markings are also misaligned to the left from the runway center. Nevatim , RW 25 --- too Left Move 8 meters to the north. Tel-Nof , RW 36 --- too Right Move 10 meters to the west.

Same thing reported by this topic and fixed by today's 2.9.7 .59074 ?

Fixed in today's 2.9.7 .59074 OK ? Thanks OnReTech.

I'm told by Updater "Your 1TB SSD has only 112GB free space less than today's 170GB needed". I'll retry updating after temporary uninstalling Kola map.

I think the contents of today's newsletter will depend on the patch released or postponed. When the patch will succeed to be released, the newsletter will say "Chinook is now on stage!". But no ---- some apologizes or other wip reports will be written instead.