DCS World TARGET profile for TM Cougar and Warthog + MFDs

[flightmedicFP-C]

So I read the install instructions and believe that I am following them explicitly. However I am not getting the scripts that are made in the CTS to show up anywhere I have looked, to be able to transfer them to DCS via the load function. Am I missing something or need to be doing something different? Like I said, I've read the instructions completely, installed the CTS and produced the scripts for the models that I selected, but cannot find them when I try to load them into DCS. Frustrating!! lol please help!!

[Home Fries]

So I read the install instructions and believe that I am following them explicitly. However I am not getting the scripts that are made in the CTS to show up anywhere I have looked, to be able to transfer them to DCS via the load function. Am I missing something or need to be doing something different? Like I said, I've read the instructions completely, installed the CTS and produced the scripts for the models that I selected, but cannot find them when I try to load them into DCS. Frustrating!! lol please help!!

 

Assuming I'm reading your issue correctly, you have been able to load the profile in TARGET, but haven't been able to load the diff.luas into DCS World. The trick to this is to find the folder titled "_for Saved Games_DCS" and then import the diff.luas in these folders to apply the settings to your aircraft.

[flyingflatfour]

Good evening,

 

 

Please forgive me but I am desperately trying to find some help with the following issue. :helpsmilie:

 

 

 

As explained a couple of months ago I am trying to get CTS working with TARGET and my HOTAS Cougar, no joy so far...

 

 

I have now determined that the main issue is not related to CTS or DCS, but with TARGET and Windows 10.

 

 

 

No matter what script I try to run, TARGET is unable to deactivate the Cougar when it creates the combined virtual game controller.

 

 

Together with this the virtual game controller doesn't reflect any axis movement or button presses from the Cougar...

 

 

No wonder I couldn't get the script running with DCS :lol::doh:

 

 

Attached is a screenshot when running an basic empty script made in TARGET with just the Cougar added to it.

 

 

Just to clarify, I am running VISTA Cougar drivers and latest TARGET version and tried with with administrator privileges and in Vista compatibilty mode but it doesn't change anything :cry:

 

 

 

 

 

Any help appreciated...

[Home Fries]

I still use Windows 7, so I've heard of this issue but have no idea how to fix it.

 

If somebody who has troubleshot this issue could please speak up, I will put the solution in my Setup Guide with proper credit attributed.

[flightmedicFP-C]

Well I haven't managed to get the scripts to even load into TARGET and or the DCS folder. So any ideas on why the scripts aren't loading into TARGET? I think after I get them to do that then I can fumble my way through the rest of it. But what I have managed to accomplish is the following:

 

Install CTS and read the PDF

Run CTS and Create the scripts for the Aircraft I own

 

after this..... I have had no luck thus far.

[The_Nephilim]

Good evening,

 

 

Please forgive me but I am desperately trying to find some help with the following issue. :helpsmilie:

 

 

 

As explained a couple of months ago I am trying to get CTS working with TARGET and my HOTAS Cougar, no joy so far...

 

 

I have now determined that the main issue is not related to CTS or DCS, but with TARGET and Windows 10.

 

 

 

No matter what script I try to run, TARGET is unable to deactivate the Cougar when it creates the combined virtual game controller.

 

 

Together with this the virtual game controller doesn't reflect any axis movement or button presses from the Cougar...

 

 

No wonder I couldn't get the script running with DCS :lol::doh:

 

 

Attached is a screenshot when running an basic empty script made in TARGET with just the Cougar added to it.

 

 

Just to clarify, I am running VISTA Cougar drivers and latest TARGET version and tried with with administrator privileges and in Vista compatibilty mode but it doesn't change anything :cry:

 

 

 

 

 

Any help appreciated...

 

 

 

So you are trying to run CTS with the Cougar Profile. So what you are saying is when you normally try to run the Profile in CTS what exactly happens?? Do you get an error message in the script??

 

 

I think you are saying the HOTAS does not work the button presses?? I am not exactly sure what your problem is as I did not see the other posts from months ago..

[flyingflatfour]

I think you are saying the HOTAS does not work the button presses?? I am not exactly sure what your problem is as I did not see the other posts from months ago..

 

 

https://forums.eagle.ru/showpost.php?p=3521905&postcount=771

[The_Nephilim]

https://forums.eagle.ru/showpost.php?p=3521905&postcount=771

 

 

 

I see you Have added the Modifiers.... we would need to get on Voice Comms to walk you through it vs trying to message you what to do..

 

 

Also with Windows 10 I noticed they add drivers and such from a windows update. If you would like to meet up on TS or something sometime let me know..

 

 

I usually use SimHQ TS3 Server are you a member there maybe you can joing Simhq and we can meet up on TS3 there some night..

Edited October 30, 2018 by The_Nephilim

[The_Nephilim]

I think the vJoy application might be the root of your Problem.. Is there any way you can uninstall or remove that vJoy and try reloading HomeFries Profile??

[flyingflatfour]

I think the vJoy application might be the root of your Problem.. Is there any way you can uninstall or remove that vJoy and try reloading HomeFries Profile??

 

I have vJoy deactivated, it does’t appear in the list of controllers or in DCS anymore, yet TARGET still can’t deactivate the Cougar to integrate it in the virtual device...

[flyingflatfour]

I see you Have added the Modifiers.... we would need to get on Voice Comms to walk you through it vs trying to message you what to do..

 

 

Also with Windows 10 I noticed they add drivers and such from a windows update. If you would like to meet up on TS or something sometime let me know..

 

 

I usually use SimHQ TS3 Server are you a member there maybe you can joing Simhq and we can meet up on TS3 there some night..

 

That’s a great idea, I use Teamspeak too, let’s discuss details in PM :thumbup:

[Home Fries]

Well I haven't managed to get the scripts to even load into TARGET and or the DCS folder. So any ideas on why the scripts aren't loading into TARGET? I think after I get them to do that then I can fumble my way through the rest of it. But what I have managed to accomplish is the following:

 

Install CTS and read the PDF

Run CTS and Create the scripts for the Aircraft I own

 

after this..... I have had no luck thus far.

 

Ok, I need more information to properly troubleshoot the issue.

 

Specifically:

• Do you use a Cougar or Warthog? Do you have the hardware properly selected in CTS?
  
• Where are you not having luck? Is it in running the script after compiling it within CTS?
  
• If it is an error running the script, what does the text on the TARGET screen say?
  

[Mayer]

Hello Home Fries,

 

I'm using the latest version of CTS with DCS openbeta.

I've the Hotas Warthog with the throttle.

 

I'm trying to use the autopilot.... normally it's configured withe the dedicated button on the Throttle:

Autopilot Engage/disengage

and PATH - ALT/HDG - ALT switch.

 

First strange behavior:

in order to activate the autipilot I need to press the Shit button (/I) + Engage/DisEngage Button

 

Second behavior: PATH - ALT/HDG - ALT switch in not working.

 

could you please tell if I've understood something wrong ?

 

thx.

 

PS: I would like to thanks you for your amazing works which I use everyday.... is there a way to donate for your work?

[Mayer]

Use the RBRT rocker for HUD brightness. Sorry for the delay; long week.

 

 

In other news, Version 2.25a is out. 2.25a adds some Huey features, specifically:

• Added functionality to Warthog throttle base
  
• For left analog throttle users, setting throttle to idle will hold PGUP to take the throttle out of stop
  

 

Yes I'm using the RBRT, but it doesn't change the brightness. just above the RBRT, there is the HUD color change and It's working.

[Home Fries]

Hello Home Fries,

 

I'm using the latest version of CTS with DCS openbeta.

I've the Hotas Warthog with the throttle.

 

I'm trying to use the autopilot.... normally it's configured withe the dedicated button on the Throttle:

Autopilot Engage/disengage

and PATH - ALT/HDG - ALT switch.

 

First strange behavior:

in order to activate the autipilot I need to press the Shit button (/I) + Engage/DisEngage Button

 

Second behavior: PATH - ALT/HDG - ALT switch in not working.

 

could you please tell if I've understood something wrong ?

 

thx.

Are you referring to the A-10C or the F-15 (which was your previous question)? The autopilot switch works differently for the different modules, so I need to know the module to which you refer.

 

Also, in response to the HUD brightness, I have verified that the keystrokes are mapped properly in the F-15. If they don't change the HUD brightness, that's an ED issue.

PS: I would like to thanks you for your amazing works which I use everyday.... is there a way to donate for your work?

 

If there's a particular module or piece of gear you would like me to support, I take contributions to that end (PM me if this is the case). Otherwise, please send any contributions to Fisher House, a charitable organization that helps wounded veterans and their families.

 

Best,

HF

Edited November 4, 2018 by Home Fries

[flyingflatfour]

Hi everyone,

 

 

So I've just spent some time with The_Nephilim trying to sort out my problems.

 

 

We're not there yet, but progress has been made. Bug thanks to him :thumbup:.

 

 

 

 

After reinstalling properly the Cougar drivers, the latest Target and CTS software, here is where we stand:

 

 

- The CTS script executes itself properly in TARGET

 

- TARGET is still unable to disable the HOTAS Cougar Joystick

- The Thrustmaster Virtual Game Controller shows up but doesn't respond to joystick inputs. Actually, we succeeded in getting this to work once but now it's broken again...

- There are still all sorts of conflicts in the DCS controls menu

 

 

 

 

So there is progress in the sense that now at least the script seems to be properly running.

 

 

What puzzles me is why TARGET still can't deactivate the HOTAS Cougar and why the virtual device doesn't respond.

 

 

The_Nephilim is wondering if there might be a clue in the name "Thrustmaster Virtual Game Controller (root)", since it should normally be "Thrustmaster Combined" or something like that instead...

 

 

Concering the conflicts within DCS, I can confirm that we have:

 

 

- cleared out all assignments to the HOTAS Cougar still showing up

- loaded up the .lua files for the keyboard to the keyboard column and for the hotas to the Thrustmaster Virtual Game Controller (root).

- added the three modifiers 30,31,32 as shown on the screenshot.

 

 

 

 

Any idea on how to take it on from here? :joystick:

[The_Nephilim]

Hey ,

 

 

I found out that if you run the CTS as Admin you will get the Root to show up. so are you running the CTS as an admin??

EDIT: I just tried running as admin it did not change mine to Root?? I think that is not the problem something else is causing the red lines in DCS.. I read through the quick start guide it mentioned when this happens with the Harrier to do certain steps but we where using the F5??

 

This should not matter from what HomeFries said.. If you look at page 17,18 in the Quick start guide you will see this mentioned about the Root device..

 

 

Where is the joystick not responding to inputs?? in the CCP?? Can you try and load a different profile in CTS and in DCS like the Su-25t??

Edited November 4, 2018 by The_Nephilim

[flyingflatfour]

Hi,

 

 

I am not running CTS as an admin...

 

 

I went to pages 17,18 of the manual and indeed it says it can be named like that, so that's not the issue it seems..

 

 

As you can see on the screenshot the joystick is responding fine in the CCP but not in the properties of the Thrustmaster Virtual Game Controller (root)... do you remember how we got that to work?

 

 

Concerning the conflicts in the DCS menu, I think we are getting there. It has to do with the modifiers. The manual says to leave the name of the modifiers untouched.

 

 

But as you can see on the screenshot, the name they have in my DCS are not the same as the one in the manual. The have an extra "Touche-" in front of them... So I changed them to match and bingo, almost all conflicts have disappeared! I guess this has something to do with using french versions of Windows and DCS....

 

 

I believe if we can get that Thrustmaster Virtual Device to work properly things should be good :thumbup:

[The_Nephilim]

If you start the Profile in CTS and run device analyzer does it work in there?? Better yet go into DCS Contorls page under options and test to see if the buttons work in there.. if they do it should work ingame..

Edited November 4, 2018 by The_Nephilim

[flyingflatfour]

Hi!

 

 

For some reason I can't explain the TM Virtual Game Controller is now working properly all of a sudden... :doh:

 

 

All buttons and axes are therefore properly showing up in DCS.

 

 

So you might think hurray this is it! :lol:

 

 

 

 

Unfortunately it seems like the bindings aren't doing what they should be doing according to the F-5E layout ... :cry:

 

 

I will be looking deeper into this and will report back with a few examples so we can try to understand what's going on :joystick:

[Home Fries]

Hi!

 

 

For some reason I can't explain the TM Virtual Game Controller is now working properly all of a sudden... :doh:

 

 

All buttons and axes are therefore properly showing up in DCS.

 

 

So you might think hurray this is it! :lol:

 

 

 

 

Unfortunately it seems like the bindings aren't doing what they should be doing according to the F-5E layout ... :cry:

 

 

I will be looking deeper into this and will report back with a few examples so we can try to understand what's going on :joystick:

 

The Warthog Joystick and throttle not being suppressed when the TARGET virtual controller is enabled is something with Windows 10. I'm hoping you guys can figure that out and report a repeatable workaround.

 

I spoke with Nephilim the other night; just so you know, the Thrustmaster Virtual Game Controller (Root) isn't an issue at all. Rather, it's what the TARGET controller is called when you run with admin privileges. Thrustmaster Combined is the name of the virtual controller when run with user privileges.

[Home Fries]

Hotfix 2.25b is up. This hotfix addresses incorrect A-10A keyboard and joystick mapping with the HOTAS Warthog.

[The_Nephilim]

The Warthog Joystick and throttle not being suppressed when the TARGET virtual controller is enabled is something with Windows 10. I'm hoping you guys can figure that out and report a repeatable workaround.

 

I spoke with Nephilim the other night; just so you know, the Thrustmaster Virtual Game Controller (Root) isn't an issue at all. Rather, it's what the TARGET controller is called when you run with admin privileges. Thrustmaster Combined is the name of the virtual controller when run with user privileges.

 

 

 

Well that is the thing HomeFires he is not running it as an admin?? but if it is ok to be like that we will try and figure out the win 10 thing??

 

 

I just don't understand why it works for me and not for him as I am on Win 10 too.. I have it happen sometimes the Hotas controller does not get surpressed I usually reboot or rerun the CTS and voila it works as it should.. But most times it just works..

[Rangoon]

Today I updated my Warthog joystick firmware from v11 to v12, uninstalled old drivers and TARGET, installed the latest version of both. I also updated to CTS 2.25b. For some reason, now when I activate my profile (Warthog HOTAS+2xMFDs), device analyzer will not enumerate more than one device (and it's not a thrustmaster device). In USB controller list "Game Controllers" I see 5 or 6 devices including the Thrustmaster virtual device. However, when I run the device analyzer from the active script window under "Tools", I am only seeing a single, unrelated device. I run "Enumerate Devices" but nothing new shows up.

 

At first, after the TARGET update, I was seeing in DCS that my X/Y joystick axes were not registering. After this, I ran the uninstall/reinstall update process again, confirmed that I could see the joystick and other devices working individually in Windows. I ran the TM calibration utilities, then ran a test script. Now sometimes I could see a few devices in the device analyzer, but not all...it became seemingly unstable/unpredictable. Whenever I run the script from CTS, it goes down to just one (not Thrustmaster) device and nothing else populates. I used to always be able to test my combined HOTAS script in the analyzer, including after running CTS, before launching DCS.

 

Has anyone else seen odd behavior with the latest TARGET version? Right now I'm stumped.

[Rangoon]

I'm basically giving up on the Device Analyzer. It seems totally broken now, presumably with the driver/TARGET updates, maybe something new in Windows 10, not sure. I'm at least able to get things working consistently. I changed around the ports I'm using, maybe that helped. So the controllers are working, and registering in Windows fine. CTS is working great. DCS sees everything as it should. Whatever my issue was clearly has nothing to do with CTS.

 

I do still get the problem after some sessions where I can't load the script again without some TM devices staying in the Game Controllers list. I get the virtual controller, but also still see MFD, Joystick, and/or Throttle populating the list. System restart is the only reliable solution I've come across.