Kappa-131st

UP. No news from ED since there annonced the new fog & dust storm, 2 years ago. No news too about the cloud that cut visual detection

It worked only between KA-50 and don't have any "code" (like "1688") (There is a button on the cockpit with 3 positions for laser code, but it is not a laser code who work with other aircraft)

Thanks a lot ! Is this possible to have MGRS minimum grid to 1x1 km ? Actually, there is only Caucasus map witch have MGRS's minimum grid to 1x1 km, All other map have MGRS's minimum grid to 10x10 km. MGRS 1x1 km are very practical in multiplayer for coordinating between different devices that do not have a datalink. (Ex: When working between KA-50 and A10-C). Providing a 1x1 km grid helps accelerate joint cooperation

It's a shame that you must download mods to have a diversity of infantry. The community ask for more infantries units for more than a decade, et ED promise us more infantries models for at least 3-4 years. Why can ED not manage to put diversified infantry units when the community can? All of the mods below were created less than 3 years ago (After ED's promise...), there are long-range ATGMs, short-range rocket launchers, snipers (anti-personnel or anti-equipment), mortars, grenade launchers, tripods with ATGM, MANPAD or 12.7... There is a real threat even to helicopters! Currenthill : Dimitriov : And more and more mods with infantries or civilians... ED, if you don't have time to create new models, suggest an integration of Currenthill models like you did with massun's pack!

Thanks a lot !

+1

Hi ED... When did you release the new infantery you tease us in.... 2021 !!! ED's news in 2021 : https://drive.google.com/file/d/1RD9nFvH7bbjUUqXcDs7AOG0A_lj1t6EP/view

I did another evening of tests with 3 allies, and the result is quite irregular: On several passes, the laser guided well all the missiles of my buddies, and on several others, the laser only guided a few missiles (often of the same device)... On the other hand, we tried different tests (at different ranges), and here are some of the returns that I observed: When the missile is fired at its range of 8 km, the hit rate is relatively good, and the countdown on the HUD goes from 30 to 0, where the laser cooling turns on for 20 seconds. Observation: Barely fired, the missile guides itself towards the target When the missile is fired at 9 km with a slight loft, the hit rate is quite good too. The missile will go straight for a few seconds before the guidance is activated, around 8 km. It will then tend to rise to fall back on the target. At 10 km, the missile must be fired in loft, and its hit rate drops drastically and depends a lot on altitude. You have to wait a good 4 seconds during which the missiles go straight before the guidance is activated (if it is activated, because the failure rate is quite high). The failure rate can also be due to the cooling of the laser which can be activated before the missile hits the target (which very often happens when the missile is fired more than 10 km away). But what is interesting is that the laser countdown at the time of lock no longer starts from 30 sec to go to 0, but starts from 60 sec, and somewhere around 30-40 sec countdown, the cooling starts. active for 20 seconds (interrupting the countdown which started from 60). at 10 km+ the missile have a very hight probability of fail because either the seeker cannot find the laser (the missiles fall like cans), or because the laser goes into cooling before the end of the guidance (loss of guidance at the end, the missile spits out near the target) Another observation: In the missile configurations DCS World\CoreMods\aircraft\AircraftWeaponPack\kh25_29_family.lua Line 668 : max_seeker_range = 8000 So the Seeker of the Kh25Ml have only 8 km of range. All the documentation I find on the net indicates that the range of a Kh-25ML is around 10-11 km. This range is not limited by the propulsion (the Kh-25 MPU which has practically the same propulsion has a range of 40 km), but is limited by the range of the seeker, which does not exceed 10 km. Also I am surprised to see this range restricted to 8 km in the DCS files. For testing purposes, I tried to increase the seeker range to 10 km, and indeed, the behavior of the missile becomes interesting: - Fired at 10 km, the seeker immediately spots the laser designation and will guide itself to the target. - Fired at 11 km, the missile must travel one kilometer before the missile manages to guide itself onto the target (with a probability that this will not work) - Fired at 12 km, the failure rate is very high, either because the seeker does not find the target, or because the laser cools before impact I therefore think that the missile's seeker should be increased to 10 km (which would remain much less than the 16 km of the Hellfire or the 18 of the AGM 65.)

Do you plan to make French units after the UK pack?

Still no rain on KA-50's canopy. Can we hope to have beautiful effects of rain like on the F-18 ? Thanks!

I don't have track (We had make thoses tests month ago), but I will try to remake tests to give you tracks & tacviews

True, Kh-25ML need to be shot with a loft. (without loft, they often drop... Even with loft, they don't have a perfect accurency) And there is another issue with Budylasing : You can not make budylasing for many KA-50 at the same time. Ex : There is a big ship with CIWS you want to hit. To maximise the chance to hit, one KA-50 make the lasing of the target, and two other KA-50 make the shots (with one or both of there Kh-25ML) The objective is to overwhelm ennemies's CIWS with too many missiles. With my squadron (06MHR), we make numerous tests : Buddylasing work perfectly for one budy but canot work for many KA-50 who shots. We have test : 1 KA-50 lasing, 1 KA-50 firering 1 KH-25ML => Ok, 1 splash 1 KA-50 lasing, 1 KA-50 firering 2 KH-25ML => Ok, 2 splash 1 KA-50 lasing, 2 KA-50 firering 1 KH-25ML per Kamov => budylasing work for only one Kamov. 1 splash, 1 drop 1 KA-50 lasing, 2 KA-50 firering 2 KH-25ML per Kamov => budylasing work for only one Kamov. 2 spash from one KA-50, 2 drop from the other Kamov PS : Of course, for our test, we are all in the same laser code position, and of course, with laser in designation mode for the one who lase, and laser off for the others. We have make a whole evening of tests, and we conclued that budylasing seam to not working with many Kamov who shots. We also try to make budylasing between KA-50 and SU-25T. Does not work at all It is a pitty because it will be very interesting to have sinergy between red coalliton aricraft, especially for aircraft with the same armament and similar technologies like the KA-50 and SU-25T -------------------------------------------------------- I tried to understand which laser codes were used by the Kamovs (we have 3 laser positions to adjust without knowing which laser code is used). For this, I tried to "simulate" budylasing using the "Spot.createLaser" function which allows you to generate a laser by configuring the code. https://wiki.hoggitworld.com/view/DCS_func_createLaser Thanks to this function, I created / deleted laser codes ranging from laser code 1000 to 2000 (by incrementing the laser by 1 every second) I put myself on arming KH-25ML & laser off and prey for my seeker to react to one of the codes laser, but it didn't work... I deduce that the Kamov's laser codes are not configured like the others laser code and are does not work for budylasing with another aircraft (like the Su-25) or with a laser designatior carried out by JTAC or created with LUA's function.

One of the great features in the Black Shark module when flying in a squadron is the ability to prepare drawings on the map for a mission using the "PREPARE MISSION" function then drawing various points and polygons on the ABRIS, which allow us to customize the display of our MFD for more efficient teamwork. However, I spotted a label's bug for a certain type of point. When drawing on the ABRIS, you can choose points such as : refpoint type (cross) airport type (pink circle) obstacle type (triangle) NDB beacon type etc... We can then specify the name/callsign of the point (in my example, P1, P2, P3 and P4). Screenshot 1 : The preparation of the mission And after saving the mission, when we take our aircraft, we see that the points are actually displayed in the ABRIS. But for all points of type "REFPOINT", there is systematically an unwanted label "REFPOINT" which is also displayed on the ABRIS. Below is a screenshot 2 : In the mission It seem to apear only for "refpoint" (In my example, for P1 and P4, there is no unwanted label in P2 and P3) Can you remove the unwanted "refpoint" label for this point type, so they work like other point types? Thank you !

How many years we must wait before ED take the pilot body back to the KA-50 and why the pilot body has be removed at first (cause we have a pilot body on BS2 before...) We had paid 3 time this module, can we have a little consideration from ED team ?

Are you sure ? The error message you show ("weapon does not exist") does not correspond to the line you indicate, (There is no questions of weaponry in this line). The following lines is supposed to guarantee that the weapon exists: if not event.weapon then return false end -- if no weapon : exit (ex: crash) if not event.weapon:getDesc()["warhead"] then return false end -- if not an ogive : exit so if your weapon does not exist (nil) then it exit the function Are you sure it isn't another script who bug ? (line 724, this script have only 15 lines...) ?

I agree that there remains ambiguity about who is really responsible for this withdrawal request. But I don't see how it couldn't be Ugra Media, ORT is talking about a request coming from a Thirt part, and all the removed territory corresponds exactly to what currently exists on the Ugra Media Syria map. Who is responsible for this request therefore becomes perfectly obvious to me. And if the partners had discussed among themselves instead of making cuts in regions already delivered to users, this suspicion would not exist. This type of problem should have been resolved before the delivery of the Sinai card. Additionally, Ugra Media is not left out as their own map, Normandy 2, encroaches on ED's "Channel" map...

Likewise, if Ugra Media does not reverse its decision IMMEDIATELY, I will no longer buy anything from them or encourage anyone in my squadron to do so.

So it's Ugra Media that we have to thank for this...

Why North of Israel have been removed in the last update ? Is this a update or a regression pack ? I have mapped many missions in this zone... Is this a Joke ? You littary removed Haifa !! They want us to refound the map ? Before update : After update : HAIFA before and after the update : @OnReTech any explaination ?

The addition of Bridge in El Mansura help convoi to cross the Damietta branch of the Nil, it is a good addition But we are very far from having smooth roads, and there is still too much lack of bridges, especially on the main roads which are cut off at each small stream... The El Mansura bridges help pathfinding determine East-West routes, but there are still very serious problems to resolve on all North-South road axes, as can be seen in this map. I am quite disappointed to see that this problem of the lack of bridges on the main roads has not been sufficiently prioritized, and has fallen behind cosmetic developments, while this problem partly prevents the editing of missions in the Nile Delta. , for example by preventing armed convoys from going up the Nile without having to make exasperating detours. The addition of a bridge on the El Mansura road junction is a very good thing, but to the extent that half of the roads do not work with pathfinding because of the roads which are cut at each watercourse, the problem major that I put back 6 months ago still remains present... These two roads are the only ones that function as a North-South axis: In the entire Nile Delta there are only 4 exploitable North South axes... null

Same Issue with EYE TRAKING... ED please make a FIX QUICKLY....

Yeah!!! We need a NUKE MOD

Thanks for checking!

Any news of the additions of numerous bridges to make pathfinding usable ?