Shadow KT

Currently, the Open Beta dedicated server install required around 118 GBs of free space, while the recommended system specs say 100GBs.

Man.... how do you do this... our scenarios always match dates and times.....

Isn't this the same as the Save/Load Static Template function in the Mission Editor ? You can save a static template from one side, which captures basically everything, except triggers and trigger zones from both side and then using the load function, load in both sides in a new file.

The ability to add a trigger action "Message to Commanders", which will allow Combined Arms slots to have exclusive access to F10 trigger actions. Instead of having to do Message to Coalition, or have a dedicated TF-51 slot with F10 actions.

Oh forgot to mention, that this also affects ships. Cuz you know, ships are going to be most used units on a map like the Marianas, right.... right ? (Not directed towards Grimes)

Maybe in reality, but in DCS currently you don't want it at 100% for that specific reason. At maximum engagement range, usually SAMs like the Patriot and S-300 are more likely to miss, than hit, making them just waste missiles. I am guessing because of lower accuracy from radar returns at range.

Seems to be a global issues with MLRSes

Since two patches ago, I've been having this issues, I don't know if it is something on my end (I am guess it is, because I've not seen anyone else complain), or a bug. When you jump in a vehicle in isometric view, instead of being able to freely move the camera around and the gun will try to catch up, the view is stuck to the gun boresight, limiting your camera traverse time to whatever traverse speed the turret has. Only way to fix this is to go back to gunner view and return back to isometric. Isometric View Bug.trk If anyone knows how to fix this on my end... I am all ears.

AI SAM ignores this Advanced Action, when dealing with incoming missiles, a lot of the times leading to waste of missiles and chances to actually hit the incoming missiles. SAM Intercept Range.trk

As this brochure is from 2019, are you sure all these things are not for the NASAM II ?

Quite interesting that they have labeled it as a SA5 radar, when it has been used with SA-10 and in general as early warning

Nevermind, I was mistaken. My post can be deleted

AI under 10-20% (Have not tested exact percent)stop firing and can barely move. In general AI under 50% have degraded accuracy, aiming time and movement speed. In case of radars (at least ground based), when they reach 50% their radar stops working.

Get a unit in a location, where it has line of sight to where you are shooting.

Track from me and a operator. He sets up panel 16 salvo, right side only. I press countermeasure button, I get default 4 salvo both sides. He presses his button, we get 16, right side only. Mi-24_CMS-20210723-120421.trk server-20210723-130159.trk Track from front and back seat (server is back seat)

Yes, I will record a video and send you the mission file, but in a PM, as it is part of a PvP scenario and I don't want the opposition to find out what we are planning

Alright.... this is weird. It only happens with two groups as far as I know, and obviously those are big SAM groups. I tried other groups in the same mission, as well as placing a new group and I have no problem left control moving the lead unit, but with these two specific groups I can't do it. EDIT: Okay, after moving a bunch of other groups, these two got unstuck as well.... this is extremely weird behavior EDIT: Okey, what the .... I placed a random blue group next to me red unit, just to test, the two red groups I had issues with unstuck... I deleted the blue group and they got stuck again. I should make a video of this....

Okey, I re-ran and I got different results. So for 30000 feet launches. I got a shoot at 14nm for the LD-10 from the S-300 and 18-19nm for an AGM-88. Which seems reasonable. Meanwhile it feel like the Patriot firing range got a buff, it shoots at LD-10s (same altitude launch) from 24nm, and at AGM-88s as far as 36nm. That said, it doesn't really help in anyway, as at that range, it just misses and wastes 3 missiles per shot

According to some online keyboard tests, yes. Maybe there is some sort of key conflict.

Okey, tried to carve a path through the woods in the mountains and stumbled across some weirdness with the scenery remove trigger. It either removed an area, which is multiple times bigger than what you had as a trigger zone, it randomly removes some bits, again outside the trigger, or it just straight up doesn't do anything, at least at an initial glance. Remove Scenary 1.trk Remove Scenary 2.trk Remove Scenary 3.trk Remove Scenary 4.trk

Interesting... Patriot intercepts from 25nm, at 30K altitude for the SD-10, but in the same conditions, the S-300 will engage at 9nm, which leaves it very little time to react to multiple shots.

Will do.

Since the latest patch, it is painfully hard to make the lead unit move on its own, without shifting the whole group. From dozens of attempts to use Control Left click, I was able to only once randomly activate this feature.

Don't know how strong the wind has to be, but I've definitely seen it happen on servers with very little no wind.

By the way, when that happens, is it normal for the gearbox to seize after what seems a constant amount of time ? I would try to auto rotate, drop the collective, start auto rotating and all of a sudden, the gearbox just seizes. and the rotor stops dead. Not really a moment in which I've looked at the RPM gauge, but could it be overspeeding the rotor ? Last time it happened, I did try to give it just a tiny amount of collective, as I am gliding down, to slow it down, but it felt all the same. Rotor stops moving after what seems to be a constant amount of seconds.