HOTAS Cougar FOxy programming question

[Slayer_42]

Hey there. first of all id like to say hey as this is my first post here in the forums.

 

Ok now im creating a new profile for my Cougar in Foxy based around the F-16 Block 52 (thus the F-16 controls haha). In real life, alot of the various buttons/hats have a different function depending on which mode (A-A or A-G) The aircrafts combat system is in. I want to simulate this by making the same thing happen on my cougar so without using a massive amount of IF and THEN statements is it possible to have the control functions changed depending on the position of the dogfight switch? (intended for use with Falcon 4.0 AF)

 

Cheers :pilotfly:

[Kuky]

/U /M /D modifies are used for that

[Slayer_42]

I think you may have misunderstood me.

 

Ok i'll try and explain this as clearly as possible....

 

So there are two main modes. Air to air and air to ground which realistically are toggled using the dogfight switch.

 

Now depending on which mode is active, the function of all the buttons varies. So for example, A-A Mode results in button 1 doing function X.

Whereas in A-G Mode, the same button (Button 1) does function Y.

A-A = B1 - functionX

A-G = B2 - functionY

 

So i guess what im asking is, 'is there a way of programming the cougar in such a way that has the same effect of creating two different macro files and switching between the two using the dogfight switch?'

 

Cheers for the quick reply btw :thumbup:

[Kuky]

I said, the /U /M /D modifier is what you want to use.. depending what button you want pressed depends in what position DF switch is in. Example:

 

BTN TG1 /U key-a

/M key-b

/D key-c

 

so pressing TG1 when DF is in up position will give key-a, when it's in middle position it'll give key-b and when it's in down position it gives key-c... couldn't be simpler

Edited April 7, 2012 by Kuky

[Slayer_42]

Forgot to mention that ive already assigned a key to those positions on the DF switch. so is it possible to keep function XYZ on the /U /M /D positions but at the same time have those positions change the functions on all other buttons? (Preferably without alot of IF and THEN statements)

[Kuky]

yes, you can do that and you don't need any logical programming.

 

You can assign any button/command to dogfight switch (buttons T7 and T8 ) any way you want and you can specify for any other button to have different key depending on what position dogfight switch is at and for this you use /U /M /D modifiers.

 

All of this you're asking is very simple to do... I wonder if you tried programmig in Foxy at all

Edited April 10, 2012 by Kuky

[Slayer_42]

Please forgive my ignorance hahaha i have indeed done a fair bit of programing in Foxy but don't know how i'd go about achieving what it is i want to do. Could you possibly type up an example of what it is im looking for?

[Kuky]

BTN S1 /U Function1

/M Function2

/D Function3

 

examle above means, pressing S1 button when dogfight is in UP position gives Function1, pressing S1 button when dogfight switch is in middle position gives Function2 and pressing S1 button when dogfight switch is DOWN position gives Function3.

 

/U /M /D modifiers have to be used at the same time (you can'y use /U on its own... even if you want to have some Fuction/key working only when digfight switch is in up position). you can for example have:

 

BTN S1 /U Function1

/M

/D

 

Pressing S1 button when dogfight is in UP position gives Function1 but if dogfight is in middle or down position it does nothing (no key presses)

 

If you still don't get it I'm gonna rep you negatively :|

Edited April 10, 2012 by Kuky

[Slayer_42]

Yes i get that. That is very simple indeed. What im looking to do is have the DF Button change the assignments of all other buttons. So for instance, the Dogfight switch changes the buttons that have been assigned to ALL OTHER BUTTONS ON THE THROTTLE AND FLIGHT YOKE.

 

DESIRED RESULT: Functions for ALL BUTTONS ON HOTAS depend on position of dogfight switch.

 

There are no button combinations within falcon 4.0 that provide the ability to do this which is why i can only achieve the desired result via Foxy.

 

If u still do not understand this then i dont know how else to explain it.

 

cheers

[Kuky]

For all buttons you use same coding as above so every button will give different key press depending on DF switch. There is no one-for-all function if that's what's you're asking :)

[Slayer_42]

Hey im back.

Thanks Kuky i've finally gotten it. I didnt realise that the /U /M /D modifiers were tied to the dogfight switch without having to actually be defined as being tied to it.

 

Well that's a major breakthrough for me and my programming ability!!!!

 

Thanx alot Kuky. :thumbup:

[Kuky]

No worries... for what you need these /U /M /D modifiers is all you need, You can do much more fancy programming with logical flags but it also gets lot more complicated (depending how complex you want to make it ;) )

[Fakum]

I am trying to use my "DogFight" switch to control the Radiator Dampers on the P-51D. I get the Radiator Cooling Damper to work just as I want it to, but when I use the (S3 Modifier for the "IN" for the Radiator Oil) same switch in the Modifier Mode, the switch does not HOLD in position once the S3 button is released? Here is my current config:

 

 

Rem ################################################

Rem T7-T8 :

Rem ################################################

 

BTN T7 /I /H /P Radiator_oil_Close /R Radiator_oil_Auto

/O /H /P Radiator_coolant_Close /R Radiator_coolant_Auto

BTN T8 /I /H /P Radiator_oil_Open /R Radiator_oil_Auto

/O /H /P Radiator_coolant_Open /R Radiator_coolant_Auto

[Rudel_chw]

... the switch does not HOLD in position once the S3 button is released?

 

I believe that it is working as designed .. as soon as you let off of the S3 button, the /I command stops. You will have to find an alternative way to handle the radiators, sorry.

[Fakum]

Ok, thats good to know. So I recall seeing "Logical Flags" (Example Below) in older profiles that I once downloaded and used. I dont really know how I would make use of these, but Im willing to try and learn if they will work if written correctly for that switch. Would I be wasting my time or is this approach for that switch workable? Thanks

 

 

E.G.

 

BTN H3U /I KD(X9) DLY(200) KU(X9)

/O KD(X8 ) DLY(200) KU(X8 )

 

DEF X10 DELAY(500) H3U AND S3

DEF X11 DELAY(500) H3U AND NOT S3

DEF X12 NOT H3U AND X8

DEF X13 NOT H3U AND X9

 

BTN X10 Trimmerreset

BTN X11 /H Trimmer

BTN X12 HoverOn/Off

BTN X13 Wheelbrakeparking

 

BTN H3D /I TrackIR_Precision

/O TrackIR_Center

 

DEF X4 DELAY(500) H3D AND S3

DEF X5 NOT H3D AND X1

DEF X6 NOT H3D AND X2

DEF X7 H3D AND S3

 

BTN X4 Axis_Reset

BTN X5 Axis_Lock

BTN X6 Axis_Unlock

BTN X7 /P Axis_Lock Axis_Trim /R Axis_Unlock

[Sn8ke_iis]

... but when I use the (S3 Modifier for the "IN" for the Radiator Oil) same switch in the Modifier Mode, the switch does not HOLD in position once the S3 button is released?

 

I know this is probably not what you want to hear, but that's pretty easy to do through the TARGET GUI. See page 23 in the documentation:

 

https://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/TARGET_User_Manual_ENG.pdf

 

You can set up a press and release. I use the warthog throttle for the P-51 but that's how I did it. Since you are using a modifier layer for the same switch, you might have to assign a new unique keyboard callback manually in the DCS spreadsheet so the "S" key is not locked up for other functions. But if you let off the modifier button and then recenter the switch it should hold. You can also set up a sequence on the opposite sides of the switch to ensure the press is cancelled out with a release before you initiate another press to close the radiator and vice versa, if that makes sense.

 

Perhaps just try an experimental configuration just on that button to see if it works like you want it?

[Fakum]

Thanks for the advise. I have to be honest, I tried to convert to the Target software about 8 years ago,, I was completely frustrated with a configuration I was trying to do, I couldnt get it to work in Target after a couple of weeks of help on the forums, I managed to achieve it through Foxy, and I never looked back.

[Sn8ke_iis]

Have a look at the current version's GUI. I have the oil radiator function set on a 3 way toggle on the base of the Warthog without a layer so not exactly what you are trying to do but it works very well. I know a little C++ and R but that just helped me read the syntax. I always use the GUI. Easy peasy. I've only had to edit the script manually a few times.

 

The first screen shot shows the oil cooler function on it's own 3 way switch. The 2nd is an example of a layer I have set for the hat switch to control trim and cockpit camera with the paddle switch acting as the modifier. The 3rd is the script.

[Fakum]

Yeah, I can get the toggle to work, just not in addition to using a modifier. That syntax in the 3rd shot, thats more scary then Foxy LOL. I have a headache already,,,, Thanks though

[Sn8ke_iis]

LOL, I was just showing you the script for reference. The Graphic User Interface (GUI) does it all for you, no scripting necessary. The GUI is all just point and click with the normal pull down, drill down menu conventions. It's very intuitive. I assure you if you can script in Foxy you can use the GUI. But whichever works best for you. Good luck, I hope you get it figured out.

:crash:

[BitMaster]

What I really miss is the simplicity of .txt file grogramming like back in the days for F22 & TQS.

 

It was superior to what TM had to offer and also better than Foxit, more flexible and better oversight what is doing what.

 

I think I need to get back into it and the P-51 is a good and useful start. Yeah...that Oil cooler.

 

Took the Stang for a flight from Mozdok to Kutaisi 2 days ago on VA server and had a wonderful hour of relaxed flying and enjoying the beauty of DCS, the only thing that needed attention was my full rear tank ( damn nasty ) and the Oil Cooler while climbing out to 30k feet. I had a -50! Carb temp, ehhh but it worked, that is another issue LoL

 

The good thing for TG is that it will stay if your DCS goes nuts or overwrites settings.

 

Maybe over Xmas in some quiet hour.

[Sn8ke_iis]

The good thing for TG is that it will stay if your DCS goes nuts or overwrites settings.

 

That's one of my favorite features. I've lost count of how many hours of fun time I've lost in CLOD and DCS due to unplugging controllers, Windows device issues, or unknowingly deleting the .cfg file.

 

I have a standard template that I use for all aircraft with consistent muscle memory for views, comms, zoom, TIR/VR recenter, etc. When I try out a new module, I can just hop in and fly without having to reassign in the DCS spreadsheet. You only have to learn one GUI and it works with all games and sims. The process of assigning a unique profile for a new module really aids the learning process. I retain it better than RTFM. Easy to back up and share as well.

 

The only issue I've had with Target is having to make sure USB power saving features are turned off in BIOS and the registry. Otherwise the script can think the device is unplugged and kick back an error. The error codes usually show up in a search engine.

[Rudel_chw]

What I really miss is the simplicity of .txt file grogramming like back in the days for F22 & TQS.

 

Actually, the programming of the TM Cougar is very similar to that of the F22/TQS .. it is still a text based programming.

 

It was superior to what TM had to offer and also better than Foxit

 

Not really .. Foxy is just a text editor with the function for downloading the profile onto the Cougar built-in. It also provides easy access to a lot of nice utilities, like a button tester, logical flag viewer ... even a nice graphic editor for creating this type of diagrams:

 

 

Target however, is a whole different animal .. it's like learning C++ all over again :( ... and it is the main reason why I never got around to replacing my Cougar with a Warthog.

[Fakum]

I appreciate the feedback guys, but I still have 1 open question from page 2, and that is, would I be wasting my time trying to get Logical flags to work? Again, I am willing to learn, but ifs the wrong application, I dont want to waste a few days, thanks.

 

 

Ok, thats good to know. So I recall seeing "Logical Flags" (Example Below) in older profiles that I once downloaded and used. I dont really know how I would make use of these, but Im willing to try and learn if they will work if written correctly for that switch. Would I be wasting my time or is this approach for that switch workable? Thanks

 

 

E.G.

 

BTN H3U /I KD(X9) DLY(200) KU(X9)

/O KD(X8 ) DLY(200) KU(X8 )

 

DEF X10 DELAY(500) H3U AND S3

DEF X11 DELAY(500) H3U AND NOT S3

DEF X12 NOT H3U AND X8

DEF X13 NOT H3U AND X9

 

BTN X10 Trimmerreset

BTN X11 /H Trimmer

BTN X12 HoverOn/Off

BTN X13 Wheelbrakeparking

 

BTN H3D /I TrackIR_Precision

/O TrackIR_Center

 

DEF X4 DELAY(500) H3D AND S3

DEF X5 NOT H3D AND X1

DEF X6 NOT H3D AND X2

DEF X7 H3D AND S3

 

BTN X4 Axis_Reset

BTN X5 Axis_Lock

BTN X6 Axis_Unlock

BTN X7 /P Axis_Lock Axis_Trim /R Axis_Unlock

[BitMaster]

That's one of my favorite features. I've lost count of how many hours of fun time I've lost in CLOD and DCS due to unplugging controllers, Windows device issues, or unknowingly deleting the .cfg file.

 

I have a standard template that I use for all aircraft with consistent muscle memory for views, comms, zoom, TIR/VR recenter, etc. When I try out a new module, I can just hop in and fly without having to reassign in the DCS spreadsheet. You only have to learn one GUI and it works with all games and sims. The process of assigning a unique profile for a new module really aids the learning process. I retain it better than RTFM. Easy to back up and share as well.

 

The only issue I've had with Target is having to make sure USB power saving features are turned off in BIOS and the registry. Otherwise the script can think the device is unplugged and kick back an error. The error codes usually show up in a search engine.

 

OK, you got me messing around with it, I actually strted to copy your Rad-Oil switch... it worked..and then I found out my Stick didn't work...ahhh...and the trial & error starts.

 

Gonna give a shot tonight, maybe 3-6h LOL....

 

I do remember that Foxy couldnt do a few things you could do with a "simple" text file, but that is sooo long ago I dont recall exactly what it was. I do know that most of my squad mates used my template... LONG AGO.

 

Door bell.... laters