noisy_lightning

Anyone been able to bind the mouse stick on the throttle of a X55 to the TDC? Seems a waste not being able to but for the life of me I csnt make it work. Sent from my LG-D855 using Tapatalk

Set the HSI to Cv Nav, knob bottom right. The aircraft is bugged.

They don't scroll through the modes no. I have had to bind different buttons to each individual PRF.

Double check the key bindings in DCS for the zoom issue. A couple of updates back the axis on my X55 were messed up and I had to remove a few binds I hadn't done myself. Sent from my LG-D855 using Tapatalk

Seems to do the trick. Cheers!

That may well be it then. Never noticed the auto disconnect before till now so assume it was part of the problem. There was definitely a cross wind though as when I switched to the F15 and took off it was noticeable. Thanks.

I am unsure if this is a Mirage module problem or if it was the Open Conflict server that caused it (unlikely for the server I think). However when I lined up, went to full power and released the brakes, like usual to about 100kt I keep nose wheel steering active, and then disable it once the rudder comes into effect. Today however nose wheel steering disengaged itself at 54kt repeatedly but at the same time went full lock left which put the aircraft into the grass end rolled it. I was not the only one on the server with the exact same issue and it happened on four separate occasions.

So I recently got FC3, I have had no issues binding HOTAS (X55) buttons in the other aircraft but for some reason on the F15 they just dont want to play ball. I should start that the only thing I have bound outside of the game is the air brake as its easier to make a macro to bind that to my specific air brake button. Everything else is bound in game. Well, the main one that just doesnt play is the Cannon, I have it bound to Trigger 1 on my stick which, however when I press this it cycles through modes, I double checked the bindings and there is no accident double double binding and so far have been unable to get around it. Equally, the trim hat doesnt seem nearly as responsive as the other aircraft of modules I have, it works but very very slowly! Any help would be appreciated!

I had a look in the software and changed it from an 8 way to a 4way and it's sorted it. Thanks!

Hi guys, I wasn't sure which section to put this in as I don't think it's a game bug but at the same time I am not sure if it's a hardware issue. I just bought my X55 and have mapped the coolie hat to the top hat switch on the right throttle (I have also tried the lower hat switch to test both with same results) Basically I have bound the hat in game and the i seem to have issues setting the right MFD as SOI it seems to not like the long press in game. I have no issues with the long left or up short to set the other SOI but just the right. I have tried binding the hat in game and in the programming software for the X55 and both return the same results. Strangely in other aircraft like the hawk I have no problems with the hat which is where I am thinking it's the A10? Hopefully someone will have a solution for me as I am falling back to using the keyboard to select the SOI at the moment.

Ok, this is my current situation. I downloaded DCS World this morning, and installed the A10 module, so now I have a working 64bit install (which is a LOT quicker than the steam version!!) I used a number of headtracker.dll files now in the following folder. C:\Program Files\Eagle Dynamics\DCS World\bin\headtracker When I now load the game with any of the DLL and am in the cockpit there is no head tracking. However I know the DLL has loaded properly as I can no longer use the hat dial on my joystick or the numpad on the keyboard to look around, and there is no log file generated with an error. I am using Windows 7 64bit, Running the most up to date DCS world, Free Track 2.1 (as 2.2 refuses to load giving me a violation error) Free Track has TrackIR enabled so I am failing to see what the problem is?

Thanks for that, do you know what the original line is for the head tracker portion, and I shall give it a go. I am downloading DCS World as I type this and will keep you updated with my progress. Cheers for the help guys.

Wonder if you guys may be able to help. A while back I managed to get DCS:A10 to work with facetracknoIR (FTNIR) but it wasnt that great at tracking movement in game and so I bought a PS3 Eye and built a 3 point IR LED clip. Freetrack works perfectly with the setup and tracks my clip with far greater accuracy than FTNIR ever did. My problem is that now I have changed the software I cant seem to get FT to translate in game to DCS:A10. I am running the steam version which is 32bit and as such have the 32bit headtracker DLL in the right place, with the input.lua pointing to the correct file. However unlike before with FTNIR it just doesnt actually work in game at all. The DLL file as far as I can tell should be the right one still, and I have tried running TrackIR Fixer along side it with no possitive results either. Any help would be excellent with this. Also while I am on, since I own DCS:A10 through steam, could I then download the 64bit version od DCS World and use the same CD Key on the A10 Module? Thanks

I just had the same issue on this training mission too, got to the exact same point as the OP and also ijozic and then it crapped out despite the fact as far as i could tell the pod did as i told it!

Just tried those myself, work a treat for deadzones, may alter them a little though as I am having to move my head far more than I would like to look at the side panels. Great start though thanks!

That was on my consideration list for about 2 seconds till I heard about the non-moving stick! As I said, I am away for four months at the end of the year with little to no internet and location its not like there is much else to do, so I bought DCSA10 as a "project" if you will to give me something to do other than just DVDs. I am getting there at the moment with the basics but serious starting to struggle. Think I shall ask for the TM:A10 as an early Christmas gift from family and my girlfriend!

I have got to the point where not having a decent stick/throttle setup is actually hindering my enjoyment of DCS:A10. And with a requirment to spend 4 months away from civilisation due to my job coming up in December decided I am going to spend some money. I am currently very tempted by the TM A10 setup, but wondering what peoples thoughts are on others such as the X52 Pro etc

Seems to be fine on my HP-Envy, the limiting factor for me is the camera as I said. But its better than not having any head tracking and much easier than using my hat switch on my joystick. Let me know how the PS-Eye works!

I have a crappy one built into my laptop, only runs at 30fps so the track isnt as smooth as it could be. Apparently the best one to use is the Playstation Eye as it runs atr 100fps. I am tempted to try and find one on ebay and try it. The free track software can track the TIR head clip, borrowing a headclip off a friend this week so I can try it and if that works better I am going to buy the head clip and stick with that.

I just tried it out for you, if I start close to my screen it locks onto me within seconds, and I managed to get about 1.5m away and it still had me. If I lost the lock on purpose it would not find me again afterwards beyond 1.5m.

Good idea. The file I ended up using was this one LINK

I have actually solved my own problem using a newer version of headtracker.dll which I found on these forums. Just need to alter the sensitivity now and get it how I want it. Way too sensitive by default but liking what I have so far!

Hey, I have searched high and low on the internet and cant see anyone with similar issues to me and so I am resorting to posting here where fingers crossed someone will be able to help. I have DCS:A10 through steam which runs fine and normal. I have also installed the correct 64bit file "headtracker.dll" in ./bin/headtracker/ and made sure its the correct directory in input.lua so I should be good to go. I have also intalled FTnoIR which runs and tracks my face perfectly in the window within the program itself. The A10.ini has been registered and the settings loaded into FTnoIR. As far as i can tell from the instructions everywhere that should be it. When I load DCS:A10 it should need nothing doing. I have tried numerous times and it just fails to track me. But instead I guess the best way to describe it is padlocks the pilots view pointing directly down and either left or right at the panels. Anyone got any ideas? Specs wise, I am running an HP Envy 17-3D. I have everything set to max settings and at 1920x1080 and DCS cruises along at around mid 20s to 40 odd depending on whats going on. Win7 64 home premium.