WarriorX

Thank you Cougar! Another successful mission, congratulations! One question, is the SAM Battery at TGT 1 active or not? If it is active, I wonder if engaging it with AGM 65's is the wiser choice instead of overflying it for a GBU 10 engagement.

I can't see what you are describing. I have the latest drivers 266.58.

ColGray, unfortunately I have never used the easy comms. But I would guess that if you hear him call wheels up, you are in communication with him. Can one of you guys/gals who are more used to the easy comms give him a hand?

Glad you got it working Elasticbleu. If you dont mind me asking, would you please share with me what it was that was hanging you up? I ask because it helps me identify confusion points in the radio use, which I can then be sure to reinforce in later tutorials. You would be helping all those in the future that get the Sim.

I know Mower, the lack of indexer line should be addressed. I just know it default starts on VHF, and if I need a reference, I use the mechanical stops to establish either end, then count back to what I want.

Allright, well I am running out of things to check. The one thing for sure is that the Radio's do work, so let's look for the last few possibilities left. First, did you confirm your airbase position by hitting F10 and then selecting the <ME> button at the top? Confirm you are at Batumi. Second, the VHF AM Radio frequency tuning dial that is on the far left should be set to 13. The dial to the right of it, should be set at 1. The rest at 0. Third, confirm you are seeing VHF AM in the top of the Communication Menu when you hit the Hotas Mic Switch FWD. Fourth, confirm you have not messed with the intercom panel. The main function dial there should be at VHF. If these last few checks dont solve it, then it may be your install, or you are doing something that I can not envision that is messing things up. Let me know, and we can work on it after confirming the above checks.

On the VHF AM, are the Mode Select dials on MAN for the left one, and TR on the right dial?

Thanks for the heads up Greb! getting them now. BTW Greb, do you follow the Uninstall/Driver Cleaner/Reinstall method? I have always done it that way and now I read in the Nvidia install procedures that that is not needed anymore. http://www.nvidia.com/object/drivers_faq.html Q: Do I need to uninstall my older driver first? A: No. It used to be the case that an uninstall was first required. Today the recommended method is to overinstall the newer driver on top of your older driver. This will allow you to maintain any current NVIDIA Control Panel settings or profiles.

What is the tower frequency? Which Radio are you putting the frequency into? Are you using the correct HOTAS Mic Switch for the radio you are tuning? Are you waiting until after the APU is on, and the APU Gen switch is on, before you begin messing with the radio's?

Having suffered through the experience that was Vista, I can say with total conviction that moving to Windows 7 64 bit, was a great move. If you can afford it, do it.

Glad to help.

Hi Tom, welcome to the Forums! Be sure to enable your access to the Beta Forums. http://forums.eagle.ru/showthread.php?t=61793 To add to what Mugenjin said, VHF AM Transmit function is handled by the HOTAS Mic Switch Forward. The UHF and VHF FM Transmit function is handled by the HOTAS Mic Switch Down and HOTAS Mic Switch Aft(Back) respectively. There are two settings for the Radio's in the Controls/Gameplay menu. Simplified or Realistic. I suggest you learn Realistic right off the bat. I put together a Radio Tutorial for those that want to learn the Realistic Radio see post #53 in the following link for the latest version http://forums.eagle.ru/showthread.php?t=61349&page=6

Hi Headspace, just want you to know why you may get a few questions regarding key assignments from some of us with the TM Wartog and a certain set of hardware. We have a few difficulties at the moment with it's programming software called TARGET. The certain set of hardware I am referring to is if you have the Warthog Stick and Throttle and have the legacy USB Simped rudder pedals which have toebrakes, that connect thru the base of the TM HOTAS Cougar, then you have 10 DirectX axis in total, on 3 controllers for DCS A-10 to use. You see right now Warthog users have a choice when running DCS A-10C. We can run without TARGET, and DCS will set up all the axis and buttons for us. DCS A-10C recognizes multiple controllers so the DirectX limit does not come into play. But we cannot easily configure the Warthog's keys to do such things as PTT and the other TARS functions. Or, one can create a profile in TARGET that sends all the same keybinds that DSC has for each button, and include the keybinds for TARS. The downside with this is that when you run the profile, TARGET virtually unplugs the Stick, Throttle, Rudder Pedals and combines them into 1 virtual controller. This has it's drawbacks as the limit for DirectX axis in one controller is 8. If you run the TM Warthog which has 7 axis, then add Simped rudder pedals which have 3 axis, you total 10 axis and exceed the DX limit for the 1 virtual controller. So user's with this hardware config have to pick between a few options. 1. Run without TARGET and use programs like Autohotkey http://www.autohotkey.com/ to run separate scripts alongside all the other programs to emulate the joystick buttons as keypresses for TARS. The downside is that Autohotkey is not easy to get set up. 2. Run with TARGET, create a profile, and decide which of the 2 axis you want to leave out. (I have read you can unplug your rudder pedals before you run the TARGET profile, then plug them back in after TARGET makes the 1 virtual controller. Then DCS will see 2 controllers, the one virtual and the rudders. I have not tried this so I can not confirm that it works.) I hope Thrustmaster changes TARGET in the future to enable it to create more than 1 virtual controller. This would solve the DX axis limit of 8 per controller.

You're welcome.

I will be glad to help. Let me know when you have read through the tutorial. Until you have the basic's down, there is no point working on the more complicated issues. Just so you know, the quick missions have the radio's set up and ready to go. What Mission are you having trouble with specifically?

If you have any questions that the tutorial does not answer, please PM me or reply here and I will be glad to help you.

Can you open a PDF? The tutorial is also provided as a PDF at that link.

I know I am going to seem like a wet blanket for this post and Conure I'm sure you have the best of intentions and are only curious, but you never know who is who on forums like this. Best policy is to not provide any information that comes close to restricted/classified/secret. You wouldn't want anything said in here to compromise the safety of the Real Life Pilots who fly not only the A-10C but the other platforms that share the same components/systems.

Thanks Shadow, to answer your question, knowing which keys that are free in A-10C is needed because a couple critical TrackIR functions need key assignments to work. Mapping these TrackIR key assignments to the TM Warthog would require the use of the TARGET Software which most are avoiding at this time. Hope this helps you understand.

No, but there is a PowerPoint/PDF tutorial with pictures at the link above. Look it over, and at least give it a try.

Sure is! John Wayne played Marine Sgt. John Stryker in the classic film "Sands of Iwo Jima". IMDB link: http://www.imdb.com/title/tt0041841/

Hi Vega, I would suggest checking this out first(Post 53);http://forums.eagle.ru/showthread.php?t=61349&page=6 Then go back to the mission you are trying to communicate with your wingman and check the briefing to see if it says what frequency your flight is on. If the information is not available in the briefing, then you can open the mission in the Mission Editor and click on your self and your wingman. Take note of the freq listed for each plane. Based on the number, you will know which radio to use to contact your wingman.

NP

I can still pan/zoom the F2/F6 view with my mouse.

I cant watch the track right now, but it sounds like you did not have your target set as the SPI (Sensor Point of Interest) (to set as SPI hit TMS forward long) Visual confirmation in HUD will show TGP diamond symbol with a line coming off of it. The steering symbology is based on your current SPI. If you did not set the TGP locked object as SPI then most likely your current steerpoint was the SPI and that is why you missed.