StrongHarm

I've done full VAC setups for KA50 and FC2, but I've held off on creating one for A-10C until the radio menu stabilizes. (See threads VAC Blackshark or VAC FC2 for more info on VAC, a vid, and voice to key command profiles I've created. If you want only the A-10C startup checklist (readback) you can get it here.) I think after the next patch I'm going to complete it as I believe the radio menus won't be changing as much in the future. If it's done correctly, it takes several hundred lines of XML, and I only want to do it once. For instance; you can say "wingman (pause) go formation (pause) combat spread", and that's pretty easy to set up as you have one line for wingman, then you create a call for each command to the wingman. However, the prefered way would be to say "wingman go formation combat spread" with no pausing between commands. To do this you need to create a line for every possible combination of commands. Yes, you can set the command time in miliseconds, but it's just not full proof and requires you to say it a certain way. With the command combination method, I can speak the commands at any tone or speed, with my pipe in my teeth, and it always accepts them. Blackshark took many many hours to complete, but it has a lot more command combinations for the wingmen. I'll post the warthog commands when they're complete. As for VAC in general, it's an awesome application and well worth less than $20. It's stable with free updates, and the support is great. The extra immersion it provides is really well worth it.

The learning curve is steep, but with a combination of the flight manual and a great community, all of your questions will be answered. Take the time to read the manual, you won't be dissappointed. Even after you master the weapons systems, you'll find that the joy of flying the hog isn't dimenished. I was flying a mission not long ago; JTAC had just given me my 9line for a bombing run on a tank element. I was coming over a mountain aligning my TGP to the target and saw a great cloud formation next to me. I forgot all about the target and played in the cloud for a while. I guess that's the good thing about flying it in a sim.. my commanding officer didn't walk up to me as I exited the plane to tear my wings off for being a goofball heheh. Welcome to the best sim and community available!

It's hard to tell if that video is real or the sim. What a testament to how great DCS is! Drat the holidays that interfere with my flight time! :)

I would like to see a DCScon at Nellis! I'd fly there for that. I'm sure the U.S. Airforce would love the free recruiting op... no have them pay for it. I'm sure it's in the budget! heheh. I advertise by word of mouth all the time, but I think my best direct advertising opportunity came at the last Dayton airshow. I stood at the A-10 Demo East booth and chatted the airman up about the sim. Several people who came to purchase t-shirts, etc. said 'wait, what sim are you talking about?'. As for virtual spaces to spread the word, I've posted my user review at sites such as metacritic.com. DCS A10C is within the top 20 games of 2011 for critic and user reviews, even with titles such as BF3 and Skyrim . It's a great way to expose the sim and give people, those with the aptitude, a chance to try it. +1 for the effort of putting up a poster!

In addition, see this post: http://forums.eagle.ru/showthread.php?p=1106259#post1106259

Thanks Sid. The answer is in post #32 http://forums.eagle.ru/showpost.php?p=1010426&postcount=32

Good idea on the cloud deck. I'm sure your mission will be great as always Grimes. I hope to see some good ideas float through this thread. Stop by from time to time and grab a few.

Agreed. Head to head the KA is done, but each pushing toward their strengths independently, in a race to do what they do best.. so to speak, will be interesting. For a real AA barrier, what I've done in the past is made a 1 mile trigger zone and put an SA15 in the center. I shut the SA15s AI down on spawn, but when someone flies within the trigger zone the SA15 AI is activated, if they fly out it's deactivated again. This was in the context of a flight of Hawgs being told by command not to persue the enemy through the mountains.

I've been here all along. Pay no mind to the man behind the curtain... he's StrongHarm.. err.. harmless.

I don't know about you, but I'm excited about the upcoming compatibility patch that will allow KA50 and A10 pilots to fly together! I was thinking of converting one of my existing missions to take advantage of the new feature, but decided against it. Compatibility brings a whole new level of creativity and opens new doors. So.. let's come up with something great as a community and I, or perhaps we, can create it in the mission editor. Below, I've listed the variables to be defined. The sub-hierarchy items are my own ideas. So anyone interested, please add to or replace each variable. Fixed Condition: Multiplayer mission with A10s on Blue and KA50s on Red. TBD: Background Story Two mechanized forces, one Russian and one American, are moving through a ravine to their perspective objectives. The clashing forces are comparable, so it's a tossup as to which force will be victorious and make it out of the ravine to continue on to their objective. Air cover will be provided by MP pilots on each side. [*]Blue Objective Tip the scales between the two mechanized forces, allowing the blue force to crush the red force and move out of the ravine to continue on to their objective. They're tasked with the destruction of a fixed target, X nm north of the ravine. If our blue forces are defeated in the ravine, eliminate red forces before they can reach and destroy their fixed target, X nm south of the ravine. [*]Red Objective Tip the scales between the two mechanized forces, allowing the red force to crush the blue force and move out of the ravine to continue on to their objective. They're tasked with the destruction of a fixed target, X nm south of the ravine. If our red forces are defeated in the ravine, eliminate blue forces before they can reach and destroy their fixed target, X nm north of the ravine. [*]Blocking Conditions Each force must hold a flight pattern at a fixed point until the other side is at their starting point as well. The mechanized forces don't move out (don't spawn) until each flight of air cover is in place. At this point command gives coordinates and tasks. [*]Blue Success Condition Assist friendly forces in eliminating all enemy forces in the ravine. Move on to destroy the command post X nm north of the ravine exit. [*]Red Success Condition Assist friendly forces in eliminating all enemy forces in the ravine. Move on to destroy the command post X nm south of the ravine exit. [*]Time of Day Start just before dawn, making both clear visual and IR visual ineffective due to rising sun/shadow contrast. [*]Starting Positions TBD. The ingress to the ravine and the ravine itself must have sufficient terrain masking for the KA50s. [*]Opposing Defenses Blue forces are heavier with mobile AAA, creating a larger threat to the KA50s Red forces are heavier with mobile short range AA missiles, creating a larger threat for the A-10s Keep in mind: There must be a way for the KA50 to terrain mask or evade the A-10 Time On Target should not be a problem if it's measured from a trigger point rather than startup and takeoff. Maybe both sides don't get tasked until the other side is also at trigger. There should be indications of the other side's progress through updates, perhaps masked as intel coms from command. This is a personal initiative, not a task given to me by ED.

I don't know about you, but I'm excited about the upcoming compatibility patch that will allow KA50 and A10 pilots to fly together! I was thinking of converting one of my existing missions to take advantage of the new feature, but decided against it. Compatibility brings a whole new level of creativity and opens new doors. So.. let's come up with something great as a community and I, or perhaps we, can create it in the mission editor. Below, I've listed the variables to be defined. The sub-hierarchy items are my own ideas. So anyone interested, please add to or replace each variable. Fixed Condition: Multiplayer mission with A10s on Blue and KA50s on Red. TBD: Background Story Two mechanized forces, one Russian and one American, are moving through a ravine to their perspective objectives. The clashing forces are comparable, so it's a tossup as to which force will be victorious and make it out of the ravine to continue on to their objective. Air cover will be provided by MP pilots on each side. [*]Blue Objective Tip the scales between the two mechanized forces, allowing the blue force to crush the red force and move out of the ravine to continue on to their objective. They're tasked with the destruction of a fixed target, X nm north of the ravine. If our blue forces are defeated in the ravine, eliminate red forces before they can reach and destroy their fixed target, X nm south of the ravine. [*]Red Objective Tip the scales between the two mechanized forces, allowing the red force to crush the blue force and move out of the ravine to continue on to their objective. They're tasked with the destruction of a fixed target, X nm south of the ravine. If our red forces are defeated in the ravine, eliminate blue forces before they can reach and destroy their fixed target, X nm north of the ravine. [*]Blocking Conditions Each force must hold a flight pattern at a fixed point until the other side is at their starting point as well. The mechanized forces don't move out (don't spawn) until each flight of air cover is in place. At this point command gives coordinates and tasks. [*]Blue Success Condition Assist friendly forces in eliminating all enemy forces in the ravine. Move on to destroy the command post X nm north of the ravine exit. [*]Red Success Condition Assist friendly forces in eliminating all enemy forces in the ravine. Move on to destroy the command post X nm south of the ravine exit. [*]Time of Day Start just before dawn, making both clear visual and IR visual ineffective due to rising sun/shadow contrast. [*]Starting Positions TBD. The ingress to the ravine and the ravine itself must have sufficient terrain masking for the KA50s. [*]Opposing Defenses Blue forces are heavier with mobile AAA, creating a larger threat to the KA50s Red forces are heavier with mobile short range AA missiles, creating a larger threat for the A-10s Keep in mind: There must be a way for the KA50 to terrain mask or evade the A-10 Time On Target should not be a problem if it's measured from a trigger point rather than startup and takeoff. Maybe both sides don't get tasked until the other side is also at trigger. There should be indications of the other side's progress through updates, perhaps masked as intel coms from command. This is a personal initiative, not a task given to me by ED.

I received a PM concerning a persistent H key after loading the profile. Thought I'd answer here for everyone's benefit. The Saitek controllers have dirty pots (bleck!). You'll notice if you open your Saitek Control Panel (rightclick controller in systray, click control panel, then click deadzones tab) that the indicators are wobley. Set your deadzones as follows and you shouldn't have any more stuck key problems. As for other mouse and keyboard problems, the Saitek Service called 'Saitek Direct Output' takes over your mouse and keyboard and filters the input/output. It's super buggy. To turn it off do the following: * start > run > type services.msc > enter * find 'Saitek Direct Output' > enter properties * Change startup to disabled * Click ok * Right click on service and select STOP It won't start up again on boot, and you'll avoid the many problems caused by it.

zGmJzODNv9o

Not as bad as when we fired on a Turkish ship.. then the Captain (of the Saratoga I believe)took a suitcase full of cash to them with an apology. :megalol: There were a lot of stupid mistakes in that period of time before information technology caught up with technology. The U.S. wasn't even guilty of the dumbest of them.. believe it or not. I was involved with a blue on blue while landing on a carrier. The boat fired a sparrow at our C-2A while about 30nm out. There were a lot of itchy trigger fingers in the beginning of the Gulf War.

SA-15! SA-15!

In my experience starting military jets IRL, the bleed air system is opened after starting the number2 engine. The bleed air system provides environmental control and resources to the aircraft (I was an environmental systems tech, so ask me if you have further questions about these systems, to include ejection seats and weapons cooling). The IGN switch, for all practical purposes, is used to do an air start. The Motor switch is used to push air through the engine without pumping fuel or igniting. This is used to get the engine to speed (26-28%) before pumping fuel and igniting, which prevents a big ball of flame out of the tail pipe. My engine start procedure: *Start APU *Left Engine to Motor *At 26% push throttle over the hump and engine switch to norm *Immediately move right engine switch to Motor *Once left engine is fully started, right will open and start to motor *At right engine 26% push throttle over the hump and engine switch to norm Real A-10C Flash Manual

Thank you, as always, Speed. The Producers are to be thanked for making the good calls, the devs for working without sleep, and the community for it's understanding. We're all (ED and Community alike) lucky to be part of such a great project. I'm excited about the future!

In his video, it is only coincidence that the AWACS gives the contact after being asked for picture. It would have reported contact once in line of sight if he hadn't made a request. The AWACS task is only airborn early warning, but being in a non-combat role it reports contacts as any other aircraft would, such as a C-130.

I would agree with that Bahger. I think it would be nice to have a com dialog with any aircraft set to recon... 'report contacts, bulls' or 'report contacts, nav point adder'.. to repeat offset coords of anything line of sight. Would you agree?

Actually, the key may be that they have a non-combat task so they're in effect calling for support. Try setting the Kiowa to task 'nothing' and reply with your findings if you don't mind.

Anything set to reconnaissance, transport, or AWACS. They have to have line of sight on the target before calling contact. You also have to have them set to a radio freq you'll be on. I like to put a predator over the AO on recon, and set his freq to AM 30 (default).

bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbaaa ...That's the sound of my brakes button being stuck just now.. how fortunate I have an example. Your HOTAS doesn't descriminate. If there's a button pressed or a slider moved, your stick will put that command out until the button is depressed or the slider is centered. It sounds like you have a stuck modifier (ctrl, alt, shift, etc.). Open your sst profile editor and see if it's snapping to one button in particular.. if so, then that's the one that's stuck (or misconfigured). Another way to tell is to hit your windows key to bring up the start menu > type the word keyboard > hit enter. This will bring up your onscreen keyboard display. It allows you to type with your mouse.. but more importantly it highlights and modifiers that are stuck (like CTRL). It may just be your keyboard. Pick your keyboard up, turn it over, and drop it from a few inches with the keys facing your desk. See how many sandwiches pop out. Also, you may want to kill the saitek direct output. As posted earlier in this thread: Luck to you.

I see several radio menu changes coming in the future. Discontinue use of this and please be patient while I wait for that feature to stabilize so I can create a full XML.

http://forums.eagle.ru/showthread.php?p=1130567

http://forums.eagle.ru/showthread.php?p=1138499#post1138499