shagrat

The most pressing issue, still is mic clicks, beeps or any sound to have a feedback for PushToTalk button pressed and release, as well as incoming transmissions. This basic audible info, if you correctly press and hold the PTT button is a key component to make a simplex transmission based radio simulation work. Press PTT - click - talk - release PTT - click. Hear a click - listen and don't press PTT - hear a click - channel free...

Hello everyone. Is there anyone who has the Komodo TEDAC? Could you please PM me. Thanks in advance.

You may want to fly MiG-21, then?

Well, it does work for everyone else, but you, it seems. I posted above with some pointers where to find details and training aid. Did you have time to go through the training mission and learn how to operate the rockets, or are you just trying to wing it quick and dirty and wondering why things don't work out? If it is the latter, nobody will be able to help you. If you are trying to learn the procedures and actually struggle with the training, or bores sighting, someone may be able to help. As posted by razo+r there are keybinds to move your virtual head in the cockpit, if you don't have a head tracker (default RSHFT+RCTRL+ Keypad 2, 4, 6, 8).

Hi, Dimitry. First an important question: did you uncheck the "Weapon Trigger Guard active" in the AH-64D special options, or bind a key to the trigger guard in the controls, so it isn't a simple issue of the safeguard preventing you from firing? The "WEAPON?" message in the IHADSS shows, you have not selected (WASed) a weapon, but it doesn't hurt to double check the trigger guard. Also, the procedures for rocket employment were not changed, since the EA release of the Apache and all three employment modes (direct, indirect and coop) work as described in the manual and explained/demonstrated in the training. With that out of the way, did you do the Training Mission No. 5 "Unguided Rockets"? I highly recommend to first read the section "Aerial Rocket Sub-System (ARS)" page 343 ff of the chapter "Weapons Employment" in the "Early Access guide" (Program files/Eagle Dynamics/DCS World/Mods/aircraft/AH-64D/Doc/DCS AH-64D Quick Start Manual EN.pdf) and if you have the time, the chapter "Tactical Employment", as well. This will familiarize you with the operation of the rockets, especially as with George AI, you need to understand both the PILOT tasks and the tasks normally done by the CP/G, that you need to command(!) George AI in addition. Flying an aircraft that requires two a person crew IRL alone in DCS means an even higher workload and complexity. IRL Apache crews are trained for quite some time, full time, every day, so each pilot and CP/G can operate both seats, it isn't a simple "hop in, point at enemy and press fire" kind of thing. Take it slow. Do the training step-by-step, listen to the instructions(!) do not rush through. Then train one method (direct fire PLT with MAN RANGE), until you are comfortable and can remember the steps. A checklist does help, as well. From what I've read, crews will go through a checklist, before a weapon engagement whenever possible. -PLT - rockets WASed -C/PG - rockets deWASed -Verify HAD - RKT NORM -Verify WPN Page - QTY and TYPE selected -Verify A/S (Master Arm) - set to ARM -Range Source - select MAN (enter distance) or AUTO Then you need to look at the intended impact area (hold the LOS reticle over the target) and maneuver the helicopter so the nose points in that direction and the "I" (Rocket Steering Cursor) aligns with the LOS reticle. If you have manual distance set fire when in range, if you have Auto-ranging set, when the Rocket Steering Cursor is solid and you are closer than 3.500m to get a minimum of precision. The theoretical range should be about 7.5 km, but the dispersion of the rockets is insane at that distance. So if you don't plan on an rocket artillery strike with all 38 rockets as a barrage, get close and align carefully. For direct fire in Coop mode, have George WAS rockets as well. Verify HAD shows COOP and George will put the dashed target marker (ACQ source TADS) on the target you made him track from his list. Now simply align the "I" (Rocket Steering Cursor) with your(!!!) LOS reticle (not the dashed ACQ source) and if the Rocket Steering Cursor is solid and no "Inhibit messages" on the HAD, pull the trigger. It takes some practice to understand and get good with the rockets, but they are quite fun.

In the Flight Manual coming with the module on page 91 and 94 are two colored tables, that I did print and laminated, when I started learning the HOTAS years ago. Memorize the switches, buttons, hats names (DMS, TMS, MasterModeControlButton, etc.) and if you employ say AGM-65 Mavericks, reference the column on the top. Now every function of the respective switches/hats are listed in that column. But as Yurgon pointed out, you need to understand the HOTAS concept of short and long presses and how the same buttons do different things with different sensors, or weapons, first.

Again, blast damage is the only thing simulated in DCS explosions. There is no fragmentation, thus no splash damage. The problem with killing any ground unit is that blast is calculated as a damage value. So in a way too small radius everything takes damage. Armored stuff takes more damage, but at the same time unarmored vehicles and before the damage model adjustment even infantry could take quite some hits without even flinching. What the script does, it ensures, that at least in that small radius unarmored stuff dies (it would be enough to incapacitate, but DCS can only do healthy, critical hit, or dead). The drawback is a dozen rockets will kill a tank, where IRL the tank would likely "just" have been shredded and the tracks damaged, periscope, mirrors and targeting equipment damaged, but it would be able to limp around and fire blindly. That said, the thing is, for me at least, to decide on the mission in the design phase and depending on opposition to use, or not use the script. A helicopter only scenario with lots (more than you would tackle with 2-4 helicopters IRL) of light armor and vehicles, I prefer the script over the frustration of needing to rearm for 30-40 minutes, simply because the 26-38 rockets' blast damage wasn't enough to eliminate 3 trucks and a Grad-launcher on a clearing in a wood, because the rockets did not have direct hits. For a counter insurgency with lots of infantry and a couple technicals and AAA with the occasional BTR it's fine without the script, since the rockets can take out infantry.

If you read the code, you will notice how it works and that it doesn't change the "splash"-damage (specifically because it doesn't/cannot change, any Lua files where the weapon parameters reside). If you would test it, in addition to looking at the code and compare the results with stock DCS, you will notice the actual effects are marginal (e.g. you still can't kill main battle tanks with a handful of HE rockets, but the infantry in the middle of a 4-8 rocket attack will no longer magically survive. Basically, after ED fixed the armor/damage for the infantry units a while ago, the infantry is dead, either with and without the script, but the area covered by the explosion is still the same, with or without the script. The thing is, that ED does not model fragmentation of explosive weapons, at all. You have blast damage only calculated from the explosive weight in the weapon definition, which is totally unrealistic, as a major lethality factor of any fragmentation weapon is the little pieces of metall shredding a certain area around the explosion (bomb, HE-shell, HE-rocket, even an RPG or handgranade). ED adjusted some weapons (by tweaking the explosives blast), but this still isn't remotely modeling actual weapon effects. E.g. blast damage does less damage to trucks than even a handful of shrapnel through the motor block would, let's not talk about infantry (try dropping a CBU-87 - blast damage never adjusted - on a battalion infantry in parade formation), or unarmored, totally exposed SAM radars and launchers. If a bomblet has a direct hit, you're fine, but no fragmentation that IRL would utterly shred the SAM site. In the end you don't need to "use" the script to simulate at least half-heartedly realistic modeling of what fragmentation damage would do. I personally don't use it in most missions I create, since ED fixed the infantry damage and rockets and 30mm HR shells can finally kill infantry. On the other hand the blast damage from ED's implementation magically kills infantry behind buildings, behind tanks etc. because it has a damage radius and everything inside a blast radius is damaged no matter what. That means danger close implementation of guided 500lbs bombs is nothing like a real bomb. Infantry standing in the blast gets killed even if shielded by a building, but at the same time the actual fragmentation radius in reality is at least 5 times higher than the blast damage modeled in DCS. If we only assume the RED 10 (Risk Estimate Distance where 1 in 10 people will be incapacitated) used to define "safe distances", we should have damage effects in 200-250m distance from the impact of a 500lbs bomb... Last I tested the damage effects to infantry end at about 40-50m. So I personally wouldn't call simulating at least a small amount of the actual damage effects of real weapons "extreme hand holding". If you need a tough challenge and hone precise employment of weapons, we can use stock DCS, to make killing stuff harder than in real life. On the opposite we need to be aware the current stock blast damage model, does kill everything in a certain (too small) radius, with no fragmentation and thus no shielding effects of vehicles and buildings. If someone's interested, the "Geneva International Centre for Humanitarian Demining" has some interesting study on weapons effects in populated areas. https://www.gichd.org/our-response/policy/explosive-weapons-in-populated-areas/ The report can be downloaded here: https://www.gichd.org/publications-resources/publications/explosive-weapon-effects/

Small, deliberate movements. Slow, rather than fast. Put an Apache on an airport, with an empty ramp and space around you. No weapons, 60% fuel. No enemies and a slight breeze of no more than 5kts. Remember to hit the pedal brakes once to unlock the parking brake(!) and then pick up the helicopter into a hover. Try to accelerate forward slowly(!) and keep the altitude at 100-200ft. Speed up to 60-70kts and decelerate again to 20-30kts. Slow and deliberate movements of the stick. Practice this transition from hover/slow forward flight through translational lift and back to a hover again. Add gentle turns and try to keep your altitude from oscillating. Slow and gentle, don't try to rush. If you get more and more comfortable with the coordination of cyclic, collective and pedal inputs, you will notice muscle memory building. Movement and coordination just happens and you will be able to pay more attention to things beside the instruments and your immediate surroundings. Don't worry if you have moments in between, where you feel like you are all over the place like in the beginning, that's totally normal. For me muscle memory usually "clicks" after a couple days to a week and a half of training every other day. If you don't use an extension on the cyclic set curves so the center has more granular control. You rarely use full deflection on a helicopter. Curves are not ideal, but it helps with fine control you need to counter the small drift movements. Things to keep in mind, the Apache is heavy, so despite being pretty agile and maneuverable it has mass and declaration/stopping takes time! If you want to stop into a hover, plan ahead. Rushing at tree top height with 130 kts and trying to get into a hover behind a tree line some 1800m in front of you won't work. If you get close to a battle position or a cover you should have decelerated, already. At 40-60 kts it is way easier to slow to a hover, than 90-120 kts. Slow and deliberate.

That's actually the best workaround for now. Grimm's fork does a good balance between enhancing the weapons effects and just adding more explosives. I tested the 2.0 version before he released it and the damage radius for the rockets is pretty much the same, but the damage dealt is increased. So it's still close to the real thing, but counters the resilience of the DCS ground vehicles. Grimm did a great job there with tweaking damage, but not overpowering individual weapons. Only drawback is, you get used to it and joining a server without or playing a campaign can put you in an "involuntary hardcore mode"...

That's what they were designed for... A rocket is not an anti-armor weapon unless you have APKWS and those are only really effective against light armor. Anti-Tank Helicopters use stealth, standoff weapons and short time of exposure to enemy fire to fight tank platoons. Apaches in Afghanistan were shot down by RPG and 7.62mm ...no AAA, no MANPADS, no IFVs with 20mm autocannons. We need to learn tactics and optimized weapons employment. Unfortunately that still won't solve the AI shortcomings and lack of detailed damage modeling. Though, ED already started working on the AI stuff. Most prominently infantry is now no longer armored like a tank on two feet, in rank formation they actually use fire and maneuver when in contact with an enemy, Mk-20 bomblets have been fixed/enhanced... Unfortunately ONLY the Mk-20, and critical damage seems to have been at least partially implemented as I have seen mobility damage, suppression effects(?) to some vehicles at least.

That's a long standing issue with the AI and ED seems reluctant to rework all the damage models for ground forces. In another thread, it was brought up again and IIRC Nineline said he will press the issue. The thing is, it seems the root cause is the AI targeting algorithm. To me it looks like they treat aircraft similar to stationary or slow moving vehicles for lead calculations.

Depends highly on your tactics and mission design. Trying to hover inside the weapons envelope of armor and AAA is a bad idea ( in DCS and in real life). If you can't sneak up on the flank or rear, you need to be mobile and use evasion, preferred with your wingman knowing what he's doing and flying cover for one another. The AI is incredibly (unrealisticly) good in calculating lead on the fly and eyeballing your flight profile, even at lowest skill setting, which is my default for ground forces for this exact reason. But despite the overperforming AI it is still possible and a lot of fun, to use all the Apache's weapons to good effects. Use rockets against their intended targets, only! Infantry and unarmored/very lightly armored vehicles. Since ED fixed the "armor" of the infantry/insurgents rockets and HEDP work pretty well, against an advancing platoon of grunts or a bunch of insurgents and a volley of 4 M229 close to an unarmored truck, a technical works pretty good. Or if you manage a direct hit on a M113 or BTR-80 it will take it out or at least cause considerable damage. The performance of the rockets should be better, sure, but they are designed as an airborne artillery weapon, intended to allow for rapid, mobile fire support against advancing motorized infantry. More modern IFVs and Tanks are typical targets for Hellfires or buddy lasing for a GBU-12 from a jet or bomber. Still we definitely need adjustment to the damage dealt to unarmored vehicles like SAM radar, launchers etc. that said, the Cluster Munitions have the same problem, though ED adjusted the Mk-20, but only the Mk-20, unfortunately. On the other hand, the US had multiple AH-64 shot down... and the enemy had small arms, the occasional DSHK, but managed to skillfully use RPG with timed detonation (airburst) to great effect. I know from experience this works pretty well, for the DCS insurgents, as well. One RPG can ruin your day. AAA and APC machine guns is something you need to anticipate. If you can't remove those from a safe distance the Pilot needs to focus on the target area and watch for tracers. If you get shot at, evade, not an aggressive break turn, a smooth deliberate change in two dimensions (speed, vertical, horizontal) as the gunner aimed at the point you should be in the future. If you can't get a good shot, abort and evade, coordinate with your wingman so he's in a position to fire at the enemy while you evade and reposition. There's a reason aircraft come in flights of minimum two. Despite the popular belief, the Apache isn't a dedicated SEAD/DEAD asset.

There's a lot of the generic declassified stuff available (even from Amazon) and for "mission" planning (in DCS) I actually prefer the trusty CR-3 most of the time. With multicrew it's even viable to hand over controls and grab paper charts and recalculate some legs, but why would you not consider to simplify those tasks when designing the system? At least the option to enter both volume and weight... Well, in the end it is how it is. Guess, today the developers of the Apache systems would do a lot of things differently, anyway.

That's not what I meant, or was remotely implying, but from most if not all accounts I came across, after let's say 3-4 months into deployment fatigue and constant stress all take their toll. What puzzles me, is these simple things, that under high stress levels and urgency, combined with fatigue isn't this little detail something the designer of an aircraft want to omit? I mean, yes you can do the math, but why add this risk, instead of consolidating measures. Just because you can simply do some arithmetic to get things going, it does not have to be a good idea. I always thought, especially in military aviation the goal is to minimize the risk and give the guys the best chance to achieve the mission goal. No offense meant, just my personal thought on "on-the-fly" conversion under high pressure.

Just looked at a "conversion table" for aviation fuel... You imperial guys do take a lot of drugs, don't you? Are we talking US gallons or Imperial, I guess US? Then 50 lbs is 7 Gallons, but 100 lbs is 16 Gallons and 200 of course is 30 Gallons not 32 and 300 lbs is 46 Gallons? Why is even the fuel handled in different measurements in the same(!) aircraft? Doesn't that beg for mistakes endangering service members? And even if nobody cares about the monkeys operating the controls, the aircraft isn't exactly cheap, either.

Setting inventory - actually being able to fill storages and fuel tanks by script commands - is a huuuuge step! Finally we can create real "convoys" that directly impact available ressources. Thank you sooo much, for finally adding this feature. Total game changer!

It is totally worth it. Btw. to easily populate a 80ies/90ies war scenario, there is the "Generator" in the Mission Editor. There is the Option to select a "Node" and drag it around, select templates to suite your scenario (there is a separate template editor in the Generator Menu, if you want to fine tune forces). In the "Node" menu, select any of the Red Templates and Blue Templates you like (rectangles show force organisation and placement, these can be dragged to match your desired "front layout". Finally hit "Generate" and add Client/Player slots as required... Not a full immersive story campaign, but a quick way to setup larger engagements. Btw. you can of course add your own templates etc.

Just go for it! Learn the mission editor, some Lua Scripting and build a full fledged "Fulda Gap" campaign. Or use the generator in DCS to create a classic red vs blue scenario, with the templates (unfortunately only fully supported on the Caucasus map).

...and its own starting position/heading/pitch etc. to know "where 3° to the left" is after launch, as the launch platform isn't necessary stable.

TV ist in der tat nicht wirklich optimal. FreeSync ginge aber auch mit 60Hz, z.B. ASUS TUF Gaming VG289Q1A oder halt sowas wie mein alter 4k Monitor: Acer Predator XB280HKbprz, 71 cm (28\"), LED, NVidia G-Sync, 1 ms, 4K der in der Tat nominell 144Hz schafft. Aber der Punkt war ja: die Hardware sollte, insbesondere mit Multi-Threading, locker in der Lage sein 4k zu rendern.

I stand corrected! It IS now possible to "limit target type" to "ground" (to prevent shooting at airborne stuff) or "air" (to prevent AAA from devastating ground forces). Definitely something mission designers should consider. But I would still prefere a general solution on the AI decision making level.

Ja, zumindest konnte ich das mit meiner alten RTX 2080 S einem i5 10600K@3.8GHz und 32 GB RAM mit der Singlethread Version, bevor ich GraKa upgegradet habe und Widescreen genommen hab. Mit Multi-Threading und deinem System solltest du auch bei guten Einstellungen problemlos 4K in 30-40 fps schaffen. Ein Faktor, der meiner Erfahrung nach eine Menge für gefühlt flüssige Darstellung ausmacht, ist G-Sync/FreeSync.

Unfortunately the relevant options don't apply for them. "Engagement range" and "Target Aircraft" y/n would be helpful. Though I would prefer a generic change in the targeting of AI so air targets get handled differently and based on height/speed will be ignored, and if they try shooting air targets, add a calculation error to the lead simulating the difficulty in tracking and judging lead in 2-3 seconds.

The real issue is, most ground forces shouldn't even shoot at fast moving, low flying jets. Their engagement time for a jet at 400 KTS and below 500m is measured in a couple seconds. It's not enough time to swivel and aim a gun, find the target, through a sight and in case of the dreaded BMPs lase the target for ranging, while keeping it in the sight with manual controls... In real life that's Impossible, so the infantry man's air defense bible says "spray and pray" or safe precious ammunition. If(!) a jet is slow enough or a helicopter high enough to spot it early enough, it's still no easy task to hit it (I know, because I did that myself during training). We were all very confident ("how hard can it be" - "Just walk the tracers on target"), but learned quickly how difficult it is to do corrections. The target flew in a straight line, towed by a prop plane and we couldn't really hit it. There's a reason why military developed dedicated Self-Propelled-Anti-Air-Artillery with radar and sophisticated targeting computers for lead calculations to be embedded with ground forces, instead of just putting larger autocannons on IFVs. I explained it more detailed in this post: https://forum.dcs.world/topic/329932-sniper-btr8082s/?do=findComment&comment=5271762