104th_Money

@DD_Friar I have been reading up on DML to incorporate it into my missions but if he isnt familiar with using it already it will probably be more complicated for him that just using ME triggers. I spent about 3 hours reading up on the DML docs and I am barely only grasping it.. @2circle To spawn random units in my server missions, I just do trigger mission start, condition random and pick an percentage and then the action group activate. If I want a chance for it to spawn again later if it didn't spawn on mission start, I run a second trigger once, condition random with percentage and add a condition time more then action group activate. In your case that you want to spawn one or the other, for the first group, trigger mission start, condition random with percentage, action group activate (random activation of first group). Next trigger once, condition time more 10, condition if 1st group dead, action 2nd group activate.(If the first group didn't spawn then it will activate second group). That way one group or the other will always spawn based on the random event in first trigger and you dont have to worry about the first group getting killed and spawning the second group because the condition time more is already passed.

A lot of it depends on your hardware. The JTF Mad Dogs have a dedicated server with a i7-12700k/64gb DDR4-3600 Ram, Gen3 2TB SSD and a dedicated 1g up/down internet connection. I regularly build missions with a combination of upwards of 1500 static/active units, 40-50 complex triggers, MIST/CTLD/CSAR/JTAC scripts and at most 10 players at one time just to give you a performance/hardware/mission unit metric to compare. We rarely have any issues at all, especially with people joining that have higher end systems. Every once in a while someone will get a quick stutter here and there but we haven't been able to specifically say that those are server related issues vs. an issue with the clients internet connections.

It doesn't work because in order for CTLD to work, the aircraft that you want to use needs to be pilot name specifically pre-named in the mission editor for the CTLD script to interact with it. The dynamically named aircraft do not haven that option so the CTLD script does not work with it.

This bug is really irritating. I have a mission that you have to kill a group of infantry and vehicles at a waypoint. Since the group alive less condition is not working, I have to use all coalition out of zone as a substitute. Only problem is that sometimes infantry, or even vehicles for that matter, go into buildings and you cant see them anymore. The group alive less than condition was a way to kill most of the infantry and still be able to trigger other things if 1 or 2 infantry was inside buildings...Please fix this, again...

Special K helped me out in Discord, I had quite a few runtimes that seemed to be causing the issue. Deleted with another program and installed the new runtime successfully. DCS working fine again.

Did not previously try as admin but just did now and getting same error. It starts and the progress bar moves a bit past half way then error. Also updated windows, ran sfc /scannow and restorehealth as well... Getting these messages

I downloaded the file in the solution link and attempted to install it. It fails to install.

So had an issue today where someone joined me in multicrew in the Kiowa. I had been flying solo earlier and was firing 1 rocket per weapons fire depress. After my copilot joined it was firing off 4 rockets per weapons fire depress. Confirmed ripple setting was at single. Issue continued after copilot exited. Anyone have any ideas on this?

So when its raining, aircraft canopies and helicopter windshields have alot of water drops on them. I noticed when switching from cockpit view to external view and back to cockpit, the rain on the canopies and windshields is gone and starts the rain drops all over again...

Sorry bud, just saw this post. My missions are quite mod heavy with tons of triggers and has custom changes to the CTLD and CSAR scripts so probably not a good example for u to check. Some of the trigger conditions are broken since the last update. Which ones are u using in your mission that aren’t working?

I had an issue last night with an old server mission that I updated with Kiowas. I selected the Kiowa and after a few seconds i got a CTD...Sent logs to BigNewy and he said to deselect Import Editor Drawings...If your mission has editor drawings for the F10 menu and you CTD when joining in a Kiowa, this is the fix...Not sure if its a PC or ED problem but wanted to give any mission makers a heads up if they encountered this...

CTLD is working for me as far as loading troops from F10 menu then dropping them into a trigger location and having that trigger function properly. I have noticed that group alive less than is not faithfully working after last update though.

You can remove scenery objects and trees in the mission editor. The ground textures will still look the same but at least you can build on top of it without the object/tree interference.

Kandahar doesnt even have runway lights at night...only the heliport runway has them...On a side note, you can lighten it up just a bit by setting time/date to have a full moon...

When landed, or starting hot in the aircraft and collective fully down, the aircraft seems to always rotate to the right a few degrees. It seemed a bit more pronounced prior to the update but its still there. Feels like the skids dont have enough resistance against the ground but after a few degrees of rotation it settles in and stops rotating.

I have same set and Kandahar works for me

Question, if say Camp Bastion has static aircraft populating locations that would be used for automatic dynamic spawn points, will the dynamic spawn point not work due to the static aircraft in the way?

Using MIST/CTLD/JTAC scripting, I am using a Reaper as a JTAC. It works just fine using orbit in advance waypoint actions and I am even able to edit lasing range of JTAC in CTLD lua. What I would like to do is have the JTAC just lase targets inside of a specific trigger zone. Is this possible?

I feel you, its crazy how one update can make something work differently and cause such issues. All credit goes to Special K though. If he hadnt been available and willing to help and opened up my files to look a things, this could have lasted forever as I would have never checked the scripts/hooks folder...Mods arent bad, we just need to clear out mods if we have issues when updating and put them back in 1 by 1 to see which, if any are the culprit.

I would program a button or switch for it, when you get to flying aggressively it may constantly go off...Its under copilot multifunctional keyboard... .

No, was not aware of that possible solution. I didnt rename my saved games folder, only removed Tacview, the OH-6A mod as well as 2 OH-6A lua files and 1 Tacview lua file in the saved games>scripts>hooks folder and all went back to normal.

Special K helped me out in ED Discord. Tacview, although disabled was still possibly causing issues. He also found that 2 lua files from the OH-6A mod may have been giving me issues. I removed Tacview and OH-6A mod completely as well as the 2 lua files and a tacview lua file. This solved all issues and brought back performance to pre update levels.

I had a stutter issue before and disabling Tacview solved it for me, but I double checked and its not enabled.

So this has to be something DCS related. I can load into a single aircraft empty mission and everything is fine. But previous large missions that ran fine even in SP are now stuttering every 3 seconds like clockwork. I can see in the FPS counter going from green to red CPU Main Thread every 3rd second for a fraction of second. I removed all mods from missions with no change in stutter. Turned off OC for my 13900k and 4090 just in case it was causing it to be unstable. No change in stutter. Updated all apps and drivers and windows updates to rule those out. No change in stutter. I swear DCS was running flawlessly prior to update...

CPU core parking still disabled, so not the issue.