DmitriKozlowsky

Which one do I prefer KA-50 or AH-64D Following is totally original "Comparing Peking Duck to French Roasted Duck. Two different dishes yet I like them both." "Dalin' I only give the best duck."

UH-1Y Venom would be welcome but , I fear, is a bridge too far. Venom has lengthened fuselage, larger interior, completely different rotor system,powerplant, gearbox, and avionics. It only superficially resembles UH-1. Its a very modern maritime and amphibious assault helicopter.

Right. https://www.bing.com/images/search?view=detailV2&ccid=RIQzITsF&id=2A315019DAEA58DCA45609A723F4380CC4CD3EEA&thid=OIP.RIQzITsFny0JJ67QrM3LmwHaFj&mediaurl=https%3a%2f%2fth.bing.com%2fth%2fid%2fR.448433213b059f2d0927aed0accdcb9b%3frik%3d6j7NxAw49COnCQ%26riu%3dhttp%3a%2f%2flh6.ggpht.com%2f_4xLi6KmWWQA%2fTHmDTBnkwRI%2fAAAAAAAABo4%2fqlzLmZjQJnQ%2fs800%2fHH-1N%2b158551%2bcockpit%2b(2).JPG%26ehk%3dXbwr7%2b5jJ%2ff599ybYqbmxCo8k9bZJAgCz17vscUy5qY%3d%26risl%3d%26pid%3dImgRaw%26r%3d0&exph=600&expw=800&q=UH-1N+Instrument+panel&simid=608031639947063215&FORM=IRPRST&ck=E1986E0703586E3C18BC85695B9896A4&selectedIndex=11&ajaxhist=0&ajaxserp=0 Otherwise it looks very similar to 1H. I am curious if the Twin engines are derated or power is limited by governors so that each engine lasts longer and has higher time between overhauls. Full power on each plant would be provided when one engine fails, hot'n'high operation, near max GW.

Modernize UH-1H to UH-1N Twin. Would it be too much of a stretch to consider that ED would not have to too much re-coding to create UH-1N module by starting with current UH-1H? There were two varieties of UH-1N. With Stability Control Augmentation System, and without SCAS. SCAS equipped UH-1N did away with stabilizer bar, but otherwise rotor system remained Bell semi-rigid. DCS players are likely to be just as happy with non-SCAS equipped UH-1N. Biggest difference is that UH-1N got two engines. So dual fuel systems, and engine power quadrants to supplement collective twist grip throttle.

I do watch CPG. On my left MFD VID/TADS, overlayed with ENG, PRF, FUEL or ASA(RWR). I kind of wish that when CPG target list is displayed, the acronyms are colored red, blue, white. So that friendly cannot be selected and engaged. Would love to be able to export left and right MFD like in RAZBAM's AV-8B. Where screens are magnified and overlayed with transparency on upper left and upper right screen corners. For some reason the IHAADS monocle display gets irritating and feels weird after a while. So I turn it off and have my L-MFD display TADS video with FLT instruments overlayed on top.

It works, because I use that in other modules. The two modifiers , on X56 Rhino (Logitech variant), are two side by side #4 and #5, on X56 throttle. The command stacking issues I was/am experiencing also happened when I use keyboard. But I think I have a better understanding of CPG command logic, so CPG GeorgeAI is less of an issue. Except with rockets. George , well my George, does not fire rockets, despite acknowledging "engaging". To fire rockets I fire them manually. 'He' also kind of weird in firing Hellfires, in that he states "Lasing", I consent to fire, he fires Hellfire. Hellfire misses. About 1/4 of time Hellfire hits. Other times it impacts to the side or sails over target. As all measurements in Army and Marines are metric per NATO agreement. Thus I notice that GeorgeAI won't engage targets, farther 3000-3200 meters or so. He tells me "Get me closer". Gun under GeorgeAI is OK-fair. IMHO the CEP and beaten zone of M230 gun is wide. Wider then KA-50 in DCS. But then again, my hovering and slow fly hovering skill with Apache could be better. It is very sensitive. I look forward to the time when FCR and Hellfire Lima Radar are available. Right now even with ACQ set to $KR, the FCR page is empty. Like a place holder. But thats OK. I have my hands full training with laser guided K variant. Cheers

Wow! What an awesome mod! The tactical deployment PDF answers some long standing site setup questions.

First! I love this mod! Absolutely fantastic brilliant work. It flies and feels like a medium-large helicopter with fully articulated rotor. It is easy to hover, after some practice, has ample power . Of course we are still flying an empty bird. No passengers, cargo, no (yet) functional weapons. Obviously, as it is free non-commercial mod, there are features we don't get. Which is OK. Flight model , to me seems , great and realistic. It can get into VRS, settling with power, and autorotations are modeled decently. Sadly, as with all DCS helicopters , damage from rotor strike is undermodeled. Meaning that blade strike should result in destruction of blades (which does happen) , rotor head, mast, powerpalnt, gearbox, and fuselage boom damage which do not occur. I do have a question on ground handling. While on taxing, if pedal deflection is higher then some arbitrary amount, I incur an uncommanded roll and dynamic roll leading to rotordisk-ground collision. Tailwheel is unlocked. So turning UH-60L on ramp has to be with great deal of care. Once it starts to dyn roll , pedal zero and cyclic counter-deflection do not arrest the roll. Has anyone else experienced this type of mishap? I do not think this is a bug, but a feature of UH-60L FM as it is implemented. Cause, IMHO, is pilot error (me), and part of learning curve. P.S. Sling ops? crew chiefs? door gunners? Are those behind SDK paywall?

We can shoot down SAMs with SAMs in DCS. NASSAMS is particularly effective against Buk(SA-11), and Patriot intercepts S-300, in DCS. The reverse is also likely. Maybe. If you can't go after radars, go after incoming munitions. Is that a RW SEAD application? Have strike package fly under cover of friendly SAMs that shoot down enemy SAMs. Super useful for CAS missions along FLOT. The tactic seems effective with destroyers, cruisers, and frigates.

Thank you. I already have it, but its great nonetheless. In fact that stacking of commands is what this thread is about.

I agree its confusing as f....

Thoroughly tested. But I will retest. The thing is that I am having close enough results using keyboard bindings, which I left at default. No worries, it will all get worked out.

Bindings work otherwise. Just George AI is having issues for me. I expect those to be resolved. Usually takes about 3 sometimes 5 builds.

Well, not has been my experience. George AI RIGHT for example with Hellfire. Sometimes the quick RIGHT changes Hellfire from LOBL to LOAL and back. Other times quick RIGHT changes Hellfire trajectory from low to direct to high. Which is great, but is inconsistent. George DOWN sometimes turns off George, sometimes resets George, other times works 'right' and presents a list of targets. When George RIGHT after target selection, sometimes George TADS lases target, other times, just adds to target list. Either way, after target is selected and told to engage via Consent Fire, George reports 'Engaging'. Sometimes George fires off a Hellfire, sometimes not despite 'engaging', other times George fires Hellfire which miss, and he keeps firing at lased target and they all miss. Gun work with George is OK. Rocket is zero effective with George. Once again, I am reporting my experience, good and otherwise. To me , I having a bit of difficulty predicting what George will do with particular command at what part of order sequence. The manual has this AI Helper menu order graph, that I am having difficult time replicating.

I bound HOCAS, Pilot GeorgeAI, and general GeorgeAI. But I also left the default keyboard binds in place. I having issues with those. Becouse it is inconsistent as to which command is executed. I am sure it will get sorted. May take a5 or 7 builds.

I am having a problem, or actually AH64D is having a problem. Its having a hard time telling difference between short press and along press. I think that is the issue here. IMHO this is engineering issue.

Yeah those Wags tutorials. They are what are termed 'wordy'. After first 5 minutes, there is little information, usefull information is presented. After 10 minutes, it just a waste of time.

Activate Target - RIGHT Is what is not working. When I do GeorgeAI Helper RIGHT it switches weapon option. Hellfire LOBL or LOAL. Up/Down to select target appears to work. LEFT switches weapon selection. Those are not three buttons. Two are modifiers on my X56 and setup works fine. Problem is target activation, not target selection. I'll look at it after work.

Those were static helos on the tarmac. But anyway. I have yet to have my George fire any weapon. Not just Hellfire , at any target. Static, moving armored, infantry, moving armor. I can manually , from pilot seat, fire gun and rockets. But if I fire Hellfire at TADS target, Hellfire flies up and into distance, with no guidance. I scroll GeorgeAI down the target list. Manually fire Hellfire, and it just flies off without guidance. George ain't lasing, even though it reports 'Lasing'. So go figure! I think the process is lacking. But its early release.

Silly me! I forgot to set fuse on the weapon prior to release. For past 4 weeks. I have been doing nothing else, in DCS, other AH64.

IMHO, dynamic roll over in DCS is nowhere near as violent and destructive that it is in real world. Going by RL videos of various types, including rotary types in DCS, dynamic roll over or any event with rotor blade strike, should result in complete destruction of rotor hub and significant airframe damage. In DCS we loose portion of blades, but the shock is not transmitted to the mast, gearbox, engine, and fuselage. The helicopter stays together, and can be shut down normally if on the ground. Tried it in AH-64, Gazelle, UH-1H, MI-24, and KA-50. In DCS if in IGE hover and blade strikes an object, the helicopter settles down without further damage. Every event of that type, in RL, that is recorded, results in catastrophic damage to helicopter.

Been off AV-8B. Reviewing using GBU-54B. So with GBU-54B selected, ARM ON, and TPOD with 1688 lase code. From about 7000 AGL. In A/G master Select target target with TPOD. Long press Waypoint Increment to load target to JDAM. Fly into release envelope, and drop the weapon by pickling the weapon. So I get error at release que, when pickle. I get flashing //// bars. I don't recall seeing those before. I wonder of JDAM engagement procedure has changed. Perhaps I forgot something. The invelope for JDAM does say IN RNG.

Under Pilot for GeorgeAI there are three commands. Consent To Fire Show/Hide George interface Request Control None of which cause GeorgeAI to fire Hellfires or any weapons as far as I can tell.

None of those change the AI helper color. No matter how many seconds I hold them down or single click or double click. But maybe my finger gymnastic are not yet mastered.

None of the George AI Helper commands change color. This makes no sense to me. It is inconsistent, becouse the feedback is .. I don't. It does not tell me anything actionable.