vgilsoler

+1

+1, totally agree.

@BIGNEWY @NineLine 7 years old bug. Should I say something more?

I didn't watch the series yet, but I read the book that is based on. In there the author explains there are several reasons to avoid bailing out, and usually the mechanical ones were the last to take in account. Basically for emotional reasons, for injured mates, trapped crew, to avoid be lynched by the people you just bombed, etc. DCS is good, but adding feelings to the IA crew is a overkill

Using DML 2.0.1 - I'll try DML 2.0.3

bomb range 1.1.0 is requiring to configure smokeColor and not using the default parameter, getting this error after droping load

@Plexus The radio menu is still unavailable. Will the radio functionality be added to the I-16?

Still no radio available in the I-16?

Just to get the facts, I hope we can reduce the last list during the year. I'm not taking in account if each modules have a long list of fixes or just one, and not including 3rd parties. 2024 Modules Updates February Patch DCS 2.9.3.51704 AH64D F/A18C F16C MI24P L39C A10CII FW190D9 FC3 KA50III CA Modules not (yet) updated in 2024 F5E F86F Mig15bis Yak52 Mi8M UH1H BF109K4 FW190A8 Mosquito FBVI P47D P51D Spitfire IX

Working fine now. Thanks a lot for your help and for the DML.

Possible bug in radiomenu: Using radio menu with 4 items, when you choose C! the message displayed is AckD instead of AckC. If using 3 items the message AckC is displayed correctly when selected C!

Exclude whole %temp% from AV is a bad security practice, so I did only for %temp%\dcs and moved it to fastest drive.

I saw it. I’m using a very old CPU so any load you can save, it matters.

This can help too Windows: Open your antivirus settings and add and exception for your Saved Games and %TEMP% folders and "C:\ProgramData\NVIDIA Corporation\NV_Cache" folder.

Working fine, thanks a lot.

same error I think Not able to test again until night

I get this error after updating When launching the radiomessage that triggers the action

Is there a way to send the same message to a two different groups/units directly without using coalition? For example to a P51D and a Spit doing escort, but not to a P47D doing CAP. The workaround I found is to duplicate the message zone and configure in each zone a different group/unit as destination.

Thank you for your quick responses and for the AMAZING! work you developed with DML. One more question, I'm thinking about to develop an interception training mission using messenger and unit zone, similar to the formation training mission. Is it possible to filter in any way messages sent by the GCI to the player if he/she is not using the correct radio channel?

It seems the problem is using Bigging Hill for another TDZ. I move it to another airfield and the error starting the mission is gone.

If I use the last version 1.0.3 then I get the attached script error. Let me try with the workaround.

The new TDZ script is giving following error when added to the mission. I'm trying to add the TDZ to Orly RWY in Normandy 2 map. When using the previous version the TDZ is showed in mission map in a path 0/180 instead of 70/250.

@NineLine The thread is tagged as only ST, but the issue is reproduced in MT too. Is it updated in the report to the DEV team?

Yes, using Normandy2. It did a clean repair and copied DCS to DCS.bak to generate a default saved games folder, but it didn't work. I tested the same mission in openbeta and it worked using 40.30 freq. So let's wait for the next update. Thank you in any case.

I've changed to 40.30 but still failing on BF109, and Dora can connect to TWR using 40.35, when I change the Dora to 40.30 then both planes are failing. The Mission Editor and F10 map show 40.35 for Villacoublay. I tried the autostart in BF109 to check if I'm missing any step, but failing too.