Daniel

Add the code in red to your file, do it for all the devices you want to exclude. include "target.tmh" int main() { [color="Red"]Configure(&Joystick,MODE_EXCLUDED); // Joystick excluded Configure(&Throttle,MODE_EXCLUDED); // Throttle excluded Configure(&LMFD,MODE_EXCLUDED); // Left MFD excluded Configure(&RMFD,MODE_EXCLUDED); // Right MFD excluded[/color] if(Init(&EventHandle)) return 1; SetKBRate(32, 50); SetKBLayout(KB_FR); } int EventHandle(int type, alias o, int x)

Thanks. :thumbup:

Same problem here, I can move the kneeboard correctly when I'm using one monitor but when I'm using three the kneeboard sticks to the bottom right corner.

I confirm, no more crashes. Thanks k0braka1!

I'm using Windows 10 and a clean install of DCS World 1.2.16.43180 and everything is fine but if I put the HeadTracker.dll into \DCS World\bin folder I get the "DCS world has stopped working" error on misison exit and sometimes also when loading a mission. If I remove the dll everything is fine again. :cry:

Ciao, con quali moduli voli?

When joystick and throttle are not combined they generate default DX buttons, for H4P it is DX19. When they are combined, if needed, DX buttons can be defined by the profile you run (or within the sim). In your case, you use macros and no DX button is defined and that's why you don't see any number lit in device analyzer. It means that in TM Combined you are pressing the H4P but you are generating a macro (F14 press) and not a DX19 press. If your solution works, then leave it as it is. I think you don't need to know which button you are pressing to get the result you need. :thumbup: If you have problems with macro overlapping when you press 2 or more buttons at the same time, if you need full control of the 2 and 3 stage switches of your WH, then DX buttons are a better solution than macros.

Joystick button 19 (or DX19) corresponds to Hat 4 Press (H4P). In your profile H4P generates F14 and SCRLCK commands. What do you exactly want it to do?

Could you post your script?

Take a look at my image. Joystick and Throttle are on the left, TM Combined is in the middle and you can see its 32 buttons. Remember that one single controller can have no more than 32 buttons so... 1 Joystick = 32 buttons 1 Throttle = 32 buttons 1 TM combined = 32 buttons (and not 32+32)

Hi, run your profile then open the TM "Device Analyzer" and you'll be able to access the Thrustmaster Combined buttons as shown in this image.

Sure F-15C_MFDs.zip

Sorry, my pofile is for TARGET Script.

Are you talking about .lua or TARGET?

+1 :thumbup:

Detto in poche parole sono i comandi Direct Input, comandi diretti dalla periferica al pc. Attivano le funzioni senza bisogno di combinazioni di tasti della tastiera.

Ha ragione, quando lancio il tuo file viene generato immediatamente il comando "L_CTL f" che hai associato allo switch FLAPU. Come dice lui ti conviene usare i comandi DX.

Non importa, ho visto il tuo file nel thread in inglese. Appena posso gli do una occhiata.

Ciao, puoi postare il contenuto del file?

A me non è piaciuta particolarmente questa frase. La vedo come un invito a metterci il cuore in pace perchè hanno intenzione di sviluppare questo genere di aerei a discapito di quelli moderni. I motivi sono comprensibili, però... :bored:

Good point, now I'm really worried. :cry:

Hello, when you write a profile you can tell which devices you wish program with TARGET. Let's say you don't want to add custom functions to the throttle, you can exclude it from the "Combined device" and it will still work as a DirectX device, while the stick is controlled by TARGET. For example, I use a Hotas Warthog and the MFD Pack. My profile replicates the default DirectX functions with the addition of some custom commands to both stick and throttle. The MFDs are non included because I want them to work as DirectX.

I would prefer the devs to finally fix it... :music_whistling:

Thanks for the advice. I could get a Quadro FX 3700 for free and I wanted to know if it makes sense to use it with DCS World.

That's why I'm asking... :D