Jump to content

Thrustmaster Cougar FOXY Profile


Recommended Posts

I have something similar

 

MIY 3 Throttle_Designator_Controller-Right ^ Throttle_Designator_Controller-Left

/I 6 23 (2 4 6 8 11 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98 ) MSX(3-) MSX(3+) MSX(0)

MIX 3 Throttle_Designator_Controller-Down ^ Throttle_Designator_Controller-Up

/I 6 23 (2 4 6 8 11 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98 ) MSY(3-) MSY(3+) MSY(0)

 

But i have to admid that this part i copy/pasted from someone else's profile and used it in mine where i need the microstick.

I have been reading through the MIX/Y help file a few times but after a few paragraphs i'm lost so in the end i just copied a working microstick part into my profiles.

The /I statement makes the microstick move faster when needed.

 

Actually, Foxy uses the S3 button as a standard modifier, that allows you to have a statement like:

 

BTN S1 /I {key generated if you press S1 while pressing S3}
   /O {key generated if S1 is pressed alone}

So I believe that, on your previous statement, the /O is missing .. it should be like this:

 

MIY /I 6 23 (2 4 6 8 11 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSX(3-) MSX(3+) MSX(0)
  /O 3 Throttle_Designator_Controller-Right ^ Throttle_Designator_Controller-Left
MIX /I 6 23 (2 4 6 8 11 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98) MSY(3-) MSY(3+) MSY(0)
  /O 3 Throttle_Designator_Controller-Down ^ Throttle_Designator_Controller-Up

 

 

What these statements are doing is creating a Digital Axis based on the analog axis of the microstick. Foxy has several types of digital axes ... your programming is using axes type 6 when you hold S3 as you operate the microstick, and axis type 3 when moving the microstick without holding S3 down.

 

A type 3 axis produces three keys: one when the axis value is low, another when the axis is in the middle, and a third when the axis value is high ...on your example the keys produced are TDC_right, null (^), TDC_Left ... the null is used because you dont want to generate keys when the microstick is in the center position.

 

I dont like to use type 3 because the center position is too small and thus any small movement of the microstick will generate TDC keys ... you can replace it with a type 5 axis, that will allow to specify exactly how you want the stick travel to be asigned, like this:

 

MIX 5 3 (0 40 60 100) (/H Throttle_Designator_Controller-Left ) ^ (/H Throttle_Designator_Controller-Right )

 

 

it divides the microstick range on three zones: 0-40% 40-60% and 60-100%

 

The type 6 axis on your sample is meant to use the microstick to move the Mouse, by manipulating the system variables MSX and MSY:

 

MIY 6 23 (2 4 6 8 11 14 17 21 25 30 36 43 58 65 71 76 80 84 87 90 93 95 97 98 ) MSX(3-) MSX(3+) MSX(0)

 

this statement divides the axis range on 23 equal parts, the first 11 parts will decrement the Mouse X position by 3 pixels, the 12th part will not move the mouse (0 pixels), while the remaining 11 parts will increase the Mouse X position by 3 pixels.

 

In my opinion, the 23 parts is just arbitrary and you can get the same effect with a type 5 axis and just three regions, giving better control over the central position of the stick (so as to not move the mouse involuntarily).

 

All this is explained with a lot of examples on the "Cougar Syntax.doc" document that is on the Foxy folder, it looks hard but it actually isnt ... as the elements of the Syntax are few and more akin to a macro language than a programming language.

 

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 3600X - 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 comment
Share on other sites

Been doing some tests between your mircostick setup and mine (i Rem out the /I part).

I don't really see any difference in game between yours (type 5) and mine (type 3) regarding movement. To me both react the same.

Probably because there's always the same character generated to move the Target Designator. I don't see any difference around center.

 

When it comes down to generating more different characters around the travelrange of the axis it might make a difference.


Edited by Lange_666

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

Good news! I got HOTAS CCP to work! I think it is was because I had my stick plugged into a USB 3.0 port and not a 2.0 port.

Regardless, the CCP is up and running. I have tried unsuccessfully to attach screen shots, can someone give me a hand? Once that is done I can accurately ask some more questions! Excited to get this far!

I have been at work for two days, sorry for the late response!

Link to comment
Share on other sites

Good news! I got HOTAS CCP to work! I think it is was because I had my stick plugged into a USB 3.0 port and not a 2.0 port.

 

 

I'm glad that you got it working, tough I doubt that the USB 3.0 may be the cause, since my own Cougar is connected to an USB 3.0 port and works fine ... but in the end the important thing is that you got it working :)

 

 

I have tried unsuccessfully to attach screen shots, can someone give me a hand?

 

 

Create an account at https://imgur.com/ ... there you can upload images, once uploaded you can use the option "copy direct link" to copy the image link to a post within DCS Forum, like this:

 

 

RaNzAsx.jpg

 

 

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 3600X - 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 comment
Share on other sites

Or the BBCode (message boards and forums) link, it includes the image tags.

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

Xhd2ol6.jpg

 

 

Hello! Here is what I have at the moment. It needs help. I am using Saitek rudder pedals, HOTAS/TQS. At this moment the range knob works in DCS from the config menu. Why is that? Where do I need to put the "+"'s to get the ANT and micro stick recognized in DCS?

Thanks again for the help! Cheers to you sir!

NbHkbAj.jpg


Edited by GreatWhiteHype
Beer can was too large :-)
Link to comment
Share on other sites

Xhd2ol6.jpg

Where do I need to put the "+"'s to get the ANT and micro stick recognized in DCS?

 

You have the "+" just like mine, and my DCS can see all the 7 axes of the Stick + Throttle, like this:

 

pjKpYlD.jpg

 

The ANT knob is identified as JOY_RX by DCS, and the Microstick axes are JOY_RZ and JOY_SLIDER2 ... it is possible that DCS isnt able to autodetect the axis when you move the control, but you can assign it manually anyway and then use the "Axis Tune" option to adjust it a bit.

 

My microstick isnt in good shape, so I usually dont use it as an axis on DCS, but prefer to use Foxy so that the microstick generates keystrokes instead.

 

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 3600X - 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 comment
Share on other sites

Okay. I am making progress. I have my ANT working and my Ranger Knob working. I am not getting an indicator for my Joy_slider2 and Joy_RZ, they are not an option to manually assign. I am not finding a way to confirm my microstick works inside the foxy program to be more precise. smile.gif Please advise!


Edited by GreatWhiteHype
Link to comment
Share on other sites

I am not getting an indicator for my Joy_slider2 and Joy_RZ, they are not an option to manually assign. I am not finding a way to confirm my microstick works inside the foxy program to be more precise. smile.gif Please advise!

 

 

Use the Viewer (on the Cougar Control Panel) to check if the microstick is in fact working, like this:

 

 

2U3SOVR.jpg

 

 

The microstick axes are ZR and S2 ... they should change value when you move the microstick.

 

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 3600X - 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 comment
Share on other sites

Houston, we have a problem..... Zero response from the microstick. It appears to be dead. Button 19 works no problem. Not sure I want to take it apart for just that, I have looked at your videos. I don't want to break a great throttle for something I can live without.

 

 

Mine still works, but the microstick axis dont produce the full range of values, so I contacted Guillemot and purchased a new Microstick for 29 Euros including shipping to my country.

 

 

I do use the microstick, usually to control the radar cursor or the TV cursor, so I prefer to try to repair it :) ... when I get the part, will report how hard is the installation .. it seems involved, as the microstick has to be unsoldered from a small PCB board and the new one has to be soldered on its place.

 

 

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 3600X - 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 comment
Share on other sites

This thread motivated me to improve a bit on my F/A-18 profile, so I've just updated it to version 2.0 with smoother airbrake operation and uses the Dogfight Switch to toggle the AA and AG Master Modes. The new version can be downloaded from ED's Users Files section:

 

 

https://www.digitalcombatsimulator.com/en/files/3301292/

 

 

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 3600X - 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 comment
Share on other sites

The Dogfight Switch to toggle AA or AG modes is great but you can do a bit more with it and free up your Hat 2 for something else.

 

 

Like:

 

If Dogfight Switch is in the up position, set the weapons system into AA-mode.

Then use S2 as a weapons selector and step through the AA weapons each time you press it (free's up your H2).

If you press it together with S3 it then releases that selected AA weapon.

 

 

If the Dogfight Switch is in the down position, set the weapons system to AG mode.

Then again use S2 as a weapons selector and step through the AG weapons each time you press it.

If you press it together with S3 it then releases that selected AG weapon.

 

 

 

If Dogfight Switch is in the middle, deselect any weapon mode and turn back into NAV mode.

If you want, you can use again the S2 for example to cycle through the waypoints (and with S3 cycle through them backwards).

 

 

 

 

 

Just an idea...

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

Lange 666, what are you using for the 3 positions of the flaps? Thanks

Windows 10 Pro - 64 Bit / ASUS ROG Strix B650E-F Gaming / AMD 7800X3D / G.Skill Trident Z5 NEO 64GB DDR5 6000 Ram / SSD M.2 SK hynix Platinum P41 2TB / MSI Gaming GeForce RTX 4090 SUPRIM Liquid X 24G / SteelSeries Arctis 7 Headset /LG-Ultragear 38" IPS LED Ultrawide HD Monitor (3840 x 1600) / Track IR4 / Thrustmaster TPR Pendular Rudder Pedals / Virpil HOTAS VPC Constellation ALPHA-R & VPC MongoosT-50CM3 Throttle

 

Link to comment
Share on other sites

The Dogfight Switch to toggle AA or AG modes is great but you can do a bit more with it and free up your Hat 2 for something else....

 

Just an idea...

 

:) I understand your idea ... but while I do try to keep some functions the same on every aircraft (like the Comms on the Throttle Hat, the Flaps & Speedbrake on the Speedbrake switch, the Snapviews on the Hat1 (shifted with S3) and the Kneeboard on Hat4 (shifted also)) ...

 

... I also want to resemble the Hotas of the real aircraft, so thats why I use the Hat2 for Weapons Select and Hat3 for Sensor Control and the Microstick as Radar Designator

 

Also, I've found that a profile with too many functions assigned to each Hat position is really hard to memorize, thats why I'm shy to use the Dog Fight Switch to multiply the amount of functions on each button and prefer instead to use it as a simple three way switch ... on this case as Mode Selector.

 

Anyway, the zip includes every file that Foxy needs in case you want to customize it to your preference, even the layout schematic is there :)

 

Best regards,

 

 

 

 

Eduardo

 

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 3600X - 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 comment
Share on other sites

Lange 666, what are you using for the 3 positions of the flaps? Thanks

 

On all my profiles i use the H3 Hat up/down for flaps together with the S3 button (so the /I).

So:

BTN H3U /I Flaps_Up

---------/O Other_function

-----H3D /I Flaps_Down

---------/O Other_function

-----H3L /I Toggle_Gear

---------/O Other_function

 

If the flaps are in position level, one press on H3D (together with S3) puts them in "Half", another press in "Full". Same going up with H3U...:joystick:


Edited by Lange_666

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

Great news! I used the manual calibration on the HOTAS CCP and my MicroStick works. It will needs some fine tuning but it works!!! SO happy right now!

 

I'm glad for you :) .. I tried it on my case and it didnt fix my problem (limited travel of one of the MS axes).

 

Lange 666, what are you using for the 3 positions of the flaps? Thanks

 

On the latest version of my Profile, I'm using the throttle's T9 button, with a Toggle trough all the Flap Switch positions, that goes in sequence down and up over the three positions of this Switch:

 

BTN T9  /I   Landing_Gear_Control_Handle-UP/DOWN 
           /O /T FLAP_Switch-HALF 
                /T FLAP_Switch-FULL 
               /T FLAP_Switch-HALF 
               /T FLAP_Switch-AUTO 

OrPP4Jp.jpg

 

Also, the Speedbrake was giving me trouble since DCS' key command opened the airbrake just a bit, forcing me to use multiple keystrokes ... I finally choose to bind the button within DCS and then use it from Foxy using it as a DirectX button, like this:

 

Cxk1OIm.jpg

 

BTN  T10  /P /H DX25
                /R Speed_Brake_Switch-RETRACT 

It works much better this way.

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 3600X - 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 comment
Share on other sites

  • 2 weeks later...
I will follow your progress Rudel, I would like to use it again at some point...

 

Hello,

 

In the Mail today arrived the package from Guillemot, France:

 

wzIRxj9.jpg

 

and these are my new spares:

 

FgMePjz.jpg

 

I will try to install the microstick this week-end, the Throttle pot will be stored as spare, since the current one is still working fine :)

 

Will keep you updated on how hard the install turns out to be.

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 3600X - 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 comment
Share on other sites

.. Will keep you updated on how hard the install turns out to be.

 

Today I disassembled my Cougar, this is the inside of the Microstick mounting:

 

5sPholj.jpg

 

I tried not to take apart more than necessary, so the cables remained connected, just removed the microstick PCB:

 

jUWZ7jo.jpg

 

The fit of the Hotas is superb, in spite of it being 16 years old, the insides are very clean and dust-free :D

 

I asked an electronics friend to desolder the microstick from the mini-board, the blue stick "sucks" the molten solder leaving the connection clean:

 

NPMQjZW.jpg

 

Unfortunately, and in spite that my friend was really careful, one of the printed lines on the board got damaged, so he replaced part of it with a small wire .. that he is preparing on this photo:

 

8EDIbQu.jpg

 

here you can see the "fix", the new microstick on the right and the old on the left ... the curved wire is replacing the broken line.

 

tMmLS8z.jpg

 

Now I've assembled back the throttle, and I'm real happy because everything is now working as it should, the new Microstick works perfectly, tough I had to re-calibrate the Cougar in order to get the full travel on the axes.

 

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 3600X - 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 comment
Share on other sites

  • 3 weeks later...

... How do I reduce the sensitivity of the mircostick within the DCS controls? I use the MS to lock up radar targets and for CCRP but the target diamond moves so fast...

 

Hello,

 

Actually, I dont program my microstick within DCS ... I do so trough the Cougar's Foxy programming utility.

 

In Foxy, I use these statements with the Microstick:

 

1) This RATE statement is for reducing the speed of character generation, to once every 90 ms, making the control a bit slower:

 

USE RATE(90)

 

 

 

2) And the next statements program the microstick for dual use: Radar/EP13 cursor movement; and Rb-05 missile control if used while S3 is pressed:

 

Rem -----------------------------------------------------------

Rem Microjoystick: Radar/EP13 Cursor & Rb05 Control (shifted)

Rem -----------------------------------------------------------

MIX /I 5 3 (0 30 70 100) (/H Rb05_stick_yaw_left) ^ (/H Rb05_stick_yaw_right)

/O 5 3 (0 30 70 100) (/H Radarstick_Left) ^ (/H Radarstick_Right)

MIY /I 5 3 (0 30 70 100) (/H Rb05_stick_pitch_down) ^ (/H Rb05_stick_pitch_up)

/O 5 3 (0 30 70 100) (/H Radarstick_Down) ^ (/H Radarstick_Up)

 

 

 

I have divided each axis in three zones of travel:

 

0-30% = Left or Down

30-70% = no action (to prevent inadvertent movement while centered)

70-100% = Right or Up

 

Used this way it works well, tough I did draw with a marker, two lines over my microstick handle, to better grasp which way is up or left :)

 

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 3600X - 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 comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...