DCS World TARGET profile for TM Cougar and Warthog + MFDs

[VirusAM]

Homefries...other 2 questions....

 

1) the num5 in my numeric keypad is not working...i mean in Windows and in the Dcs settings menu it works and it is recognized correctly but in the Hornet if i press it nothing happens. Is it a Dcs bug?Am I the only one having this issue?

 

 

2) i am about to join a virtual squadron which uses universal radio, with his teamspeak plugin, but i cannot manage to make it work with your profile.

I see that your profile supports simple radio and vaicom, but is there a way to make it work with Universalradio as well?

Thanks as usual

[Home Fries]

- the RDR range and mode are still acting in the reverse sense with the F-5E (CW vs CCW)

 

Fixed for next release!

[Home Fries]

Hi, could someone please give me some advice. I've correctly mapped all the buttons and I am able to engage NWS HI with S3, while I am on the ground. Then I am departing, after shortly after I raise the landing gear with S3 (Shifted) an the China Hat. I am no longer able to lower the gear. It seems that the S3 (shifted) will no longer work. I have to do i by the KB. And then when I am landed, I cant engage the NWS HI. It seems something wrong with the S3.

 

Could someone help me? I rebuild the script, full reinstall. Mapped the modifiers and so on.

It's possible it could be a bug in the script, as CHF dynamically remaps with the profile because of TriggerZoom. However, the AV-8B and F/A-18C are two aircraft that don't remap S3 with the gear up or down, so I'm not sure why that dumped on you.

 

I'll investigate further, but if you could tell me everything you were doing with the profile while flying the plane (assuming it was the Hornet) that would help me with my troubleshooting.

 

I was unable to duplicate this error. Any information you can provide (such as what you were doing, which macros/functions were in use, e.g. CommState), and does the error repeat? If it repeats, is there a sequence of events you can use to consistently trigger the bug?

[flyingflatfour]

Fixed for next release!

 

Thank you SO much!!

 

Would you consider as per previous post modifying the F-5E TQS mapping when using VAICOM to re-assign the comms switch aft position to intercom so as to be able to talk to the ground engineer using VAICOM without talking over SRS in multiplayer ?

 

Concerning SRS, any idea on how to deal with the problem regarding Windows 10 not hiding away the Cougar when Thrustmaster Virtual Device is running?

 

And last but not least, have you been able to think of a work-around for us VR players not using MFDs? :D

 

Thank you very much Home Fries for your great work, best wishes for next year to you and your beloved ones! :thumbup:

[Home Fries]

Would you consider as per previous post modifying the F-5E TQS mapping when using VAICOM to re-assign the comms switch aft position to intercom so as to be able to talk to the ground engineer using VAICOM without talking over SRS in multiplayer ?

 

<...>

 

And last but not least, have you been able to think of a work-around for us VR players not using MFDs? :D

The VAICOM/SRS integration is a global routine, so tweaking it for something like that would have to be done across the board. I don't intend to do anything with VAICOM/SRS at this point unless it's a bug fix. For the MFD thing, I have some ideas, but it will require some re-tooling. I'm getting into the busiest part of my year, so I'm putting projects with global profile ramifications on hold until the spring.

 

Concerning SRS, any idea on how to deal with the problem regarding Windows 10 not hiding away the Cougar when Thrustmaster Virtual Device is running?

I don't know, and this has been a frustration for as long as Win10 has been around. If you do find something, please let me know so I can put it in the Setup Guide.

 

Thank you very much Home Fries for your great work, best wishes for next year to you and your beloved ones! :thumbup:

You're quite welcome. BTW, I appreciate all the reports you've been making. This profile is so extensive with so many possible configurations that I depend on bug reports for almost all non-catastrophic bugs.

[flyingflatfour]

The VAICOM/SRS integration is a global routine, so tweaking it for something like that would have to be done across the board. I don't intend to do anything with VAICOM/SRS at this point unless it's a bug fix. For the MFD thing, I have some ideas, but it will require some re-tooling. I'm getting into the busiest part of my year, so I'm putting projects with global profile ramifications on hold until the spring.

 

Not sure what you mean by global routine, since the radio mappings are different for each module? As far as I understood I thought all that was needed was to remap the switch to VAICOM TX5 for the F-5E profile when using TQS + VAICOM option ticked in CTS?

 

 

I don't know, and this has been a frustration for as long as Win10 has been around. If you do find something, please let me know so I can put it in the Setup Guide.

 

Wilco :thumbup:

 

 

You're quite welcome. BTW, I appreciate all the reports you've been making. This profile is so extensive with so many possible configurations that I depend on bug reports for almost all non-catastrophic bugs.

 

My pleasure !

[tea_cypher]

Evening Home Fries.... just got the Gazelle, found a slight issue with using the Minigun, I have to use the M variant to switch toe the gunner position, then to L Profile so you can actually fire the gun.

[VirusAM]

is there a way to make the profile work with universal radio teamspeak plugin?

[Home Fries]

Evening Home Fries.... just got the Gazelle, found a slight issue with using the Minigun, I have to use the M variant to switch toe the gunner position, then to L Profile so you can actually fire the gun.

Thanks for the report. I'll look into this.

 

is there a way to make the profile work with universal radio teamspeak plugin?

 

I won't be directly supporting UR, but it should work the same way as SRS. Just assign the different radios to the comm switch/mic switch, and choose whether to use PTT Common in CTS (though if you use VAICOM, PTT Common is automatically deselected).

[Home Fries]

Not sure what you mean by global routine, since the radio mappings are different for each module? As far as I understood I thought all that was needed was to remap the switch to VAICOM TX5 for the F-5E profile when using TQS + VAICOM option ticked in CTS?

 

I mean that I have one communications init routine (2 if you count the one for the Warthog that is called by the main routine for WH users), and it determines the user's configuration (e.g. VAICOM, SRS, and whether CommState is enabled or forced) and the number of radios in the module to determine the mapping. I also have reserved DX20-23 for all voice comms (20,22-3 for SRS/VAICOM, 21 for TS3/Discord). I also recently discovered that these buttons must remain reserved for SRS/VAICOM even if the aircraft has only one radio (this issue is addressed in 2.28).

I won't be reserving any more DirectX buttons; every DX button I reserve for a global routine is one I can't use for a discrete switch or joystick/MFD button.

 

If you have some suggestions within this configuration, please let me know. The only thing I can think of is assigning DX21 to TX5 if you prefer to shut off TS3/Discord once in-game.

[VirusAM]

DCS World TARGET profile for TM Cougar and Warthog + MFDs

 

Thanks for the report. I'll look into this.

 

 

 

 

 

 

 

I won't be directly supporting UR, but it should work the same way as SRS. Just assign the different radios to the comm switch/mic switch, and choose whether to use PTT Common in CTS (though if you use VAICOM, PTT Common is automatically deselected).

 

 

 

thanks...but the problem i am encountering is that left and right comms switch registers as pulse presses, while i need hold presses for universal radio. Or should i use different buttons from the ones used for ai comms in the game?

 

ps my fssb r3 lighting arrived and it is great...i upgraded its electronic with the warthog one and i can decide if use the warthog axes and buttons or fssb ones...or a combination of both.

Edited January 1, 2019 by VirusAM

[Home Fries]

thanks...but the problem i am encountering is that left and right comms switch registers as pulse presses, while i need hold presses for universal radio. Or should i use different buttons from the ones used for ai comms in the game?

 

Make sure you directly enable SRS either from CTS or using the RMFD during profile hot-swap. Once SRS is enabled, the buttons will go from pulse to sustain.

[VirusAM]

Make sure you directly enable SRS either from CTS or using the RMFD during profile hot-swap. Once SRS is enabled, the buttons will go from pulse to sustain.

 

 

 

yeah i did that. But unfortunately now i have another problem, universradio telies in teamspeak but with teamspeak i cannot bind the warthog throttle buttons. It seems a persistent and annoying teamspeak bug

[Home Fries]

yeah i did that. But unfortunately now i have another problem, universradio telies in teamspeak but with teamspeak i cannot bind the warthog throttle buttons. It seems a persistent and annoying teamspeak bug

 

Yeah, that TS3 bug is annoying. You can get around that by setting Teamspeak/Voice Chat Hotkey as DirectX to 0 in CTS. Then the script will use ScrollLock (or whatever you have set in CTS) for the PTT.

 

See page 14 of the Setup Guide for details.

[smytilineos]

Wrong mapping for Huey kneeboard activate

 

Hi Home Fries,

 

Am I right saying that the left MFD long-hold press for kneeboard activate is wrongly mapped?

[flyingflatfour]

I mean that I have one communications init routine (2 if you count the one for the Warthog that is called by the main routine for WH users), and it determines the user's configuration (e.g. VAICOM, SRS, and whether CommState is enabled or forced) and the number of radios in the module to determine the mapping. I also have reserved DX20-23 for all voice comms (20,22-3 for SRS/VAICOM, 21 for TS3/Discord). I also recently discovered that these buttons must remain reserved for SRS/VAICOM even if the aircraft has only one radio (this issue is addressed in 2.28).

I won't be reserving any more DirectX buttons; every DX button I reserve for a global routine is one I can't use for a discrete switch or joystick/MFD button.

 

If you have some suggestions within this configuration, please let me know. The only thing I can think of is assigning DX21 to TX5 if you prefer to shut off TS3/Discord once in-game.

 

That would work, since I either use TS3 with a permanent transmission for early training flights in MP or I shut it down completely for full immersion using VAICOM + SRS :thumbup:

[Home Fries]

Hi Home Fries,

 

Am I right saying that the left MFD long-hold press for kneeboard activate is wrongly mapped?

 

Which module/profile?

[smytilineos]

Which module/profile?

Sorry. Of course. The Huey. Warthog.

[RedeyeStorm]

Hi Home Fries,

 

Awesome work I must say.

 

However I can't get it to work. First some system info. Using Warthog with Saitek rudder pedals and Oculus Rift. Also using VAC+Vaicom Pro with chatter pack.

 

I have cleared out all joystick commands in DCS for A10A, General and UI layer.

I loaded the following Lua's in the following order:

 

- TARGET A10A kb v225b.diff.lua

- TARGET A10A wh v225b.diff.lua

- TARGET UILayer js VR1 v168.diff.lua

 

I have been trying to get the A10A to work. First Viacom is not working right. It reports that the PTT button is not configured right. So voice commands doesn't work. The assigned HAT

reports the same key button 21 for all four directions and press.

 

 

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.

 

Hope you can help me.

 

RedeyeStorm

[flyingflatfour]

I've been fiddling a bit more into DCS today, here's what I found:

 

 

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:

 

 

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 ?

 

 

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

Edited January 7, 2019 by flyingflatfour

[flyingflatfour]

Here are a couple of screenshots trying to help understanding what is going on.

 

 

The first one shows the status of VAICOM and SRS when pushing the Comm switch forward (physical "VHF" marking on the Cougar TQS), the second one backward ("UHF") in the F-5E using CTS.

 

 

 

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".

 

 

Best regards

Edited January 7, 2019 by flyingflatfour

[Home Fries]

Sorry. Of course. The Huey. Warthog.

 

 

 

It should work for the Huey. For the Warthog, OSB20 is mapped to the same OSB in the plane, so you need to hold it with S3.

[Home Fries]

First Viacom is not working right. It reports that the PTT button is not configured right. So voice commands doesn't work. The assigned HAT

 

reports the same key button 21 for all four directions and press.

 

You need to enable VAICOM and SRS in the Communications options in CTS.

 

 

 

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.

 

 

I’ll look at it when I get home from work. I can only test the profile mapping itself, as I don’t use VR.

[smytilineos]

Hi again Home Fries!

 

I noticed a problem with the Bf-109 warthog profile.

 

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.

 

Bug or me doing something stupid?

 

Many thanks,

 

Stefanos

 

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...

[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.

 

<...>

 

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...

 

 

 

Thanks. I’ll take a look at these issues tomorrow.

Edited January 8, 2019 by Home Fries