Jump to content

HOTAS Cougar software on a modern Windows


Recommended Posts

Hello,

 

While I do realize that the preferred joystick on DCS seems to be the TM Warthog, those of us that still have the previous model, the Thrustmaster Hotas Cougar, are somewhat left behind and there is little support for our Controller.

 

Up until a few months ago I was happy to just use the DCS Control Configuration to setup my Cougar for each DCS module, but browsing through the User Files section I found the Foxy profiles that a spanish user of this forum ( @Legolasindar ) had shared for Flamming Cliffs 2.

 

I saw then what I was missing by just using the standard DCS Control Config ... using the Cougar native scripting one could bind complex key combinations to the plane's commands, and have more programming positions by using the Dogfight switch of the Cougar.

 

But I needed to install the TM software in order to try the native profile ...

So, I began the rather complex journey of trying to use old software on current Windows ... I purchased my Cougar new in 2002 and it really shows when you try to find new software for it.

 

After a while, I managed to get everyting working on my Windows 8.1 gaming machine (actually its Windows Server 2012r2, but its almost identical to Windows 8.1) ... on this thread I wanted to share with other Cougar owners, all the steps for getting the Cougar software fully working on a modern 64 bit Windows.

 

1.- Install the TM 64 bits Drivers:

 

This is the first step, and probably most Cougar owners have already performed it. The driver can be downloaded from Thrustmaster:

 

https://support.thrustmaster.com/en/product/hotascougar-en/

 

The specific file that we need is the 64 bit driver: Package drivers - Vista RC2 (64bit)'

 

Once downloaded, change the .exe properties, so that its compatibility settings are: "Windows Vista SP2" and "Run as Admin" is selected:

 

f01.jpg

 

After setting these compatibility options, unplug from the computer the USB cable of the Cougar and then run the installer, it should show:

 

 

f02.jpg

 

The installer will copy the driver files into the default folder C:\Program Files (x86)\HOTAS ... and after a while it will ask you to plug in the USB cable of the Cougar, like this (sorry, my Windows is in spanish 🙂 )

 

f03.jpg

 

The install should finish after a short while, like this:

 

f04.jpg

 

After the installer finishes, it will start another program to update the Cougar's firmware and it will fail because it doesn't have the admin rights:

 

f05.jpg

 

This is no big deal, since most likely your Cougar already has the lastest firmware ... no new firmwares have appeared since 2003.

 

Now, restart the computer so that Windows can load the drivers properly and recognize the Hotas Cougar.

 

2.- Fix the Cougar Control Panel:

 

The driver installation will leave on your desktop an icon to run its Control Panel ... this software needs to run with Admin privileges, so open up its properties and select "Run as admin", like this:

 

f06.jpg

 

Now, if you try to run the Cougar Control Panel you will most likely get this error:

 

f07.jpg

 

To correct it, look in your folder at location "C:\HOTAS\drivers" and find "STTubeDevice203.dll" file. Then copy and paste the "STTubeDevice203.dll" file into "C:\Windows\SysWow64" folder, like this:

 

Copy from here:

 

f08.jpg

 

... into here:

 

f09.jpg

 

Now, the Control Panel should run without further problems:

 

f10.jpg


 

f11.jpg

The Thrustmaster software actually installs not only the Cougar Control Panel, but also several small utilities ... the most useful for debuging profiles is the Button State Viewer, which allows you to check not only the button's state but also the logical flag's too:

 

f13.jpg

 

so I have placed a shortcut for it on my DCS icon collection:

 

f12.jpg

 

I will continue on the next post, with the setup of the Foxy programming software, so see you later 🙂


Edited by Rudel_chw
Fix images lost

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites
  • Replies 142
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Hello,   Thanks a lot for such a detailed post. I don't really make use of custom startup options so I have not had to face this kind of issues, but it is good to know.   What I did found out is the

3.- Install the Foxy programming software:

 

This is more of a complete programming environment rather than just a "software", tailored for the creation of TM Cougar scripts using a GUI interface. It's version 4.0 can be downloaded from Thrustmaster:

 

https://support.thrustmaster.com/en/product/hotascougar-en/

 

The specific file that we need is called "Hotas Cougar Foxy v4.0" and this is the link:

 

http://ts.thrustmaster.com/download/accessories/pc/hotas/software/foxy/foxyv4.zip

 

Once downloaded decompress the zip file and change the setup.exe properties, so that its compatibility settings are: "Windows Vista SP2" and "Run as Admin" is selected, as shown here:

 

f14.jpg

 

Afterwards, we run this setup:

 

f15.jpg

 

The default installation folder is C:\Program Files (x86)\Foxy\:

 

f16.jpg

 

... but I prefer to locate it within the rest of the TM software, so I change the path to this:

 

f17.jpg

 

Then the installer will run and we will end up with version 4.0 of Foxy:

 

f20.jpg

 

Remember to tick the "Run as Admin" compatibility option on Foxy's shortcut:

 

f29.jpg

 

Now, we can update Foxy to the latest version available (from about 2004), by downloading this patch:

 

http://cougar.flyfoxy.com/files/Foxy42beta.zip

 

This has no installer, you just decompress it and then copy the 13 files that it contains, over to the Foxy folder, replacing the older versions that are on that folder. Now, when we run Foxy it should show this version number on its about box:

 

f21.jpg

 

Clean Up the Hotas/files folder:

 

The Cougar software comes with several sample profiles for games of the 90's and 2000's stored on its /Hotas/files folder:

 

f22.jpg

 

I've saved them on a backup folder and then cleared the folder so that only my own profiles are there ... this makes for a cleaner development environment 🙂

 

f23.jpg

 

4.- Using Foxy:

 

Now we can run Foxy and use it to create or modify Cougar profiles:

 

f24.jpg

 

The Cougar Programming Syntax is available on Foxy's Help menu, a very complete 150 pages MS Word file that it's a pleasure to read ... written by Foxy's creator, Dr. James "Nutty" Hallows ... my gratitude to him for his creation.

 

If you compile one of my profiles, you may came across this error:

 

f25.jpg

 

This happens if you have never on this PC calibrated the Cougar; the calibration is started from the Cougar Control Panel, by clicking on "Manual Calibration":

 

f26.jpg

 

The calibration process is easy and consist on just moving every axis to its full extent:

 

f27.jpg

 

... then the calibration data is stored and Foxy can use it:

 

f28.jpg

 

The Hotas Cougar's memory can only hold a single profile at a time, so, when we want to use a different module than the last time that we used DCS ... say, the last time we flew the Blackshark but today I want to fly the Su-27, we need to first run Foxy to download the correct profile into the TM Cougar.

 

To ease somewhat all this profile mess, Foxy allows to create a Menu with all of our DCS Modules, that will allow you to download the correct profile and launch DCS in one swift step.

 

To create this "Games" Menu, you first load in Foxy the profile ... and then use this menu option:

 

f30.jpg

 

Now copy from the DCS icon the fields "Target" into "Executable" and "Start in" to "Working", like this:

 

f31.jpg

 

We will end up with a Menu listing all of our DCS modules, well just a single one for this example, but you get the idea 🙂

 

f32.jpg

 

And that would be all, we now have on our PC everything necessary for developing and modifying Cougar profiles ... in the meantime you can download some of mine, that you can use as is or as starting points for creating your own:

 

For DCS Su-27: https://www.digitalcombatsimulator.com/en/files/2326383/

 

For DCS F-5E: https://www.digitalcombatsimulator.com/en/files/2322364/

 

For DCS Blackshark 2: https://www.digitalcombatsimulator.com/en/files/2312882/

 

For DCS Su-25T: https://www.digitalcombatsimulator.com/en/files/2282430/

 

So, that would be all and hopefully it will be useful to Cougar owners.

Cheers.

 

🙂


Edited by Rudel_chw

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

Perhaps a silly question, but I'm curious if there's a special reason why you'd use the old Foxy software instead of the newer Target (which AFAIK supports Cougar as well)?

i386DX40@42 MHz w/i387 CP, 4 MB RAM (8*512 kB), Trident 8900C 1 MB w/16-bit RAMDAC ISA, Quantum 340 MB UDMA33, SB 16, DOS 6.22 w/QEMM + Win3.11CE, Quickshot 1btn 2axis, Numpad as hat. 2 FPH on a good day, 1 FPH avg.

 

DISCLAIMER: My posts are still absolutely useless. Just finding excuses not to learn the F-14 (HB's Swansong?).

 

Annoyed by my posts? Please consider donating. Once the target sum is reached, I'll be off to somewhere nice I promise not to post from. I'd buy that for a dollar!

Link to post
Share on other sites
Perhaps a silly question, but I'm curious if there's a special reason why you'd use the old Foxy software instead of the newer Target (which AFAIK supports Cougar as well)?

 

Agreed, I would definitely use TARGET.

It is a different beast all together from Foxy so has a bit of a learning curve, but still a very powerful program.

 

Actually for me I have gotten where, at least in DCS, I prefer to setup my Warthog in the game controller GUI...

Don B

 

My VKB Gunfighter MK III Pro L Review

EVGA Z390 Dark MB | i9 9900k CPU @ 5.2 GHz | EVGA RTX 3090 FTW3 Ultra | 32 GB G Skill Trident Z 3200 MHz CL14 | Corsair H150i Pro Cooler | Samsung 970 Pro, 970 Evo 1TB m.2 Nvme |VKB GF MK III Pro L Ultimate Grip| Virpil CM3 Throttle |Reverb G2 | 

Link to post
Share on other sites
Perhaps a silly question, but I'm curious if there's a special reason why you'd use the old Foxy software instead of the newer Target (which AFAIK supports Cougar as well)?

 

Not really :)

 

I tried TARGET for a while (when I was trying to use Home Fries' scripts) and found that only a true computer programmer could learn it ... I'd rather spend my time flying on DCS than struggle with programming in TARGET :)

 

Foxy is simple enough that I can usually create a new profile in a few hours, the longest step is creating the Macro file that contains all of the game's commands. Once you have the Macros, creating the profile is short and simple.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites
Not really :)

 

I tried TARGET for a while (when I was trying to use Home Fries' scripts) and found that only a true computer programmer could learn it ... I'd rather spend my time flying on DCS than struggle with programming in TARGET :)

 

Foxy is simple enough that I can usually create a new profile in a few hours, the longest step is creating the Macro file that contains all of the game's commands. Once you have the Macros, creating the profile is short and simple.

 

Well, there is the Target GUI where you define the key commands and then assign them to buttons easily, but unfortunately it lacks all the other features of the Target scripts (e.g. even a tempo function for long presses).

 

Pretty lame of them not to add more functions to it, IMHO, so if Foxy allows you those some of those things with a simpler notation than Target scripts, I fully understand why you'd stick to it.

i386DX40@42 MHz w/i387 CP, 4 MB RAM (8*512 kB), Trident 8900C 1 MB w/16-bit RAMDAC ISA, Quantum 340 MB UDMA33, SB 16, DOS 6.22 w/QEMM + Win3.11CE, Quickshot 1btn 2axis, Numpad as hat. 2 FPH on a good day, 1 FPH avg.

 

DISCLAIMER: My posts are still absolutely useless. Just finding excuses not to learn the F-14 (HB's Swansong?).

 

Annoyed by my posts? Please consider donating. Once the target sum is reached, I'll be off to somewhere nice I promise not to post from. I'd buy that for a dollar!

Link to post
Share on other sites
Agreed, I would definitely use TARGET.

It is a different beast all together from Foxy so has a bit of a learning curve, but still a very powerful program.

 

That's the beauty of Foxy: it's powerful but without being complicated ... and you can do things that are impossible using just the game controller config.

 

Let me show just one example ... on the Su-27 your weapon system have five different modes of operation; using Foxy I can assign all five to a single button (Hat2 UP button) ... that cycles among them; the programming for this is:

 

BTN H2U /T Close_Air_Combat_Vertical_Scan_Mode 
       /T Close_Air_Combat_Bore_Mode 
       /T Close_Air_Combat_HMD_Helmet_Mode 
       /T Longitudinal_Missile_Aiming_Mode 
       /T Beyond_Visual_Range_Mode

For this to work, I have to define these macros on the asociated Macro file, that correspond to the actual keyboard key that DCS uses for each control:

 

Beyond_Visual_Range_Mode = 2
Close_Air_Combat_Vertical_Scan_Mode = 3
Close_Air_Combat_Bore_Mode = 4
Close_Air_Combat_HMD_Helmet_Mode = 5
Longitudinal_Missile_Aiming_Mode = 6 
Air-To-Ground_Mode = 7 

Now, the Cougar has a "shift" button (the S3 button), that allows us to give dual function to every other button of the Cougar; so I can modify the above script to perform another function in adittion to selecting the weapon system's modes, for example to change the radar into Track While Scan Mode the script would look like this:

 

BTN H2U /I Radar_RWS/TWS_Mode_Select
       /O /T Close_Air_Combat_Vertical_Scan_Mode 
          /T Close_Air_Combat_Bore_Mode 
          /T Close_Air_Combat_HMD_Helmet_Mode 
          /T Longitudinal_Missile_Aiming_Mode 
          /T Beyond_Visual_Range_Mode

/I designates the macro that executes if I press H2U together with S3, while /O designates the Macro that executes if i press just H2U

 

I dont want to bore you with more examples, but this should show the power of Foxy along with its simplicity.

 

Cheers!

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

I am still using HOTAS Cougar also and its programmed in Foxy and I still like it, not too difficult to program but is very powerful at the same time. Still serving me well all these years.

No longer active in DCS...

Link to post
Share on other sites
  • 7 months later...

My only problem with the old cougar is every once in a while I get a "device detection error" and the only way I can get it going again is to plug it into the old old old XP machine and set it up there. Than move it back to the Win10 machine. Don't know why it does that but it does!

 

Menessis

Link to post
Share on other sites
My only problem with the old cougar is every once in a while I get a "device detection error" and the only way I can get it going again is to plug it into the old old old XP machine and set it up there. Than move it back to the Win10 machine...

 

Sorry to hear that ... makes me glad of not having yet changed to Windows 10, I'm still using a server variant of Windows 8.1 and it works just perfectly for my needs ... only downside so far is that VoiceAttack is not compatible.

 

My Cougar is still going strong, and I still program it using Foxy :)

Best regards.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites
  • 4 months later...

I have Foxy profiles for all of my modules. Recently I purchased the Harrier and plan on getting the F18. I wanted to start simplifying my HOTAS, and since there are rarely any Foxy profiles available anymore, and I dont want to try TARGET again, or create a fresh profile for the Harrier (Im simply not well versed or good at it) I simply wanted to go into DCS Options and assign HOTAS buttons by simply clearing the currently assigned commands and hitting a button on the HOTAS to assign it, but it does not seen to work, no buttons are recognized? It does recognize the "S3" on the Stick though as a modifier? With the Cougar CCP turned OFF (Not Emulating), why wont DCS recognize switch positions of the HOTAS? Thanks.

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to post
Share on other sites

... I simply wanted to go into DCS Options and assign HOTAS buttons by simply clearing the currently assigned commands and hitting a button on the HOTAS to assign it, but it does not seen to work, no buttons are recognized? It does recognize the "S3" on the Stick though as a modifier? With the Cougar CCP turned OFF (Not Emulating), why wont DCS recognize switch positions of the HOTAS?

 

 

I've just checked on my own DCS 2.5 and with the Cougar placed on DX mode (on CCP shows up a red button "emulation is OFF"), I find that I can directly bind the buttons within DCS, like this:

 

 

QEVATou.jpg

 

 

However, the Cougar's Throttle Microstick cant be seen by DCS on this Mode, as it isnt recognized as an axis nor as a button.

 

 

That's why I prefer to keep using Foxy to program the Hotas as I best see fit, my current setup for the Harrier is this:

 

 

gEFr7OQ.jpg

 

 

I haven't shared it with the community yet because I havent wrote the instructions to use it, but if you want to try it, I could write them and publish it tomorrow.

 

 

Best regards,

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

Interesting,, With Emulation OFF, I was not able to bind a HOTAS button? I wonder if there is something else I need to do? Anyway, I would love to get a hold of anything you can provide me. You dont have to go crazy with instructions, I would be glad to take the Macro and joystick file even in Word format? I will PM you my email address,,, many thanks.

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to post
Share on other sites
Interesting,, With Emulation OFF, I was not able to bind a HOTAS button? I wonder if there is something else I need to do?

 

It`s strange .. I usually run my HOTAS with emulation ON, but today I only turned it OFF, then immediately started DCS and went to the Controls setup to see if I could bind come buttons .. and it just worked ... very strange, perhaps you have loaded some other software that interferes with the joystick ¿?

 

Anyway, I would love to get a hold of anything you can provide me. You dont have to go crazy with instructions, I would be glad to take the Macro and joystick file even in Word format? I will PM you my email address,,, many thanks.

 

I understand, but my Foxy profile has bindings for the snapviews (a feature that I like to use) and for the communication software that my On-line Squadron uses, so I prefer to write a small one page detailing this things, just to be sure that the profile will work for you. I promise to post it no latter than tomorrow.

 

Feel free to modify the profile as you wish, since its a version 1.0 (meaning, I´m still learning the Harrier so I haven't yet reached the best possible button configuration :)

 

Best regards

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

Hi there and thanks for making these profiles. I'm having some noob issues - I'm assuming it's my lack of knowledge which is the main cuplrit...

I'm getting the profile loaded ok - but having problems getting the "basic" function to work.

Eg the F5 profile is loaded and the profile button is green - some of the switches/rotaries work, but the gun doesn't work - ie when the main trigger is half pressed the gun doors don't open and when the trigger is full pressed the gun doesn't fire.

The zoom rotary works, the speed brake/flap swich works etc. Also, the trim hat works, but the pitch trim is in the opposite sense! Ie trim back, nose goes down...

Any ideas? Thanks.


Edited by Joe Lighty
Link to post
Share on other sites

The Cougar profiles are dependent on the keyboard keys binded to each function, I try to stick to the default keys of each module, but sometimes an aircraft changes the keys either due to a DCS update or because the user changes them.

 

I'm right now away from the computer, but will check the F5 and see what keys it is using for the gun and trim, and amend the profile if needed, I dont remember from memory, because I havent flown the F5 on the last several months (I flew mostly the Viggen, the Mirage and the A-10C).

 

Best regards

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites
Thanks for your quick response - please don't waste too much of your time on this - I'm sure I've set something up incorrectly, I doubt it's a problem with your profile!

 

 

It's not a waste of time, as I like to take care of my profiles :) ... I did a quick check (ie, didnt test all of the Hotas functions) and found that the Trimmer does work as well as the gun trigger. Please check your DCS control config and make sure that the Stick commands are binded like this:

 

 

XhhGs2F.jpg

 

 

As you can see on the pic, the Thrustmaster column has not a single bind, thats because the Cougar in emulation mode Works just like a keyboard .. so when you press the trigger lightly, the Cougar will generate a "t" key, and if you press it all the way will generate a space bar keypress :)

 

 

The Trimmer on the F5 is setup so that when you push the Hat forward the aircraft's nose will dip, while if you pull the Hat towards you the nose will raise.

 

 

Hope this will steer you into correcting the problema. Best regards,

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

Just a side note here if it is relevant? In Foxy, make sure you use LOWER CASE letters instead of UPPER CASE,,,, Its been so long for me, that cost me over an hour last night trying to figure out why "C" was not working in my Macro. Thats because "C" in Foxy emulates a key press of "SHFT c", DOH!

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to post
Share on other sites
... You dont have to go crazy with instructions, I would be glad to take the Macro and joystick file even in Word format? I will PM you my email address,,, many thanks.

 

 

Hello,

 

 

Here are the files of my Profile: https://www.digitalcombatsimulator.com/en/files/3154766/

 

 

There are four files, the .TMM is the macro file (in Foxy Format, which is actually just plain text), the .TMJ is the joystick file, the .RTF are the instructions, and the .JPG is a diagram to remember which button does what.

 

 

Feel free to customize it for your own needs, for example if you already have rudder pedals, you may then use the ANT Wheel for something else.

 

 

Best regards

 

 

PD: Regarding the use of the Snapviews, I made a 1 minute video showing its use:

 

 

 

 

To enter a snapview, you push Hat2 on any of four directions and it will turn the snapview on, the headtracking is disabled and you can then use the mouse to click on any control that is on view, to exit the snapview, you press the SAME Hat2 direction again ... this will reactivate the Headtracking and exit snapview. It wont work properly if you press the Hat2 directly onto another direction (like it happened to me after snaping into the Right MFCD :) )


Edited by Rudel_chw

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites

NICE! Thanks,, I will review tonight,,,,

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to post
Share on other sites
  • 2 weeks later...

I just found your foxy page here today.New to DCS,but have been using Foxy for years.I have it installed now.My Question---in trying to update to 4.2 I am able to extract, or drag and drop all update files but the 4.2 exe.

Do I need to uninstall and apply 4.2 before running program?

Thanks

GunslingerII

Link to post
Share on other sites
...

Do I need to uninstall and apply 4.2 before running program?

 

No, the patch files are simply copied over the already installed 4.0 Foxy, like I shown on post https://forums.eagle.ru/showpost.php?p=3019972&postcount=2

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia GTX1070ti - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar - Oculus Rift CV1

Mobile: iPad Pro 12.9" of 256 GB

Link to post
Share on other sites
  • 1 month later...

hey guys, does anyone have this issue where restarting the cougar does not keep the previous manual calibration?

 

every time i restart my computer or disconnect the cougar, i have to open CCP, go to the calibration tab and select "manual calibration".

 

only then it will operate in manual calibration mode.

 

it does not matter what settings i put in the startup options area (user mode, manual calibration, select profile to be loaded and click save)... it always returns to auto calibration on startup.

Link to post
Share on other sites

Sorry, but I never had that issue through many PC builds. I have no idea what would cause that? I suppose if that were me and no one came through with any suggestions, I would re-install

Windows 10 Pro - 64 Bit / GIGABYTE 3866MHz GA-Z170X-Gaming 7 MOBO / Intel i7-6700K 4.0GHz Processor (OC to 4.Eight) / G.SKILL TridentZ Series 32GB DDR4 3200 Ram / Samsung 850 EVO 500GB SATA III SSD / EVGA 2080 Ti FTW3 Hybrid/ Onboard Audio card / Creative Inspire 5.1 Surround Speakers /LG-Ultragear 38" IPS LED Ultrawide HD Monitor / Track IR4 / Saitek Pro Flight Combat Pedals / Virpil HOTAS

 

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...