Ant0ine

Recently while writing a guide I noticed the issue as well. I usually fly WWII with right throttle as throttle and left as RPM/propeller pitch so I never really noticed the issue. To solve that, and also to make our physical detent match perfectly with virtual detent while retaining a linear throttle response curve, I created small deadzone at the MIL throttle position. Please see the guide.

You could use voice attack to map keyboard shortcut to your MFD button and mouse button. Last time I used Voice Attack can indeed take keyboard, mouse, and controller as input. You could also use Vjoy+Joystick Gremlin, Joy2Key, Target.. UCR. The most all in one programming software is Vjoy+Joystick Gremlin in my experience.

This? If so, if you instal Gremlin then you should use Gremlin to make that curve instead of the DCS tool. Using the DCS tool you can not get a perfectly linear response before/after the AB detent point which by the way isn't accurate. Please read more about that and see an exemple here.

Vjoy+Joystick Gremlin. https://whitemagic.github.io/JoystickGremlin/ Map some Vjoy button or keyboard shortcut on your slew axis and then choose on which range of the axis those button/keyboard shortcut should be triggered. I can provide more help if needed.

https://github.com/evilC/AutoHotInterception I think we can also use UCR (from the same dev) with the interception driver. This will allow us to remap keyboard/mouse independently individually as with AHI, but using UCR we can remap to Vjoy button/axes, which is much better than remapping to crazy keyboard shortcut.

I'm checking right now, I was wrong.. Apparently we can not map a joystick to control external view, we can only control cockpit view with controller axis.. For external view I only see mouse.. Well, you could use joystick Gremlin to convert your joystick into mouse. I'm doing it right now. But as I expected the result isn't great (not better than with a mouse, I mean it is easier to hold a constant deflection but it isn't smoother). Even at low speed the image rotation isn't smooth. I think the issue is that the minimum rotation we can do in external view is way to large. https://whitemagic.github.io/JoystickGremlin/ Quick screenshot to show an exemple. I'm testing on my rudder, you want to remap X and Y mouse axis to your joystick X and Y of course. Edit : Just found this. https://github.com/Kaidrick/DCS-External-Camera-Interaction-System

To get that to work in DCS, you'll certainly have to make the 3D mouse seen as a Joystick. It might even work like that by default I'm not sure. All that to say, that you could simply use a joystick, or rather 2, to get all 6dof just as we do in Space Sim such as Elite Dangerous and Star Citizen. To control your camera. You would have much more throw with normal sized joystick, and much better axes separation as well.. (And so better result). Also two T16000 would be much cheaper than those 3D mouse.

Yes, that is exactly what cams are for. By default the AviaSim - Soft Center (Non-Linear) is installed on the T50CM2 stick base, you should try the No-Center AviaSim Cam.

https://www.ebay.com/itm/Repair-Service-Thrustmaster-Warthog-Throttle-Main-PCB-Bricked-Warthog-Fix/233195609114?hash=item364b8a9c1a:g:0woAAOSwWrxcH5VO

Really? We can bind keyboard shortcut using the Virpil Software now? :sly:

https://forums.eagle.ru/showthread.php?t=249484

On the MFG cam aren't symmetrical. https://mfg-sim.com/download/CAM_Presentation.pdf

Uhm I think you can use the Logitech Driver driver/software package. https://download01.logi.com/web/ftp/pub/techsupport/simulation/Flight_Rudder_Pedals_x64_8_0_213_0.exe Link above is the latest version for Win 10 64bit. If that doesn't work then you can find much older Saitek driver here : ftp://ftp.saitek.com/pub/software/

Make sure to unplug your joystick BEFORE installing Target. Here is a quote from the Target release note. http://ts.thrustmaster.com/download/accessories/pc/hotas/software/TARGET/ReleaseNotes_TARGET-v3.0.18.328.txt

Here is a way to do it. I did it on a keyboard key quickly but doing it a any controller button would be the same. https://imgur.com/a/1GhmuAs

I remember I encountered that issue. It was a while ago and I am not sure if it was related to windows 10. However. I remember that in my case, the issue was due to my Steam controller wireless USB dongle. I know someone else who had the issue due to a similar dongle for one of his mouse. In this reddit post I propose a few alternative to the Thrustmaster Target Device Analyser. .. I'm trying the device analyser right now and can't get it to work either :joystick:. Well, I'll keep using Vjoy+Joystick Gremlin to remplace Target, and the Joystick Gremlin input viewer as main monitoring tool. It doesn't do keyboard and mouse monitoring however. For that I continue to use the TM Event Tester.exe. I find it easy to read with press in Red and release in Black.

Virpil rudder do have Toe Brake on 2 of their 3 available rudder. https://virpil-controls.eu/shop/rudder-pedals.html I think that will be hard really. Could you at least put something in between the wall and the rudder so that you can push on the rudder without it moving? Here is the POV from someone who tried quite a lot of high end Rudder.

:thumbup: +1 for Joystick Gremlin.

Yes we can map several joysticks within DCS menu.

But you can have several "joysticks" in DCS. One could be dedicated to your "view control".

Can't you have both mapped at the same time?

Wouldn't a joystick be best for that? Using a mouse I would try to convert mouse input into Vjoy axes. Using FreePie for exemple. And this script.

I don't know how to do that with Target, double tap isn't explained in the Target Script Manual, however you could do a tempo. Short press/Long Press. Or you could use Joystick Gremlin which provide option for both Tempo and Double tap. https://whitemagic.github.io/JoystickGremlin/

Make sure to tick "TrueView" in the Track IR software option. So that translation are relative to rotation. This way if your view is rotated 90 to the right and you translate forward, your virtual head will translate to the right, closer the right wing instead of closer to the front windows. Your Track IR Z axis should be mapped to translate head forward/back instead of zoom, then to zoom you have different option. You could use button to increment/decrement, or use an axis. I'm not sure how your knob work, please explain me, does it modify an axis or does it send different button pulse depending if you rotate it one way or the other?