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:

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:

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

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...

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

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...

Hi, I have of course configured the script within CTS before compiling it and launching it :thumbup: I tried to launch it both from CTS and from the TARGET editor, same results. Could you explain why it would make any difference ? Thanks

Teamspeak is not running and I have cleared all Cougar assignments, to no avail... :cry:

By the way, I tried running a script provided by the TARGET software: just like this profile, when it launches the Cougar Joystick initially disappears from the list of USB controllers then reappears together with the Thrustmaster Combined Virtual Controller...

Right, that would be lovely! Any idea why I have these conflicts showing up in the DCS settings menu?

Hi marcocom. Exactly, that’s what I thought, too. But the values have been properly set to 0 in CTS for the Warthog stick and throttle... If the lack of MFDs is indeed the problem then I guess I just misunderstood the requirements and will be looking for another profile, for I don’t have any use of them in my VR headset :smilewink: Thanks for your reply!

I’ve had the same issue myself, turns out it is mostly related to insufficient lighting and/or obstacles too close to your WMR headset making it too difficult for the built-in cameras to determine their environment. This makes it impossible for the software to choose in which tracking universe to operate (seated, standing, full scale) so it reverts to a safe default 3DOF mode until conditions are met for 6DOF again. Hope this helps :thumbup:

Hi, I have actually had to turn reprojection OFF because of horrible artefacts all over the cockpit making it unusable. Anyone having artefacts with this feature turned on?

Good evening everyone and big thanks to Home Fries for your amazing work! I am coming back to combat sims after a ten year pause, a lot of things have changed for me since Lockon, the only thing that hasn't is my venerable HOTAS Cougar :-) Here are the steps I've been going through so far to get things working: - buy a new gaming PC and install windows 10 pro 64bits - install Cougar VISTA drivers the proper way - install latest TARGET software, do a manual calibration and check all is working fine - install DCS World 2.5.0 release version and add FC3 module The next step was finding the best HOTAS profile available and that's when I found this one ;-) I have tried to the best of my abilities to follow the setup guide step by step and taking all the time needed to choose the right options for the script but unfortunately I am facing an issue where DCS is seing multiple conflicts in the commands assignments... here are a few screenshots to illustrate and maybe help me find what I am doing wrong? Concering CTS and the screenshots, I would like to add the following: - I installed the optional custom LUAs for DCS World Main Install using OvGME (only for FC3) - I installed custom snapviews - within DCS World I have only added modifiers to the Su-33 which is the aircraft I am using for testing - I did load the keyboard and cougar profiles from within the DCS World controls menu - I do not own the Cougar MFDs nor did I install their drivers - vJoy as a device refers to a virtual joystick program needed by another sim I am using (iRacing and the irFFB utility) Other than the red lines appearing everywhere, I also noticed the following: - the HOTAS Cougar stays visible along with the Thrustmaster Virtual Game controller in the Windows USB menu whilst the TARGET script is running... isn't it supposed to be deactivated by TARGET to avoid conflicts? - the script reports USB HID devices not found when launching By the way, how is the arrestor hook deployed with this profile for the Su-33?? I couldn't find it... Any help appreciated! [ATTACH]186878[/ATTACH]