Kappa-06MHR

I have make tests and I agree with you : - Laser range sometime decrease under 60 sec (40 sec) without explaination. It reduce range of shooting for the budy. On this case, laser go to "pause" more quickly than expected. - when trying to make multiples shots, sometime it work well for the two Kh-25, sometime, only one Kh-25 do the job, the second fall. And when we try budylasing with two budy, it work for only one budy... I have try with two KA-50 firing 4 Kh-25. There is alway a fail for one of the two KA-50's misssiles

It was a shame that ED didn't make the possibility to do budylasing with other craft, JTAC unit with FAC mission or Su-25. Any moderator can explain more about that? Does ED have any plan to improve budylasing between KA-50 and other craft?

Yes; I have try 111, 1112 & 1113 with Spot.createLaser() It does not work

Does anyone know the 3 laser codes used by the KA-50 for the Kh-25? I want to try budy lasing with Su-25 T, or use JTAC soldier with FAC mission, or try to use lua function : Spot Object Spot.createLaser(Object Source , Vec3 localRef , Vec3 point , number laseCode) The objective is to create a laser designation for the Kh-25 ML. But there is no documentation on the laser codes used by the KA-50. There is a 3-position rotary button in the cockpit to change the laser code of the KA-50, without knowing which laser codes are used. @ED, can you give us some feedback? Is budy lasering possible: - Between devices of different coalitions - Between Russian aircraft (such as the Su-25 and the KA-50)? Buddy lasing is already possible between KA-50 knowing the Kamov laser codes would allow us to carry out tests between different devices

And mine : https://www.digitalcombatsimulator.com/en/files/3334726/ Bourget's style

I challenge you to succeed in firing 3 complete 12 Vikhrs loadouts without burning out your laser, even if you pay close attention to the cool down times. It always burn somewhere between the second and the third loadout.

Bullet on glass, rain on glass.... KA-50 is the first module of DCS, the one that all begun... But we also have the feeling that it is the one that is also the most forgotten by ED

Respecting the counter will certainly preserve the laser for longer, but even if you strictly respect the cooling counters, you will realize over a long gaming session with several resets that your laser will always end up being burned. Even if you're careful. After around 24 Vikhrs fired, the laser will always end up being burned, and respecting the counter will just prevent you from burning out even sooner.

Realisic. It is the KA-50Sh with Sam<profanity>'s optronic turret. But this is the 90's glass cockpit's KA-50, the one we hope for BS-3 but we never have.

The laser of the Kamov always get damaged after ~ 24 missiles (with one rearming), even if you stricly wait for the countdown. An option for the ground crew to change the laser (with motor hot, quick time fix), will be a good solution indead!

ABRIS uses the GLONASS navigation system based on a satellite constellation to navigate. It is a Finnish civilian navigation computer added temporarily during the design of the Kamov prototypes. The Kamov's navigation instruments, the compass and the PVI are based on the inertial unit. Why, when the inertial unit is not aligned or not reset (INU heading is "incorrect"°, that of the ABRIS is also wrong? Why does the heading of the ABRIS always seem perfectly aligned with the heading of the inertial unit? Why is the Abris, which is a navigation system completely independent of the inertial unit, erroneous if the alignment or recall of the INU is not done? Normally, ABRIS could almost be used to manually realign the heading, if necessary, for example. The INU's problems should never impact the course set by ABRIS. However, it is obvious that the ABRIS information is based not on GLONASS but on the INU, since the precision errors of the INU are also passed on to the ABRIS, that the non-alignment of the INU gives a totally wrong course on the ABRIS... Can we make these 2 systems independent?

Is anyone had tested buddy lasing between Kamovs, SU-25 since BS3 and the remake of the Kh-25ML ? (ex : smoke on engine) Is it work ? Is the laser code of the Kamov is 1113 ? Is the 3 position switch of the Kamov work, and is it really change the laser code ? If yes, what are the three possible laser's code ? What are thoses lasers code for each position ? Does it work with JTAC ? I think buddy lasing is a very great fonctionnality to increase cooperation between aircrafts, but ED doesn't say much on this subject, a vagueness seems to have been maintained for years. The KA-50 and the Su-25 could cooperate together, it seems, but very little practical information, even the manual does not indicate the laser codes of the 3-position switch, nor even if this switch is functional...

A new version of Arleigh Burke-class ?

I'm awating bridges, for my part ^^

up

Frenchpack 5.0 !! https://www.checksix-forums.com/viewtopic.php?f=435&t=219504

Hello Flappie! I don't see anything on changelog, is there any fix schedule? (I must try if the issue always exists, but I try in december, and still not fix, i must try since the last update.)

Hello @ED, any news ?

I hope the addition of other Turkish assets ^^

It will be so cool. But a Lianing livrery for Kuznetsov is also accurate

Thanks a lot, it will be very very great !!! With the addition of bridge to solve pathfinding issue, this map will be so great !

PHL-11

They have Rafale!

I will try to explain the problem with this map in pictures: No bridge to cross one of the largest cities in the Nile Delta, Mansourah, supposed to be a real road crossroads : No bridge at Shirbin too, another city on the Damietta Branch of the Nil : In Damahur, there is the bare minimum to cross the largest rivers, but practically nothing to cross the small rivers. 80% of the bridges are missing! And all this for the major cities of the Nile Delta... There are practically no bridges in the smaller cities or in the inter-urban space! Consequences on pathfinding with a practical case: I take a vehicle on the coast and I want to go to waypoint 1, south of El Mansura: Despite direct roads, there is no major bridge around the city, the convoy is obliged to do a very large detour to the West and the South between Tanta and Al Zaqazik I now want to take my convoy to Waypoint 2 : New Damietta. While with the expected routes passing through El Mansura (there would be 65 km of road), the convoy will literally take a 200 km detour passing next to Al Salihiyah, the Suez Canal and passing through Port Said!!! Ok. Well, I want to go back to El Mansoura for my Waypoint 3, but this time, I'm going to stay on the same side of the Nile, I could probably hope for a direct route since I'm not crossing any major rivers..... And Well no ! Even so, the lack of bridges over simple small streams forces my vehicle to make a huge detour, returning through my origin point. It is practically impossible on this map to have a fairly direct route because of the quantity of waterways and the total lack of bridges!!! And for my last waypoint 4, I'm going to push the pathfinding problem of this map to the absurd: As the crow flies, my waypoint 3-4 is 35 km. By road, it is practically the same distance theoretically since there is a direct route between these 2 waypoints. But the lack of a bridge will force you to make a detour of around 160 km! These absurd pathfinding problems can be reproduced almost anywhere in the Nile Delta, making this map a real headache for a missionmaker in order to determine convoy routes, or coherent road axes. However, it would not take much to solve this problem: Simply the addition of a hundred bridges scattered at least in all the major or secondary cities of the delta, and on all river routes. For me this problem should be the ABSOLUTE PRIORITY of OnReTech, because in my eyes it is considerably more important than adding more details to the pyramids, adding new types of trees or buildings... The map must be PRACTICAL, otherwise, it will be shunned by missionmakers. It doesn't seem to me that these additions are that complicated to make, but their importance is crucial for the appreciation of the map! I wanted to do some dynamic missions on this new map which excited me and which I found magnificent: I quickly returned to the Syria map, because I couldn't do what I wanted due to the total lack of bridges... It's a shame for a suh beautiful map!! We are not only fly over the Delta. We make CAS missions for Helicopter and CAS plane. So the roads must be pratical for convoy!

I love this card, it's really fun to play. On the other hand, if it is very rich in roads, it is extremely lacking in bridges, to the point that drawing up a convoy route to cross the Nile delta considerably restricts the possibilities. For the map to be truly perfect and usable, you have to add many bridges across the delta, like thoses who really exists ! Once this is done, the map will be really excellent! As it stands, it limits a lot of possibilities, it's a shame