StrongHarm

From a previous post:

I've put together a sound layout that I had to share. It really immerses me in Blackshark. I purchased a Razor Blackshark Headset. If you haven't seen these headphones you should check it out. It's a metal construction helo can replica... very well built and looks cool. It has a great mic and sound. This is the first headset I've used where I actually had to turn the bass down. Next, I added a splitter and ran the other output to a 1000 watt tuner. I have a big bass speaker that sits between the wall and my pedals. The result is that I have my cans on my head, but I can hear sound outside of them as well. I have the bass turned up on the external sound so the woofer gives my pedals some serious shake. It simulates sounds being outside your headset.. like IRL. It occurs to me that if ED could split the aircraft radio out to the 'default communications channel' in windows, and all other sounds to the 'default device channel', the sound split would add even more realism... but that's ok.. this is cool enough. Thought I'd share.

I agree, it's important to map Alt AP to HOTAS. I have all AP buttons mapped to the CMS on my WH HOTAS. If you have a WH, check out my control profile. Also, if Alt AP is causing you more problems than it should, be sure you're using your collective brake. It's important. Here's a good explanation by PeterP. Another alternative to VoiceAttack is Voice Activated Commands (VAC). It's inexpensive and very well supported. I can talk with my pipe in my teeth and it still recognizes my commands. Awesome app. You can get my prepared VAC profile, with command reference sheet, here. I only use it for DataLink and interaction with wingmen/tower, but that's over 200 voice commands. You can very easily add your own commands simply by typing what you want to say, then the key that should activate when you say it. No training or any other action necessary. The command builder is the best reason to use VAC.. it's a no brainer.

From a previous post:

Sometimes taking the shortcut ends up being the long way home. Watching vids and asking questions in MP will get you 70% of the way in an exponentially longer time. Reading (not memorizing) the manual takes very little time and provides further questions, and enough knowledge of the manual to know where to seek reference. This does require some degree of self discipline and interest in the details though, I don't disagree. Yurgon, you're right, this discussion has veered way off course.. it became a discussion about the manual and level of interest in detail rather than trying a different airframe. Allow me to politely agree with you; the time to embrace a second airframe such as the KA-50 is really a matter of preference and level of engagement. If someone hasn't read the A-10C manual, no, I don't think they'll be successful with a second learning task. My suggestion is to master one rather than dabble in many... it's so much more rewarding.

I think you're right.. it's all about personal preference. I'm so adamant about embracing the 'study sim' aspect and fully understanding the platform because of the reward I've experience. It's exhilarating to complete a complex evolution without hesitating with the subsystems, or to pull something off that you know would have made you a ball of flame if you didn't have full mastery of the aircraft. It's the difference between playing Highway to Hell on the guitar in front of a bunch of drunks, or playing Black Mountain Side by Zeppelin while camping alone. They both hold purpose.. but the reward of experiencing what Jimmy Page intended in that acoustic piece is so worth the time spent dissecting the true complexity of it. But that does go back to what you were saying.. it's personal preference. Some people aren't interested in exploration beyond 3 cords and a distortion pedal.. and like wise some people just want to blow shit up, then play a different game. I personally view it as a simulation of the complexity and hard won mastery that the pilots truly experience.. and for the first time (debate unnecessary) we have the ability to be fully immersed in an aircraft and (most of) it's subsystems. I'm just boggled as to why people wouldn't embrace the chance. The journey is it's own reward. But you're right.. that's simply one man's opinion.

IceBurner, I built an X52 profile long ago that I believe people are still using. I put a lot of time into analyzing and designing an intuitive setup. If nothing else it may serve as a good starting template for you.. I learned a lot of hard lessons while perfecting it. http://forums.eagle.ru/showthread.php?t=59208&highlight=x52+drop+check

For those of you who don't like to read the manual.. or long posts like my last one... here's the smiley face pictograph version: :thumbup: :book: :thumbup: :smartass::pilotfly: OR :joystick: :cry: :joystick: :mad: :joystick: :cry_2:

I enjoy soaking up the technical details from the manual. I don't disagree, I think the DCS Warthog manual was written to be like a tech pub, like the Navy NATOPS manual (which I loved as well). The Falcon manual was epic, and co-written by an amazing Viper pilot. I still have the hardcover binder style 1st edition... and I keep it in a sleeve to preserve it. It's a classic that will never fade. Dudester22, if you find the self discipline to give the manual a quick read (not thorough the first time.. just a quick steady read) then when you go back to it as a reference the dots will connect. The reward is WELL worth the time spent. People brag that they 'click learn' Warthog, but in the end the breadth of the subsystems do not lend to learning by chance, and those people invariably end up learning less than half of the true capabilities. Sure, not everything is in the manual, but it is a superb foundation... really the only foundation in my opinion. Here's an old post from when Warthog was in beta entitled 'RTFM' that has some interesting poll results, but here's the gist of why the manual appeals to me:

But can you imagine....

I love my Hawg, as most of us do. Putting forth the effort to master the A-10C platform is so rewarding that it's clearly worth the time. The speedbumps and grey areas are part of the lure. I'm ashamed to say I indulge in reading the manual sometimes even though I've read it dozens of times.. it just rocks. From time to time I like to take short breaks from my Hawg so it won't become tedious. These are the times I jump in my Shark for some rotor wing love. I was compelled to drop a note for anyone who hasn't mastered the KA-50; the effort and reward levels are on par with the Hawg.. if not greater. It's a bastard of an airframe to learn, and the sensors are archaic and utilitarian, but OH MAN once you master it.. it's just a blast. If you're looking for a change of scenery and want a challenge.. jump in that Blackshark. It kicks ass beyond belief. My 2cents contribution.

From a previous post:

This error occurred in Deployment09 as well. Again, going into the mission planner before mission start and changing the paint scheme from 'Army Standard' allowed the mission to load successfully. I did notice that the Description.Lua for that skin changed in May... FYI. I've attached the associated files in case a dev or tester needs them for troubleshooting. Hope you guys are doing well. Update: I deleted the Army Standard folder and allowed it to re-download. Same symptom persists. I took a look at the LUA and associated files and didn't see any obvious syntax issues. Russia Standard Army.zip

The key command repeats to get to a further stage in the command. For instance, Datalink Mover Four does the command to select the first mover, then 'repeats' until it arrives at the fourth.

VAC actually uses the WSR engine. It just makes it A LOT easier to capture and organize profiles, add sleep commands, create multi-commands split by millisecond delay, etc. It's the design interface that VAC provides that makes all the difference. It's nice that you can just type some text and choose a key command that corresponds, then just use it. Without training it or any other modification, I can create a profile and talk with my pipe in my teeth and it still picks up the connection between my voice, the command profile, and the corresponding key command. It's a great tool made by an individual who stands by his product. I didn't mind at all paying the reasonable cost for such a useful app. We must support good devs so they'll continue to provide good code. When you use the profile, be aware that since some of the radio commands are contextual, they won't work properly if you're already in the middle of another contextual communication flow (startup / take off for instance). I plan on altering the multi-commands where ever this is possible to clear the flow (F11 string) before issuing a command, but have to find the time to do it. :) Be sure to use the handy key I provide later in the post. I should edit the OP and add this image. It's also attached in Excel format within the ZIP file. Don't hesitate to ask questions if you run into issues. Enjoy

Laser standby is situated on the mic hat along with hardpoint selection.. so you can quickly select your hardpoint then activate laser intuitively. The only time I don't have the laser in standby is when I'm actually ranging or there's ordinance in flight. I've rearmed several times in a single mission without burning it out using this method.

You can learn more about the trim . Reset trim is necessary sometimes when the inputs become non-relative (non-FFB). Reset trim was added to compensate for the fact that you can't 'feel the physical difference' on the stick between center and current offset as the pilot would. The addition of reset trim shouldn't be a problem in my setup as it was added with a paddle modifier. Here's my VAC post. This should get you started with a decent profile.. and before people start screaming about the fact that it's not perfected to their preference, let me provide a disclaimer: I spend a good deal of time analyzing and capturing the most efficient procedures and control methods FOR ME, and then I share them with the community because I like to contribute. If you don't like it simply don't use it.. but don't begrudge me for attempting to contribute. I don't see the very thorough post on the ABRIS I was referring to either.. maybe I posted it in the Testers Forum. Here's some of the key points from another very early post I wrote on the subject in 2010: Don't give up on the ABRIS and other systems in the Ka50, Bee_Sting. There's a lot of knowledge that you don't need to make things blow up.. but I have a hunch you might be someone who wants to blow things up with style.

I stand corrected.. it was when I was on E-2C that I had to do ramp APU startups. It was over 20 years ago and I have a fondness for the Tomcat.. so I guess I associate memories with it by default.

I'm re-flying all campaigns right now.. as I do love my Blackshark. On Deployment Campaign, mission 07, I successfully pulled of the CSAR and received 'Mission Success', I then flew the rest of the route back with the Mi and landed at the base. I decided to watch the Mi land as well. As soon as it's tires hit the runway I got 'Mission Failure' and the game crashed. After going back into the campaign I found that I had still advanced to Deployment08. This is just an FYI.. no complaints here. Great work on continuing refinement of KA-50, dev team! I'm glad it's still getting some love. What a phenomenal product!

The A/A Hardpoint select is that useless that it hurts, and thats just one example. 1/2 of the setup is useless in combat where you nearly never have time to switch around inside the Cockpit. I use every single command, personally. If you don't use AA mode against other helos you're probably not going to hit them. Same with moving vehicles. The reason I've keyed commands that you 'nearly never use in combat' is because frankly they are useful.. but you don't use them because they're too hard 'for you' to activate during combat. Consider that if you were in a real Blackshark you would know where the switches are without looking at them (trust me, I could do a complete APU startup of an F14 without looking at a single switch when I was in the military). You can setup the DL system instead of the ABRIS as a another example. I use Voice Activated Commands for my Data Link and all wingman/tower interaction. Sorry.. The ABRIS controls are extremely useful. I often mark enemy weapon range thresholds on the ABRIS before IP, without ever taking my hands of stick and throttle.. and a huge number of other useful tasks. Do a search for my post on the ABRIS to learn more about utilizing the ABRIS to it's fullest. The UV-26 can easily be one button also. I use different profiles depending on whether I'm just dropping flares as a deterrent or dropping to actually spoof. You should too.. And why do you need the reset trim, autodescent and Throttle as keybindings? If you're not using trim reset, there's a whole world of helo piloting you're missing out on. If your question is: 'why is trim reset on the throttle?'... It's there because that's the easiest key to hold down (which is why the US Military made it the 'mic switch' in the A-10C).. and I hold trim reset while maneuvering, as do most people. I do also just turn heading AP off instead if I'll be maneuvering for a very long period of time. CONCLUSION: There are some things missing from this setup if you don't use Voice Activated Commands (VAC) or a TrackIR, granted. But do I hope that you can see that it provides more of a 'Hands on throttle and stick' .. you know, HOTAS.. than the default DCS KA50, Warthog profile. In my OP I should have stated 'superior mapping for advanced pilots'.. sorry about that.

After today's update I attempted go into campaign mode and DCS crashed with the below error. Work around was to go into the mission editor on campaign mission start and change the paint scheme of player blackshark. 00015.302 UNKNOWN WinMain: 00015.456 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-01.bmp 00015.460 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-03.bmp 00015.464 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-02.bmp 00015.467 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm_b.bmp 00015.470 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm_centre.bmp 00015.474 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50_st_paint1.bmp 00015.478 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-05.bmp 00015.488 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-06.bmp 00015.497 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrm-1.bmp 00015.501 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-lrmpart-1.bmp 00015.510 ERROR DXRENDERER: DXDefTexture: failed to open file ka-50-paint1-def-04.bmp

The devs are pretty good at deprecating the control LUAs, but I've learned over time that in the end it's better to just re-key everything. There may be some subtle change to the file that can cause intermittent issues. I created a diagram for myself and find that it's pretty quick and easy to key it back in due to the friendly interface. Here's my profile: Analysis Results: KA-50 and WH HOTAS

I agree completely with ff4life4. The key is studying the manual and understanding the subsystems and theory of operation. Just when you think you've mastered the bird, you learn to utilize another subsystem to great advantage; such as marking target enemy weapon range thresholds on your ABRIS. Where controlling the airframe is concerned, I wasn't really good at it until I spent a whole day just doing funnel maneuvers around stationary objects (rotate around it while keeping the nose pointed at the object). This ingrained the muscle memory necessary to use the rudder, collective, and cyclic to compliment one another. As someone else said, fixed and rotor wing aircraft are very different, that's why the US Military very rarely rates people on both.. it's dangerous. It's similar to the contrast between playing the guitar and the drums; the guitar requires you to multitask, but with focus on the frets (fighter and sensors).. the drums require you to coordinate foot and hand movements to the point where you no longer perceive them as separate appendages (helo and cyclic/collective/rudder). Concerning autopilot, I've started turning the heading AP off instead of using the flight director. I find that it provides me a more stable platform. I've bound the four AP buttons to my CMS hat on the WH HOTAS. If anyone is looking for a much more professional and intuitive WH HOTAS setup, see Analysis Results: KA-50 and WH HOTAS

That's just a damned shame!