Le0kong

If you want the head movement to be more sensitive, that is, turning your head a little translattes into the virtual head turning a lot, there's two ways. Either just increase the 'Sensitivity' slider in the Profile page, for both Yaw and Pitch. Or in the Curves tab right click in both Yaw and Pitch curves and select Linear. Fine tune the right upper most dot to the right to how many degrees you want the virtual head to move. The vertical show how many degrees you real head moves, and the horizontal to how much degrees it should be translated. So if the curve is straight line in the 40 degrees in both horizontal and vertical you have a 1:1 mapping from your head into the game.

Great narration! Just a direct explanation, no Library of Congress/Car analogies. Talking in a calm way, not like everything is about to explode. Much better then the normal Discovery/HistoryChannel/NG exaggerated narrators. :thumbup:

The great thing about the A-10C was that nobody had any idea in how to use it and how it avionics work. It was great in the beta with most topics being discussions on how things work, and basically the entire community learning at the same time. I learned a lot from this, more then the manual even. But if the next module is a F-16, and since it looks like most here played Falcon, most topics will be on "why things are not working the same as in Falcon". For me is the contrary, why show the model prior to releasing said module. The improved external model is a great 'marketing' point to sell another module. I think this level of detail is the new "base" on which all external models will be upgraded with the time.

Just a note to make sure if the TV you can get is capable of displaying the PC image 1:1 (pixel per pixel, no resizing/stretching/over-scan) and with no post-processing. Some cheap TVs, specially with all the crap TVs on sale in this country, can't do that. Normally there is a function called 'Game Mode', 'PC mode', '1:1' or something like that. But it's better check on specialized forum to confirm the TV exact model is really capable of that, before buying it.

The only time i see the CDU display this way is if the CDU is in the WP page and is showing the MARK point 'Z' and you do a gun run. But it works normally after, you can change the waypoint with no problem.

First try the fix in the second post in the FAQ here: http://forums.eagle.ru/showthread.php?t=67747 If it still crashes then delete the 'Input' folder inside the 'Config' folder in your 'Saved Games' folder: '...%user_folder%\Saved Games\DCS Warthog\Config\Input'

Not sure if that's what you want, but the rule i used to map the HOTAS to a joystick(when i was using a 360 controller, very limited in buttons) is by order of importance and frequency of use. Here it is the order i used: 1 - Gun trigger, 1° and 2° stage on separate buttons, weapons release 2 - CMS forward&aft first (fly with countermeasures on semi-auto, so no need to change profiles, only dispense and stop) 3 - Speedbrake 4 - Slew ( i love looking around with the TGP, even when there's no reason :)) 5 - DMS hat (always zooming the TGP and changing weapons/waypoints) 6 - Trim hat (if you practice to trim before you move, you can even move it to the keyboard) 7 - China hat (frequent use to toggle the FOV, and slave the sensors) 8 - TMS hat (changing from AREA to POINT, to lock on vehicles on the move needs to be done fast) 9 - Coolie hat (at least the 'up' to make the HUD SOI, the rest you can use the mouse and click on the MFCD) 10- Master Mode button (in case you spot a helicopter right in front of you, changing fast to A2A helps a lot) The rest is not so bad if you need to use through the keyboard, but if there still space on the HOTAS: 11- Boat Swtich 12- Autopilot 13- NWS (Pinky) button (use auto-lease and you will only need it on takeoff) 14- MIC hat (the default ones in the keyboard are horrible, either use 'easy comm' or change the keyboard one to something more easy to remeber) 15- Pinky switch *If you don't have a head tracking device then adding a hat to move the head around should go together with the slew on importance. In my case i used two modifiers buttons, this way you can use like there's three modifiers by using the two simultaneously, like this for example: HAT -> move view around HAT + Mod1 -> DMS HAT + Mod2 -> TMS HAT + Mod1 + Mod2 -> Coolie So with just a hat and two buttons you now have FOUR hats! :D Looking for the profile other people created for the same HOTAS that you have can help give you ideas too. And don't forget to print the tables in the manual from pages 84 to 90, and write notes on them to where you put them on the HOTAS, that helped me the most.

I think you can do that on the A-10C with the update function on the CDU.

For me FLIR just need some fine-tunning. At 1:30 on that video you can see the trees, but only the trees outline, there's no 'texture' in them. On DCS the trees texture is very visible and sharp, it could look more like in the video by simply being blurred or of lower resolution. Another thing is making all trees of the same light levels, on this screenshot some are white others black.

None that i know of. And since the last FreeTrack as released in November 22nd 2008, i don't have much hope. :(

Since it says this on the Natural Point of View website: I think this mean we will need not only need a new TIRFixer but a new FreeTrack version capable of using the 64bit interface of DCS.

Working very well with A-10C here too. Most high settings, at 1920x1080 and 4xAA/8xAF. Got mine some 9 month ago and is still working great, even with overclock from 850 to 920 and memory from 1200 to 1315.

I never change anything in game, since after applying the TIRFixer for the DCS engine it sees FreeTrack as TrackIR. All adjustments i do through the FreeTrack program.

Like Burner said, it works, you just need to patch the file again after installing the patch.

You can't link directly to the DCS executables, you need to pass some arguments toghether on the link. Here is the 64bits multiplayer for DCS:A-10 for example: "G:\2\Eagle Dynamics\DCS A-10C\bin\DCS.exe"[color="Red"] --net-mode gui[/color] I don't use Steam, but i think that is the problem you got.

Thanks for sharing these pics Viper. I have the same headphones then Alex on the A-10 picture. :) We need a making-of now.

You can, just remeber that if it is a Type 1 or 2 you need to call 'IP INBOUND' and 'IN' before the wingman attack or you get a 'ABORT, ABORT, ABORT'. Although i'm not sure if it will work well when the attack needs to be done at a precise heading, since you can only say north, south, east and west.

Haven't tested yet since performance of the Final is excellent on 32bits for me, even on my slightly-old-cheap-midrange computer.

Here is a screenshot showing what we mean. Note the gun cross is not oculting the HUD SPI box, that is what that IFFCC option does.

I'm using it through a Wiiremote and it's working very well. The problem it's only works in the 32bits DCS:A10C using TrackIRFixer. I heard you can use PPJoy to use it with the 64bits DCS:A10C, but i never tried that). So, it does not have Freetrack capabily, but there's a workaround. You can get TrackIR Fixer here: http://naturalpointofview.blogspot.com/

Attaching a track could help, to give you a precise answer.

If i remember correctly, to change weapons in game mode you use the 'D' key, 'M' is for the MasterMode in sim mode.

Note that the option name is 'CCIP Gun Cross Occult', it only works when you are in CCIP mode. In GUNS mode it will always occult the symbollogy. Never seen anybody able to any other way.

If the trim is not working try turning the force feedback in the options off.

Yes, you can use them and both simultaneously too. Like Crosser said just select them manually, it will say 'Air to Air' mode, use the 'Weapons Release' on the HOTAS to turn them on and off. I tried blue and red and works ok.