marrow

I'm having the same issue. Tornados just keep orbiting.

I'm having this problem as well. With the new mission file. Nothing happens after changing frequency as instructed after the event just after takeoff.

Trimming and other problems with FFB effects might be caused by wrong FFB axis settings. I've noticed that with MS FFB2 I usually have to "swap axis" from the FFB settings and also sometimes invert X and Y.

Regarding the question whether FFB and non-FFB behaves differently when trimming after a radical stick movement: it doesn't. You will get a bump in both cases. But since you can spam trimmer with FFB it's not a problem. Just trim, trim and trim all the time while maneuvering and there won't be big changes between trims and no bumps. Also bumps are easier to fix with trimmer spamming. Press and hold is another method that I used with non-FFB, but with FFB I don't like it since the stick goes limp while the trimmer is held down.

Do you use TrackIR? I noticed some Flaming Cliffs aircraft have TrackIR Z-axis defaulted for Zoom view instead of move forward/back. It might be conflicting with your slider axis zoom.

Let me explain how I got it to work, I copied \Eagle Dynamics\DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\Throttle - HOTAS Warthog.lua to \Eagle Dynamics\DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\Thrustmaster Combined.lua When I start A-10C in DCS, it'll use this as default profile for TM Combined and basically think it's a TM Throttle. BUT you have to have exactly same DX buttons in the Combined as in the default Throttle. Then, if you make changes to the TM Combined input options, DCS will create \Saved Games\DCS\Config\Input\A-10C\joystick\Thrustmaster Combined {xxx}.diff.lua with ONLY the changes you make. So it's fundamentally different system than before. I haven't used manual loading of profiles in DCS so I can't comment about that, but perhaps 1.2.8 broke something in there?

Few things I have learned about the current input setups: Each aircraft has default profiles for each device, e.g. \Eagle Dynamics\DCS World\Mods\aircrafts\A-10C\Input\A-10C\joystick\Joystick - HOTAS Warthog.lua Your personal changes (and changes ONLY) to the default profiles are saved in e.g. '\Saved Games\DCS\Config\Input\Joystick - HOTAS Warthog {FB419CA0-B25D-11e2-8009-444553540000}.diff.lua'. 1.2.8 has a script that copies and converts your old personal "device".lua configs to new "device".diff.lua configs so that they are compatible with the new system. You can delete the whole Input folder and as soon as you start to modify the default inputs it will create new personal folders with .diff.lua files only. If you are using TARGET with TM Warthog like I am (I only use it only for the Throttle, Joystick and MFDS are own devices since I don't need to customize those), you can create your own "default" device profile for A-10C just by copying 'Throttle - HOTAS Warthog.lua' in DCS folder to 'Thrustmaster Combined.lua'. It will use it as default profile for device 'Thrustmaster Combined' and all the 3-position switches work as they should, as long as you map the relevant switches to DX buttons same way as the throttle has for default.

I have the same problem. I've tried different browsers and machines and it's the same page all over.

Regarding this last point. You can start Target and run a profile with one command. I've made shortcuts like this on my desktop for all my profiles: "C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "E:\Thrustmaster\Target scripts\ka-50.tmc" This works for scripts and GUI profiles. When you stop the script it also automatically exits Target. So it's pretty easy to start and stop and switch profiles. And if you don't like to have extra shortcuts on your desktop you can always make a custom toolbar in your taskbar for the shortcuts. :thumbup:

Yes. Options - Controls - Axis commands - Camera Zoom View (mouse) Mouse wheel is axis MOUSE_Z. Invert that from the axis tune.

I've had the same problem with TM TARGET. Sometimes if a command involves modifier (e.g LCTRL+c for cannon round selector) the sim registers it randomly without the modifier (in this case "c", which is cannon select). I think the problem is that the command is too fast and thefore the sim might miss the modifier. It's easy to fix if you are using text scripts for making the profiles. There you can set the duration of pulsed commands. It's this line: SetKBRate(60, 70); First number is duration of pulse (in ms) and second number is delay between chained commands. Default duration for pulse is 32 ms and it caused the problem you describe. I found that increasing pulse to 60 ms fixed the problem in my case. If you are using GUI I'm not sure it's possible to change the duration. I suggest that you learn the basics of script language, it's much more versatile and even faster to make profiles after you learn it. Read the "TARGET_Script_Editor_Basics" and you are making your own scripts in no time.

It really bugs me that the Su-25T HSI doesn't show the correct direction and distance information for selected waypoint while in other mode than NAV. Can anyone explain why it works like this? Is it "realistic"? It seems odd that you can't see crucial waypoint information while in A-G mode.

I think modding has always been interesting part of ED products. Now that we will have DCS World to manage all the products, maybe it could also include a manager for user made content? ED web page has a good section for user made content and mods, but installing is another matter. I don't say it's hard, just that you need to fiddle more or less or use 3rd party apps. It'd make sense to integrate mod managing to the core IMO.

I've trouble with cockpit lights in BS2. Flood light or the bluish NVG light doesn't work. The only cockpit lights working are the instrument lights. All lights work in BS1. I've tried different driver settings and game graphics settings but nothing seems to help. I've Radeon 5850 with latest drivers. Any ideas what's going on?