lxsapper

Not really, doesn't sound very appealing to me. Maybe for Helicopters, but DCS does that already. What's wrong with the A-10C trim? I've always thought it was fine both for non-FFB and with FFB (I have some MSFF2 to try this things out and that I was going to use on a project that never quite made it off experimental phase).

Try using Tm calibration tool as well.

I have been very vocal against Target in the past, and there is certainly a lot I dislike about it. But I'm coming to terms with it and appreciating the abilities that script affords me. In particular I'm a lot less dissatisfied with it ever since I found out about the 128DX inputs hack. Having only 32 on a software that forces me to join in 1 device all my programmable devices was a big no-no for me. I particularly appreciate it as the only way in DCS to match perfectly my planes afterburner activation point on the axis with the physical detent position. With no silly custom curves, well technically it's still a custom curve but it's output is two linear straight lines.

I think I still have them on my HD. I'll get back to you on it.

Yes they are all using the same texture ATM.

I'm using TM TARGET to do this, but you could do it, with a number of solutions including Joy2Key and I belive RSmapper should have the function as well. Other Hardware manufacturers like saitek probably have it as well but I'm not sure.

I don't think your perfect solution can be reached. To be honest the new integration options don't seem that useful to me, but they can both inhibit Viacom from transmitting to AI or SRS from transmitting to other players. The two options as far as I can tell are mutually exclusive. Or rather neither AI or players will hear you when both are in the channel. And keeping both options Off seems like neither will if both are in channel. I haven't tested it, but like I said this options don't appeal to me. So, also because I am now flying with a squadron that has certain radio procedures, my solution was: Turn off Integration all together, use Viacom in "single PTT mode" with TX5 (intercom) selected as my PTT. I still keep my TXs bound the same as in SRS, a bit unnecessary now, but it's easy to switch configuration so everything is a go for several options. Pros: - My AI and Human comms are kept absolutely separate, unless I'm flying same plane co-op and I don't see that as a problem at all. - When talking to AI other players will hear my "pilot voice", they won't hear me double. Turning off pilot voice, only does it for you. - If I need a backup using options, no one will hear that. And again they will still hear the command with my Pilots Voice. Cons: - I "lose" realism when transmitting to AI, using the same button for all radios. - I can't use the "Radio Tune/Channel" commands from the basic plug in, as they require you to key the radio you want to tune. But I can still use Radio Tuning with Jester, but personally I like to keep it that way (just missing Select Channel for Jester). In the end it's always a trade off. Kudos to Hollywood and SRS team for joining efforts trying to solve the problem, but I think it's an unsolvable one. At least they offered us options to work with. as another tip, I keep another backup to talk to AI, I don't use the option to "hide menus", and my PTTs in my HOTAS are programmed to send the DCS radio PTT when I short press them, If I press them longer than 300ms then they talk to SRS/Vaicom, the Menus won't show unless I intentionally short press the PTTs.

Right here https://forums.eagle.ru/showthread.php?t=262400 And thanks for the Help!

For anyone interested here is the code. lightcontrol.zip

Nvm was finaly able to figure it out.

Are you saying "Options" first? If you are not then the Menu won't show, and you are still able to say "Take #" but it won't do anything. If you are saying "options" then the Menu should always appear regardless of other options, like - 'Hide Menus' etc. In any case I think I may have found an issue with the "options" menu, but I'll need to do further testing.

Hello @Drakoz, I have been able to put something together that is working very much like you describe after SGT Coyle pointed me in the right direction. I still haven't looked at your code to see what else I can learn, but I'll do it later. I am very much implementing it the way you are, down to the Binary code to display aircraft, and the print to Script editor window. A bit redundant now that I had the idea after helping SGT coyle in another thread, of having spoken wave files with the aircraft's designation being played when switching profiles. I used an online site to generate the wav files from text to speech. I am also using separate files for each aircraft to keep things simple, I have one main file and then secondary .tmc's that get called from the main one. What I'm having difficulty now is adjusting the backlight intensity on the Fly, this is what I'm doing so far: I only pasted here the relevant lines.

Don't know if this is the cause, But on the "Preferences TAB" make sure you check "Allow Options"

The forum is deleting backslashes from the copy/pasted code. Probably why yours isn't compiling for me, and mine for you. So here is an image from the code in target:

Testes the Huey, it was working fine for me, can't reproduce.

This are the relevant parts of what I'm using: I had to place the swavplayer.exe in the same folder as my .wav's, I counldn't get it to work any other way.

If that is the exact code you are using you are missing ":" and a couple""in there: I got it working, and it's very similar to what you have.

Not tested the Huey myself but if this is new maybe something caused by integration, try switching it off and see if that makes a difference.

I have to disconnect and reconnect Joystick and throttle from the USB ports in order to avoid the issue where they don't get virtually disconnected when running the TARGET profile. Sounds like you are having the same issue. When you run your profile they should turn into thrustmaste combined device.

I got it working with this code: system ("spawn -w "e:\\sWavPlayer" "e:\\sWavPlayer\\sWavPlayer.exe untitled.wav""); I cannot get the thing to work on a button press. It will not compile. I can't complile you code for a button press eighter: MapKey(&Throttle,LTB, EXEC("system("spawn -w "D:\\DCS_Device_Profiles\\Common_Files" "D:\\DCS_Device_Profiles\\Common_Files\\TARGET_DOWN_Layer.wav"")"));

I think TheHog is right SGT Coyle, you need to call upon the executable to run the wav file, Target as far as I know can only execute executable files, but your code looks like you are trying to call upon the .wav file directly.

Thank you SGT Coyle, I think I can definitely start doing something with that. Thank you very much!

We used to have discrete switch positions for all flap positions. I don't know when, but Flap_Middle no longer exits in the mapable commands? Why has this been taken away? And can you please bring it back? I can work around it, but i'd prefer to just have it still.

They are not unfortunately. Also hoping @Hollywood_315 adds them some time in the future. along with a couple others that are still missing.

You can assign them to do anything in the Sim, including pushing the corresponding MFD buttons. ${1} Some modules will assign them the proper assignements of this once DCS recognizes them.