Catweedle

Thanks, Bignewy. I see very similar behaviour also on the Msta artillery -- ignores 25mm HE depending on angle of impact. Should I post a video/trk for this as well?

Wrt. the "say again" concept: you could achieve this via adding the tasks as radio command/-s tree, e.g. "TASKS"->"NEW TASK [TIMESTAMP_1]"..."NEW TASK [TIMESTAMP_n]", and in turn have the commands print the task descriptions on activation.

Indeed -- I keep forgetting about this option. Only drawback using this method is you will not be able to control conditioned spawning (efficiently), i.e. if one group spawns, some other group/-s wouldn't.

If you are not into scripting, randomized unit spawning can also be achieved via mission editor functionality only (keyword "triggers"). Randomized spawning of non-units, however, is a different story. Although a bit rusty (but still valid), you might find these simple tutorials by pickinthebanjo helpful: - - There is also a page on the DCS wiki explaining triggers and mission randomization: DCS_editor_Randomization

You might want to either take a better look or check the trk file.

I have noticed that the armored Ural 4320-31 ignores 25mm HE rounds depending on angle of impact. This is happening with the latest open beta version as of today. I have done a quick video on the issue and attached the .trk file. 25mmHE_test.trk

I partially agree.

Hey Gizzy/ED, I think something fishy is going on after the armor and M134 adjustments in the latest patch/-es: depending on angle and/or orientation of some APC types (e.g. AAV-7) , the M134 does no damage at all. However, some APC -- e.g. the BMP-3 -- are completely bulletproof against the minigun, no matter what angle it's hit at. I've done a quick test on that, and I think the current state is not a feature but a bug: As you can see, only if the AAV7 is positioned/facing perpendicular to the minigun, it takes damage. I've attached the .miz and .trk for this video. m134_test.trk m134_test.miz

The mission files are archives -- open them with Winzip, Winrar, etc. Inside the archive you will find a file called mission.

I'd suggest to create a couple of planes with the desired loadouts, and then use a text editor to find those planes and, hence, their loadouts/pylons within the mission file. An example for your request could be (rockets on pylons): ["payload"] = { ["pylons"] = { [3] = { ["CLSID"] = "{FW_190_R4M_RGHT_WING}", }, -- end of [3] [2] = { ["CLSID"] = "{FW_190_R4M_LEFT_WING}", }, -- end of [2] }, -- end of ["pylons"] ["fuel"] = 388, ["flare"] = 0, ["chaff"] = 0, ["gun"] = 100, }, -- end of ["payload"]

I think you are missing that this type of artillery has large minimum engagement ranges (~11nm Smerch, ~8(?)nm Uragan), and their target points might be too close. The min. range is depicted by the green circle if you select a unit in the ME. I've just tested both units and they work fine if targets are between min. and max. ranges.

I have witnessed the same -- I reproduced it in a new mission with some AI Mi-24's and me sniping them in a Gepard. Doing the "right" amount of damage indeed makes them emergency land on water: AI was set to passive defence, running the latest OB as of today. --- Thanks, Flappie -- video is public now.

Give this a try for SP missions.

T-90 uses the controls "Sight Zoom In/Out" to gradually zoom in/out (check CA key bindings). AAV-7 has no zoom.

KC-135 MPRS is in CoreMods\aircraft\AV8BNA\Textures\KC135MPRS, for AI aircraft skins also check e.g. WorldTexturesBMP(1..n).zip in the other folder I mentioned before.

Many can be found in Bazar\World\textures, inside the zip-archives. The archives starting with Y (Y, Y2, ...) contain many of the ground units, if that's what you're looking for.

Greetings -- crashing on PG no matter what since the last OB update, e.g. creating a new mission in the ME -> crash to desktop on empty loading bar (which sometimes shows for a brief moment); extended log attached; using Windows 10 Enterprise. dcs.log.rar