RedX

Like Mad Dog says above, it may be possible to achieve what you want without using TARGET software at all. TrackIR identifies joystick clicks just fine like other software such as TeamSpeak3, too. When mapping the keys, just make sure that there are no buttons depressed in your HOTAS by checking the status in the game controller section of Windows control panel first. Some software have problems otherwise. In A-10C you can add functions to the joystick column so that they are clickable with the ADD function by editing the Input config files. Just take the rows you need from default.lua in Config\Input\Aircrafts\A-10C\joystick and add them into your joystick profile. You may need to remove the custom mappings saved by the sim (the file with the long alphanumeric ID string of the game controller) so that the initial settings are read again from the files in the above folder. The "down/pressed" and "combos" may need to be checked for the rows added to the joystick profile file.

HOTAS WARTHOG Member No. 04624, Southern Finland. :cold:

Ok, hreich, here you go... I hope I didn't misunderstand what you want to do but I believe you want to do exactly what I did. I mapped my TM WH throttle to do landing gear, caution light and jettison weapons like this: 1. Open file explorer and navigate to <A10 installation folder>\Config\Input\Aircrafts\A-10C\joystick 2. use notepad++ to open file Throttle - HOTAS Warthog.lua 3. open in another notepad++ tab the file default.lua 4. find in default.lua the function you want to map in your HOTAS (which is not available for mapping by default, i.e., not clickable with ADD button); example for landing gear: find Landing Gear in the file (CTRL-f in notepad++), you'll see a row with {down = iCommandPlaneGear, name = 'Landing Gear Up/Down', category = 'Landing gear panel'}, (row #813) 5. Paint&copy that with the mouse. Now go to the tab with the Throttle - HOTAS Warthog.lua file. Paste that line somewhere in the file, like in the "-- Systems" section and add "combos" command for proper throttle button like this: {combos = {{key = 'JOY_BTN15'}} ,down = iCommandPlaneGear, name = 'Landing Gear Up/Down', category = 'Landing gear panel'}, (inserted row #285) This makes the red throttle button (button number 15) to function as the landing gear switch. 6. Find the original mapping (if it is set by default) in the file and unmap it by deleting the "combos" part of the row. E.g., for button 15 replace the row {combos = {{key = 'JOY_BTN15'}} ,down = iCommandPlane_HOTAS_LeftThrottleButton, name = 'HOTAS Left Throttle Button', category = 'HOTAS'}, with {down = iCommandPlane_HOTAS_LeftThrottleButton, name = 'HOTAS Left Throttle Button', category = 'HOTAS'}, CTRL-f with "BTN<number>" can be effective here. :smilewink: 7. Repeat for any other commands you wish to map. If you don't remember the numbers for the buttons, you can bypass the part of adding the combos to the line you've pasted into the throttle config file. You should be able to set the mapping in the options panel of the sim by clicking the ADD buttion if the corresponding row is inserted in the file. 8. Save the files (remember to keep a backup of the original before messing with them!) and exit notepad++. 9. IF YOU HAVE PLAYED THE SIM AFTER INSTALLING IT, chances are that the sim has written your custom mappings on the hard disk. Following the above mentioned approach and using the default mapping as a starting point, you should now remove any mappings for the throttle saved by the sim earlier or you will see no results in the sim. So, navigate to <A10 installation folder>\DCS Warthog\Config\Input\A-10C\joystick and delete the file Throttle - HOTAS Warthog *.lua where * stands for any alphanumeric string you happen to have as your throttle ID string. (The custom mappings are saved in that folder.) 10. Start up the sim, go to options panel and check that you did everything right and adjust if needed. Map any keys that you didn't give combos for. If you want to change things later without deleting the custom mapping files, maybe it works if you read the post by slimakwielki above. 11. Crank up the turbines and go kick some Shilka's ass. :joystick: Hope this helps. It's roughly what I did.

My TM warthog hotas throttle has a blown backlight LED. (See the attached image.) I've seen many times brand new products with blown bulbs but this is the first time I notice that an unused thing has a dead LED on it - it's very rare. There's voltage across it, I checked. How did this pass to get the QC stickers? Wow. :blink: Am I the only unlucky one with such a rare failure? The retailer was talking about several months of waiting time if they replace the throttle... what about sending it directly to ThrustMaster, I guess I would have to pay for the shipping? How long time did you have to wait for the bricked throttles to be replaced? If I could find similar LED somewhere I could solder the new one in it myself but that might void warranty, which is a bad option if the thing decides to go belly up and brick itself some day like many of those have... Any suggestions? :cry: TM should really be more careful when choosing their chinese manufacturers... :mad:

You bet, just a question of timetables. Actually, I wonder how many DCS'ers there are here. There really should be a Finnish DCS squadron like Kyllikki in ARMA 2 etc!! Even if we don't really have the hogs, but hey, they didn't model the F-18's yet :)

Oh, and only use the copy&paste procedure. NO modifications of values.... :smartass:

WTF :badmood: Kemijärvi ~80% and I'm stuck with 6% ? :mad: I'm south Finland and started downloading within 1h30mins of the release. Dammit. :crash:

Tomorrow morning (Greenwich +2) when I get to work I'll try to sneak a torrent seeder into one of the computers connected to the superfast university network :punk: (provided I succeed to download the files by then myself, now at 20kB/s)) So when is the first patch due? (trance music & :clap: :clap: :clap:)

WUAAHHAAA !! Evil trick to skip beta 5 like this :megalol: BTW there's roughly 2 replies per minute in this thread so far (~120 in 1h) --> Downloading and :joystick:

An old thread but it seemed suitable :thumbup: This is to share some material on the Thrustmaster Cougar MFD button panel setup I did. Just in case someone finds it useful. The Cougar MFD panels are mounted on either 24" main screen (1920x1200) corners or on a separate 15" screen (1024x768, analog vga) using small velcro strips. For Black Shark use, I set image on them with 4:3 and 3:4 ratio and the sides are used for labeling the buttons. I attached a powerpoint file (black&white) which can be printed and cut with scissors to fit in the Cougar MFDs. Either print on paper and set between the plastics, or print on a transparent film... Just modify it to your key assignments and fine-tune according to your viewing angle/perspective. When panels are attached on the monitor, just the 3:4 screen area is seen between the button labels - see the picture. Works well.:prop: Below are the monitor setup files (config\monitorsetup). 24" screen: 24" + 15" screen (horizontal spanning for fullscreen and good FPS on windows XP; with 1920x1200 scrolling area and 1024x768 viewable area on the 15"):

Currently no problems with 266.58 so far. Earlier I had a problem with any driver > 196.21: I got BSOD every time exiting a game with newer drivers... turned out to be Symantec antivirus running out of kernel space. Now antivirus problems are fixed and new drivers work just fine.:thumbup: FPS I haven't measured/compared to the old ones.

Interestingly, I've run into this "black hole around the sun" -problem, too. Got a cheap 2ndhand side monitor and tested multimonitor setups when it occurred. Just to check, I attach a screenshot of the thing (ignore the panels, it's the black circle partially overlapping the top part of image). I did some poking around and here are the conditions when I get it: - main camera display size is less than the desktop resolution (in the screenshot it's just a few pixels smaller), and - HDR on When testing, on my system the black HDR circle on sun does NOT depend on the following factors: -fullscreen on/off -AA, AF, or any other NVIDIA display adapter aliasing or texturing settings that i could find -MSAA or TSSAA in-game settings -texture level, visib. range, shadows setting, cockpit display resolution, scenes setting, heat blur setting, aspect ratio -AA gamma correction, AA transparency setting, extension limit, anisotropic sample optimization, triple buffering, vsync -desktop resolution or size -whether multiple monitors are actually used or not -overclocking settings Nvidia driver does not give (or I haven't found) "edge-detection" option. Just as long as I've got HDR on and main camera display has less pixels than the total viewport of the game I always seem to have this black hole effect. In addition, I'll post another Fraps screenshot of the "noise" I have on the screen in the area which is not covered by the main camera. The HDR effect "leaks" from there, maybe that's got something to do with the problem. The random color noise varies each time but is always there unless it is covered by the active graphics (view camera/mfcd), with or without the HDR effects. Annoying if I want to set up the MFCD's on the small side screen... System: Win XP 32bit, Nvidia drivers v266.58, DCS A10C beta4 fresh inst. Intel Q9550, ASUS P5Q deluxe, Audigy 4 sound, EVGA GeForce GTX460 dxdiag attached

Another problem report Hi all Here's yet another display problem report. The earlier-mentioned cloud problem, disappearing graphics, FPS slowdowns, etc. reported in a few threads here are bothering my system, too. I use Windows XP, 4GB ram, Nvidia (ASUS) GTS8800 512 (G92 core), Q9550 processor on ASUS P5Q deluxe. Fresh, full beta 4 install, haven't found nvidia panel settings that fix it yet, using HDR makes things a lot worse (more problems and they appear more quickly when starting the game), never alt-tabbed... To not overclock doesn't help to this one.:cry: To provide details, I've attached some log files, and dxdiag report to this post in a zip file to this post. This time it also crashed on exit. It also includes an interesting screenshot of the MemStatus program (which monitors both main and graphics memory usage) after running the simulator and reports that the A-10C has actually used five times as much graphics memory as there is available. The number is always the same (unless with very low settings and quick exit or otherwise so little memory was used that the reported value is "normal" below 400mb or so - happens rarely; BTW, I also get problems with low settings on graphics, just takes some time or a mission with more stuff/terrain details in it). I thought that maybe this is somehow related to the apparently common problem of some, maybe especially Nvidia 8800 series owners?, running into graphics problems. Just for the kicks, there's also a few screenshots of graphics glitches I encountered that are most likely due to the above-mentioned problem.:lol: To Nate or other devs: low/medium/high settings do help, indeed, to some extent, but do not completely prevent the problem. I'm starting to believe that the problem just takes more time or luck to show up if less memory is used. Perhaps there is serious problem with memory allocation/handling in Win XP systems here? If you ED guys need some extra testing (if you didn't pin down the problem precisely yet), just let us know. More data on request :smartass: Yours, X

Thanks for the suggestions, goldfinger. Actually, I did try the on-board sound card (result: no crackling but just silent gaps in sound equivalent in time scale, less than a second). Other slots I didn't try so far. However, I was very very surprised to note that stock speeds got rid of the sound problem, since any other program including "torture tests" on the system show no problems when overclocked to the current values. Of course the performance suffers when using stock speeds. Naturally, I checked into this a little deeper: It seems that, while overclocking the processor does not cause my problems, the increased frequency of the memory chips at 1088 MHz gives audio problems and at 901 MHz they are gone (the memory chip speed options are in steps only using my settings). The screen occasionally has stutters when i would expect sound pops, though, but maybe this is the same that everyone else is getting (when many mountains or other objects are visible, for example), i.e., other than sound problems. I was not able to find anything useful by googling on this. Perhaps some sync problem with motherboard/processor - video card or motherboard - sound card ? And, in this case, why any other program/game does not have problems? And, maybe there are options in BIOS to remedy this? ASUS boards seem to have a lot of undocumented options for tweaking and overclocking. This is very interesting.

Is it possible that my sound clipping problem is related to graphics rendering somehow? Freemem reports weird numbers on video memory usage, such as -2.5GB available (yes, negative number). A wild guess: could it be that my whole system including the sound threads are halted for a very short time when the drivers are importing stuff in the video memory from main memory, and that when there are objects in view, for some reason the game does this repeatedly resulting in the clipping/popping/crackling sound effect? Graphics seems to be twitching simulatneously. Hmm. Can it be checked that the game recognizes the amount of video memory correctly?

Considering my budget constraints I purchased the 80GB Intel X-25M about a year ago. It has been big enough this far to contain all my installed programs, although 160GB would have been nicer, of course. Windows is installed so that "documents and settings" and any other user data is on another, traditional hard drive. Loading times are excellent with the SSD compared to traditional hard drive.

Thank you for the help. However, and unfortunately, this did not help with the "popping" sound problem. The audio is lagging noticeably, though. Especially so if using higher values than 1024. Any other suggestions?

Hi all I encounter the following problem with sound. Game: A-10C beta2, beta3 both at 1920x1200 full screen, default install. When: In game, most of the time. Paused, non-paused. It does not happen (badly) when looking at clear sky or something that clearly brings the load on the CPU/GPU/computer in general down. What happens: Sound makes clicking/crackling/snapping/popping sound. In short intervals well below 1 second, the sound disappears and returns. The "cut" and "return" of the sound is accompanied by a loud pop. This happens frequently so that the total effect is a crackling sound on top of the normal sounds. After some time the sound may disappear completely or screw up the sounds entirely. After some more time the sounds may come back, but again with the crackling effect or as totally distorted noise and disappear after some time again. Any other game like GTA4, Black Shark, ARMA2, LockOn FC2 does not produce this effect. Instead, after DCS A-10C has messed up the audio, all the other programs on the computer are also affected - even if DCS A-10C is shut down completely. E.g., the MP3 player makes cracks and pops, too. Until reboot. Sound card: Soundblaster Audigy 4. When I switched to motherboard's soundMAX chip, the crackling sound is replaced by sound disappearing, i.e., the sound disappears in similar very short intervals but the "cutting" of the sound will not make a pop each time but the audio is just silent for a fraction of a second repeatedly. So the problem is there with other sound drivers too. Other hardware: Intel Q9550 overclocked to 3.84GHz, ASUS P5Q motherboard, 4GB memory (>3GB in use due to windows XP), nvidia 8800GTS 512MB display card (driver version 197.45), windows XP sp3 and manually installed redist-directx package. What made no difference so far: messing around with hardware drivers; windowed mode; changing any in-game graphics settings high-med-low or HDR, TSSAA, MSAA; killing other processes or turning off trackir; changing 3D options like buffering, anisotropic filtering, etc. in nvidia control panel; changing audio options like 2 speakers, headset, EAX, etc.; reinstalling game with or without directx package. What seems to help: reducing resolution to 1600x1200 or so (although a couple of cracks can be heard at the start of mission when un-pausing); or having a view at 1920x1600 so that nothing complicated is visible, like the HUD, terrain, buildings, mountains at a distance or anything but sky or something. When something comes into view, the sound problem occurs again. Just having higher FPS alone does not seem to do it, the effect can occur with both low and high average FPS. It varies 5-30 depending on the settings and scenery viewed. I would understand if it seemed to be just FPS issue but there is something else to it. Windows XP problem? (edit: OC'ing the cpu should have no effect; it is stable for 48h tests with, e.g., prime95.) I'll attach dxdiag output and an MP3 sample of the effect to this post. Any help or ideas to get this fixed are appreciated.