Ant0ine

You have to map Track IR Z axis to moving head forward/back instead of zoom.

You are excluding your joystick from the script so I guess it won't work. Remove "Configure(&Joystick, MODE_EXCLUDED);" at line 5. I advise you to add a line for all the device and simply comment with two slash // the line of the device you want to include. So in your case it would be : Not a must, be cleaner, you won't see this kind of stuff in your log : The rest looks good to me. Btw, are you johntarr on the Hotas Discord? Hon0 here :v:

Hello, can't tell for the X52 PRO. But my dad just got the X56 to remplace his 52PRO and I took the ocasion to initiate him to Vjoy+Joystick_Gremlin. So he isn't using the Logitech profiler at all, or, rather, he use the default profile which simply report a DX buttons for all physical button. Pinky is DX 6 as well. And even if we use Gremlin he still added the pinky as modifier, using the DCS modifier tool, it works. If Joy.cpl (the windows game controller panel) see DX 6 when you press your pinkie button, then DCS should see that as well. If not there is something weird, maybe another profile is automatically loaded when you launch DCS? Dunno. Same deal for the 3 positions of the mod selector.

Isn't it the LowRes 8w we want in this case? Apparently is quite a new option? https://forum.il2sturmovik.ru/topic/970-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%BC%D0%B8%D1%80%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B5-%D0%B4%D0%B6%D0%BE%D0%B9%D1%81%D1%82%D0%B8%D0%BA%D0%BE%D0%B2-%D0%BE%D1%82-vkb/?do=findComment&comment=759811 Alex made the change just after he responded in this topic, asking for the same thing. https://forums.eagle.ru/showthread.php?t=265831 Edit : My bad, the goal here is to ensure we hit main direction, not diagonal as in the other post. Well for that we could increase deadzone. Not sure if the most recent added something to help hit the main direction. Afaik it help to help diagonal without first hitting main direction.

? https://github.com/BurnyBurns/controller_maps/tree/master/maps/ch_products

It is to make sure our physical toggle switch is always synchronized with the virtual toggle switch. Like physical down position is "Gear Down" and physical up position is "Gear Up". If we don't use Target or a similar program nor edit lua file then all we can do is use DCS "Gear Toggle" on the up position, in that case to drop the gear you have to flip the switch up, and to raise the gear you have to flip it down, which will do nothing, and up again. That sucks, and that is why we want each position of the switch to send a signal to the PC. And we prefer to use dedicated "Gear Up" and "Gear Down" command for exemple to make sure the physical and virtual switch remain in sync. Cause for exemple I could flip the switch down to drop the gear. But then if I press G or click in the cockpit or flip the switch when DCS doesn't have focus or something like that, then it would desynchronize the switch if we mapped the "Gear toggle" on both physical position of the switch. Using dedicated command the switch could still be desync, but the next time we'll use the switch it would do nothing because gear is already up, or down.

To do that you'll have to use Thrustmaster Target (Or another similar program). Because by default only the ON position active a button.

It's like my post is invisible. ¯\_(ツ)_/¯ You can NOT calibrate in Target, nor in DCS. To calibrate the Warthog throttle and joystick you need tool provided by TM that I saved in my DropBox and shared in my previous post. Yes they come calibrated. You shouldn't have to calibrate except maybe after you have disassembled and disconnected/reconnected some board in the throttle or joystick. I sure had to calibrate my joystick after I did . And also after I changed a friction pad in my throttle and so had to disconnect the main board. I also have to calibrate my throttle depending if I want to use the vanilla detent piece that come with the throttle, or a no detent mod that I use when I fly machine that doesn't require any detent. This way I can profit of a larger throw and so more accuracy.

Uhm that post might help you. I tweaked mine so that in diagonal I could easily/reliably trigger two button. What I couldn't do, and I think it can't be done, is to tweak our hat so that we can hit diagonal directly, on a hat set a POV. https://forums.eagle.ru/showthread.php?t=247988 Edit : To illustrate what I mean. http://forum.vkb-sim.pro/viewtopic.php?p=37236#p37236

Neither, here are the tool you need to calibratre your Warthog Hotas, remove/reset any calibration you've done in Windows before : https://www.dropbox.com/s/7ogb522axno2akn/HW_Stick%20Calibration_V1.13.exe?dl=0 https://www.dropbox.com/s/ca4sgzfrprayh42/Throttle%20Warthog%20Calibration%20%28V1.07%29.exe?dl=0

It might be because "at rest", the gimbal can't perfectly, physically recenter the grip due to its weight distribution. And so the spring would help you during a very short travel to recenter the stick, and sudenly the force would revert. That would feel as the wall you describe. I had that on my VKB Gunfighter MKII + 20cm curved extension + MCG PRO with 2x50 spring and Cam#10 (soft center). But it was my fault (at least partially), my mount wasn't perfectly lvl, so the grip would rest a little aft. It was really small, something like 2%. But I could really feel that sudden change of tension/tension direction when passing by the gimbal center.

Can you show us your line of code? Edit : Heh disregard.

Hello, I can help but I'm not sure how the cougar throttle speedbrake switch work nor what you need exactly. But here is my guess as to what you have to do. Pulse instead of hold. To do that in Gremlin I use macro. So instead of this : I would do this :

If you want to load a Target profile then yes. However to load a "DCS mapping" you do not need it. I mean the stuff saved in C:\Users\UserName\Saved Games\DCS\Config\Input\... BUT, if the people sharing their mapping are using Target then yes you'll need to run both their Target profile and their mapping file in order to use their configuration. You have the Warthog, so Target or another similar program is also required if you want to make proper use of the toggle switch on the throttle. At least for the module that doesn't support them directly. Afaik only the A10C module does it. But I wouldn't be surprised if ED did something for the F18 and the F16 as well. In short the problem is that without Target, we can not map the OFF position of our Warthog Throttle toggle switch. So for exemple if you want to map the RDR ALTM toggle to the F18 Baro/RDR Altitude Switch then you can't do it properly. The game provide all the option needed : But our RDR ALTM toggle only send a signal when we flip it Up. And not Down. So someone not using Target would have to map the cycle Baro/RDR to the up position. And to use it one would have to flip the switch up, then next time down, and up again. :doh: Using Target we can map both the ON and OFF position of the switch and so no problem. For exemple : //RDR ALTM MapKey(&Throttle, RDRNRM, PULSE+DX62); MapKey(&Throttle, RDRDIS, PULSE+DX61); +1 :thumbup: You could also solve the Warthog toggle switch "issue" using Joystick Gremlin. Exemple here : First macro for the up position, second macro for the down position. I made a little post to explain how to make physical detent match with virtual detent, here it is. You could do the same stuff using Target Script Editor.

I would rather say that with cosmosim cam the force will increase linearly, while with avia cam it will increase exponentially. Exemple here with T50 base, cosmosim cam (Green) versus Avia Cam no center (Orange).

Maybe the magnet moved a bit.. Here is a post in French describing a similar issue and sharing a solution. http://www.checksix-forums.com/viewtopic.php?f=283&t=205003

It might be possible to modify some game config file to do that but I have no experience in doing so. To do that I would use a 3rd app configuration software like Thrustmaster Target or Vjoy+Joystick Gremlin. With those I could make the hat control an axis, and adjust the rate and scale of change of the virtual axis. Let me know if that solution is ok for you and I'll try to explain how to do so.

You should merge your pedal axes in order to do that properly. If your pedals driver doesn't provide that option then I advise you Vjoy+Joystick Gremlin.

Yes, they are developing a collective. I use google traduction..

https://forum.virpil.com/index.php?/topic/853-%D1%80%D0%BE%D1%88-%D1%80%D1%86%D1%88-%D0%BF%D0%B5%D0%B4%D0%B0%D0%BB%D0%B8-%D0%BF%D0%B0%D0%BD%D0%B5%D0%BB%D0%B8-%D0%B8-%D1%82%D0%B4-vpcockpit-heli-%D1%82%D0%B5%D0%BC%D0%B0-%D0%B4%D0%BB%D1%8F-%D0%B2%D0%B5%D1%80%D1%82%D0%BE%D0%BB%D1%91%D1%82%D1%87%D0%B8%D0%BA%D0%BE%D0%B2/&page=2&tab=comments#comment-7376

Target work by combining/merging your physical controller(s) into a single virtual controller. Due to some limitation from.. Windows? Or Direct X I'm not sure, the target virtual device is limited to 8 axis, 32 buttons, and one 8 way hat. Source, page 3/60. You're not obliged to include all your physical controllers into the script. Usually we only include the ones on which we want to do advanced programmations. Joystick and Throttle usually. Rudder.. Not really, and MFD isn't an issue cause no axis. All that is by design indeed, it is quite annoying.. I personally tweaked some Target files to allow the Virtual Controller to use more than 32 buttons, but afaik we can't do that for axes nor hat. Here is a post explaining how to do that to get 120 buttons. You must use Target Script Editor however to profit of this tweak. If you do not want to learn Target Script Editor but want more than 32 buttons, 1 hat etc.. Then I strongly advise you to use Vjoy+Joystick Gremlin.

Yes of course. Only on "very old" game that only support one controller you would have problem. If you want to play such game then you would have to use 3rd app software to combine all your hardware such as Warthog Hotas + CH rudder into a single virtual joystick. This is, honestly, easily achieved using Vjoy+Joystick Gremlin.

Good find, I learned about this windows store issue not long ago but I didn't think it was related to your issue. :doh: https://forums.eagle.ru/showpost.php?p=3925050&postcount=20 A little sticky in the Thrustmaster section could be nice indeed, with this issue, also the TeamSpeack joystick plugin, and also maybe the target release note saying it is important to disconnect controller before installing target..

Good luck.