NhiTrac

Thanks both, works a treat. For some reason I thought you couldn't assign it like that :)

Shouldn't be a problem as I'm using it now on Win8, both drivers and software. That was one of the things I noticed as well re TM not having Win8 drivers and software. I guess they didn't need to?

You folks using the paddle to centre TrackIR, is this through the TARGET program? I love how my TMWH (picked it up yesterday) is PnP for DCS A-10, however I'm struggling to find out how I can map the paddle to reset track ir without using any other program... Perhaps someone has a profile that emulates the PnP function for A-10? Cheers all

Serial #11109 Sydney, Australia

Think I know what I'm doing wrong... Not lasting when making a target my SPI. Carried 12 GBU12s to practice first two completely missed, after I started lasting when marking a SPI, they all hit. Even at different altitudes. Could this be it or just coincidental?

Thanks for that. I'll give that a go over the weekend too. Btw, if you're selecting lase at 30s before impact, what happens when the impact time is less than 30s? E.g 8000ft should be less than 20sec before impact I think. Ps. I'm a bit confused after RTFM, page 552: Tip: for best accuracy, start to lase the target 12 seconds before impact. Page 556: Tip: For best accuracy, set this to 8 seconds before impact. If set to 0, the laser will default to firing 4 seconds before impact. Given second talks about auto lase, I thought it'd be the same? Edit: Page 559: Note: To improve accuracy, it's recommended that you deliver these bombs from above 15,000 feet AGL and delay lasing the target until 8 seconds before impact. Truly confused :helpsmilie:

Havent had the time to try it on 12 sec as suggested above, though I've tried it with autolase and manual lase.

Cheers guys I'll give 10 to 12 sec before impact a go. And I'm certain the laser isn't being masked as I fly dead straight until impact.

Semi thread hijacking. Are there any guides out there as to when one should fire the laser? Maybe a scale of some sort? I understand ~15 seconds before impact is recommended for bomb release at 12,000 to 15,000 ft. However it seems to be a hit and miss for me. A lot of the times the bombs waaaaaaay overshoot my target. Sometimes I lase instantly and it falls on target. Turn around, do the exact same and I completely miss. Can't really see a pattern here... Any help appreciated. Cheers

My two months old X-52 Pro is going back for a refund this week or the next. My issues: Stick Unit - Whole stick came a little loose. Can push the whole stick downwards towards the base a notch. - Springs quote tacky and doesnt allow for smooth control. - Random fluctuations along the stick axis. E.g i'll have autopilot on, hands off stick, then bam I'm rolling left. - Random presses of the hatswitch Throttle Unit: - Electrical zapping noise when the lights on the throttle slider is on (the ones that turns green/red depending on throttle lever location). Noise gets better when light is turned off. Worse when at max brightness. - Pretty much all the swivel knobs have had fluctuations at the centre. Only way to fix this is to have a massive deadzone which, well. Isn't the best. I probably got a dud unit but after some reading on the interweb, i'm not the only one with these issues. Thankfully the store have agreed to a refund. Am tossed up between the TMWH and X65. So far its about 55% TMWH, 45% X65...

Can I just chime in and say that TrackIR is an absolute MUST with any flight sim. Hell I even find it useful in FPS such as the wonderful ARMA series. And its a true saying, once you go TrackIR, you can't go back. Give it a go, you'll wonder how you've been flying without it for all these time.

Thanks again guys. I think I almost have the basics down pat. Will continue with the 'practice practice practice'. This certainly is a rewarding sim once you nail something. Cheers

Cheers guys, I'll give that a go. Hard now splitting my time between this and ARMA3!

While we're on this subject, whats the most efficient way to get the senors onto the ground when all you have are steerpoints? I've been doing the Weapons Training single mission a lot as that lets me fly around and test different techniques and weapons etc. However when I "TMS UP and CHINA HAT FWD LONG", it always points at the steerpoint, in the sky... About 10,000 ft up, which makes it a bit hard to slew the camera down to the ground and find the target. Surely I'm doing it wrong? I watched a youtube video which says you can manually edit the elevation point in the CDU. However following that same process, it was already at zero. Any help would be appreciated. Cheers

Yup. Face palm moment it is. Thanks both. That explains it and that illustration just nails it in. Ps I've done the landing training mission a number of times and it works fine, can pick up the ILS without a problem. Its when I do a different mission and attempt to land myself that I get into trouble. More practice it is. Cheers again.

Hi crew, Absolute NOOB and pretty sure this is going to be a face palm moment for me on the first reply, but am desperate, so here it goes... I'm and am struggling a bit with the very basics, navigation! Have been trawling through the gigantic DCS A-10 manual/forums searches, youtube vids etc but can't seem to find my answer and am hoping you guys can help. I can navigate just fine following waypoints etc, however if I'm coming into land and ATC gives me a heading to fly E.g. fly heading 200 for 8 (I turn so HUD tape is indicating "20" which also matches the HSI needle), I then check ATC and ask for assistance (azimuth reading?), it'll tell me I'm actually flying heading 160 or something like that. I.e. a totally different heading to what I'm currently flying, which is what they initially gave me. Have I gone off on a wrong trail and totally missed something so obvious with regards to using the HUD's Heading tape to navigate? Looking forward to any help I can get. Feel free to have a giggle too. Cheers

Mate, you have indirectly solved my problem! In summary, I'm using an apple keyboard so don't have a "Pause" button so I remapped that to "P", and Stage 1 Trigger to "Shift + Space". However it seems that DCS does not like the "Shift + Space" combination and therefore doesnt work. Just defaulted everything and remapped the pause to something else, and whatdoya know... It works!!! Thanks for that. Now I can get on with the other basics. :beer:

Hi all, Complete noob here to both the forums and DCS A-10. Hoping to not go O/T too much, but I am struggling to get my X-52 Pro Stage 1/2 Triggers to work in-game. Currently have Stage 1 Trigger mapped to "Shift + Space" which should enable PAC. Stage 2 Trigger is mapped to "Space" which should fire the GAU-8. Both are just key presses. However nothing will happen in-game when pressed. If I map Stage 1 Trigger to "Space" ie Guns, then it'll work fine but obviously without PAC enabled. Can anyone please point me in the right direction? Thanks :helpsmilie: