western_JPN

My experience and guessing. Current (First release) QAG doesn't support any mod airplanes as not only for Player but also enemy / friendly AI ones even ERA = "All" and Country = "Joint Task Forces XXX". Perhaps that's planned feature. Btw mod vehicles or mod ships can appear as enemy targets.

When SCENARIO's ERA is set "Cold War 1971-1991" , F-15E S4+ and F-4E-45MC become missed from AIRCRAFT list. "All" ERA setting is needed to use them. This behavior looks similar to Mission Editor's Historical Filter function.

Start from the ground is not suitable for "Dogfight" or "BVR" missions, I see. How about "Bomber Intercept" ? No CAP air forces scramble to coming enemy bombers from HAS near the runway end.

My CWG ground attack mission by F-16CM progresses 95% ... (and stuck ) Last 6 lines of dcs.log is here --- 2025-05-22 01:49:21.065 INFO TERRAIN (Main): lSystem::InitScenes() 2025-05-22 01:49:21.065 INFO EDTERRAIN4 (Main): ITerrainContextImpl4::setTrafficDecimation(0) 2025-05-22 01:49:21.066 INFO EDTERRAIN4 (Main): ITerrainContextImpl4::setDate( day=22, month=6) 2025-05-22 01:49:21.066 INFO EDTERRAIN4 (Main): ITerrainContextImpl4::setTextureMode(full=1) 2025-05-22 01:49:21.068 INFO Dispatcher (Main): load terrain done 2025-05-22 01:58:58.225 ERROR GRAPHICSVISTA (Main): Can't open model shrubforest.

Hi. An Essex generic scb125's livery "CV-9 USS ESSEX" folder isn't updated from 0.4.1 time. and other four ships' liveries folders (CV-14, 16, 19, 34) have each dds files but not loaded by each description.lua files. I don't know these description.lua contents (only one line "cv31_ship_registry_number" is written) are correct as planned or not. When correct one, other unloaded CV-XX Clean.dds, CV-XX OUTLINE.dds and island_signs BLACK 2.dds files are needless to be placed --- better to remove. If those one line description.lua are temporary file and planned as drawing different deck lines or tones in the future, I think better to write loading those dds files in description.lua by false flags.

From Su-25T manual

https://en.wikipedia.org/wiki/Richtfunkstelle_Berlin-Frohnau https://en.wikipedia.org/wiki/Gartow-Höhbeck_transmitter https://de.wikipedia.org/wiki/Sender_Torfhaus

Even Gazelle, maximum weight SA 342M (with 4x HOT and 99 percent fuel) and no wind weather --- starting on slot 26 leads crashing into the terminal building. Slot 25 has a safety takeoff route once south - east - turn to north, but Slot 26 wants to go straight to the north. sa342m_aiTO_templhof_cwger_20250513.miz

Factory built F-4EJ until 1981 didn't have bombing computers. JASDF decided to modernize F-4EJ into F-4EJ Kai from 1982 and total 90x F-4EJs were converted to -EJ Kai until 1993. F-4EJ Kai got a new FCS with bombing calculator, HUD, HOTAS throttle grip, AGP66J with AIM-7F illuminator, new RWR, new IFF etc. So F-4EJ Kai had bombing capability , and photos with Mk82 training bombs were taken in 1990s-.

Those grass area is historically correct. After 1955 reopen or 1967 paved runway opening, Braunschweig has been used for only general aviation or air sports, never for military. The grass slots are used by gliders or light weight single props. In DCS flyable, Christen Eagle II maybe able to use those slots. Yak-52 and WWII single props are also perhaps ?

I don't know what graphics editor application jack333 is using or each texture files' internal formats (and their three letters filename extensions) ... How about Color Space mismatching trouble ? When BMP or PNG is chosen as exporting graphics format, results may be changed in keeping or discarding Color Space information. TGA or DDS (DCS's default format) might not have Color Space information and no difference after exported by applications.

Hi. Your log shows that Windows' Pagefile is only 9064 MB. When main RAM is 64GB, Pagefile may need at least 32768 MB (or 65536 MB when possible) for DCS.

reported here as a terrain mesh bug ?

I've reproduced it. Not only C-130, perhaps all AI airplanes (I test C-130 and F-16CM) may crash into the mountain on 69-56'33"N / 23-31'55"E / 458 meters altitude in straight approaching Alta RW 29. This terrain mesh is correct in comparing with Google Earth , and Norway official chart warns this mountain as obstacles around Alta. Straight-In RW 29 maybe impossible, circling approach is needed. Map module side AI flight route (or rule) tweaking is needed ?

already reported here ---