lxsapper

I feel stupid now, I verified this yesterday and I was sure it was set. Anyway got it working now... :music_whistling:

Set your TXs like hollywood said and use TX1 for the ARC159 Remember this is now a AIRIO command as Jester has no controls in the Back for the ARC-159.

That would be a YES for me. Does TX6 work with a DX button for you?

I've had that approach as well but I've found that sometimes I do want to have the ability to center with my keyboard, for example I may be messing about with TrackIR and my Hotas is disconnected. Just a headup, depending on the user this may be completely irrelevant.

This is a conflict that happens to some TARGET Users with some people blaming in on one thing or the other. When running a profile in TARGET you should only see the Thrustmaster Virtual Controller, the other devices should be hidden to windows and DCS (or any other game). I have this problem as well but all I do to fix it, is stop the profile disconnect the controllers USB plugs and reconnect them and run the profile again. There is another way to get around it which is to create a batch file to run the profile on windows startup, but I've found that this does not work everytime.

I have found this issue as well. It only happens when using a DX button a keyboard stroke works fine. I am positive it's not an issue on my end because I've tried both assigning other DX buttons to TX6 and assigning those particular DX buttons to other TXs. They always work with other TXs and none will work with TX6. I've raised the issue to @Hollywood_315 before, but he thought it would be something on the side of Voice Attack, and although I can see his reasoning, I don't see how that can be the case either as assigning the DX button always works correctly with TXs 1-5 or in other profiles I've made to Start/Stop VA listening, the problem is only with TX6 on the Vaicom profile.

You are getting a conflict with the default function of F12 within DCS. TrackIR usually suppresses the Sim use of the binding when it's the same, but I've seen it conflict as well. I Change the Centering in TrackIR Software to R_Ctrl+R_Shift+F12 as that doesn't conflict with any DCS Function and then Bind that with TARGET to my HOTAS, but you could also do it with something like RSMapper or any other software that allows you to emulate keystrokes with your DX controller.

Good to know @Hollywood_315 ! :) And Thank you!

So I now have a working Jester Wheel while using Vaicom! :) Is this By design (Hope so)? When was it added. I really wish @Hollywood_315 could provide a better change log between versions. The side bar in the manual doesn't cover everything. And "Various Fixes" is too little information, specially when we report bugs but never quite get the feedback of when the fix is implemented.

Hello @HILOK This was my own gripe with TARGET but since I've found a hack in this forums to Use up to 132 DX inputs plus the directional Hat with it, I'm back at using it and it's great. This is actually one of the functions I have in my TARGET profile, I use the same DX inputs for VAICOM TXs and I swap that input around my HOTAS depending on the AC I'm flying.

It's the only way presently to have your Afterburner detent match the physical device precisely and linearly. So I use it. And also because trackIR makes no distictions between DX Button # on my stick and my trottle.

You are correct in your conclusion, that this is not possible because the module does not have discrete commands for those functions. In some modules it's possible to add some discrete switch positions by doing some LUA editing. I'm not sure about the SU-25T or other FC3 level modules.

I have this problem as well and this along with other solutions, do not work for me. Having the TARGET profile load up right away on boot does work. But not every time. My work around for this is Stop the profile, exit TARGET. Disconnect the Warthog Stick and Throttle USB plugs (or turn them off on my chinese USB Hub with a switch for every port), connect them again, make sure TARGET is started on Administrator mode and relaunch the profile. Usually works first time, but may take more than one try. I also have a seperate issue where my joystick will sometimes not be functional after launching thrustmaster combined, stoping the profile, disconecting just the stick, reconnecting and running the profile again also clears this for me. I suspect this isn't really related to the first issue and it's something to do with my hardware itself. Anyway if this can help someone else, it's my experience with it.

I also have this problem, already reached out to Hollywood about it, but he had no idea what may be causing it. I've reinstalled VA, VAICOM all to no avail. It only happens with VAICOM installed, and I may be running another profile, as long as VAICOM is installed it keeps crashing from a from a couple minutes to over half an hour, but it always ends up crashing. Didn't use to have this problem I think only started to happen after .17 to .18 I think.

Thank you to ED for this. Its very appreciated by our small community!

In TARGET GUI you put the DOT on the Sequence Circle on the Command creation box and then Create a separate command for each keypress on your sequence all commands on assigned to the same button of course. Hope that made sence.

Disregard it was something on my end that had gone wrong with the update I believe. No need to go into details, but removing and reinstalling the module cleared the problem.

Ok I find this strange no one else is reporting this, but after the update auto wing sweep is totally messed up for me, among other things the wings will not return forward automatically after the program has sweped them back.

I just have it programed as DX inputs like this and the assign them in DCS. To the Right and Left Throttles On/Off positions. MapKey(&Throttle, IDLEROFF, DX68); MapKey(&Throttle, IDLELOFF, DX69); MapKey(&Throttle, IDLERON, DX70); MapKey(&Throttle, IDLELON, DX71);

Interesting, but I don't find this necessary for the F-14 as it has a diferent set of assignement for the back seat. And you can't use both at once. I actually leave most my inputs as DX assigned in game and just use target to do very specific things. In the F-14 I may have DX1 do one thing for the Pilot and another for the RIO. But this is not how it works in the C-101 all commands are avaiable to you at all times. So you have a for example a trigger assignement for the front seater and another for the back seater and they are both acessible to you regardless of the position you are in. Granted they activate the very much do the same in the plane and commands are mostly mirrored between cockpits, so it doesn't mater much if you are activating a particular input for the Front or Back seat, but... I can be really anal about this things.

As for using IF conditionals have a look at page 43 of the TARGET Script manual.

As far as I know you can't really delay the shift. What you can do is program a conditional input, that works as a shift, but it's not really a function like the IO or UMD shift states. You can use If conditionals or you can EXEC alternate "programings". For example this is part of a profile for the C-101 I made: MapKey(&Throttle, EFLNORM, EXEC("FrontCokpit(); ActKey(KEYON+PULSE+USB[0x1E]);")); MapKey(&Throttle, EFLOVER, EXEC("RearCokpit(); ActKey(KEYON+PULSE+USB[0x1F]);")); int FrontCokpit() { MapKey(&Joystick, TG1, DX1); MapKey(&Joystick, S1, DX3); MapKey(&Joystick, S2, DX4); MapKey(&Joystick, S4, DX6); MapKey(&Joystick, H2U, DX7); MapKey(&Joystick, H2R, DX8); MapKey(&Joystick, H2D, DX9); MapKey(&Joystick, H2L, DX10); } int RearCokpit() { MapKey(&Joystick, TG1, DX72); MapKey(&Joystick, S1, DX73); MapKey(&Joystick, S2, DX74); MapKey(&Joystick, S4, DX76); MapKey(&Joystick, H2U, DX77); MapKey(&Joystick, H2R, DX78); MapKey(&Joystick, H2D, DX79); MapKey(&Joystick, H2L, DX80); } What it does is that when I Use the EFL Swith UP it programs some buttons on the stick a certain way and switches to the front cockpit. When I move it down it switches to the rear cockpit and reprograms those buttons with other inputs. But it doesn't use a "built in" TARGET shift mode to do this (I was already using the shift for something else). EDIT: Some of that code is showing wrong because of forums functions and I can't be bothered to fix it, sorry.

You can also bind the long press to a null event instead of an unused DX input.

speed-of-heat I can see the aparent usefullness of what you are trying to do. But keep in mind that you can still program keypresses/inputs to your shift or UMD. So if you program a momentary inputto your shift button, it will basicaly still do what you want, granted depending on what you are trying to do, there may be some situations where that shift still activating momentarily may be undesirable, but I've used it and it works fine for my aplications. (hadn't seen your code yet when I posted)

I think this means the same... and this... I believe, yes we told you that this devices normaly do not need calibration. But there is some circustances when you do. And frankly from my experience the affirmation that the controls calibrate itself when powered up is tottaly bogus. They do retain their calibration very well and basicaly will never drift.