pellelil

Just ordered a 10 cm today, but I have my throttle on the desk, so I don't think I could have a longer.

I only have a single profile that works both for Pilot and CPG. The only pure CPG folder I have is this one: The folders I have for lights and radio works both for Pilot and CPG (even though CPG have fewer lights to operate):

One thing is the accuracy of the coordinate stored in the database, but another issue is the accuracy when obtaining the position of the point to be stored (prior to storing it). The current position of the chopper is obtained from GPS/INS with the accuracy it provides. Then you have to use the azimuth of the laser, and the measured distance, and then from that the location (to be stored) is calculated.

Have just released version 1.02 with the following changes Its no longer necessary to press the "Activate" button after startup. Added program arguments, so you can use "-Minimize" (without quotes) in your program short-cut, to start the program minimized. Updated the manual with new download links, and describing the command-line arguments added in this version. Only one instance running is allowed

Normally discounts don't apply to the latest released modules

The list should be intelligent to only group when there are multiple of the same type: SAM TANK x3 INF x8 In this case we could select the (single) SAM without having to "open" a "group" with only a single element. Likewise I miss the feature to simply ask George so attack all targets of a specific type. E.g. In the case above its a lot of key-presses if you want George to attack all of the INF with the Gun. E.g. right-short to attack (if there is only a single of a specific type), or right-short to "open a group" (if there are multiple of the same type). and then use right-long to attack all targets of the specific type (e.g. INF).

Add an invisible FARP in ME

The files are multi-layered and your text should be added to the top-layer which for both the stick and throttle is called "Labels". It seams I left it locked by default for the throttle, so here you need to unlock it before being able to add/edit text, however it is unlocked for the stick.

Those template were made with the (free) program InkScape. In the adobe suite I would guess that Illustrator would be able to open/import SVG files. Otherwise I would guess that InkScape would be able to save/export it to a format that could be open/imported into Illustrator !?

I recently released this tool which allows you to map up the "off-positions" of the 2/3-way buttons on the Warthog throttle. Hence I personally use the 3 positions of the pinky-switch for NVS-OFF/NORM/FIXED. The program requires the vJoy (virtual joystick driver). https://www.digitalcombatsimulator.com/en/files/3321311/

No there are no programming available, hence nothing to setup. I simply gives access to-/makes it possible to assign actions to the "off-positions" of the Thrustmaster throttle-buttons, so in DCS can assign actions to all 2/3-positions of your 2/3-way buttons.

It have always annoyed me that I could not map the "off-positions" of the 2- and 3-way buttons on my Thrustmaster throttle. A two-way button will generate a "button-press" when toggled to one position, however when you toggle it to another position that "button-press" will simply go off, and it will not generate another button-press (hence nothing to map/bind). Likewise a 3-way button will only generate a "button press" in the up-position and another "button press" in its down-position, however it will not generate any "button-press" when put in its middle-position (e.g. the pinky-switch forward/aft will generate button-press 13/14, however nothing in its middle-position). I know you can handle this via Thrustmasters Target-software, however as your Target-profile boils down to a single virtual device (hence a finite/limited number of axis and buttons), I've always found it to be "too simple" for my taste (in this aspect the software for CH-products is much better). Also you can do it via various other 3rd party software, such as VoiceAttack or JoyToKey. However these are more complicated to setup, as you often have to create/use a specific profile for a specific aircraft, since they need to "send" specific key-combinations. So back in 2019 I decided to write a small program that lets me do so via vJoy (that is a driver for up to 16 virtual joysticks, each with multiple axis and up to 128 buttons). Joy2vJoy is hard-coded to ONLY work with the Thrustmaster throttle and the vJoy driver is a requirement (vJoy is not bundled, but download links are listed below). I initially had plans to expand this program with support for additional devices and add scripting. At one point I had a development versions with LUA-scripting support, however it was not running reliable, so I scraped it. In its current form I have used this program with DCS since 2019 myself, and have never had any issues. The program is written to be light on CPU-usage, so your frame-rate in DCS is not affected, but I suggest you only enable "Update checkboxes" when testing how the software is working. If you haven't done so already you need to install vJoy (links below) and create a single virtual Joystick with at least 21 buttons (I simply made one with 128 buttons). In the enclosed manual (PDF-file) I show how this device is created, and how you can test it is working, using the programs installed with the vJoy driver (you only have to do this once). From that point you simply need to run Joy2vJoy prior to starting DCS (or whichever sim/game you want to use it with). The way it works you map your physical buttons to actions in DCS using the physical Thrustmaster throttle (as per usual). However to map-up the "off-positions" of the various 2/3-way buttons you in stead need to map up "button-presses" on the jVoy device to the action you want to perform when a physical button goes off. E.g. for the DCS AH64 I use the 3-way pinky switch on the throttle to control NVS-OFF (aft), NVS-NORM (middle/off) and NVS-FIXED (forward). The Pinky-switch forward/aft generates button press 13 and 14 on the phycial throttle, so I use theese buttons on the physical device to map-up NVS-FIXED/OFF. However I then use button 13 on my virtual vJoy device to map to NVS-NORM. It is a coincidence that it is also button 13 on the virtual device, so either use the table in the PDF-manual too see which virtual button-presses are linked to which physical-buttons, or simply check "Update checkboxes" in Joy2vJoy and see what happens when you press the physical buttons on your Thrustmaster throttle (which check-boxes are checked/un-checked). In the screen-shot above (both "Activated" and with "Update checkboxes" are enabled), the check-boxes in the left side of the screen represent the physical buttons on your Thrustmaster throttle, and the check-boxes in the right side represent the virtual buttons of the 1st vJoy device. Download link for Joy2vJoy: https://www.digitalcombatsimulator.com/en/files/3321311/ Links for the vJoy driver, both for usage with Joy2vJoy and/or the Streamdeck-vJoy plug-in: https://github.com/njz3/vJoy/releases (as of now version 2.2.1.1) https://github.com/jshafer817/vJoy/releases/tag/v2.1.9.1 (older version) Version 1.03 (April 10th 2022) Added virtual (Off) button 22, when Throttle Hat is centered. Added short-cuts (e.g. "ALT+C" to toggle "Update checkboxes). Added ToolTips to Physical/vJoy checkboxes (shown when hovering mouse ower these). Added management of "Initial Status" profiles. Enabled mirroring of Off-buttons Enabled mirroring of Physical TM-Throttle buttons (and POV Hat) Enabled mirroring of Physical TM-Joystick buttons (and POV Hat) Version 1.02 (April 3rd 2022) Its no longer necessary to press the "Activate" button after startup. Added program arguments, so you can use "-Minimize" (without quotes) in your program short-cut, to start the program minimized. Updated the manual with new download links, and describing the command-line arguments added in this version. Only one instance running is allowed. Version 1.01 (March 2022) No need to toggle all buttons (on/off) of the physical Thrustmaster throttle at start-up. Released here at DCS as a zipped-archive (to be copied where you want it). Version 1.00 (2019) Released as an installer (via a Thrustmaster FB-group). Recorded video for the release of version 1.03 both explaining how to use the program in general, and what was added to version 1.03: Beside using vJoy for the Joy2vJoy software I also have begun using vJoy with my Stream Deck (SD). I started to use Joy2vJoy when I got the DCS F18, and for the F18 I made an SD-profile for the F18 simply sending key-combinations from SD to DCS. However it was a drag finding out which keyboad-combinations that were in use in DCS, which I needed to define/use both in DCS and SD (given many keyboard combinations that DCS will acccept, cannot be generated by SD). So for my AH64 SD-profile I instead decided to use a plug-in for SD that lets my SD button-presses generate vJoy button presses. So as of now I have no less that 5 vJoy-devices (virtual Joysticks) defined. The first vJoy device is only used with Joy2vJoy (can't be shared with the SD plug-in). However the other 4 vJoy-devices (each with 128 buttons) are only used with the SD plug-in. Hence via this plug-in I have no less than 512 virtual buttons in total, that I can map between SD and DCS. Even though you define devices with 128 buttons, there might be programs/games that are only able to see/use the first 32 buttons (however DCS can see/use all 128 buttons on each device). Another bennefit of using this vJoy plug-in for SD over generating key-presses is that you can use multiple buttons at the same time. E.g. pressing two SD-buttons (or more) at the same time, I can both increase the lights for SIGNAL and PRIMARY in the AH64 at the same time. Had I used traditional key-combinations, I would first have to increase one, and then the other. Here below is a link for that plug-in for SD, and a link for a package I made with nearly 300 (button) graphic-files to use if you want to build an AH64 SD profile. In the zip-file for the latter you also get a full list of which actions you could choose to map to actions for the virtual devices 2-5 (4 devices each with 128 buttons): https://github.com/ashupp/Streamdeck-vJoy https://www.digitalcombatsimulator.com/en/files/3321046/

Known issue:

Sooo many memories of the old Janes Longbow Ever since I got the first DCS World I kept my fingers crossed that we one day would get an Apache. Normally I am jets all the way, but the Apache have a special status for me (thanks the those old Janes Longbow's). Thank you ED for finally including the AH64

@skyrat simply map up the action "Clickable Mouse Cockpit Mode - On/Off" to "MOUSE_BTN3". By default pressing the scroll-wheel is mapped to something else (forgot what)

My bad, I though you meant to zoom the cockpit view, and not zoom the DTV/TADS. You then probably need some external software !?

You can map up the mouse scroll-button (pressed) to toggle the cursor you normally move on the screen (forgot the name of the action), and then simply use the scrool wheel to zoom in/out (moving the mouse will pan the view around)

I always make kneeboard pages for my HOTAS (Warhog throttle and stick). They are a great help when building up your muscle memory, and as a reminder when returning to a module you haven't been using for a long time

Beside keeping an eye on the VSI-tape, I also think the flight-path-marker (FPM) is a great help to spot when you start to drop too quickly or raise because you added too much collective.

Also you have to make sure that NVS mode is set to Off.

No only for the Stick, Throttle and MFDs

I power up the bird and move the cursor so it touches the left side of the left MPD. As soon as I touch the "border" it becomes frozen. After touching the border I try the next 5 seconds or so to move it right, but it stay froze. Then I let go of the hat (let the hat center), wait 5 seconds or so, and now I can move the cursor to the right again. AH64_Frozen_Cursor.trk

I noticed that the cursor in most cases will freeze when it touches the screen edge. However if I center (let go) of my axis hat mapped up to the cursor (TM Warthog throttle). Then I will be able to move the cursor again.

@sobe here is a link for (blank) the SVG-templates: https://www.digitalcombatsimulator.com/en/files/3321035/

@sobe these are made from my own SVG-templates, originally made with InkScape. I have since moved on to Affinity Designer, hence that was used to make these particular ones for the AH64. I have just uploaded my (blank) SVG-templates to the user section, and they currently await a moderator to release them. These SVGs are made as multilayered files where you can lock/unlock and make layers visible/invisible. @cow_art I had to let it sink in, but eventually I took your advice (thanks). I moved the Trim/AP functions to the TMS-hat, so they are more easy to reach. Flying mostly solo, I think I end-up interacting more with George (especially if in the front seat) than using the WAS-switch or sight-select, hence I decided to moved the George-AI functions to the DMS-hat and in the process also moved the two George-AI functions I had put on the CMS (shifted-left/right). So now ALL George-functions are on the DMS-Hat, and I used the 2 remaining shifted-positions (up/down) on the DMS to swap seats (Pilot/CPG), and "I have controls" - its officially called something else The WAS-functions and Sight-select (shifted) were moved to the TRIM-hat. I then decided to move the LRFD 1st/2nd detent to the NSB-button (at the root of the stick), which freed up the "Weapon Release Button" where I put "IAT: auto/manual" and "OFP: Ret TADS LOT".