GurbY

All buttons show response in the joystick control panel: both scrollwheels push and scroll and the middle buttons evenso. I waited till prompted to connect the stick... I did remove the driver and installed "fresh" again (removed everything in registry), still the same..

OK; I will take a look at that when I'm home. After I received the X52Pro I downloaded the latest drivers from the Saitek website. Could be the directoutput driver..?? When I don't have a profile loaded, the screen says "Mode x" (where x = 1,2 or 3) and "No Profile". Thats it. BTW, I've been searching but can't find the 6.6 driver you mention...? Do you have a link?

Nope. When I get to lets say 100Mhz, and turn the wheel, nothing happens...

I'm using OpenTrack, although not with cam but with smartphone tracking and I must say, very pleased with it!

Ah... NOW something is happening...! I start the d.o. file (screen stays black and does NOT close..?) and start DCS. I choose an A10 hot mission I created. What I see on the MFD is: TENS Power Volume Knob 1, 2, 3, 4 100Mhz pushing the scroll wheels changes the above. That's all that is happening, in the A10C cockpit nothing changes. To be complete: - I have a X52 Pro - I own DCS World A10C

When I copied the directoutput a10a.lua in scripts, I saw there already was an export.lua file. Is that correct? And if yes, I assume I have to overwrite it? **EDIT** I looked at the export.lua that was already in the dir: nothing in it. So, I copied the above file in the dir. I started the A10 lua file, again: a very quick (dark) cmd window. After that: in DCS, in the A10: my X52 Pro MFD still shows nothing, only "Mode 1" and "No Profile" (and date and time ofcourse, which changes when I use the scroll- or push buttons...)

Algerad3: I followed the above post. I installed Lua for Windows (5.1) and put the saitek.dll file in the above mentioned dir. I click on the A10 lua file, but all that happens is a black (cmd) window, which stays like that until I stop it. If it runs, the MFD on my X52 Pro becomes blank; only time and date is visible. If I run DCS and start an A10 mission, nothing happens. If I close the cmd window (still black..) the MFD gets the "No Profile" message again. What am I doing wrong..?? **EDIT** I rebooted; now after clicking the A10lua file the cmd window opens for half a second or so and closes. Still, nothings happens on the display in DCS...?

See the main screen - Encyclopedia....

OK Tnx, will take a look at that! I found something for the iPad (A10 Virtual Cockpit Free) but it would only do rather limited stuff.

OK; but how do you set it up on DCS? I found several sorts of software (like Air Display) to turn an iPad into a second monitor. But what do I have to do in DCS..?

In FSX I had an android tablet as my 2nd screen, a moving map display. Does anybody knows if this is possible in DCS either on android or ipad? (not map per se, but radar or other mfd)

Great action, Bitmaster and Griffon26! Kudos to both of you!!!

Charts are outdated, I agree. But as an aid to "which runway where" it gives sufficient information IMHO.

If you have an Android phone (prob also available for Apple, dunno), go to play store and search for DCS manager. Checklists for Ka50 and A10 and all airport charts and -comms.

I managed to get a good lock with tms up this time. Force correlate didn't work out, have tot experiment a bit more with this. Tnx for all the info!

Ok, will try fc! Tnx!

Sorry, but yes, I use narrow fov... When I zoom the tgp 100% the tgp is point in the middle of the target...

Hi, First of all: I'm new here, but are using DCS quite some time. Bought the A10C in the christmas sale. So far I'm getting along reasonably fair. However, I do have an issue with shooting mavericks. In short: I created a mission (flying 6000ft above Batumi, enemy AAA at Kobuleti). I select the MAV (AGM64H) on the DSMS. EO is on, TGP is on, etc. With the TGP I slew to one of the AAA targets. TMS up to make it Point. TMS up Long to make it SPI (I get 'TGP' in the HUD instead of 'STPT'. China FWD Long, and the MAV on the right panel slews to the SPI. I wait till the target is in range (under 9nm) and start clicking TMS Up (with MAV as SOI) to try to get a lock. However: it will NOT lock the target, although it is pointing right at it. What I have to do is slew the MAV sensor just a little under the target (I'm about 5nm out now....) so it starts moving again, and when it moves over the target again it locks itself. This can't be how I should do it I guess, but I can't find it. Read (printed...) the manual and did the step-by-step actions as described. Also read the threads on this forum, but can't figure out why the MAV doesn't lock albeit the correct pointing at the target... (again: when unbreak the lock from the SPI and move the MAV, it locks itself and I can shoot a missile...) What, o what.. am I doing wrong...???

Weird... I had it enabled, didn't work. Disabled: didn't work. Enabled it once again, and... WORKS! Anyway, thanks for your reaction!!

Hello, I bought the Huey and are trying to get familiar with it. So far most of it is ok. However, I cannot find a single way either to aim the co-pilots flexible sight (and so, aim the corresponding gun) or aim the guns of the door gunners. I tried with TrackIR aiming on/off (I don't have TrackIR), alt-c changing mouse input, the various keys like ,./; but nothing is moving either the sight or the guns... What am I doing wrong..??