Fri13

It is ridiculously easy with ZU-23-2 to hit a relatively slow moving target. It doesn't matter is it a fighter or helicopter if it is flying toward you, it is easy to shoot down. If it is a flying in a beam, then it becomes far more challenging against a fighter as you need so long advance that it is no use. Against a helo that moves < 100 m/s it is possible, but > 100 m/s plane and it becomes again wishful thinking. As targets that flies over 200 m/s (380 knots) you have 0.2% change to hit a thing. So pretty save to attack utilizing speed. Self-defense is about that, self-defense. It is not about shooting out low level flying objects around you as AI does in DCS. It is just to deny them from attacking you, so flying toward you. Just get the threat get altitude and in MANPADS or radars range. A simple 12.7 HMG does that amazingly well for couple km ranges, but don't expect to hit a fast mover flying around you. But they can't do anything to you either by that way. If they want to attack at you, they need to turn nose toward you and that is when they are very vulnerable for self-defense weapons like 12.7 mm. Take a ZU-23-2 and it will shred them to pieces, and if not that, then at least force them to brake off the attack and deny them from attack. This is why AI in DCS is so stupid that they waste ammunition for flying targets that just goes around them. And there AI has this magical perfect, even a 30-50 degree lead capability. There is a reason why the frontal sector is only armored, like in Mi-24 the bubble canopy is just plastic that normal bullet goes through, but the flat front glass is armored against 12.7 mm or even 23 mm HEI. The cockpits armor plates are as well around the pilots but only against low altitude bullets, they will come in so high angle that they will ricochet from it. A tail boom is behind everything, it is well protected by it location but get good hits there from a side and you have change to rip it off. Changes for anyone hitting you with a small arms weapons, HMG or even 20-30 mm cannon from a side is very small, requiring you to be slow and close. But that is the cold war era. Now you have like CV9040 (or even CV9030) with automatic TV/FLIR tracking with laser rangefinder and it is almost 100% first burst kill for few kilometers range. But those things needs to know from where the attack comes so they can have barrels pointing a proper position to begin. This is why you don't do hovering attacks as you are too easy target, and why "pop-up slide" tactic is in use even for west, where Russia never thought about going for hovering attacks. In a forrested areas engament ranges are usually below 2000 meters at 100 meter altitude. Go lower and you are quickly below 1200 meters. Go to tree tops level and you are mostly under 500 meters. There you are not utilizing much targeting on ground targets, but neither do they engage you so easily. This is the DCS problem that people place units at open where anyone can engage them from 40 nmi if so wanted. While in reality you do not expose your forces to other long range weapon, you force them to come close for knive fight. And DCS doesn't support that almost at all than in few places. If someone wants to advance over wide open area, they will die if there is enemy waiting them to do so. Show that was the only video....

It is not just one video. There are hundreds of cases where missile exploded near, took out another engine or damaged some systems. It is anyways RTB if not landing as soon as possible. But there are as well cases where single explosion took the helo down as burning, it is just more dramatic and people hears those more.

Noticed same thing first thing in the video. I don't know have I ever seen Hind have a curved rotor blades, instead the coned from the root as the photo at bottom. So more as a V than it is now as U shaped. It looked like the those blades are about to give up at any moment.

Sorry, couldn't fix your mistake....

Funny thing is that Theory is a real thing... If it works in theory, then it should be simulated.

The manual says that as every designation becomes TO by default, you have AUTO and guidance on it. Selecting any other target or mark point than TO, will automatically designate them to system. Only two ways to undesignated target exist. Press NWS button to undesignate. Or unbox the DESG in EHSD. Pressing release button = designate. Pressing trigger = designate. Selecting Markpoint or Target Point = designate. Use DMT or INS = designate. Select "Use" in CAS page = designate. No where needs pilot to first go to tick DESG to get designation, than when wanted to designate a waypoint....

What is what I wrote exactly. Hence "for a reason", why they do not make graphics exact. It is not really so difficult.....

TAC-000 the 2002 edition. The 2008 edition for H4.0 doesn't say it would have been modified to different.

This is from S.E.Bulba from russian forum: And that is not even the one I said earlier that I have seen (as it was with the exact display that the 3D animation uses with exact same display and all). What a Chicz as well said in Russian forum is that they went to own graphical visuals for a reason. So instead missiles they have just the triangles and primary threat is circle. This because their system does not react to anything else than missiles.

Still in a factory. Will be rollin out in matter of weeks...

That should only be when the pilot unboxes the DESG after designation exist, and then the target is unesignated (same as pressing NWS) and AUTO etc becomes invalid options. Every single designation steps procedure in the manual says that there is no such step as "Menu -> EHSD -> DESG". It doesn't exist. It is not requirement. It is very specific there. It is as well written that when ever the TD is done with INS or DMT that DESG will be boxed automatically. When the pilot wants to designate a waypoint, then pilot needs to select them with the Up/Down and only then press DESG to create in its position a Target Designation. Selectin any other than T0 will as well designate them (23.9.9). The manual is very specific about methods like how a pilot can in NAV mode designate a target for AUTO or CCIP delivery without MENU -> EHSD -> DESG and switch automatically to AG master mode, have previously selected weapon used with its proper mode (AUTO or CCIP) and all for that weapon and guidance to created TD.

That is.... anyone can do things at the high altitude... But this old coldie... That thing is so crazy in agility.... Hopefully the FM will be properly done.... Look at the 01:30 part in second video.... And KUDOS for that! It is unforgivable that module news and progress reports are not made first here - in the Official DCS forum. But in a private Discord channel that majority doesn't even use, or never find anything from there years to come. History is important, why there should be a record about it.

2.5.1 AUTO Delivery Mode page 2-57, two last paragraphs. 2.5.6 CCIP Delivery Mode page 2-69, last paragraph. When in AUTO or CCIP modes, the release of weapon (successful attack) will add a attack line to the EHSD page that goes through the TD diamond. The attack line is set to heading that was the aircraft ground track on moment of weapon release. The attack line can be rotated once created by using a Course Set Switch if required (for setting example a second attack direction). This should happen as well in the CCIP-AUTO conversions, and likely too when the weapon is released, rockets or gun is fired. The attack line would guide pilot back to area by knowing what was the first attack direction. EHSD_re-attack_attack_line.trk

The DESG is incorrectly modeled at the moment. The DESG in the EHSD should be automatically boxed every time a pilot performs a target designation. To undesignate a target the pilot has two means, either press a NWS/UNDESG button, or press OSB 1 on EHSD to unbox the DESG. This is reported in: Now comes the questions: You have a target designation and you press OSB 5 to activate TACAN. Why should target and TACAN symbols get both the course line? At this moment we have Steerpoint and Target Designation wrongly made, where both get the course line. So we already have not one, but two course lines on EHSD. What should happen when the TACAN is enabled? We should get a third course line? Likely we should have course line priorities as Waypoint -> Target Point -> TACAN and see only a one course line all the time.

Yes, as I said, it is about the updating the aircraft position when no other means are found. It is a nav update. It is not about designating targets on the map, pilot is not creating a system target. It as well talks about slewing the crosshairs and not moving a TD. There are two types of Designation Position updates: 1) WYPT Designate update; and 2) MAP Designate update. A WYPT designation update uses the designation’s known location and its slewed position in the HUD to calculate the aircraft’s position. A MAP designation update uses the slant range and bearing of a HUD designation and its slewed position on the map to calculate the aircraft’s position. A Designate Position update will update the aircraft position and the INS position. You likely meant is: 23.13 POSITION MARKING, second paragraph. Or 23.2.2.2 MAP Designate Update The NFM-000 is just a addition to the TAC-000. You need to first read the TAC-000 to have the base knowledge of the systems, and then read the NFM-000 to see that what changes has been done to systems that are explained in TAC-000. But please offer a newer one. After all, all modules in DCS are suppose to be based to public information without backroom information that is not accessible for confirmation. The information about the DTED in the NFM-000 states that there is no such target destination as we have. We don't have DTED added to Harrier in DCS, and it is a separate map data for the use, a separate map tile set. The NFM-000 as well writes about how example TOO button does only in H4.0 aircraft record the information of map coordinates without altitude information. Point still is, the aircraft doesn't know target altitude via EHSD unless it is a radar MAP mode that would perform ranging to it. And there is no target designation by using a map, but map can be used to update aircraft navigation position.

My Ovgme compatible mod that will change the one line in the KA-50 trigger config to make it Up and Down switch compatible. Here is it content from line 275 and 276. {down = iCommandPlaneModeCannon, value_down = 1.0, up = iCommandPlaneModeCannon, value_up = 0.0, name = _(' Gun Select Toggle'), category = _('Ins Cyclic Stick')}, -- {down = iCommandPlaneModeCannon, name = _('Gun Select'), category = _('Ins Cyclic Stick')},

Only as long that such tech does not cause performance loss to a other brand users. Like if this would be 150% increase to Nvidia users and -20% loss for AMD, then it is No-go. If this is 50% for Nvidia users and 0% loss for AMD, then it should be a green light.

You just said that it works as I said it does... Hence no reason not to implement it as it is not causing problems for AMD users. Yes I know that, why if you read carefully my post, I wrote: "It shouldn't be implemented if it is not very simple". If it takes a 50 hours from one to implement it, giving a Nvidia users XX % performance increase while AMD users receive 0%, then it is worth it. If it takes 5000 hours from five to implement it, then it is not sensible thing to do. Understand the point? That is the case. ED has stated that they do not implement anything that is benefitical for one but not to other. So they want to walk the "middle path" that leads that both sides are suffering as neither one will get the features they would benefit from. These things should be case-by-case considerations by ED instead hardline policies. Hypothetical example, if we would be talking here that Nvidia that has 80% of the market share, would benefit from this feature in VR by 300% performance increase, but nothing for AMD. And it would be just a few hours from couple programmers to implement it. Why shouldn't they? It is a feature and capability in the hardware that someone decided to buy. It is not about does a DCS World work with only Nvidia or AMD. Otherwise we can stop right here every development because Nvidia 7xx series card owners can't anymore play DCS World in VR. The Windows 7 lost its support. The Facebook account is required for Rift Owners etc etc... If one's hardware offers performance benefits that doesn't affect others, and it is acceptable implementation (it is provided by the Microsoft, Nvidia, AMD or someone else for easy work) then it should be considered is it to be added.

KA-50 MCG Trigger.zip

If the technology is not only for one vendor (Nividia or AMD) then it should be implemented if just possible. If it is just for one vendor but not for other, then it shouldn't be implemented if it is not very simple and it is causing extra performance loss to another. And that is it.

No need for special features for common one as it should be needed only for server side in multiplayer, but that is where many fly alone. Make a own group in bindings settings named as (AI Co-Pilot Commands) or something. As it is unrealistic that one flies Kiowa alone for combat. Make it so that only when player is a left side seat the commands are usable, so not on right seat. This is again something that should be in master category like F-14 RIO and Pilot, that you have two separate sets for left/right seats. That you activate/disable by switching seats. This means that you don't share same bindings with seats and so on you can make so that one can't operate otherside functions accidentally. Can bind same joystick button to separate things on both seats.

Unrealistic co-pilot modes are needed. - Level flight. To initiate it you need to fly +/- 3° bank and pitch. - Turn flight. You need to be >3° bank but +/-3° pitch and your current deg/s magnetic turn is maintained that you have when activating. - Auto hover. Not a perfect but one that balances you in 2-3 meters from a hover position. Need to be +/- 1° in pitch and bank, and speed < 5 km/h. And then of course piloting commands for Co-Pilot. - Turn 5° left/right - Turn 15° left/right - Turn 45° left/right with those you can just command pilot to perform one heading correction, and fine tune with tapping couple times if needed to do 10, 30 or 90 etc heading changes. - Slide little to left/right (1-2 meters) - Slide to left left/right (10-15 meters) - Move to left/right (1-2 m/s constant speed) as long hold or when commanded again to stop. - Get down, set altitude to 3-5 meters from a ground. - Go little lower, 1-2 meters lower. - Go lower, 5-10 meters lower. - Lower altitude, 1-2 m/s constant speed until commanded to stop or until 2-3 meters from ground. And same to up, but with with couple extra to get easily to 20 meters, 50 meters and 100 meters pop-ups. Then are other special commands. - Get around. Where current heading is remembered but co-pilot turns helicopter around to return to previous position depending speed. So perform a small circle to little back. - Evade. Where pilot performs same but with CM and maximum speed, so further back. Speed adjustment - Go slow, 5-10 knots - Speed down/up by 10 knots Notice, there is no need for AI to do these automatically, to adapt to them etc. Just have a Co-pilot AI to do exact requires moves to gain those in limits. So one can example get to hover behind building or trees and then perform pop-up, slide, get in cover, and get helicopter fly circus as manually set attitude.

I agree that chocks should be removed as they are so buggy, until they can be properly programmed. It has been years and we still have so simple things as wheel chucks causing severe problems.... It shouldn't be difficult really. Chocks are status modes. If chocks are On, then wheels doesn't turn or move as they are locked to terrain and add a 3D model around wheels. If chocks are Off, then wheels are free and remove 3D model. I haven't seen DCS model anywhere proper tire physics where you could roll over the chocks with ie. full afterburner. And tires would interact with them in slow forces pushing in them. And this would mean in Harrier that you would get over them with vertical take-off as they would be just obstacle without actually locking tires on surface.

CEP = 50% of the shots should fall inside the radius, rest to go outside. But if CEP is 500 then it should be about 1000-1500 meters at maximum where you can have majority to fall in.

Well, we don't know what the KA-50 would really have become, and what it was between first serial production standard and after that, but what is known is that it went plenty of upgrades at the end. So most fictional stuff is really still just the MWS integration to KABRIS. It was better yes back then, but maybe there is something with the lighting that makes it very short range one? Some expo specifications states that the President-S has in those UV sensors a RF antennas too, as well that the turrets has the RF jamming capability against RF missiles. But it doesn't specify is it only for a KA-50 set then (that would be safer to assume). If we consider a common war logistics, less you need to transport and manage a unique parts then better. Meaning that it is safe to guess that in final form of the KA-50 + KA-52 plans it would have been as much as possible with same parts, only having really the front section (cockpit) as different. Meaning that all wings and computers and all would have been pretty much same all way to the MFCD's and sensor pod and all, except KA-52 would have had something little more as extra. Now the logistics and maintenance would have been far more easier when you have mostly same parts shared between your war machines. What is actual KA-50 collective weapon station hat functions? It was stated that it was mistranslated.... That it is not a Inner + Outer + A/A + All (inner + outer). As if you think about it that way as it has been so far, you don't need a separate A/A switch if you have only Inner or Outer stations. You would always select A/A missiles with that. And ALL (both) is required because if you have both stations with rockets or bombs, you want to be able select separately inner, outer or both. But how you would choose a third station that is only for Igla missiles? You would not make "Outer, Center, Inner, All". That is why we would need the proper information that what is the station selection hat functions. In the KA-52 later on when it got the MFCD's for weapon selection (first ones were with same as our KA-50), it got as well the three stations and so on you choose wanted weapon from MFCD easily. And if you have Vikhr with a Anti-Air programming functions, as A/A mode (activate fragmentation sleeve and proximity fuze enabled) and then A/A mode with Head-On mode (proximity fuze delay removed so Vikhr doesn't fly past the fast moving target that flies toward Vikhr), then you wouldn't need some of those buttons with the hat to select A/A mode. Example you would have just the collective A/A mode to set Vikhr to A/A mode. And then have own unique button to set Vikhr proximity fuze delayd or instant in other panel. Or you wouldn't have a A/A in the collective hat as you have A/A mode in the panel next to require A/A HO mode as you anyways need to switch there. Considering that once you activate Igla missile, you activate its battery and you have limited time to keep it operating. So you don't want to accidentally activate them. Where again a hat with UP position for A/A mode makes more sense as you usually use just left/right ones. With Igla you don't want to take hand off from collective or cyclic to do enable them, as in fast situation you need to be just activate them purposely and get them launched. And that is where the collective hat is good place as you can do that, but not too easily by accident. When taking in consideration that you are not going to hunt aircraft with helicopter, it is just for self-defense and for that you don't want to waste your AT missiles or Rockets, you just add third station to allow equipping them if and when needed. Similar thing as with Apache, that capability is there but as it is not required as there is no such scenario, you don't even train pilots for that and everything is hold in the dry dark warehouse for the day when Apaches fly to situation where they really need to be avoiding fighters.