vgilsoler

Knowing that I’ll retry changing the zone sizing. With declone I had weird behaviour, but I didn’t investigate deeply to provide you enough reasonable evidence. I’ll take a look on group trackers too. Thank you very much again and again

Hi, Looking for help again. I'm trying to remove a cloned air formation wih wiper when they reach a zone in the map. But It seems wiper is not able to detect the formation as unit (cat=1) I tested with B17 (WW2 assets pack) and A20G (non WW2 AP) nullnullAny advise? Regards, Jueves_Negro_v1_debug.miz

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 September Patch DCS 2.9.8.1107 F16C F/A18C AH64D CH47F A10CII MI24P UH1H FW190D9 KA50III Modules not (yet) updated in 2024 FW190A8 (It seems it is updated in patch 2.9.6 but not appears in changelog)

The issue seems to be solved both using and not using WW2 assets pack. Thanks again.

Able to reproduce error again without WW2 asset pack units, and 2.3.4 modules version. Many, many thanks for supporting guys like me forcing the limits of DML and DCS. Normandia_captura_base_debug.miz

Do you want hear something weird? In this mission, if you add one more red unit from WW2 assets pack it will fail. If you put a new blue unit (from WW2 pack or stock game) it will work. If you put a red unit from stock it will work too. Don't ask me how many times it tested the mission to found that. xD Normandia_captura_base_debug.miz

I tried with the mission without WW2 assets and worked successfully. However the original mission with WW2 assets pack is still getting error. I removed the factory zones and only spawned units from the start are present. Is there any tip to speed up debugging the issue instead removing (or replacing) units in the mission? Maybe a unit has something weird in their name? or perhaps could the problem be with some units are deployed using DCS template like Flak18 Battery?

I've replaced the ww2 pack units. The mission starts with units and factories started, then a pulse at 5s move them to paused, when an IA P-51D enters in the zone it activates the units and factories and when it exits the units and factories are paused. Until here everything works succesfully. But, when the P51 enters again in the zone to activate units and factories I got the script error. Maybe the number of units in the zone is the problem? Or maybe new units from the factories? Normandia_captura_base_No_assets.miz

Getting this error when activating impostors. I'm using DML v2.3.2. I think the problem is that I have factory zones inside the impostors zone. I use the same flag to activate impostors and pause the factory zones, I use another common flag to deactivate impostors and activate the factory zones. The rational behind is to start/stop fight/production when allied aircraft is in/out the impostors zone. Tested and failed on both DCS v2.9.8 and v2.9.7 I attach the miz for review if someone can help. Normandia_captura_base.miz

It is the WW2 Assets pack. But it helped to find the issue. There was a flak88 unit from the stock game in the mission. After I removed it, the other guns started to fire.

I think I found the problem. The flack88 from the stock game can not be mixed with flack88 from WW2 Assets Pack in the same mission.

Yeah, It is what I think. But what sounds strange is that the empty mission with only the flak template worked correctly, but in the attached mission the same flak template with the DML modules loaded not. I'll try to load the same used DML modules in the empty mission one by one and test again.

I put an enemy flight near the guns to test. DML should do nothing with the flaks. They are not inside any zone.

Hi, Always amazing your work and effort. Not sure it is related to DML or a bug in DCS, but I put a flak41 template in a mission with DML and only the 20mm guns are firing. If I put the same flak41 template in a fresh mission, both 88mm and 20mm fire. The flak is not located under a trigger zone influence so I think the problem is not related to DML, but in the fresh mission it worked. I attach the mission if it is possible you can point to any clue, I already reported the bug (if exists) Normandia_1Vida.miz

I share the mission, you can test it with the flak group in Cabourg and the P51D and B17 flying over. Normandia_1Vida.miz

I’ve configured a battery flak41 template in a mission, and only the 20mm guns are firing. The flak41 template has the kdo. Is there any other flak template working? Or all templates are bugged?

@NineLine @BIGNEWY any update on this? Still under investigation?

The idea behind that is to run missions like coop style. “One life, one plane, think carefully what you’re doing”

One question I haven't found answer, well in fact there are two questions: - Is there a way to prevent users from changing their coalition after joining one with DML? - Is there a way to prevent users from resloting to another airframe type? I can limit the coalition pilots using limited_airframes, but if there are slots available the dead user can jump to another type. For example, I setup a mission with 6 pilots in a team with limited airframe and ssbclient single use. if only 2 pilots join the mission and one of them crashes, he can stiil jump to 4 available slots. So one airframe can be used only one time, but pilots can be used more times. Or is it possible to link in some way each time a pilot join to the number of limited airframes? Not sure if I explained well myself.

No error message with v1.7.0. Happy to help to improve DML. Thank you very much for your help and effort.

I'm getting this error when launching the mission in multiplayer using "limited_airframes" module. The mission seems to run fine after the error and counting dead pilots correctly. I'm using DML version 2.3.0 - limitedairframes 1.6.0

I moved it using windows method but DCS server is not reaching it, however DCS client works perfect. Maybe having an intensive resource app using same drive as system is what is not a good idea, in my opinion.

@BIGNEWY @Flappie Could this be reported and fixed? If the DCS client can work with "saved games" outside C drive, other DCS stuff should do it too, isn't it?

That will be the second phase. First, confirm if all modules have some "love" during the year. At least, this year it seems true. Second, lets see the quality of these updates. Are they are resolving bugs? adding new features? or just cosmethics?

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 August Patch DCS 2.9.7.58923 F16C F/A18C F-86F AH64D Modules not (yet) updated in 2024 FW190A8 (It seems it is updated in patch 2.9.6 but not appears in changelog)