DCS World TARGET profile for TM Cougar and Warthog + MFDs

[Home Fries]

The gear up LMFD button (should be LOSB17 with S3) was not working (it was selecting the aircraft I have assigned for the profile switching mode).

 

I checked the code and you appear to have REMed out the lines for LOSB16 and LOSB17. I unREMed and it worked.

I actually fixed this issue this past weekend while working on something else. It's ready for the next build.

P.S. The UH-1H kneeboard button is still not working. Pressing LOSB20 produces DX26 (with modifier 30+31). I remapped and I'm ok but I still suspect this might be a bug...

LOSB20 should map DX24 with 30+31, but you're right that the mappings weren't updated. When I removed DX20-23 from the MFDs for SRS compatibility, I guess I didn't update all the modules. If you see anything else like this, please let me know. I'm trying to run down the stragglers.

 

This is also fixed and will be in the next build.

[Home Fries]

1) SRS device recognition problem: fixed by creating a blacklist.txt file excluding the HOTAS Cougar device (found in clientlog.txt), giving way to the Thrustmaster Virtual Device. "Allow other devices" should be turned off. :thumbup:

Could you please give me some step by step instructions on how to do this, as I don't use Win10. I will drop it into the Setup Guide as an appendix and give you credit for the section.

 

2) PTT common: I am confused as to what this actually implies. The CTS manual states that if VAICOM and SRS are used together, then PTT Common cannot be used as a feature on aircraft with multiple mic switches.

 

If I understand this correctly, PTT Common means that there is one physical mic switch that triggers the selected radio if multiple radios are available?

 

What is actually meant when saying that you "choose to use PTT Common" ?

 

SRS by default will only switch to a radio when it's button is pressed and then needs the PTT button to be pushed to actually talk. There is however a setting that turns the radio buttons into individual PTTs.

 

Could it therefore be clarified what to do if using VAICOM + SRS with the following aircraft?: Su-27, Su-33, F-5E, F-18 ?

This is correct. With PTT common, you can use 3 buttons or keys to select the radio, then the same button for PTT which will engage the selected radio. You have this option in SRS, but you just need to sync your CTS settings with your SRS preferences. PTT Common is not an option when VAICOM is enabled, so in your case you should not use it.

 

Could you also clarify the Cougar reference for this aircraft when VAICOM and SRS are activated in the script? Comm switch forward is shown as "PTT Common", backward as "AI Comms / CommState".

Up is just push to talk for TS3/Discord, while down is for AI Comms (DX20 is mapped to the radio button in the F-5). With SRS/VAICOM, down also doubles as radio1/TX1.

 

3) A-10A profile: (HOTAS Cougar + shifted trim=1) the pitch trim is reversed

looking into it. Since I don't use VR, though, I may not be able to duplicate this. In the DCS Options, does pressing trim actually select the proper direction (e.g. H1U trim down, H1D trim up)?

[Home Fries]

S3 is working for some commands but can't change mode on RWR or select canon. It just fires the canon. Most importantly TrimHAT doesn't work at all. I have set CTS to hat as trim. I am at a loss what is wrong.

A-10A profile: (HOTAS Cougar + shifted trim=1) the pitch trim is reversed

 

Fellas, I was unable to duplicate these issues in the DCS Options menu. S3+S5 toggled cannon, and S3+H4L/R cycled RWR mode. Trim orientation also appears proper in the menu. I also doublechecked the H1_Init() and H1_Init_WH() code for orientation and saw no issues (both Cougar and Warthog).

 

Please try to duplicate these issues both in the DCS Options menu and in-game and let me know if there's a difference. Also, RedeyeStorm, please verify you have DX30,31,32 set as modifiers in both the A-10A and UI Layer.

[flyingflatfour]

Could you please give me some step by step instructions on how to do this, as I don't use Win10. I will drop it into the Setup Guide as an appendix and give you credit for the section.

 

Here you go:

 

"When encountering the situation where Windows 10 does not let TARGET hide away the physical devices, SRS may not detect the Thrustmaster Virtual Device in the Controls menu but your physical device instead. To correct this, follow the following steps:

 

1) run SRS client at least once, with the option "Allow More Input Devices" turned ON, then close the application.

2) navigate to SRS installation folder, locate and open the clientlog.txt file.

3) scroll down to the bottom of the file and locate the line that says:

 

"Found Device ID:0400044f-0000-0000-0000-504944564944 HOTAS Cougar Joystick Usage: Generic Type: FirstPerson"

 

4) Copy and paste your conflicting device ID (just the string as highlighted in bold above) to a new, blank text file and save it in the same folder named blacklist.txt

5) Start SRS Client, this time turn OFF the option "Allow More Input Devices"

6) You should be able to bind your controls notmally now.

 

Final remarks: if more input devices are connected and are still conflicting, follow the same procedure for those extra devices, or add the one device you want to be recognized (Thrustmaster Virtual Device) in a whitelist.txt file.

 

 

This is correct. With PTT common, you can use 3 buttons or keys to select the radio, then the same button for PTT which will engage the selected radio. You have this option in SRS, but you just need to sync your CTS settings with your SRS preferences. PTT Common is not an option when VAICOM is enabled, so in your case you should not use it.

 

Roger, got it. I have changed my SRS settings so as to remove the bindings for PTT and Intercom Modifier, and have turned ON the setting "Radio switch works as PTT". Radio 1 is bound to Joystick btn 19 / Radio 2 : btn 21 / Radio 3 : btn 22 as per CTS manual.

 

Concerning the TQS comm switch terminology I believe there is a lot of confusion going on. Could we agree to call the physical switches according to their lettering and their corresponding directions? Do we then agree that the VHF switch position means pressing down / UHF = up / IFF OUT = left (seen from the pilot seat) / IFF IN = right ?

 

This helps to verify wether the CTS references layouts are matching what's going on in DCS.

 

In addition, I shall add that the CTS "Settings" page shows a "TQS CommSwitch Mapping" that uses yet another set of switch names (T2-5 / Up-Dn-Fwd-Aft) that add to even more misunderstanding, as I don't see what Aft/Fwd would mean on the TQS ? On the Warthog though that would make sense I guess.

 

Concerning the A-10A, using this combination of VAICOM+SRS + Cougar, this is what I find for the Comm switch:

 

- IFF OUT = left = SRS Radio 1 = VAICOM TX1 = AN/ARC-186 VHF AM

- VHF = down = SRS Radio 2 = VAICOM TX2 = AN/ARC-164 UHF

- IFF IN = right = SRS Radio 3 = VAICOM TX3 = AN/ARC-186 VHF FM

 

So if this is as intended, I believe the CTS reference layout is wrong: TQS VHF / down is shown as mapped to "PTT Common" when it is actually "UHF". Wouldn't it also help to change "VHF2" to "VHF(AM)" and "VHF1" to "VHF(FM)" ?

 

There is a screenshot attached showing the A-10A and the status of SRS+VAICOM when pressing TQS IFF OUT / left. SRS picks it up as Radio 1 (VHF AM) and VAICOM as TX1/VHF AM. Is this as intended?

 

 

Up is just push to talk for TS3/Discord, while down is for AI Comms (DX20 is mapped to the radio button in the F-5). With SRS/VAICOM, down also doubles as radio1/TX1.

 

If I understand correctly, this is then what you call "PTT Common" in your reference layouts? If so I believe this is misleading for those who run VAICOM+SRS and therefore do not use PTT Common.

 

I am wondering if in fact there isn't as well a misinterpretation between you and me regarding the way to read out the reference layout box for the TQS Comm switch?? This might explain the confusion with the radar range setting as well?

 

According to my intuition, the reference layout box should be read according to the switch lettering that appears right below it on the drawn TQS. If we take the F-5E as an example here, "PTT Common" is in the upper position of the layout box, which corresponds to VHF, so that means pressing down on the physical button...

 

... which does not match you're describing above?

 

Going on with the F-5E, pressing on TQS VHF / down has no effect, neither on SRS nor VAICOM. Please see attached screenshot showing the status of both when pressing that button.

 

Isn't it because SRS sees the F-5E's sole radio as "Radio 1" and is therefore expecting a press from TQS IFF OUT (Joy btn 19) to trigger it, when we are pressing TQS VHF (Joy btn 21) instead?

 

VAICOM sees the F-5E radio in the TX2 slot, but you said above that TQS VHF / down is mapped to TX1, and that is indeed what VAICOM sees is being triggered, but doesn't transmit in DCS since it's not on the right node.

 

Still with the F-5E, presssing TQS UHF / up will result in TX1+TX4 being triggered in VAICOM when it should have been reserved for TS3/Discord, right ? Again the reference layout seems inverted here, showing TQS VHF / down mapped to "PTT Common" (TS3/Discord if I am following) and UHF / up mapped to "AI Comms".

 

Looking at the VAICOM settings this makes partially sense to me, as Joystick btn 21 is assigned to TX4 which is AUTO. Still don't understand why that would trigger TX1 as well... In fact I don't understand why this binding should be left for those who use SRS+VAICOM without a PTT Common ?

 

Wouldn't it be possible instead for those who do not use TS3/Discord with a PTT, to bind TQS UHF / up / Joy btn 21 to TX5/INTERCOM ?

 

For the sake of troubleshooting, I have attached a screenshot of my VAICOM settings and SRS controls to verify they match the setup required by CTS.

 

 

(A-10A trim issue) looking into it. Since I don't use VR, though, I may not be able to duplicate this. In the DCS Options, does pressing trim actually select the proper direction (e.g. H1U trim down, H1D trim up)?

 

Please find attached a screenshot showing the options menu and the device analyser when pressing the H1 down. The line that is highlighted in french means "Trim - pitch down", so in my case it is indeed reversed.

 

 

Keep up the good work, I hope I haven't been too hard to read but things are still not clear in my mind so I'm trying to adopt a standard terminology :thumbup:

Edited January 11, 2019 by flyingflatfour

[Home Fries]

Here you go:

 

<..>

 

Thank you for that. I'll get it incorporated for the next release.

 

Concerning the TQS comm switch terminology I believe there is a lot of confusion going on. Could we agree to call the physical switches according to their lettering and their corresponding directions? Do we then agree that the VHF switch position means pressing down / UHF = up / IFF OUT = left (seen from the pilot seat) / IFF IN = right ?

 

This helps to verify wether the CTS references layouts are matching what's going on in DCS.

 

In addition, I shall add that the CTS "Settings" page shows a "TQS CommSwitch Mapping" that uses yet another set of switch names (T2-5 / Up-Dn-Fwd-Aft) that add to even more misunderstanding, as I don't see what Aft/Fwd would mean on the TQS ? On the Warthog though that would make sense I guess.

 

Concerning the A-10A, using this combination of VAICOM+SRS + Cougar, this is what I find for the Comm switch:

 

- IFF OUT = left = SRS Radio 1 = VAICOM TX1 = AN/ARC-186 VHF AM

- VHF = down = SRS Radio 2 = VAICOM TX2 = AN/ARC-164 UHF

- IFF IN = right = SRS Radio 3 = VAICOM TX3 = AN/ARC-186 VHF FM

 

So if this is as intended, I believe the CTS reference layout is wrong: TQS VHF / down is shown as mapped to "PTT Common" when it is actually "UHF". Wouldn't it also help to change "VHF2" to "VHF(AM)" and "VHF1" to "VHF(FM)" ?

 

There is a screenshot attached showing the A-10C and the status of SRS+VAICOM when pressing TQS IFF OUT / left. SRS picks it up as Radio 1 (VHF AM) and VAICOM as TX1/VHF AM. Is this as intended?

 

<...>

 

Going on with the F-5E, pressing on TQS VHF / down has no effect, neither on SRS nor VAICOM. Please see attached screenshot showing the status of both when pressing that button.

I see where you are going with this. The switch position is "up and down" rather than "forward and aft," so the orientation is actually opposite the UHF/VHF markings on the diagram. That's just legacy from the previous template that had the same orientation. As for the T2-T5, this is Thrustmaster terminology that dates back to the F-16 TQS for DOS, but I can certainly apply the UHF/VHF/In/Out terminology when I need to update the jpegs for something else.

If I understand correctly, this is then what you call "PTT Common" in your reference layouts? If so I believe this is misleading for those who run VAICOM+SRS and therefore do not use PTT Common.

 

I am wondering if in fact there isn't as well a misinterpretation between you and me regarding the way to read out the reference layout box for the TQS Comm switch?? This might explain the confusion with the radar range setting as well?

 

According to my intuition, the reference layout box should be read according to the switch lettering that appears right below it on the drawn TQS. If we take the F-5E as an example here, "PTT Common" is in the upper position of the layout box, which corresponds to VHF, so that means pressing down on the physical button...

 

... which does not match you're describing above?

I realize I got a little sloppy with the PTT Common terminology, but in this case for people who use PTT Common, the 3 radio switches select the radio itself and the TS3/Discord PTT acts as PTT Common. So this is technically correct.

Please find attached a screenshot showing the options menu and the device analyser when pressing the H1 down. The line that is highlighted in french means "Trim - pitch down", so in my case it is indeed reversed.

I'm not sure what to say. Somehow it got switched up; even the key commands match the up/down, and the diff.lua format means it wouldn't be a language issue. For now, just reverse the polarity by assigning DX30+Hat1U/D to the trim as required.

Keep up the good work, I hope I haven't been too hard to read but things are still not clear in my mind so I'm trying to adopt a standard terminology :thumbup:

No problem. This only makes the product better in the end. I welcome all constructive input, though real life considerations may slow my response time for the next few months.

[JanRalle]

Since I had almost no other issues with CTS i also want to Use the Trigger Zoom but can't get it to work.

I tried different Modules like M2KC, F-5, F-18 but noting ever happen at first stage trigger.

 

Using Hotas Warthog and TFPR Pedals and until now no MFDs.

Things I tried until now are different settings for everything labeled with trigger zoom, different modules, loaded the bindings fresh into DCS keybindings and DCS repair.

When I check the button it only press the Joystick Button 1 only and nothing other in the Target event tester.

 

Beside this I had no flaws in die Bindings, Snapviews work as well.

Maybe had to do something with Snapview Boresight and Snapview Classic? (what is here the difference?)

 

Edit: Im using Headtrack/Opentrack

Edited January 11, 2019 by JanRalle

[flyingflatfour]

I see where you are going with this. The switch position is "up and down" rather than "forward and aft," so the orientation is actually opposite the UHF/VHF markings on the diagram. That's just legacy from the previous template that had the same orientation. As for the T2-T5, this is Thrustmaster terminology that dates back to the F-16 TQS for DOS, but I can certainly apply the UHF/VHF/In/Out terminology when I need to update the jpegs for something else.

 

In fact it kinda depends on the position of the throttle lever. In full aft position, the Comm switch is almost horizontal, thus VHF = forward / UHF = backward.

 

When the throttle is full forward the switch is almost vertical, then VHF = down / UHF = up.

 

So if I understand correctly, the TQS reference layout box for the comm switch currently shows the opposite of the UHF/VHF diagram laid out on the stick just next to it.

 

Thus, the "PTT Common" is in fact assigned to Comm switch UHF / up / backward.

 

I don’t know if it’s just me who finds it counter-intuituve but yes I believe it would help a great deal to update the layouts by duplicating the VHF/UHF/IFF diagram inside the box for the Comm switch assignments :thumbup:

 

I realize I got a little sloppy with the PTT Common terminology, but in this case for people who use PTT Common, the 3 radio switches select the radio itself and the TS3/Discord PTT acts as PTT Common. So this is technically correct.

 

Makes more sense now. May I suggest to enrich the layouts to clarify the various possibilities, for instance by using a colour code indicating what the Comm switch will do according to which options are chosen regarding VAICOM, SRS and PTT Common ?

 

I'm not sure what to say. Somehow it got switched up; even the key commands match the up/down, and the diff.lua format means it wouldn't be a language issue. For now, just reverse the polarity by assigning DX30+Hat1U/D to the trim as required.

 

Will do, thanks :thumbup:

 

Did you have a chance to look into the issues I was raising concerning the Comm switch for the F-5E in my previous post?

[Home Fries]

Since I had almost no other issues with CTS i also want to Use the Trigger Zoom but can't get it to work.

I tried different Modules like M2KC, F-5, F-18 but noting ever happen at first stage trigger.

TriggerZoom must be activated by pressing S3+TG1. The logical gear state must also be up (i.e. the profile must think the gear is up). You can tell that the gear state is up when LED2 on the LMFD is out. Then when you press S3+TG1, LED2 will flash, letting you know that TriggerZoom is active. Then TG1 will control zooming in and out. S3+TG1 again will disable TriggerZoom.

 

If the settings don't work well for you, it may take some tweaking. Try different values in the TriggerZoom category of the Global Values in CTS.

Maybe had to do something with Snapview Boresight and Snapview Classic? (what is here the difference?)

Classic SnapView is the default view in DCS (which is usually looking slightly down at the instruments), whereas the Boresight SnapView centers the view on the HUD or gunsight. Boresight is set so that TriggerZoom will zoom in on the HUD/gunsight when the view is at default.

I don’t know if it’s just me who finds it counter-intuituve but yes I believe it would help a great deal to update the layouts by duplicating the VHF/UHF/IFF diagram inside the box for the Comm switch assignments :thumbup:

I can certainly make this happen whenever I update the controller graphics.

 

Makes more sense now. May I suggest to enrich the layouts to clarify the various possibilities, for instance by using a colour code indicating what the Comm switch will do according to which options are chosen regarding VAICOM, SRS and PTT Common ?

I can, but it's not really a priority. There's already a table in the User Reference.

Did you have a chance to look into the issues I was raising concerning the Comm switch for the F-5E in my previous post?

I have not. I'll try to get to it soon, but my free time is limited for the next few months.

[flyingflatfour]

I can certainly make this happen whenever I update the controller graphics.

 

I can, but it's not really a priority. There's already a table in the User Reference.

 

May I offer my help with reworking the reference layouts?

 

 

I have not. I'll try to get to it soon, but my free time is limited for the next few months.

 

Of course, I understand. In the meanwhile, is there a way for me to edit things manually to get SRS + VAICOM working on TQS VHF / down together with the F-5E AN/ARC-164 UHF radio (SRS Radio 1 / VAICOM TX2) ?

 

Cheers

 

FFF

[Home Fries]

May I offer my help with reworking the reference layouts?

Thanks for the offer, but I have a huge photoshop template I use for these. It would be easier for me to do it and then update incrementally.

 

A question, though: would you (or anybody for that matter) prefer Up = Fwd and reversing the orientation of the existing diagram, or do you prefer Up = Up/Aft and just reversing the UHF/VHF symbology?

Of course, I understand. In the meanwhile, is there a way for me to edit things manually to get SRS + VAICOM working on TQS VHF / down together with the F-5E AN/ARC-164 UHF radio (SRS Radio 1 / VAICOM TX2) ?

Both up and down should already press DX20 to transmit on SRS radio 1 and VAICOM TX1, with up also simulcasting on DX21 for your TS3/Discord PTT (or PTT Common). Is this not the case with your build?

[flyingflatfour]

Thanks for the offer, but I have a huge photoshop template I use for these. It would be easier for me to do it and then update incrementally.

 

A question, though: would you (or anybody for that matter) prefer Up = Fwd and reversing the orientation of the existing diagram, or do you prefer Up = Up/Aft and just reversing the UHF/VHF symbology?

 

Not sure of what you mean but as I said, what is intuitive to me is that the layout should be according to the TQS lettering shown on the layout, thus TQS VHF = arrow pointing upwards, meaning pushing the switch forward/down.

 

The last thing I would do would be to reverse the actual VHF/UHF symbology (=lettering) on the reference layout, as it wouldn't correspond to the actual TQS anymore, adding to even more confusion...

 

If I were you I would copy/paste the VHF/UHF/IFF lettering in the middle of the box so as to replace the Comm Switch words.

 

Please find attached an example of what I would wish for :D

 

Both up and down should already press DX20 to transmit on SRS radio 1 and VAICOM TX1, with up also simulcasting on DX21 for your TS3/Discord PTT (or PTT Common). Is this not the case with your build?

 

Please refer to my previous post with extensive information and screenshots regarding this.

 

After trying again it seems that SRS does pickup on Radio 1 through DX20 after all, no idea why it didn't work last time...

 

However VAICOM pickups up on TX1 when the F-5E radio is seen by VAICOM on node TX2 so nothing happens.

 

But what you are saying is correct: pressing TQS VHF / down triggers DX20 and UHF / up triggers DX20+DX21

[JanRalle]

The Trigger Zoom is now working in the F-5. thanks for the push in the right direction.

 

But in keybindings diff.lua kb v226n/r of the mirage 2kc the trigger zoom is bind to PCN Dest and PCN enter.

The zoom itself is bind with Modifier joy_btn30+* and joy_btn30+enter

[Home Fries]

The Trigger Zoom is now working in the F-5. thanks for the push in the right direction.

 

But in keybindings diff.lua kb v226n/r of the mirage 2kc the trigger zoom is bind to PCN Dest and PCN enter.

The zoom itself is bind with Modifier joy_btn30+* and joy_btn30+enter

 

Ok, thanks. I'll fix that for the next release.

[Home Fries]

Not sure of what you mean but as I said, what is intuitive to me is that the layout should be according to the TQS lettering shown on the layout, thus TQS VHF = arrow pointing upwards, meaning pushing the switch forward/down.

 

The last thing I would do would be to reverse the actual VHF/UHF symbology (=lettering) on the reference layout, as it wouldn't correspond to the actual TQS anymore, adding to even more confusion...

 

If I were you I would copy/paste the VHF/UHF/IFF lettering in the middle of the box so as to replace the Comm Switch words.

 

Please find attached an example of what I would wish for :D

Thanks for the input. The enclosed graphic is what I'm thinking for the F-5, though I haven't put in SRS/VAICOM text yet. Bottom line is that any AI Comms or CommState button should also correspond to SRS/VAICOM with the appropriate radio.

 

 

However VAICOM pickups up on TX1 when the F-5E radio is seen by VAICOM on node TX2 so nothing happens.

 

But what you are saying is correct: pressing TQS VHF / down triggers DX20 and UHF / up triggers DX20+DX21

I looked into this, and apparently VAICOM now defaults to TX2 for the radio (because it's UHF), even though it's radio 1 in SRS. This is even the case in VAICOM's multiplayer mode. This is radio1 in SRS, so there's a disconnect between programs. This possibility is also why I've kept the SRS/VAICOM mapping to a HTML table - it's much easier to update when there are changes or new things are discovered.

 

Your best bet is to set VAICOM to SNGL mode and assign the radio to TX1 using the arrow keys. I'll look at the VAICOM thread to see if there are any plans to sync with SRS.

[flyingflatfour]

Thanks for the input. The enclosed graphic is what I'm thinking for the F-5, though I haven't put in SRS/VAICOM text yet. Bottom line is that any AI Comms or CommState button should also correspond to SRS/VAICOM with the appropriate radio.

 

Great, makes much more sense now :thumbup: (at least to me :D)

 

I looked into this, and apparently VAICOM now defaults to TX2 for the radio (because it's UHF), even though it's radio 1 in SRS. This is even the case in VAICOM's multiplayer mode. This is radio1 in SRS, so there's a disconnect between programs. This possibility is also why I've kept the SRS/VAICOM mapping to a HTML table - it's much easier to update when there are changes or new things are discovered.

 

Your best bet is to set VAICOM to SNGL mode and assign the radio to TX1 using the arrow keys. I'll look at the VAICOM thread to see if there are any plans to sync with SRS.

 

 

I agree and indeed that is what I am using as a solution for the time being :thumbup:

[Home Fries]

The Trigger Zoom is now working in the F-5. thanks for the push in the right direction.

 

But in keybindings diff.lua kb v226n/r of the mirage 2kc the trigger zoom is bind to PCN Dest and PCN enter.

The zoom itself is bind with Modifier joy_btn30+* and joy_btn30+enter

 

This bug has been fixed for 2.28. In the meantime, you can go into the DCS_M2000C.tmc file and change line 106 to read:

TriggerZoomEnabled		=	2;

[DaddySchlich]

Hi, I just purchased the Warthog Dual Throttle on sale, but plan to continue using my MS FFB2 stick because I love FFB with my helos.

 

Does it make sense to try to use these profiles with this setup? Or are the presence of both the Warthog stick and throttle so integrated into them that use of them would just cause inordinate headaches?

 

Thanks in advance for thoughts!

[flyingflatfour]

Hi Home Fries,

 

 

I've been fiddling around a bit with the Su-33 lately. :wub:

 

Concerning Air-to-Air refueling, there is a special ACS flight control mode that has to be activated by pressing RCTRL+R that helps a great deal to stabilize the bird for refuel.

 

On Cougar, would it be possible to map this to Button 5 together with extending / retracting the refuel probe?

 

Also, there is another feature that would be handy to have mapped somewhere: LALT+I to lower/extend the titanium air intake protections. Helpful for carrier take-offs :smilewink:

 

Best Regards,

 

FFF

[Home Fries]

Concerning Air-to-Air refueling, there is a special ACS flight control mode that has to be activated by pressing RCTRL+R that helps a great deal to stabilize the bird for refuel.

 

On Cougar, would it be possible to map this to Button 5 together with extending / retracting the refuel probe?

I'll look into it on Wednesday when I have some time.

 

Also, there is another feature that would be handy to have mapped somewhere: LALT+I to lower/extend the titanium air intake protections. Helpful for carrier take-offs :smilewink:

That's on the Warthog and the MFDs; no room on the Cougar TQS. :(

[Home Fries]

Hi, I just purchased the Warthog Dual Throttle on sale, but plan to continue using my MS FFB2 stick because I love FFB with my helos.

 

Does it make sense to try to use these profiles with this setup? Or are the presence of both the Warthog stick and throttle so integrated into them that use of them would just cause inordinate headaches?

 

Thanks in advance for thoughts!

 

It makes perfect sense, at least with the UH-1 and Mi-8. I use a SWFFB2 for those, along with the throttle and MFDs for collective and buttons. That's the reason most functions are TEMPO'd as well as shifted.

 

You'll still want the WH stick for the Ka-50 and Gazelle, though, because of the buttons.

 

EDIT: from what I understand, you don't actually have a WH stick. That might make things dicey from a configuration standpoint. While most functions are TEMPO'd, some functions that can be executed on the ground require the stick, as do state toggles. If you do have a WH stick and just want to use the FFB2, then no problem at all.

Edited January 14, 2019 by Home Fries

[Home Fries]

Concerning Air-to-Air refueling, there is a special ACS flight control mode that has to be activated by pressing RCTRL+R that helps a great deal to stabilize the bird for refuel.

 

On Cougar, would it be possible to map this to Button 5 together with extending / retracting the refuel probe?

 

I think you'll like what I did.

 

S1 Long now cycles both the boom and ASC mode, but it doesn't stop there. Holding S3 while double-tapping S1 cycles the ASC mode (just in case you want full ASC control). When you press S1 Long again, the boom will retract, and ASC mode will return to normal. If it was already toggled to normal, it will not toggle again (a simulated discrete state).

 

There are also corresponding MFD functions as well as discrete modes on the Warthog throttle.

[DaddySchlich]

Thanks! I'm afraid that I do not have the Warthog stick or the MFDs. We're taking this a step at a time. Is there a way to determine what will work and what won't without the stick?

 

Much appreciate the help.

 

Daddy Schlich

[flyingflatfour]

I think you'll like what I did.

 

S1 Long now cycles both the boom and ASC mode, but it doesn't stop there. Holding S3 while double-tapping S1 cycles the ASC mode (just in case you want full ASC control). When you press S1 Long again, the boom will retract, and ASC mode will return to normal. If it was already toggled to normal, it will not toggle again (a simulated discrete state).

 

There are also corresponding MFD functions as well as discrete modes on the Warthog throttle.

 

Fantastic!! :clap:

 

Next question is: when is 2.28 due :lol:

[Home Fries]

Fantastic!! :clap:

 

Next question is: when is 2.28 due :lol:

 

You're a beta tester, right? I'll have this up tonight. 2.28 should be released in the next couple of days if there are no new bugs or major changes in tomorrow's DCS beta release.

[Home Fries]

Thanks! I'm afraid that I do not have the Warthog stick or the MFDs. We're taking this a step at a time. Is there a way to determine what will work and what won't without the stick?

 

Much appreciate the help.

 

Daddy Schlich

 

Honestly, the most important features require the stick and to a lesser degree MFDs. Use the controller diagrams for inspiration for your throttle mapping, but I would stick with just using the DCS Options menu.