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.

Da lege ich doch den Gehstock beiseite und werde hier nahtlos anknüpfen: Damals, jaja, öffel, nun kömmt der Jungbrunnen von DCS, brav-brav, recht so, wohl getan! Daran werden sich die Herren messen lassen müssen.

Folks, I'm blown away! Need coffee? Beer (non-alcoholic until version 1.0)? PLEASE go on with that project, that's beyond anything I could have imagined for DCS.

Let's hope the developers spend time for the FLIGHTsimulator-aspects of DCS. Would be most satisfying to do the real navigation with dead-reckoning, RDF and GEE. For this the brains need (AI-) boots to keep her straight and level!

Another variant, this time without the final straight flight path: " ... The Circle was made to go to one side of the Target, as the Bombs departed Tangentially when released from the Aircraft. Calculations depended on knowing the Height & Speed of the Aircraft, which, of course, the Pilot had to maintain dead Accurately. ..." (https://masterbombercraig.wordpress.com/bomber-command-structure/no-8-pff-group-bomber-command/pathfinder-force-pff/pathfinder-methods/oboe/) According to this the final heading correction offered a last chance to correct to the intended release-heading. If the pilot at that moment was in the process of correcting the plane back into the middle of the Oboe-track the error was just some yards. No problem to release with such a small error to the left or right. Releasing bombs when heading just a few degrees wrong would result in a *much* larger error.

Good find - thx. I *know* I read a detailed description of the procedure in another's veteran report, too. Can't find it - grr! Those 7 sec time for correcting the heading are really short with a good chance to screw it up ... so why taking such a risk? Good question, indeed. But turn it around. Flying a really long track precisely within 30 yards first. And then let the plane go straight & level for 3 min before the drop, without the remote reference? There's a big chance for large errors in those last 3 min, too. You're right, this detail needs to be fixed - I'll try to find an answer. That's one of the most fascinating aspects of mission-building in flight-sims. You believe to understand what happened? Try to simulate it and you soon know what's missing.

Draken35 - from your read-me in "OBOE.txt" "... Release heading. At the time of this writing, it is not clear to the author when the pilot should turn into the release heading but as a best guess, since it is calculated from the release point to the target, is that the pilot should start turning into the release heading when the release signal starts. ..." Smith & Smith (2003, c.a., p134) described the Oboe-training: "... If the run was ultimately completed, the release signal - five dots and a two-and-a-half-second-dash - was transmitted three minutes after (signal) D. I would indicate the start of the seven-and-a-half-second release signal by a dramatic raising of my left arm in front of Johnny who hastily made any small adjustments of his heading to that given at briefing. ..." Bold by me - I think that question is answered. Just 7 seconds to correct the heading AND set the plane back to level again! Those men really had to react on spot. What a pressure to do it right as a marker for a large raid. Failure means hundreds of bomb-loads wasted and maybe a number of air-crews killed for no or at least disappointing results. As always with a bit of caution about details published 50 y later. But they describe THE critical phase of all the Oboe-missions. Both Mr. Smith show a great respect for details all the time - I see no reason not to trust them.

Good reading - bomber support mostly, good overview over 100 Group operations. I very much hope there will be mods to simulate ground- and sky-markers. The Viggen-inventory has some nice flare bombs for target illumination - hopefully to modify and use as target-markers or even a kind of night-photo-flash? A lot of bomber-mission types should be available without the drop-snout, too.

Wow - thx! That's exactly what I was hoping for! Here's a first-hand WW2-report by a Mossie-navigator about Oboe-missions (pp 141): Smith, Albert; Smith, Ian (2003): Mosquito pathfinder. A navigator's 90 ww2 bomber operations. Manchester: Crécy.

Since there's a direct relation to the FuG-16-topic: Afaik still open.

Mikhail does a great job, folks! Hardware came within a few days to Germany right to my door. Very well protected, no administrative acts - paperworks perfectly done! Checked the hard-, firm- and software - flawless. That's very good craftsmanship, no gaps, no waggles. Screwed the mount to my wooden chair, adjusted the collective (freedom given by the mount plus-minus 10 cm ca.), tighten again - rock-solid. Only thing to do - same solution I use for the Virpil-joystick: a holey old sock fixed with a rubber-band to cover the mechanics against dust. Thank you Mikhail!