Retnek

Stumbled over this topic by chance - just a few years old, not long ago a patient DCS-follower, right? Please check https://vaktelforlag.se/produkt-kategori/english/ The volumes of "Black Cross vs. Red Star" are on hand again! Enhanced editions and new volumes, too! The books are THE standard on that topic and an immersive reading, too. (should end the daylight robbery by second-hand gangsters )

Das - aus berufenem Munde - könnte helfen:

Imho it'll be fine if you offer the choices the pilots had in flight, too. The present solution is definitely better than it has been. That vague option "Function delay mode" just for some types of fuses is quite confusing. Maybe all I need is more distinct presentation of the options and/or another wording - suitable for a non-native speaker.

No photoshop, both screenshots during a single-player-session yesterday, ca. 21:30 GMT. The level of detail is just like the first pictures in this thread from 2020, so it might be old content on that PR-billboard. Anyhow - a good reason to point on the profound need for an analogue Delta-Mirage. The F-1 is marvellous, a true gem. Now the next step to a classic Mirage delta-wing, please ... The upcoming Kfir is a close relative to the Mirage V - the good old war-hero Mirage III would be a proper choice. I personally would love to see the Mirage IV, but she's far away from the mainstream.

Testing some stuff SP in the South Atlantic, I gazed by chance at a billboard - Airport-Road, Port Stanley airfield: HELLO - who's this? Isn't "proximamente" Spanish for "soon"? Just a remnant from the early days of developing the map or is it a hint? I like that kind of humor, btw:

Very nice skins, thank you! A detail: just by habit I placed the files via OvGME in the user-part of DCS (something like "ssd:\users\username\Saved Games\DCS\Liveries\Fw-190D9\...") and it works fine. Later I found your advice to place them into the core-part - like "ssd:\PathToDCScore\Bazar\Liveries\FW-190D9\...". Is there any strong reason to place the skins in the core-area? During the last few years usually we were advised to place add-ons user-owned-part in "saved games" if possible.

It was fixed with DCS 2.8.3.38090 Open Beta, at least for me.

Helpful note - thx! I prepared 3 mods in OvGME with the factors 0.2, 0.4 and 0.6 (line 101 in DCS MT 2.8.3.37854 now) - easy to exchange while testing different planes and light regimes.

Sorry, in contrast to this thread imho the fuses still aren't right. First one is easy. The German fuse 25c had a long "Vz Mode function delay" of fourteen (14) seconds, not 8.5. Since the delay is relevant for attacking in larger formations it should be corrected. Like it was done by the Germans advancing from fuse-model 15 to 25. Please check the documents given here: and here: I learned in mission-editor one should use the "function delay mode" "fixed" to set the fuses, not the "variable" one. So for fuse type "Zünder 25C" in mode "Fixed" there is given this pattern: oV Mode Function Delay (oV = no delay) = 8.5 sec mV Mode Function Delay (mV = with delay) = 8.5 sec Vz Mode Function Delay (Vz = retarded mode) = 8.5 sec Sturz Mode ARM Delay = 80 ms Waagerecht Mode ARM Delay = 80 ms "Function delay" here is the time from impact of the bomb to it's ignition. "Arm delay" is the time the fuse needs after leaving the bomb-rack to change the status from "safe" to "armed". For the fuse-type "Zünder 25C" in mode "Variable" there is given this pattern oV Mode Function Delay (oV = no delay) = 0 sec mV Mode Function Delay (mV = with delay) = 80 ms Vz Mode Function Delay (Vz = retarded mode) = 8.5 sec Sturz Mode ARM Delay = 80 ms Waagerecht Mode ARM Delay = 80 ms Historically correct values for fuse 25 for an (extended) table should be (sources see above and below) oV Mode Function Delay (oV = no delay) = 0 sec mV Mode Function Delay (mV = with delay) = 80 milliseconds Vz Mode Function Delay (Vz = retarded mode) = 14 sec Sturz Mode OV ARM Delay = 3 to 6 sec Sturz Mode MV ARM Delay = 5 to 10 sec Waagerecht OV ARM Delay = 3 to 6 sec Waagerecht MV ARM Delay = 0.7 to 1.6 sec For the time-to-arm this table gives detailed numbers: I know the fuses are still work in progress. Your way displaying the values in a "variable" and a "fixed" mode will add to confusion, too. Whatever I try - I'm not able to find a way to prepare my Anton via the mission editor to drop bombs historically correct using the mainly used fuse-type 25. Add-on 15.03.23: Here's the most detailed documentry about German bomb, fuses etc - always worth a look for British and US-documents and procedures, too. Sorry, in German only and a somewhat strange HTML-setup ... http://michaelhiske.de/ German fuses: http://michaelhiske.de/Wehrmacht/Luftwaffe/Zündervorschriften/StartSeite.htm Zünder 25 f.e. = 152/8 & 152/22 & 152/27

Thanks! Very nice - that's a real improvement for the WW2-scenarios. Here's two pages from the Luftwaffe's service regulation LDv 5-1 from June 1943 - hopefully useful: PS: don't get me wrong - it's already fine as it is! Looking at the videos you already implemented some typical details and differences between Allied and German airfields.

PS: mir hat sein GUI-Tool immer gut geholfen, incl. der o.a. Reparaturfunktion. Letztlich ruft er damit die Original-Konsolen-Befehle auf, nur mit mehr Komfort für Mausschubser. Vorsicht, auch per GUI-Zwischenschicht kann man sich DCS wirksam zerlegen.

Das sieht nicht soo falsch aus - da fehlt wohl ein Leerzeichen: ...\DCS_updater.exe repair Anführungszeichen sind normalerweise nur dann nötig, wenn Leerzeichen irgendwo im Befehlspfad vorhanden sind. Der ganze Katalog schön ausführlich:

Very nice mission - a pop-up window during loading, phase "Export Start", mission still is doing fine after that. Hope it helps & thx

The Ka-50-III would profit very much by realizing the Ka-50N- and Ka-50Sh-projects. Add the badly missing night-capabilities, please, that would be an obvious customers stimulation.