Weegie

Are you using the TARGET GUI or scripting? I'm guessing the GUI. A lot of people have problems with TARGET and don't use it for that reason. I used to use the GUI but now script, it's pretty powerful and can make a huge difference to the versatility of the HOTAS. Personally I'd gladly pay for a similar generic keymapper, let alone the axes, but there is nothing out there that comes close to it, especially if you persevere and take the time to learn the script. As far as your problem, as already said, don't try to get TARGET to recognise anything. Just put in your keybinds and make up a profile, then run it. Open up DCS and it will recognize the profile automatically. I've never tried to get TARGET to recognize anything. You can check if the keybinds are working using the included Event Tester which is also in the TARGET package In your settings you'll see that the individual TM compents have disappeared and been combined into a TM virtual controller. TARGET can be a bit finicky at times but overall for me it works really well

You need to remove the brake lever pin first, I can't remember correctly but think the pin is held with a circlip. You take the pin out and pull off the lever. After that it's just as you said, remove the Allen/Cap screws and split the stick. Then there is another screw to remove the tailpiece itself, but it really is very obvious when you take it apart. It doesn't fall to pieces like the A-10 stick with the top coming off, much simpler. Don't sweat it, you'll be fine The only problem is if you have ordered a metal tailpiece it need to be tapped for the screws, which can be tricky, but doable.

Ordered a SuperTaurus & got it in a little over a week. I was expecting a long wait and was delighted when it arrived so fast

Heh Bailey I noticed that you didn't use the manual tuning in the Viggen I managed it it's quite a carry on, I've also got a selector command for the base channel that jumps past these ALLM channels that are in the selector. The command is a bit slow to execute as there are a few calculations and a bit of manipulation required (and my programming is a disgrace) I've got frequencies for UHF & VHF for all the Fields in Caucasus, Gulf & Nevada in the profile Drop me a line if you want to add it into your Viggen profile

I installed the angle tail piece into the Hornet Stick, it's identical to the Warthog and is easier to install. I can't remember the details the only thing that's a little tricky is taking out and putting back the lever at the base. As far as angle I don't know what the original/real stick has. Personally I always went for the 13 deg angle 15 deg offset, but it's a personal thing

Anybody know where the Kneeboard is meant to be? I can't find it, there was a statement about it being present in the Knneeboard builder too, but dammed if I can see it

Haven't tried the Hornet for ages so returning to it ATC in landing mode is great but I cannot get it to hold in cruise, flaps auto, gear up cruising around 300 knots, speed just decays

Thanks for coming back on and reporting that Pudu I'll need to try it, just haven't had much time in DCs recently and when I do I just always go to the Open Beta

Hi Pudu No I didn't get an answer and I haven't got around to experimenting with it If I do try it I'll post up and drop you a PM to let you know the outcome

slaintemaith As Andy t has said, but I wonder if a Windows re-install has screwed with the USB adresses for you devices. Check in your Saved Games\DCS\Config\Input\<Plane Name>\<control type> for any module you like. If the HOTAS mappings are gone and replaced by the DCS default. Check to see if the filenames for the devices are the same, on your backup and on the new install. If the long address in curly brackets is different on your new install and your backup for a given device. Then you can get the HOTAS settings back by copying the address in the new install and rename the ones in your backup to the new address. Then delete the file in the new setup and copy the renamed backup over to the new Saved Games\DCS\Config\Input\<Plane Name>\<control type>. If you followed that I'd try it on a device to confirm it all works then progress to the next one. Of course don't delete or change anything before making backup copies in case it all goes pear shaped. If you backup up then you can re-enstate Bit of a pain but its happened to me more than once. Keeping backup copies is a must.

Yeah sorry for the late reply I just opened the game with Vaicom open and no probs, but I have yet to test it fully. Too much other stuff going on like the Ghost KC-130

Not saying it's the issue but are you running Vaicom? There has recently been an update but that was my problem initially Run a repair, then, do not start DCS with Vaicom enabled if you've not downloaded the latest Vaicom patch

Yup I disabled Voice Attack, did a repair and got in Thanks BIGNEWY, I actually found it in another thread a few down Looks pretty awesome

Having a similar problem Downloaded the update and now it just hangs at 10% on the splash screen

I'd like to see some info on the starter too I find it difficult to believe that the starter was either higher or lower rated than the actual voltage available. I only know automotive DC starters but in my experience what would happen is exactly what grafspee stated at #11 Seen cases where coils are given over voltage to help ignition systems during starting, but I don't think that's relevant as aircraft use magnetos

After a little time bouncing and rolling, I think I found what I was doing wrong. On approach I developed the left roll and trimmed to suit. What I didn't know was when really close it dimishes, so with the trim in the left roll becomes a right roll. Now I just fly through it

It's Wake Vortice that's the culprit, I just disabled it in the mission................no roll I don't remember this before I always fly with it enabled and never had the problem, perhaps in the interim it's been tweaked. Thing is most comments I've seen from fighter pilots state that it's a little easier IRL, yet DCS is making it more difficult Oh well no point in bitching just need to suck it up and get more practice in Thanks for all the suggestions

randomTOTEN you may be right I noticed later that when a way out it seemed stable, when close to Herc the rolling to the left started. I can't recall Wake Turbulence being so severe last time, but perhaps its been updated. Ok I need to spend some more time establishing exactly what is going on and when. I'm not saying its not all my imagination because I just could be so out the groove and forgotten how difficult it is. Thanks for the replies, if I manage to pin it down more I'll post up Not saying its a bug at all just curious what others thought and why I seemed to be struggling so much

Yeah Ok perhaps that's the problem, I was flying with the throttles split Using a TM Hog throttle and the throttles are split I'll check that out. Surprised it makes such a difference with the engines being so close together, but I'll check that for sure Thanks all

Being flying warbirds and returned to the Hornet to sharpen my refuelling skills Flying a simple refuel mission with no wind & firstly it seems to always want to roll to the left. Trim that out and then it's rolling to right, it just seems difficult to fly wings level It's making it almost impossible for me to track the basket. I seen some post last year about it weathercocking into the wind but would have thought surely that was fixed by this time When I approach the basket it seems that the basket acccelerates to one side yet it tracks quite steady as I approach it until I'm close Is it just my imagination (not ruling it out) or has something changed, just don't remember it beiing this difficult before? Don't think it's wingtip vortices as I usually approach from below

I'm running one rev behind on the software and I use hubs without issue Are we talking GUI or Script Editor? Are you using keyboard commands in your TARGET profile (I assume yes) Have you tried using the Event Tester supplied bby TM to test that everything is working as it should there? I've had controllers not being recognized before but never anything that crashes the game, strange.

Well Grisly we at least agree on something I'm totally with you the TakeOff assist and the AutoRudder are BOTH to be avoided at all costs. Like you I couldn't control the aircraft worth a damm on taking off or landing. Regarding the whole flight envelope, I just don't know as with any one of these options enabled I just could not get off the ground, most of the time I don't understand how either option helps but I'm flying with rudders IMHO both of these options make things considerably worse in any module and the first thing I do is turn them off As already said though there have been a lot of posts about these options and quite a lot of YouTube tutorials will tell you the same thing You got to watch sometimes the updates will re-enable them, but it's pretty easy to know as you'll just crash out as the AI willl be fighting your inputs and it will not end well As far a liking or not liking it would be a sorry world if we were all the same and preferences are just that

Yeah I'm the original poster and I'm sorta wondering why you hate it so much. I don't do much combat so is it limitations there? As for flying I find it incredibly easy to fly, take off isn't hard and in the air it seems more responsive and less vice prone than any of the other warbirds. Landing and taxi-ing are a bit tricky, but the Kurfurst is IMHO a far trickier proposition especially to land straight.

Very interesting all, didn't realize the thread had come alive again. Got some more experimenting to do..................Now if I could just stop that nasty pull at the end of landing before coming to a stop. On landing, it's a fantastic module for trying 2 point and 3 point touchdowns. When you 2 point it, jeez does that tail stay flying a long time, seems much longer to me than the Spit. Having so much fun with this bird, it's a real challenge, I wouldn't have liked though to fly it everyday, day in, day out, for real, if the real thing was anything like approaching the behaviour of the sim and I think it probably was judging by its reputation Thank you all for the continued input

I've noticed this from time to time too, it seems to happen more with the Spitfire than other modules, but that's anectodal I haven't done any testing to prove it It normally happens on Multiplayer, I can't think when I've lost the bindings in SP. Anyway what happens is all the bindings go to default like a new module, as LeCuvier explained Shutting down and restarting DCS has always cleared the fault and brought back all the keybinds This has only started in the last week or 2, it will be interesting to see if more people start to experience it Again as LeCuvier states it's a good idea to copy your bindings and save them elsewhere in case DCS manages to corrupt them, especially if you've invested a lot of time setting them up