Retnek

Just to clear the facts: in my version DCS 2.9.17.12034 this file: ...\DCS\CoreMods\WWII Units\SpitfireLFMkIX\SpitfireLFMkIX.lua looks encrypted to me. No way no longer to enhance this Seafire-mod, right?

Thx, that's the correct values & easy to replace in the lua. I've checked > dozen different lua-files from ship-mods, sadly there was no properly commented or documented version about the values used. Some of the comments one can translate from Italian or Russian, others are educated guess-work, but remain vague ... try and error, if there's need for a certain mod (and time for it). btw: the bow-waves of the German cruiser seem to be a bit more complicated - Hipper is fine, Eugen and Blücher show that set-off (s.a.) on the Kola-map. On the WW2-Marianas-map all three are aligned correctly. Without a well-kept and documented sim-engine the time-requirement for such kind of maintenance becomes a serious show-stopper.

THAT's the way to go - please!

Hopefully the Corsair blows the fire below the DCS-WW2-boiler ... steam, Chief, steam! German Navy ships 4y later still look great in Norway's fjords! Z39 (bow wash & exhaust) Prinz Eugen (bow wash set to the right and very low) If there's a chance to fix such cosmetics via lua and a tutorial nearby ... please point on it!

Thx, that's good to know. No deadline expected or intended - can't be that easy or you'd done it already. when it's done -

I know the not-feature "automatic release" for years now ... from time to time I check the forums if there has been any progress. Sadly parts of DCS more and more drift into an attitude "good enough to pre-sale is good enough at all". Heatblur has been at the quality-side over the years - I hope they remain on that path. Sufficient communications sometimes is part of it, too. The handbook is done fine, but you use that "light grey" in an unusual manner. You expect people to read that content printed in that very light grey? To me that is a way of hiding content. To me it contains a message: Dear reader, ignore the light grey parts because that's "w.i.p." It will become readable when the feature is finalised. @Zabuzard my key point has been "a feature like 'automatic chaff release' is that obviously useful most pilots sooner or later will try it". Low hanging, ripe fruits imho.

Sorry, a feature like "automatic chaff release" is that obviously useful most pilots sooner or later will try it. Most tutorials out there state "there's an automatic chaff release, too". Even the official manual has it, in light grey letters. No warning, no hint "don't trust, don't use, broken". That's a very effective way to frustrate newbies and learners ... Where's the problem to place a description like "inactice - WIP" next to the "A" at the selector? And just one sentence in the handbook?

Plus another year ... no message, no results

Heclak was seen last in the DCS-forums 26. Sept. 23 ... he is/was part of the A-4-project, too. Looks like he's very much into other projects now: https://github.com/heclak https://github.com/heclak/flybywiresim-aircraft The most relevant part of the site presenting his ELINT-App seems to be written in Java-Script. Maybe enough for an inspiration what direction to go for new solution of the problem?

Here's an original bomblet-pattern from a BL-755-test to offer some evidence to play with: Roughly simplified there's a rectangle "core-zone" of 100 * 50 m = 5000 sqm. 1/3 of the bomblet outside, duds etc pp there's still 100 bomblets inside, one for every 50 sqm. Each of the bomblets had a forward AT-capability and produced 1400 fragments ... Really bad options for any-one or -thing unprotected or lightly armoured in that zone - something like 90% targets with damage >50% seems reasonable to me. 50 sqm is a 5 * 10 m rectangle - 2 scouts or 2 armoured carriers and maybe 1.5 larger tanks like MBT or SPG. So something like a 25 - 50% chance for a direct hit.

Wow, that's good. There's always a need to communicate shooters positions to allies via network - resulting in some delay. Perfectly fine to display a message and get the details via the F10-map.

You bet - thanks a lot for offering it! This technology is an important factor especially in small-scale encounters - a spearhead of few tanks now has MUCH better options. Will be a pain for airborne AT-sorties f.e. Changing the parameters you prepared will allow to quickly review the outcome of encounters. btw: An important factor is the capability of that system to fix the position of a shooter instantly (within limits, naturally). Would be the icing on the cake if there's a way to add a detection- and information-routine. Anyhow, that technology weights a lot, is very expensive and most complicated. But there's good reason the burden is added to more and more vehicles - your script is dead on progress.

https://www.digitalcombatsimulator.com/en/support/faq/repair/

A 3060 Ti here with 8 GB vram, 3440 * 1440, AMD 3700x - lower middle-class, maybe. Hollywood-gimmicks switched off I'm going > 75 fps in the really demanding F-4F. I tried - one by one - a few selected mods like the A-4, Gripen or the Raphale - a bit lower, but still above 75 on average. I start the mission on ramp or go straight and level for the first one or two minutes - my limited vram shows. The sim-engine needs a long time to arrange itself. Hopefully they are able to optimise the memory-management. I still have some degrees of freedom to reduce demanding details like trees foliage, spawn distance etc - but no need to now. The map is early beta, will change a lot.

Thanks, smaller she is beautifuller!