cfrag

It's called 'code engineering' -- these things seem easy when it's done right. Hopefully ED try it sometime.

Well, I didn't say so, but yeah, I'll take the Phantom to wake up my neighborhood and launch a missile into my elementary school, exactly as Calvin envisioned it in Watterson's seminal Comics. Spelling correct that, Frau Dröge!

Wow! Ugra's Syria convinced me, Normy 2 made me a believer. It's difficult for me to convey my feelings (and probably too high expectations) for this map. I was born and raised in cold war Hamburg, served in the cold war (western) military (in Neumünster, Hamburg and occasionally, during NATO exercises, in some other Truppenübungsplätze in West Germany), met a fantastic girl from West Berlin (and visited her often), protected our side from the 'lousy communists' on the Harz side, and now can't wait to take a plane ride to my past. Good luck, and Godspeed, Ugra!

Done. It's now a config item menuName Name of the menu that heloTroops puts in the players UI to allow them to access heloTroops functionality. Defaults to “Airlift Troops” Enjoy, -ch heloTroops.lua

I could try and make it a config choice. Watch this space

Thank you so much for taking the time and making the effort to track down some bugs. Uh. Nice catch! This is a strange one as it only applies to dynamically spawned players, and Expansion (I think) doesn't yet support it (because DCS's mission API is so crude). Nevertheless, I hope I'll be able to patch this quickly. Sigh. DCS's API is the gift that keeps on giving, isn't it? Again, my thanks for documenting this! I should be able to guard against that quickly. Root cause is DCS passing out nonsensical/erroneous information (pointing to a deallocated unit), and DCS then stumbles when the script asks 'tell me more about that unit'. I don't think that they are connected, but you never know. I'll try and remove the bugs that you kindly documented. and we'll see what happens. From what I've experienced, the bugs that the scripts throw are all recoverable and should not cause the server to disco anyone nor restart. That being said, DCS itself resides on a terribly unstable core that dates back to the late 90s of last millennium, with libraries that are 32 bit code. DCS should be fully restarted (better yet, the entire server) once every 24 hours because it can corrupt your main memory and cause crashes for no apparent reason. My dedi servers (managed by the kind people at Fox3) restart once daily for exactly that reason. I hope I'll have a n update ready soon.

Simply use the method of spawning that you prefer, and better fits into your design flow. Both methods use coalition.addGroup() to create the units, there is no performance benefit for either. There is a marginal overhead at mission creation when 2 (sides) x 5 Spawn Points x 20 Units = 10 Groups and a total of 200 units are deallocated and DCS must perform its (not very good) garbage collection. Since it happens at mission start, I believe it to be insignificant.

And time accel doesn't? DCS is a game, and the object is to have fun. I don't mind when people say that for their enjoyment they want some arbitrary process simulated - it's a wish forum after all. And some 'realistic' inventory management is something that may be fun - "warriors win skirmishes, logistics wins the war". DCS's warehouses can do this, and - ironically - only in multiplayer: you can use warehouse inventory to limit the amount of aircraft that can spawn from an airfield. Let's try and keep off the 'realism' argument and focus on 'good experience' instead. I'm looking forward to see if and how ED bring this aspect of supply/demand/reinforcements to a dynamic campaign. Any undamaged modern aircraft that has seen action should realistically be out of the game for a day at least (maybe less for warbirds), a damaged one for a month at least. Same for pilots, so we are disregarding realism anyway. Let's focus on fun.

While indeed an interesting detail, that may rule out multiplayer - because time acceleration for a player simply doesn't work for for multiple. Most modern planes also have repair times measuring in months, not hours, so a plane damaged past a (very low) threshold may as well be counted as lost.

Indeed. To me it's both frustrating and heartbreaking that my favorite game as such an abysmal API. We all know that the data is there, it's just not (yet) accessible.

Unfortunately, no. Callsigns can be assigned via tasks, and there currently no (published) API for accessing a unit's current callsign.

Not yet. I'll see if it is accessible from within MSE.

Version 2.4.5 - 20250313: Feature update: csarFX, heloToops drop formation One of the little nagging things about DML's csarManager was that it, well, didn't really manage CSARs, just SAR. Putting the "C" in CSAR was something I did some time ago with a small add-on that not only adds enemies around the evacuee, but it also significantly dials up the visual candy and arranges nice debris, and in the case of SAR adds accidents on roads. The module csarFX exists separately, and transparently adds all these features to existing missions with little to no effort. If you have seen one of "Angels" or "CESAR" missions, you have seen csarFX in action. I've now merely brought csarFX to DML standard, and added a significant new feature to csarManager itself: the venerable autoCSAR module now can trigger true CSAR missions for any pilot that ejects and touches down inside a CSAR zone, auto-generating hot LZ, debris and everything. Other than that, DML has received a number of smaller bugfixes and enhancements, with DML's "crown jewel" heloTroops receiving a significant polish: players now can choose how the formation in which troops that they deploy form up around the helicopter: the classic circle around the helo, and now a line to the left and right, or a gaggle behind the aircraft. All this via commuinications, so merely updating the module brings this feature to your mission. All Changes: Documentation Main - csarFX (new) - heloTroops (new drop formations) QuickRef - csarFX (new) Demos - follow me (update) - SAR and CSAR, sitting in a Tree (new) Modules - airTank 1.0.2 - better integration with fireCtrl.enabled - csarFX 2.0.5 - Initial version (yeah, don't ask) - csarManager 4.4.0 - integration with autoCSAR: trigger CSAR zones - integrtaion with csarFX - fireCtrl 1.2.0 - new onStart attribute - new ctrOn? attribute - new ctrOff? attribute - heloTroops 5.0.0 - drop formation options via UI - playerScore 5.2.2 - removed type in feat - sitting ducks standalone 1.0.1 - hardening against DCS bugs - smokeZone 3.0.1 - removed bug during data load - unitZone 2.0.1 - removed deprecated 'coalition' and 'uzcoalition' Enjoy, -ch

Perhaps some day later. The issue here is that with radioMainMenu you can (and people do) build large structures, and mainMenu IMHO is a cute hack that isn't well engineered to support this (DCS's menu structure isn't at all, so I would need to build a system to manage that, and resolve issues where DCS's menu structure simply fails).

Thank you @Penfold-88 - some analysis showed some missing explanation in the manual: radioMainMenu and attached radioMenus must have the same access restrictions (e.g. coalition: blue) else the main menu can't be found and the menu attaches erratically.

At first blush, all seems to be fine. Please verify that you are using the newest versions of the modules. If that doesn’t help, post or send this (or a simplified version of the miz, no mods please) via PM, and I’m sure we can have 5his resolved quickly.

Thank you for that report. I'm not sure that there is anything I can do (CA isn't well integrated into DCS) but I'll surely have a look.

Indeed an important question - did you and @Grimm hash this out, or is this an initiative of your own? Will the branches perhaps merge?

Yes, and easily so: Open ths mission in mission editor, then Click on the 'zones' button (three interlocking rings) Click on Show all Click on the zone named "persistence config" Change the value of "saveInterval" from 5 (current value) to 1 Save and you are done.

And this is single-player only, and the "X: Command..." are module-specific, i.e. the mission may not run with a different module. VERY time-consuming, frustrating and limited. But it is possible. just like @Minsky kindly pointed out.

There currently is no good way in DCS to associate a livery with a unit, so livery support can only be provided for some modules. Spawners who can spawn any typeName cannot provide livery control in a meaningful way. Cloners can do it if you manage the livery in ME by assigning it to the clone template.

Please ensure that USSR (the country) is allocated to RED. I think in your default setup, it is NEUTRAL, which forces the error.

"And if I'm flying solo At least I'm flying free"

HIghlander?

Understood, and thank you for looking into this, BN. That being said, most players don’t strike me as the kind of people who are interested in the difference. When they play a miz, they may likely expect the save state function to work, irrespective of the fact that a designer used a script or not. If they used a script, the miz is likely not compatible with restore. That may lead to some rough experience for your players, as „don’t use missions from userfiles with scripts“ seems a hard sell if you want to make userfiles more popular. We‘ll see how this turns out, I fully trust ED’s strategy on this.