Mr.Scar

Wanted a full fidelity Mig-29 since Lock On, but was in love with it since i was a kid. Used to see a lot of those, just like the Mi-24 since Polish Air Force operates them. Dream come true.

Want to bump this topic up. Now i do not want to gripe, but i recently picked up the KA-50 after aroubd 2 years, and have a blast with it. Its a great bird to fly and kill stuff with. However i am really wondering about one thing. Is adding a FLIR to the ka50 really a big deal? I mean i know the whole story from the formal perspective, and some things cannot be modelled because of security reasons. But truth be told if we could simply get the flir for the shark it would be awesome. Just add flir, plus 2 buttons to change WHOT to BHOT and thats it. Heck, it can even be named the KA-50N and it could be a very limited version due to security stuff. I have No idea what kind of fancy systems it has, but truth be told if we would get the shark as it is right now + flir i would be a happy man. Would it make the shark on par with the apache during night ops? Probably not. But it would allow for better night ops. So simple question is, would it be possible to get a flir, without any special systems? I mean, do it in a way that it does not raise any security concerns. Im a simple man that finds fun in simple things. However i might be missing something, that is not that simple as i imagine it. I fully respect that. @BIGNEWY Thanks in advance and please dont kill me for asking this question, if you have already been spammed with it in the past.

Bump this topic up. Wonder if there is anything going on here. I love rotorcraft and it would be great to get a heli equivalent of the tomcat/hornet, that works with the supercarrier. Looping in also @BIGNEWY @NineLine Thanks in advance for any feedback.

Thanks for sharing. I like the F16, but have not flown it that much. Same Goes for the Hornet, since im a rotorhead mostly. But i will take a Look at it, since recently i have been checking out both the Viper and Hornet. Maybe i will give one of them a shot, and see if multi role fighters get my attention.

Maybe it would be a good idea to add something like this: On the target list, where you select what the CPG has to attack, add some few options like: 1. Engage AA 2. Engage Tanks 3. Engage soft targets 4. Engage Infantry 5. Engage targets of opportunity (Here George would have the freedom to choose targets, depending on threat priority) 6. List of specific vehicles start like we have it now. But esentially, the options above this would make him fire at targets until you tell him to stop, or he looses visual.

+1 for the reset trim, same reasons for me as OP stated.

Yup, got to admit it also went through my mind. Should have mentioned it in my previous post, because like you said the AH-64 was designed to stop the soviet armored divisions, and now when i think about it, having a lot of Hellfires without the need to travel a long distance, might actually make sense. Was thinking about more current scenarios and forgot about the Cold War stuff. My bad.

How long you can be in the air with current fuel load before the need to return to base and refuel

For the very same reason people avoid SPAMRAAM loadouts on the Hornet. They generate too much Drag even in BVR, and you do not want much drag while defending from a incoming missile. 16 Hellfires loadouts might work in War Thunder, but DCS aint War Thunder. And aside from people wrote already above, several factors. From my side 1. Depends on the mission. If you know 100 tanks are heading towards your base, and you and your buddy in a second Heli are the only Apaches in the Area, you will probably want 32 Hellfires, to destroy as many as possible. But in my opinion this is a highly unlikely scenario. 2. 8 Hellfires, 300 rounds for the 30mm + Hydras give the best tactical flexibility. You destroy high threat targets with Hellfires (like SPAA) from safe range. Finish off tanks with the rest, and use rockets on light armor targets and even soft targets. You mop up the rest with the 30mm while orbiting at a safe altitude when nothing can hurt you. The 30mm is a fun badass gun, but its used the same way like the 30mm on the A-10. Gun that should mainly be used in low threat/SPAA/MANPAD free environment. 3. You probably would not want to take 16 Hellfires for the very same reason you would not take 3000 rounds (correct me if im wrong, but i think the Apache can carry so much ammo) of 30mm ammo on the Apache. Insterad of a ammo drum, you take an additional fuel tank for longer time on station. 4. As a follow up to point 3. Having fuel means time on station. And being able to get somewhere and then back without the danger of running on fumes, is more important than 16 Hellfires that you will not even use, when you run out of juice. 5. Drag and weight. Its up to the Heli pilot to get to a target area, even with waypoints. You never know if you will have to climb a mountain or take a round around them. I would not want to drag 16 hellfires and then just smash into the side of the mountain becuase their weight while mountain climbing made me crash. 6. Helicopters usually work in pairs, and with a flexible loadout they can rain hell. No need for 16 Hellfires on one helo. 7. Helicopters are well helicopters. FARPS are somethings that can be used, not only fly to a target area far away form the airport. So a heli can always get to a FARP, refuel, reload, and quickly get back. So no, 16 Hellfires are a no go for me, but maybe I am wrong. Anyway, just my 5 cents.

Thats a good argument, thanks! I think i will also swap the rudder axis and place it on the throttle instead of the twist grip. It works much better this way (it worked with the Huey and KA-50). When its on the twist grip, the Apache is wobbling around too much

Hi, I have updated the file for the AH-64D Pilot + a bit of bindings for George AI. with fresh keybinds. Based on DCS: AH-64D | Controls Setup video by Wags. Small disclaimer, file is subject to change since i still have to take the Apache for a spin with those settings, so the final config might change depending on what i will think is necessary, and has different priority. Its probably in no way perfect, but if someone finds it useful, please feel free to use those settings. Below the axis settings, that I also use for the Huey. Still few bindings are left blank, profile will be updated/changed as mentioned above. Feel free to share/modify according to your own needs. Feedback is also appreciated. 1. Cyclic Pitch and Rolls Deadzone - 3 Sat X - 100 Sat Y - 100 Curvature - 15 2. Collective Deadzone - 0 Sat X - 100 Sat Y - 100 Curvature - 0 3. Rudder Deadzone - 3 Sat X - 100 Sat Y - 75 Curvature - 15 4. Power Levers (Both) Deadzone - 3 Sat X - 100 Sat Y - 100 Curvature - 15 5. Zoom View Deadzone - 3 Sat X - 100 Sat Y - 75 Curvature - 15 6. Hocas Cursor Controller X and Y Axis (Y Axis Inverted) Deadzone - 3 Sat X - 100 Sat Y - 100 Curvature - 15 thrustmaster__t16000m-fcs--layout_1.2.pdf

Want to give my gratitude also. Took the AH-64D for a short spin yesterday, only startup, take-off, some flying around and landing, but it is a joy. The sound, the design, the readable cockpit, its all awesome. Its Christmas again for me. Thank you ED.

Hi all, Need some advice on setting up the controls for the AH-64D Apache for Thrustmaster T16000M FCS, without Rudder pedals. The mapping is based on the original post from Wags, under this link. My layout is still WIP, so a lot of buttons are still not mapped, but i need some feedback if I am doing it the right way. The intention is to have the flight controls, sensors, weapon selection setup as intuitive/making sense as possible, with the rest of the stuff like NVG, engine manipulation, formation lights etc. setup on the buttons of the base of the stick. The setup is for Pilot only. So in general, please take a look at this, and tell me if it makes sense to you, or some bindings have other priority, since i have a sense that i am walking a bit in the dark here. Also the layout is based on the frame of CMDR Bezdi, and is editable, so if you have the time to look at it and edit it, please be my guest. Any advice is welcome. Last thing, probably a stupid question, but does the Apache has some kind of trimmer reset button? Because i am either blind, or not able to find it. Thanks for the help. thrustmaster__t16000m-fcs--layout_1.2.pdf

Exactly. Thats why i think the Apache is worth the wait

I think i can almost say the same. Thanks to the Su-25, Harrier and A-10 i have discovered that i absolutely love ground pounding. But i was missing something... I dont know exactly why, but something told me to focus more on helos, and i did my research, focused on the Huey for training, and boy oh boy... how it clicked. Then i tried out the Black Shark, started re-learning it and i was sucked in for good. At that point I knew a helicopter is what i wanted. Its kind of funny when i recall it now, because before i discovered that helos are the thing for me, i was jumping around like crazy between different jets, but only the Harrier and Hog had those quirks that kept me longer with them. It was all much more personal, and with the Huey/KA-50 it was even more personal. The thing about helicopters that attracts me the most is that, no matter if its bare bones, or some advanced machine with flight stabilization, it always provides hands on flying experience. And now that the AH-64D Apache is coming, I expect the flight experience will be similar to the Black Shark but with a lot more toys to play with. I simply like the idea of getting up close and personal in a Helo. You see ground troops, you help them out, you are there when they need you and you can see all that. It provides a certain level of satisfaction that i was not able to find when flying fast movers. Where a jet is a assault rifle, the AH-64D is a shotgun. And i love shotguns...

Try out the link i have posted in this topic, it shows a summary for each module and is in my opinion very well described. It is a few months old already, but i think it is still valid. As for the modules you mentioned. 1. Mig-21 - i do not own it, but i have read/seen on yt that it is a jet that tries to kill you almost always. The knowledge what to do when something fails is especially vital, so i think it is not a begginer friendly aircraft, but i have heard opinions that once you tame it, it is rewarding as hell. But this is only what i have heared about it. 2. Mirage 2000C - I have it, and have flown it, but not before the recent changes. I have heard it got a lot of love from the developers (there is a changelog on the forum, on the topic dedicated to this, you might want to look at it) as for flight characteristics. Its a delta wing, its very fast and very agile, its an excellent dogfighter (check out GrowlingSidewinders videos on YT about it, he explains a lot how to fight in this thing, and he even has videos of a real Rafale pilot that was sitting in the Mirage and dogfighting him.) 3. In my opinion you can never go wrong with Flaming cliffs 3. Sure, no clickable cockpits, but a lot of aircraft and campaigns, that you can mess around with and get the following things: - you get a feel about both eastern and western aircraft - you get the A-10A which will give you a feel how A2G works - You get the Mig variants with PFM and the F-15C, which are again great indications on eastern/western aircraft characteristics. - Because there is no clickable cockpit, you focus on the basics, like takeoff/landing, weapons employment, BFM, BVR and you are not "bothered" by systems management. In my opinion it is a great initial point before advancing to something more complex. Especially if you are just starting with DCS. 4. You can always ask yourself a question: Am i more into A2G or A2A or a mix of both? If you know the answer to that what clicks with you, it will also narrow down further the options which module to choose.

Ok, i have confirmation that the document is ok, unclassified and for public use. So here it goes. To quote from the main site what this document is about: "This monograph examines the planning methodology of US Army Corps for employment of the AH-64 Apache attack helicopter in tactical deep operations. It takes an analytical approach to define the deep environment in which the AH-64 must operate. Planning techniques for deep operations tactics are found in a handbook produced at Fort Leavenworth in 1990 and some corps standing operating procedures. These techniques place emphasis on a targeting methodology called D3A decide, detect, deliver, assess. This methodology provides sufficient information for engagement of enemy targets. However, the AH-64 requires information on many areas of the deep battlefield that will provide freedom of movement through or near enemy forces to gain positional advantage for delivery of their fires. This paper will provide a piece of the analysis necessary to reassess the planning methodology and ensure a more thorough technique. The first part of the monograph informs the reader about the theories that have defined tactical deep operations. These theories were developed and well documented in Russia between World War I and World War II. Later, the United States identified their own need to produce deep operations doctrine. Deep operations principles are now an integral part of the overall tactical concepts in US Army doctrine. Parts two through four describe the environmental conditions in which the AH-64 operates during tactical deep operations. These conditions include the AH-64, the command and control structure, and the potential enemy force. The AH-64 possesses certain capabilities and vulnerablities as a combat system. These are described as they relate to the actual equipment design, the average pilot and co-pilotgunner, and the terrain. The unit structure is described along with unit employment in deep operations and unit command and control." Source: https://apps.dtic.mil/sti/citations/ADA339637 Direct link: https://apps.dtic.mil/sti/pdfs/ADA339637.pdf I think it might be a interesting read about deep operation tactics, where the document takes the AH-64 specifically into account.

Haha, good one. Yeah, i will just send a priv msg to someone from ED. The document i am looking at, screams about unlimited public distribution everywhere, but i do know that documents have a tendency of having some hidden/small written details like: You are only allowed to distribute it in the United States. And then all hell breaks loose... But anyway, thanks. Better safe than sorry.

Hm, i have found a interesting document on the internet. But after reading what you wrote here, i am not entirely sure i can post it. I have checked the document myself, and according to the info it states: Distribution unlimited, but i do have my doubts now. Law and security guidelines can be a pain, but I do not want to do anything wrong. Do you think it would be best to ask someone from ED, like NineLine or Bignewy about it before posting?

I will put it in a simple way. Its better to be patient and have a nice surprise, than have high and made up expectations generated by the hype train. To elaborate, it all boils down to personal perception and after considering all pros and cons, answering one simple question: Do I want to get a EA module now? Early Access in gaming industry is nothing new, and I think most people should be aware by now of what pros and cons it has. Its up to themselves to decide, if they want to spend money on it, or wait till it meets their expectations. I myself bought the AH-64D already. Because of the following factors: 1. Its something I was waiting for a long time 2. I am a rotorhead 3. I am fully aware that development takes time, so even after the AH-64D will be available for flight, there will be things still to be implemented. 4. In my eyes DCS provides top-notch quality modules, that get completed eventually. So waiting an additional few months, or even a year does not bother me in any way, because i know i will get high quality stuff in the end. 5. I like watching how new things are being fixed/implemented, new missions and campaigns are added, and thus new experiences are being provided. 6. Patience always payed off in DCS for me, as it does by flying helicopters. For me, its the road that matters. The end goal is there, so that after reaching it, you can make a new one. Just my opinion on the topic and how I approach such things.

Good choice and welcome to the rotor head world, where crazy is our trademark I don't know if you considered it already, but a few tips if you don't mind: 1. If possible, get rudder pedals. The twist on the stick can do the job, but will make your wrist tired on the huey. 2. If you have something similar to a FCS 16000 Thrustmaster throttle and stick, you can bind the rudder on the rocker axis (that big black plank that is moving left and right) i use this and find it quite comfortable. It is even more comfortable to use when a helicopter has flight stabilisation systems, but nothing beats rudder pedals in the end. 3. Always pay attention to the torque, be it by eye on the gauge or by listening to the engine/airframe sounds. If you get red on the gauge, and pull the collective too hard, you might experience your rotor blades getting a life of their own and flying somewhere in front of you. 4. Practice low level hovering, it is the most tiresome aspect in the huey but will give you a lot of experience regarding rudder pedal, collective and stick sensivity, as well as general flight characteristics. When hovering, try to fix your sight on one particular point in the distance (tree, building, wathever) when navigating the huey you will be using a lot of landmarks and its a good idea to be able to focus on one to keep the course correct. 5. When you see from the cockpit perspective that everything is wobbly when doing manoeuvres at high speeds, don't worry. From a spectator point of view you are looking great. 6. VRS (Vortex Ring State) happens when you are too slow while trying to land, you need to feel the moment and speed depending on the weight to slide. But when you feel VRS is catching you (wobbly and shaky helo at minimal speed) pull a bit harder on the collective to compensate and don`t crash into the ground. It will take time, but you will get there. 7. Most importantly, have fun! My advice might not be perfect, since there are more experienced rotorheads out there, but those are the things I have learned, so I hope it helps.

What @Yurgon said, i can recommend aswell. Also, this hoggit post contains a great write-up done by the author that covers everything we currently have in DCS. It might give you good indications what to try out first.

Im waiting for multithreading and vulcan. Because it will mean better performance, and better performance will get us closer to see the official dynamic campaign mode. Modules are great, but a thriving dynamic and changing battlefield is the thing that will complete DCS. At least for me. So i hold my thumbs for fantastic news in 2022, as i did in 2021, which was also great.

I use the FCS Thrustmaster 16000, throttle and stick. Works very nice on win 10 and the latest DCS version. Only problem I had was the axis jumping around erraticaly, so i had to dissasamble the throttle and stick and use WD-40 on it. Never had any problems since then. I dont know what exactly your problem is, but i think it would be nice if you could share info which DCS version you are using. Because it can be several factors. 1. Conflicting with other controllers. 2. Drivers 3. Check in windows controllers if detect the stick/throttle at all. Attempt to reinstall drivers via the control panel? 4. Check the controller settings in the DCS menu? 5. If possible, try connecting the T16000 to another laptop/pc wathever, just to check via the windows controllers if it works and you get the reaction/movment there to conclude if it is a hardware problem or a software one. 6. If it works on a different PC/lap, try connecting to other USB slots on the pc you are flying? it might be some usb issue. Bios, usb slot got worn down etc. etc. My help might be however limited, since i do not use the older version and windows 7 since a long time. So it will be hard for me to assist in full detail. But the first thing i would try to do is to figure out if it is a hardware or a software problem.

If you like the AH-64D Apache on Range video, you might also like this. Its funny how i found this, when i was looking for videos about the Abrams Apaches are shown at the beggining and around 2:28. Some sight to see... But anyway, the topic is a nice clickbait. I almost fell for it haha. Good job.