DCS World TARGET profile for TM Cougar and Warthog + MFDs - Page 163 - ED Forums
 


Notices

View Poll Results: How shoiuld the Autopilot Altitude and Heading/Track Switches be mapped on the RMFD?
Keep DH/DT with Hdg Hold and BA/RA with Alt Hold (keep apples with apples) 0 0%
Map BA/RA with Hdg Hold and DH/DTwith Alt Hold (like actual panel switches) 2 100.00%
Voters: 2. You may not vote on this poll

Reply
 
Thread Tools Display Modes
Old 06-01-2020, 06:26 PM   #1621
Home Fries
Senior Member
 
Home Fries's Avatar
 
Join Date: Nov 2012
Location: Greater Washington DC Area
Posts: 2,961
Default

Quote:
Originally Posted by Charlie122sq View Post
Nope, is Hotas cougar with cougar stick
Ok, I'll try to duplicate with the Cougar.
__________________
-Home Fries
Fear the Bolts!


The average naval aviator, despite the sometimes swaggering exterior, is very much capable of such feelings as love, affection, intimacy, and caring.
These feelings just don't involve anyone else.


Provide your inputs for CTS 3.0
My DCS Files and Skins
My DCS TARGET Profile for Cougar or Warthog and MFDs
F-14B LANTIRN Guide
Home Fries is offline   Reply With Quote
Old 06-01-2020, 07:15 PM   #1622
Lorthirk
Member
 
Join Date: Jan 2018
Posts: 183
Default

So... I'm following the discussion even though I don't use VAICOM, but I'm really interested in the whole project (as Home Fries surely knows )

Being a Software Engineer when outside of the cockpit, I can't help but reason about the whole code base. I know we're about to hit the "critical mass" of the script, so I think that the time for a major overhaul is coming.

Now... for sure, TARGET scripts are not meant to be THAT module, and what Home Fries achieved here is quite impressive IMHO. Nonetheless, we need room for further improvements.

So, here's my first thoughts: I think we should find start to branch the scripts according to... something. I don't know exactly what the best way do this can be, but the first thing that comes in my mind is to split the code base between Cougar and Warthog base. I think this should help split the code base pretty much evenly, and would also help reduce the complexity.

What do you think, Home?
Lorthirk is online now   Reply With Quote
Old 06-01-2020, 08:50 PM   #1623
tomeye
Junior Member
 
Join Date: Apr 2020
Location: Greece
Posts: 36
Default

Quote:
Originally Posted by Home Fries View Post
Fellas, I'm glad we're having this conversation. I started this profile years ago for the Cougar when the only modules were the A-10C, Ka-50, and FC3 (then the P-51 shortly after). The baseline was the A-10C and the only voice solutions were TS3 and the TS3-based TARS (a spiritual predecessor to SRS).

Since then I have modified the code to include the Warthog and then two years ago I changed VAC/TARS support to VAICOM/SRS. Now that I'm very close to the stack limit that TARGET can handle, I will need to revamp my comms code again to streamline it. I have already tried to make the Warthog Mic Switch as standardized as possible, but I'm not sure I'll be able to do the same level of standardization with the Cougar without sacrificing some functionality.

Here's what I try to do with comms:
  1. Single Radio: T1 (Cougar) or MSD (Warthog). MSU/MSP for TS3/Discord (often shared with T1 for Cougar, but sometimes T3 Up).
  2. Dual Radio: T4/T5 (Cougar Left/Right) or MSR/L (Warthog). MSU/P TS3/Discord (T3 for Cougar).
  3. Three Radios: T2/4/5 (Cougar) or MSR/L/D (Warthog). Again, MSU/P or T3 for TS3/Discord.
I changed the helos to match their HOTAS (trigger is normal for helos, except for the Ka-50 which uses the pickle button), but you should always get MSP for TS3/Discord. I also changed the F-16 to do Up/Down on the TQS, which matches the actual F-16.

I see that for helos or single radios, MSD and MSU/MSP are both mapped to DX21. Is this correct?
tomeye is offline   Reply With Quote
Old 06-02-2020, 01:09 AM   #1624
Home Fries
Senior Member
 
Home Fries's Avatar
 
Join Date: Nov 2012
Location: Greater Washington DC Area
Posts: 2,961
Default

Quote:
Originally Posted by Lorthirk View Post
So... I'm following the discussion even though I don't use VAICOM, but I'm really interested in the whole project (as Home Fries surely knows )

Being a Software Engineer when outside of the cockpit, I can't help but reason about the whole code base. I know we're about to hit the "critical mass" of the script, so I think that the time for a major overhaul is coming.

Now... for sure, TARGET scripts are not meant to be THAT module, and what Home Fries achieved here is quite impressive IMHO. Nonetheless, we need room for further improvements.

So, here's my first thoughts: I think we should find start to branch the scripts according to... something. I don't know exactly what the best way do this can be, but the first thing that comes in my mind is to split the code base between Cougar and Warthog base. I think this should help split the code base pretty much evenly, and would also help reduce the complexity.

What do you think, Home?
Problem with breaking the code that way is that I'll have to do twice the work, or I'll have to develop one, then port it (which will be a configuration management nightmare with updates). However, if I can figure out a way to alias &Joystick and &HCougar, I could have over 90% of the stick solution with one code base. I'd still have to do the throttles individually but that isn't a big deal.

I'm thinking three things are going to happen, and sooner than later (though I need a big block of uninterrupted time to make it work). First, I'll tweak the communications routines. I have completely separate routines for Cougar and Warthog because I ported the Warthog later and I wanted to be able to compare the code side by side. I could combine much of that and use the same variables, and I will need to streamline the comms code. This means that the PTT Common option will go away (this is obsolete since SRS became the game standard anyway). That will reduce the permutations in the comms. options (especially true in the Cougar routine). Next, I'll stop programming for every single option and start programming for a common denominator (or series of popular options). This is where I could use your input on what you all use and what you don't care about.

Next, I'll start globalizing as much as I can, particularly with MFDs. Right now there is a convention, but each module library has its own MFD routine. Globalizing the MFDs and then calling individual routines to re-assign differences is less efficient programming, but may reduce the stack overhead.

Finally, I'll move the non-DCS programs like IL-2 and Elite Dangerous to a separate profile. I'll ideally want to update the CTS EXE to have a new GUI and call different files, but nothing else needs to change.

I welcome any other inputs or suggestions
__________________
-Home Fries
Fear the Bolts!


The average naval aviator, despite the sometimes swaggering exterior, is very much capable of such feelings as love, affection, intimacy, and caring.
These feelings just don't involve anyone else.


Provide your inputs for CTS 3.0
My DCS Files and Skins
My DCS TARGET Profile for Cougar or Warthog and MFDs
F-14B LANTIRN Guide
Home Fries is offline   Reply With Quote
Old 06-02-2020, 04:37 AM   #1625
overalien
Member
 
Join Date: Feb 2006
Posts: 212
Default

Quote:
Originally Posted by Home Fries View Post
Problem with breaking the code that way is that I'll have to do twice the work, or I'll have to develop one, then port it (which will be a configuration management nightmare with updates). However, if I can figure out a way to alias &Joystick and &HCougar, I could have over 90% of the stick solution with one code base. I'd still have to do the throttles individually but that isn't a big deal.

I'm thinking three things are going to happen, and sooner than later (though I need a big block of uninterrupted time to make it work). First, I'll tweak the communications routines. I have completely separate routines for Cougar and Warthog because I ported the Warthog later and I wanted to be able to compare the code side by side. I could combine much of that and use the same variables, and I will need to streamline the comms code. This means that the PTT Common option will go away (this is obsolete since SRS became the game standard anyway). That will reduce the permutations in the comms. options (especially true in the Cougar routine). Next, I'll stop programming for every single option and start programming for a common denominator (or series of popular options). This is where I could use your input on what you all use and what you don't care about.

Next, I'll start globalizing as much as I can, particularly with MFDs. Right now there is a convention, but each module library has its own MFD routine. Globalizing the MFDs and then calling individual routines to re-assign differences is less efficient programming, but may reduce the stack overhead.

Finally, I'll move the non-DCS programs like IL-2 and Elite Dangerous to a separate profile. I'll ideally want to update the CTS EXE to have a new GUI and call different files, but nothing else needs to change.

I welcome any other inputs or suggestions

Yep. I think you're in the right track. The issue is that this wonderful software caters for every possible permutation of hardware software and supported games as an all in one package! It's a herculian task which has been most admirably delivered, but must be a nightmare to maintain and incrementally expand. Perhaps a poll to your users might give an indication of who is doing what with it right now might help you to focus? Modularising and setting it up on GIThub may also elicit some collaborators and might create developmentvspecialisation for various features to reduce the pressure and workload on you.... Something to consider.


Sent from my iPhone using Tapatalk
__________________
__________________
overalien
Hog Driver starting to really like the Tomcat

System specs:
Intel i7-8700k - OC to 5.0 GHz
| 32 GB RAM 3600 MHz | Nvidia 1080ti SLi | Mixed Storage - Win 10 and DCS on Samsung SSD 970 Pro


Flightgear:
7 Displays (3 x 1440p, 1 X 1080p, 3 X Lilliput Touch) | 3 x Cougar MFDs
| Warthog HOTAS | Thrustmaster TPR Pedals | iBEAM Shaker + Simshaker for Aviators w. Sound Module | Helios | VAICOM Pro + AIRIO | TrackIR 5
overalien is offline   Reply With Quote
Old 06-02-2020, 06:26 AM   #1626
Lorthirk
Member
 
Join Date: Jan 2018
Posts: 183
Default

Yeah, about putting it on Github... Unless you don't have something against sharing your cose, I would consider it!
Lorthirk is online now   Reply With Quote
Old 06-03-2020, 01:18 AM   #1627
Home Fries
Senior Member
 
Home Fries's Avatar
 
Join Date: Nov 2012
Location: Greater Washington DC Area
Posts: 2,961
Default

Quote:
Originally Posted by Lorthirk View Post
Yeah, about putting it on Github... Unless you don't have something against sharing your cose, I would consider it!
The very nature of TARGET means that my code is shared! I'll look into it.
__________________
-Home Fries
Fear the Bolts!


The average naval aviator, despite the sometimes swaggering exterior, is very much capable of such feelings as love, affection, intimacy, and caring.
These feelings just don't involve anyone else.


Provide your inputs for CTS 3.0
My DCS Files and Skins
My DCS TARGET Profile for Cougar or Warthog and MFDs
F-14B LANTIRN Guide
Home Fries is offline   Reply With Quote
Old 06-03-2020, 07:02 AM   #1628
Lorthirk
Member
 
Join Date: Jan 2018
Posts: 183
Default

Well... I know Github a bit, since I use it every day at work. If you never used Git or other SCMs in general it could be a bit hard to grasp in the beginning, so should you need any hint, of any kind, feel free to ask!

Also, should you decide to go ahead and put the code in Github, all the issues management could be moved from Trello to Github, using a single "hub" for all things about CTS development, from source code to management, and trust me, it helps keeping track of all this stuff together. But of course it's your call.
Lorthirk is online now   Reply With Quote
Old 06-04-2020, 06:47 AM   #1629
Dutch60
Member
 
Dutch60's Avatar
 
Join Date: Jan 2005
Location: Netherlands
Posts: 211
Default

Now that the P-47 is pre-released, is there a profile for the P-47 coming?
__________________
System
Spoiler:
i7 8700K @ 5.0 GHz (H115i)
GTX 1080 Ti SC2 Hybrid @ 2025 MHz
32 GB RAM @ 3866 MHz CL8
TM Warthog HOTAS + MFD's
MFG Crosswind
Asus PG348 @ 3440x1440 GSync
Valve Index VR
TrackIR 5
Win10 x64

Modules
Spoiler:
FC-3
A-10C, F-16C, F/A-18C, F-86F, F-5E, F-14B
M-2000C, AJS-37
MiG-15bis, MiG-19P, MiG-21bis
L-39, C-101, Yak-52
Spitfire LF, P-51D, P-47D, Bf 109 K-4, Fw 190 D-9, Fw 190 A-8
UH-1H, Black Shark 2
Nevada, Normandy, Channel, WWII Assets, Persian Gulf, Super Carrier

Last edited by Dutch60; 06-04-2020 at 08:16 AM.
Dutch60 is offline   Reply With Quote
Old 06-04-2020, 11:52 PM   #1630
Charlie122sq
Junior Member
 
Join Date: Jul 2018
Posts: 18
Default

Hi Home Fries, i am trying to setup the SRS as manual says to use the F18 and MIDS radio, i set SimpleRadio Standalone value to 1 in Global section. I execute the script and then open SRS, i set RADIO 1 and RADIO 2 in buttons 20 (comms switch left) and 22 (comms switch rigth) but when i try to set RADIO 3 in button 21 (comms switch down), button 20 is activated or "keyboard 44" is displayed:



and button 23 (comms switch up) doesn't even work. So if i push comms switch left or down, button 20 is actived or "keyboard 44" displayed, rigth is button 22 and up doesn't activate anything.

I try in DCS controls setup to set buttons 21 and 23 and they are not working. In DCS i can use button 20 and 22 for SRS comms , but when i depressed any one, sounds like a double click and "TR" turns on and off even if i keep pressing the button.

I have checked the buttons in case they were malfunctioning in Windows, others simulators and without the script running and all of them are working fine.

This is with a HOTAS COUGAR with COUGAR stick

Last edited by Charlie122sq; 06-05-2020 at 12:02 AM.
Charlie122sq is offline   Reply With Quote
Reply

Tags
cougar, hotas, mfd, thrustmaster, warthog

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 12:30 PM. vBulletin Skin by ForumMonkeys. Powered by vBulletin®.
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.