Ayindi

Navigation in DCS is pretty easy I think. Since you are flying rather short routes you just have to follow the lines in your TAD. Difficult Landings can be done by doing your own missions in the mission editor. Wind, bad weather all is there, but you basically need to do it on your own. I would still say, if you are more interested in "just flying" and navigation stick with FSX, but if you also like the weapon management and strategy part DCS is really worth a try. A10C is probably the most complex module you could get. This module would give you the best in all relevant categories. Hint, its currenty for 40% off on steam (not sure about the regular DCS shop) so it would be a great time to start with it in case you dont have it yet.

I think finding targets, is actually a very tricky part, be it in reality or in DCS. Thats what JTAC and Awacs are good for and if you have to do it for yourself this is VERY difficult. The actual flying is just a rather small part in DCS (at least in A10C) A10C is more a "weapon management simulator", a "strategy game" (what to kill first) with a small "action part" (= flying). Thats also something I had to learn. Contact JTAC to get some targets, find them with your targeting pod, then probably turn around to make a new approach, set markpoints,probably turn around again to make the final attack run to actually shoot things. Thats probably also how its in reality. I'm quite sure every A10 pilot has flow more circles in his / her lifetime to plan things then any other pilot. :P I would expect that real pilots with better training can basically do this easily in one or maybe two approaches, but for me with limited time and training its usually flying back and forth several times (or in circles) until I can shoot something. It will get better when you become more skilled. So dont expect to spot your target and then pewpew... :D Just dont be too hard to yourself and expect that you do everything as good as you would expect from a real pilot. Always remember that those guys spend hours and hours and hours of training and get paid for this and they have the real controls. They can touch things in the real cockpil while you have to use the mouse or find the right key on the keyboard so you are also in a "handling disadvantage" even if you have a HOTAS and the MFD Panels. You do this for fun and will most probably never get as good as a real pilot just because of the lack time you can put into this or the lack of equipment. This is also something I had to accept.

Hi, not sure about FC3 (dont own it) but I have seen the same issue with the Huey Training and I think also some other modules. Some work though...

Actually, I did not have much problems I just needed to delete the general "config.lua" (not 100% sure about the name - cant check now) and started up the openbeta. I got a strange stretched screen, but I could enter the options, reselect the approriate resolution and since then everything worked fine. There was no need to also delete my controller config and it was ported just fine. I dont have the MIG 21 module though. I can 100% confirm that A10C and HUEY did work flawlessly.

Great thanks, it has helped me a lot! :) However, I have some remarks. I'm sorry in case these have been mentioned before, but I dont wanted to read 10 pages. So just in case: please forgive me! ;) The instructions.txt says basically "just" copy it over your current file structure and it should work. At least thats how I understood it. Since the lua files contain the USB id which is probably unique on every PC I had to manually load the "diff" files in the main DCS menu (being in the plane does not work) to make it work. Not sure if that was clear to everyone else, but at least for me I had to try a little. Maybe the instructions should be updated to be a bit more "dummy" safe? :D

Thank you! Deleting the config folder in the mission worked fine! :) Really seems to be an issue with the german version of this mission. I also tried the EN version and this one worked fine initially.

Thanks for your answers so far. I will check that with the lua files. I can definitly exclude the possibility of external infrared sources like sunlight or other stuff. I can really reproduce it without any problem. Load this mission -> wont work, load another mission -> will work. It's definitly something with the mission.

Hi there, first I was not sure were to post this. This is some kind of issue with the hardware (=TrackIR) and I can also not say if this is just A-10C Module related (I dont own other DLCs yet). However, since it is a little strange I decided that this forum is hopefully still the right place.. My problem is that TrackIR behaves not correctly in the standalone mission "In the gras" (German Tile: "Im Gras" - not sure what the english title is) Normally, when I yaw my head I can usually look like 170 degress back in the A10 which is realistic behavior, but in this one mission the head movement does not stop at 170 degrees and I can twist my virtual neck about 270 degrees around. This is very annoying and makes this mission basically unplayable because I constantly loose orientation when I look back. My virtual head just turns much too far. Overall precision and sensitivity seems to be the same as usual but in this mission it just does not stop turning of my head at 170 degrees. I tried several other missions: I have flown basically all instant missions, have played some autogenerated missions and completed all training missions. In all of those missions TrackIR behaves correctly. Just this one mission is strange. (and maybe some others I did not try, yet) Has anyone made a similar experience and knows a fix? Unfortunately, this really makes this mission unplayable. Its just one so far, but its still annoying. Has anyone a hint what could be wrong here? Thanks in advance! :)