DCS World TARGET profile for TM Cougar and Warthog + MFDs

Just out of curiosity, i tested the airbrakes binding yesterday. If I'm nof wrong, I could stop airbrake extension mid course, but when I would retract it, it would retract completely.

Yes you are correct the open airbrake in the Tomcat opens it gradually while held and stops when released. The close command closes it all the way when commanded. I think I have found a little trick for it, but I can't be sure from memory, have to check when I get home.

Ok Just Checked no tricks for the F-14, I think I was thinking of a profile for another plane.

Hi to all,

I am totally new to the TM TARGET software and the CTS One. I found a complete Cougar for very few Money, and I bought it. Changed ANT ELEV Pot and MAN RNG Pot. I am trying to use the CTS Software because I am too lazy to build my own profiles. I have also Foxy and CCP installed. The problem is: I build a script for an airplane, and the I lauch the targett software inside the CTS one. When I am inside DCS I cannot find my Cougar mapped. I tried to see the analyzer to check if the Cougar is ON, but it is stuck, the analizer recognizes my Cougar but I got no response from axes or buttons. If I close the CTS software, and use the TM Target alone, the analizer recognizes my Cougar and I can see the sliders moving when I use my Cougar. Do I make something wrong? or someone has a workaround?

With Foxy I have no problem in DCS.

Thanks in Advance

Emanuele

PS: I have Windows10, and I have already disinstalled the Windows Store.

I know this has the lowest priority of all the issues you ever came across, but I'm reporting it just for the sake of it.

F-14 Pilot, TEMPO Shift+ROSB15 doesn't trigger Walkman Switch Side. Additionally, the default key binding (RAlt+B) conflicts with the default Tacview Bookmark hotkey.

Another issue: Shift+JOY_BTN5 doesn't perform Stick Show/Hide. It looks like the command is missing from the DCS Controls page, but it could be me...

I know this has the lowest priority of all the issues you ever came across, but I'm reporting it just for the sake of it.

 

F-14 Pilot, TEMPO Shift+ROSB15 doesn't trigger Walkman Switch Side. Additionally, the default key binding (RAlt+B) conflicts with the default Tacview Bookmark hotkey.

 

Another issue: Shift+JOY_BTN5 doesn't perform Stick Show/Hide. It looks like the command is missing from the DCS Controls page, but it could be me...

Nice catch on the Walkman. Fixed internally and will be in the next release.

I couldn't find an issue with the Joy_BTN5. Joy_BTN30+Joy_BTN5 shows in the Thrustmaster Combined column for both Cougar and Warthog, and the control map in the Options menu is responsive when the stick is pressed. I have not had an opportunity to test it in the sim itself.

Also, still in the F-14 Pilot:

-Nose Strut switch is not working. Improved LUA Controller Mod is installed but the profile does not have any binding for those controls

-Is LANTIRN supposed to work with Improved LUA Controller Mod? The box in the Profile JPG says it should, but I have no LANTIRN command on the profile, and I couldn't figure out how to make it work...

I couldn't find an issue with the Joy_BTN5. Joy_BTN30+Joy_BTN5 shows in the Thrustmaster Combined column for both Cougar and Warthog, and the control map in the Options menu is responsive when the stick is pressed. I have not had an opportunity to test it in the sim itself.

What's the name of the control exactly? I couldn't find anything reated to hiding the stick... Maybe it's Improved LUA Controller Mod again?

I can confirm that both Sitck Show/Hide and Nose Strut bindings are missing from Improved Controller Mod, so enabling the mod will break that functionality. I manually added them again and now I have those bindings.

Probably the mod was build on an older version of the F-14 module, and now the two files diverged. I'll try to get in touch with the Mod author to check if he can update it.

My only question is about LANTIRN now.

I can confirm that both Sitck Show/Hide and Nose Strut bindings are missing from Improved Controller Mod, so enabling the mod will break that functionality. I manually added them again and now I have those bindings.

 

Probably the mod was build on an older version of the F-14 module, and now the two files diverged. I'll try to get in touch with the Mod author to check if he can update it.

 

My only question is about LANTIRN now.

I should be able to do the comparison when I get home from work.

I compared the controller mod with the latest default.lua, and while there are differences in the keyboard file there wasn't anything different about hiding the stick or kneeling the aircraft. I'll try to test it tomorrow or the next day. In the meantime, I updated the default.lua to account for the new toggle functions; this will be out in 2.44.

In my controller mod the stick hiding was missing altogether, and the kneeling command was under -MODIFICATIONS instead of being under Flight Control. We are talking about the same mod, aren't we? :huh: I'm using the file downloaded from the first post of this thread

EDIT: Oh, after using CTS for almost three years I JUST DISCOVERED the "_Custom LUAs for DCS World Main Install" folder. So I guess you're talking about THAT mod version! I'll just make the comparison, but I have no doubt you're right about it. And this also answer my question about LANTIRN. I'll report soon.

I can confirm that using your version of F-14 Controller LUA Improvements fixes all my other issues about nose strut, stick hiding and LANTIRN. Sorry about that!

Just one last question: will you update your version of the mod with the differences you found between the Mod and the original LUA?

Also, in your mod, three bindings are missing from the Alerax mod:

{down = device_commands.ENGINE_Throttle_Temp, 		cockpit_device_id = devices.ENGINE, value_down = -1, name = _('-Throttle Temp COLD'), category = { _('-MODIFICATIONS')}},
{down = device_commands.ENGINE_Throttle_Temp, 		cockpit_device_id = devices.ENGINE, value_down = 0, name = _('-Throttle Temp NORM'), category = { _('-MODIFICATIONS')}},
{down = device_commands.ENGINE_Throttle_Temp, 		cockpit_device_id = devices.ENGINE, value_down = 1, name = _('-Throttle Temp HOT'), category = { _('-MODIFICATIONS')}},

in Alerax mod, they're located between

{down = device_commands.INLET_RAMPS_RightSwitch, 		cockpit_device_id = devices.AICS, value_down = 1, name = _('-Stow Inlet Ramps Right Switch STOW'), category = { _('-MODIFICATIONS')}},

and

{down = device_commands.ENGINE_Air_Start, 		cockpit_device_id = devices.ENGINE, value_down = 0, name = _('-Engine Airstart NORM'), category = { _('-MODIFICATIONS')}},

I can confirm that using your version of F-14 Controller LUA Improvements fixes all my other issues about nose strut, stick hiding and LANTIRN. Sorry about that!

 

Just one last question: will you update your version of the mod with the differences you found between the Mod and the original LUA?

 

Also, in your mod, three bindings are missing from the Alerax mod:

 

<...>

Added.

Selecting I16 profile returns following error:

"Runtime Error: Divide by zero in AirBrakeProc ( line 1704 in DCS/DCS_Global_Subs.tmc )Aborting script (check output above for reason)...

Script stopped!"

My config: Warthog stick & throttle, MFG rudder pedals, 2 thrustmaster MFCDs

Selecting I16 profile returns following error:

 

"Runtime Error: Divide by zero in AirBrakeProc ( line 1704 in DCS/DCS_Global_Subs.tmc )Aborting script (check output above for reason)...

 

Script stopped!"

 

 

 

My config: Warthog stick & throttle, MFG rudder pedals, 2 thrustmaster MFCDs

Will investigate. Thanks for the report.

Selecting I16 profile returns following error:

"Runtime Error: Divide by zero in AirBrakeProc ( line 1704 in DCS/DCS_Global_Subs.tmc )Aborting script (check output above for reason)...

Script stopped!"

 

My config: Warthog stick & throttle, MFG rudder pedals, 2 thrustmaster MFCDs

The I-16 shouldn't have an airbrake, so somehow the airbrake routine wasn't cleared out completely on the I-16 profile init.

Which profile were you using prior to switching to the I-16? This will really help me run the issue down.

The I-16 shouldn't have an airbrake, so somehow the airbrake routine wasn't cleared out completely on the I-16 profile init.

 

Which profile were you using prior to switching to the I-16? This will really help me run the issue down.

Since I tried the I16 right after loading DCS, I switched from the default A10-C profile (the one from CTS)

Thanks. Just fixed it for the next release.

In the meantime, you can go into the DCS_I16.tmc file and change the values on lines 58-59 from 0 to 1, e.g.

BrakeOnCycleTime		=	1;
BrakeOffCycleTime		=	1;

That should at least prevent the DBZ error.

Thanks. Just fixed it for the next release.

 

In the meantime, you can go into the DCS_I16.tmc file and change the values on lines 58-59 from 0 to 1, e.g.

BrakeOnCycleTime		=	1;
BrakeOffCycleTime		=	1;

 

That should at least prevent the DBZ error.

As always, you’re very reactive and helpful.

Thanks a lot !!!

I will repost my request, if someone can help me It will be very appreciate:

Hi to all,

I am totally new to the TM TARGET software and the CTS One. I found a complete Cougar for very few Money, and I bought it. Changed ANT ELEV Pot and MAN RNG Pot. I am trying to use the CTS Software because I am too lazy to build my own profiles. I have also Foxy and CCP installed. The problem is: I build a script for an airplane, and the I lauch the targett software inside the CTS one. When I am inside DCS I cannot find my Cougar mapped. I tried to see the analyzer to check if the Cougar is ON, but it is stuck, the analizer recognizes my Cougar but I got no response from axes or buttons. If I close the CTS software, and use the TM Target alone, the analizer recognizes my Cougar and I can see the sliders moving when I use my Cougar. Do I make something wrong? or someone has a workaround?

With Foxy I have no problem in DCS.

Thanks in Advance

Emanuele

PS: I have Windows10, and I have already disinstalled the Windows Store.

I don't know if it's the same for the Cougar, but for the Warthog, once the CTS script starts, you have to map Thrustmaster Virtual Device on DCS, not the independent devices.

What an amazing piece of work and an unbelievable gift to the community. Thank you very much!

What an amazing piece of work and an unbelievable gift to the community. Thank you very much!

Second that. Home Fries is a legend!!!

Sent from my iPhone using Tapatalk

Hi Home!

RAZBAM announced here that there will be some changes in the upcoming updates for the M2000 according to AdA feedback. I cannot be sure about how this will turn out exactly until the updates are released, but if I'm not mistaken we will need a new button mapping since TWS/STT (H2 UP) will only switch the radar mode and won't perform AA Designate anymore.

Again we'll have to wait for the module to understand whether I'm right or wrong, but should I be right (something which rarely is :D) I would propose these changes:

A first, more invasive but slightly more realistic alternative, can be:

- H2 UP will switch TWS / STT but won't lock the target anymore

- Slew Control Push will perform AA Designate

- H4 Push won't do Target Unlock / Special Mode Deselect anymore, but will do Magic Slave / AG Designate/ INS Position Update

- Shift + H4 UP or DOWN perform Target Unlock / Special Mode Deselect, unchanged from current profile

Another more intuitive, although a bit less realistic, alternative could be:

- H2 UP will switch TWS / STT but won't lock the target anymore

- Slew Control Push performs Magic Slave / AG Designate / INS Position Update, unchanged from current profile

- H4 Push won't do Target Unlock / Special Mode Deselect anymore, but will perform AA Designate

- Shift + H4 UP or DOWN perform Target Unlock / Special Mode Deselect, unchanged from current profile

What do you think?

Hi Home!

 

RAZBAM announced here that there will be some changes in the upcoming updates for the M2000 according to AdA feedback. I cannot be sure about how this will turn out exactly until the updates are released, but if I'm not mistaken we will need a new button mapping since TWS/STT (H2 UP) will only switch the radar mode and won't perform AA Designate anymore.

 

Again we'll have to wait for the module to understand whether I'm right or wrong, but should I be right (something which rarely is :D) I would propose these changes:

Thanks for the heads-up on this change.

I definitely want to keep target lock on H2U because TDC Press will often slew the cursor for warthog users. I'll definitely have a shift/tempo function for TDC Press and STT/TWS toggle, but I'll have to see what works best. I may have it as selectable in CTS options as well. I'll have to play with it when it changes to see what works best.