All Activity

How? There's no mouse interaction. The cursor doesn't change to green.

hello. you both should start your own topic in case your issue causes are different. post you DCS.LOG in the new topic.

Das kann ich dort auch nicht herauslesen. In einem Discord war tatsächlich ein Bekannter betroffen, der hat aber nicht dazugesagt, welches Windows er nutzt. In seinem Fall schien ein Reboot zu helfen, immerhin.

It would be nice if the Mission Editor showed a waypoint list for the selected route in whatever grid format you choose. This would allow easy sharing of exact routing between different airframes in multiplayer. I haven't seen a way to do this without hovering over each waypoint and copying the grid down in the mission editor, unless I'm missing something.

Was für ein Display!

Насчёт F/A-18 не знаю, но что вы называете таким "долгим" сроком? CVN-71 в 2002-м провел 160 дней подряд в походе, например. Воздействие агрессивной среды, самолеты не прямиком с конвейера туда попадают, опять же.

Well, I did some testing just now and woo I've taken @RealDCSpilot advice and installed the latest DLSS and set it to Performance and Preset K. Sharpening I guessed at 0.2, I haven't played with it yet so I don't know what image/performance compromise will be needed. I've upped the SuperSampling in Steam to 130% (from 100) which I reckon is quite a big leap! The Image Quality is fantastic! Hard to quantify, of course, but as an example I can now read the smudged and faded cockpit labels in the F-14B without moving my head. I used to have to lean forward and get close in. The countryside looks amazing and it still rips past smoothly. My first impression as I loaded in was "Wow, that's much better". Framerates have dropped back, as you'd expect, but I'm genuinely holding >50 FPS everywhere, even when taxiing at Ramat David. The range seems very small, which I wasn't expecting. I don't see over 60FPS in my test mission but it is always smooth and that's all I need. I did try 150% SS to start with and found that the FPS dropped to unacceptably choppy levels if I went very low over Lake Gallilee - possibly because I have water at Medium against all advice. Moire effects are improved too, even the fences at Ramat hardly shimmer now when before they were an horrible mess. Anyway, that was my test mission Cat vs Eagle instant action in Syria. I'll see how MP holds up but I'm hoping it will be OK as I've got a decent CPU and I'm now mainly GPU limited. I'm sure there will be more tweaking to come but I think I have a very solid baseline with much nicer visuals. @JMW I tried to reproduce the glitch you described but I couldn't. The brightness appeared uniform, even when I ducked into the cockpit and squinted at the sky out of the corner of my eye (without moving my eyes, of course). So I can't help you there, sorry. @mbucchia You are a legend amongst VR enthusiasts! Thank you so much for your work. Specs for reference. CPU: 9800X3D - Stock Clocks / AIO cooler GPU: Asus 4080 (vanilla, no overclock) MEM: 64Gb @ 6000MT/s Storage: PCIe Gen 4 2Tb WD_Black SN850 (PS5 version!) for DCS, 1Tb Samsung 980PRO for Windows. MOBO: ASRock X870E Nova WiFi (hoping it doesn't pop my CPU!!)

Hi, I like the Kola map a lot, but noticed that villages and small towns are mainly concentrated around airports. We can see the names of all towns/villages throughout the map in the mission editor, but most of them are not (yet) represented on the map. I understand that it's a big ask to have all of them represented, but will there be some more added in the near future? It would certainly fill the large voids we sometimes come across when flying on the map (where there should be some villages IRL), which I personally find its biggest shortcoming. Thanks!

Feature Overview StrikeFire lets mission editors and GCI/JTAC controllers use F10 map markers to task friendly launchers to strike nearby enemy ground/static targets. The system assigns one round per target, enforces true range envelopes per missile family, and throttles engagements to prevent AI lockups. It also provides quick spawn presets for H-/K- at the marker position, plus a one-shot CLEAN command to remove all units created by this script. Image Tutorial : Step 1: On the F10 map, place a marker anywhere and enter [H-BRG]. (Please ensure the distance between the launcher and the target is within 8–160 nautical miles.) nullStep 2: Place a [FIRE] marker near the enemy target you intend to strike. Step 3: Enjoy! Key Features Type [FIRE] (or plain FIRE) in a marker and the script will scan within SEARCH_RADIUS (default 3000 m) and auto-assign shooters. One round per target with de-duplication so clustered units aren’t counted multiple times. Hard range checks: GMLRS 8–160 nm; ATACMS 8–160 nm; 9K720 40–215 nm. Spawner: H-/K- presets; each launcher is its own group (can fire simultaneously); supply trucks are merged into a single group. Type CLEAN in a marker to delete all units created by this script. Installation In Triggers → MISSION START → DO SCRIPT FILE, load StrikeFire.lua (or use DO SCRIPT and paste the source). No dependencies. Works on Dedicated Server. Marker Commands (F10 Map) [FIRE] (brackets optional; FIRE also accepted) Coalition inherits the marker creator (Blue/Red). The script treats the marker owner as friendly and fires on enemy. Scans for enemy Ground + Static within SEARCH_RADIUS meters of the marker. Allocates 1 round per target using the nearest launcher that is in range and has remaining budget. Temporarily sets ROE to Open Fire, then restores it shortly after. The marker is auto-removed when processing is done. Spawner keys (place in marker content) H-BLK, H-SEAD, H-DS, H-QRF, H-BRG → HIMARS presets. K-HE, K-CL, K-MIX, K-DS, K-BRG → 9K720 (Iskander) presets. Legacy aliases also supported: HIMARS-BLOCK, HIMARS-SEAD, HIMARS-STRIKE, HIMARS-QRF, HIMARS-BARRAGE, ISK-*, 9K-*. Spawns at the marker point; each launcher is its own group; supply trucks merged. The marker is cleaned after spawning. CLEAN Removes all units created by this script. Quick Reference (Tuning) Adjustable parameters near the top of the file: ------------------------------------------------------------ -- Configurable Parameters ------------------------------------------------------------ local SEARCH_RADIUS = 3000 -- meters (search radius around marker) local FIRE_RADIUS = 120 -- FireAtPoint dispersion (m) local MAX_BATTERY = 24 -- max launchers that can be tasked at once local DEBUG = false -- debug output & temporary markers ------------------------------------------------------------ -- Weapon Ranges (nautical miles) ------------------------------------------------------------ local RANGES_NM = { HIMARS_GMLRS = { min = 8, max = 160 }, HIMARS_ATACMS = { min = 8, max = 160 }, ISK = { min = 40, max = 215 }, } ------------------------------------------------------------ -- Ammo Budget (per-vehicle effective cap) ------------------------------------------------------------ local TARGET_BUDGET_PER_FAMILY = { HIMARS_GMLRS = 6, -- per-vehicle target budget HIMARS_ATACMS = 1, ISK = 2, } Usage Tips Ensure each launcher sits within its family’s range; otherwise the target may be skipped. The script de-duplicates nearby units; if you want looser clustering, increase DEDUP_EPS. Keep one launcher per group so multiple vehicles can fire simultaneously. The script briefly sets ROE to Open Fire and then restores it; adjust the delay with RESTORE_ROE_SEC. Troubleshooting No shots fired? Check: The marker’s coalition (Blue markers direct Blue launchers to attack Red, and vice versa). The target is within the marker’s SEARCH_RADIUS, and at least one launcher is in range. Ammunition isn’t exhausted (per vehicle: GMLRS 6, ATACMS 1, ISK 2). License & Credits Free for use in missions and servers. Please credit “StrikeFire — Remote Ground Strike.” Strike Fire V1.lua

The Misters says it is too early to say at the moment.I think maybe the Dymnatic campaign,mig29,AAQ33 sniper pod,F18 MSI...etc maybe have a higher pority...But Fat Amy can bring a HUGE new player to DCS. The Misters says it is too early to say at the moment.I think maybe the Dymnatic campaign,mig29,AAQ33 sniper pod,F18 MSI...etc maybe have a higher pority...But Fat Amy can bring a HUGE new player to DCS.

Ok i've just checked again, sorry it's a week later than I said. But it's still respawning without tasks when using late activation. I'm just using a basic MIST respawn script that I've used for other missions over the years, anyway here's what I have tried: if not Group.getByName('GroupName') then mist.respawnGroup('GroupName', true) and: if (Group.getByName('GroupName') and #Group.getByName('GroupName'):getUnits() < 1) or not Group.getByName('GroupName') then mist.scheduleFunction(mist.respawnGroup,{'GroupName', true}, timer.getTime() +1) and finally: if mist.groupIsDead('GroupName') == true or (Group.getByName('GroupName') and #Group.getByName('GroupName'):getUnits() < 1) then mist.scheduleFunction(mist.respawnGroup,{'GroupName', true}, timer.getTime() +1) I know all of those pretty much are just minor variations on the same respawn script but I figured I may as well try as many different once I can find via the forums just in case something has changed in the last year or so.

Okay thanks for the heads up. Will the engine management card in cockpit be updated to reflect the actual engine type in the module anytime soon?

If A2G is your thing I'd say the Viggen might be worth your while. It's older with less complexity and no MFDs, which means no learning endless MFD pages. It was my first FF module, and I really liked that everything was based around low, fast flight, so my entire experience was refining that one way of flying. I really got a buzz out of going supersonic so low I had to *gain* altitude before releasing AIR bombing. It also took most of the difficulty out of target spotting, it's a lot easier at low altitude.

Ich habe das entsprechende Update auf meinem Rechner mit Win11.

Может через 20 лет антикор против соли лучше стал. МиГ мог применять Э и без прошивки, она меняет только расчет зоны ПР, СУВ без неё считает что ЭР это Р.

Ich glaube hier liegt ein Missverständniss vor. Die Zahl VOR dem Schrägstrich zeigt nicht den Alignment-Status an, sondern ist lediglich ein Timer der die Zeit mitzählt. Steht da 2.6, heißt das nur, dass das Alignment seit 2,6 Minuten läuft. Über den Status sagt das aber nichts aus. Der eigentliche Alignment-Status steht hinter dem Schrägstrich und erst wenn dieser auf 10 heruntergezählt hat ist das Alignment durch und RDY blinkt.

Hi, Fist of all, thanks for these nice additions to the default map. Is it possible to have an idea of the future locations that will be added? That's in order to avoid duplicating efforts, since as you can see in user files, all the member's static templates try to recreated similar layouts with existing static objects. Also, there' a discrepancy between real name and what what's on the game map for COP Deysie that appears as FOB Daysie in game (it's actually a COP as announced and there's a spelling mistake). Thank you

Лётчики американской палубной авиации использовавшие F-18 на такой долгий срок в походы не ходили, конечно же.

Hello @Talisman_VR . How's it going so far? You liking it still?

No, I totally agree. I was just wondering how X-29T and other TV would work

Hello, I found a strange bug: Since the last DCS update Japanese WWII ground units (and only those) disappear after destruction. Dead static objects of the same ground unit types placed on a map are not visible after loading the mission. Track file of a demonstration mission is attached (Combined Arms is needed), a short (cutted) video can be found here: To be sure it isn't an impact by some mod or script I did a cleanup and a repair with "check all files" and "search for files after repair" and started DCS with a virgin Saved Games folder. In dcs.log appear the following lines: 2025-08-18 16:55:04.018 ERROR TRANSPORT (Main): ShapeTable shape not found TYPE_89_I_GO_DESTROYED 2025-08-18 16:55:04.020 ERROR TRANSPORT (Main): ShapeTable shape not found TYPE_98_KE_NI_DESTROYED 2025-08-18 16:55:04.022 ERROR TRANSPORT (Main): ShapeTable shape not found TYPE_94_TRUCK_DESTROYED Japanes units disappear after destruction.trk

Welches OS betrifft das denn? Windows 10? Windows 11? Beide? Aus dem Artikel geht das leider nicht hervor...

I already did all these things (and I also wrote it) someone should do if he is facing a bug. I used a virgin Saved Games folder, removed all mods from core, did a cleanup and repair with "check all files" and "search for files after repair". The destroyed japanese units/static objects are definitively gone since the last DCS update. Before, they were there (I played the same mission before and after the update). Yeah, maybe you're right. But they came with the Corsair, so it is a little difficult to decide to what topic the bug report belongs to.

Интересно, что в последних обновлениях появились возможность применять комбинации оружия ГУВ + НАР. Раньше можно было только гув + бомбы.

Campaign was excellent hopefully one day Afghanistan mi8. The new map amplifies good plot and acting for best impression.