lxsapper

Yes it's possible to have the same DCS function beeing controlled by more than 1 key/joystick bind.

I am using this exact behaviour on my Warthog programmed through TARGET. Using short press for DCS comm switches and long presses for SRS/Vaicom.

Not necessarily, you'd still need to read it off the kneeboard and input it into the aircraft.

One day I hope to figure out Ikarus. But the few times I tried it I couldn't figure out how To swap monitor much less how to resize a damn profile...

+1

The Cleanest way to do it is making a separate profile with those commands and append (piggyback) that profile onto the Vaicom profile. You can also add the commands onto Vaicom profile. Either way to use those commands use TX6. Edit: Didn't see Waistcat response before mine, you can also do that. But since TX6 is already on Vaicom for that very reason you don't have to.

All good now for me!

Right now Vaicom is working for me, but like others I'm not getting responses from AI, this is audio responses only, as I get onscreen text responses (with that option enabled). With Jester AI I still get both audio and text confirmation, this is only happening with other units like Tankers ATC etc. Not sure if it's a Vaicom issue or DCS, have to test.

Hello @Hippo, turns out I was wrong. What you want to do can be done inside DCS. Very simply chose a modifier, either one of the existing ones (RCtrl, Lshift, etc.) or chose a button on your Joystick that you can spare and add it as a switch type modifier. I recommend this as the shift state will work as ON/OFF instead of having to hold a button or key on your keyboard. Next go to your axis assignment clear the throttle assignment. And assign it again but with the modifier you choose. Tune the Axis: You can reduce the Y saturation, without selecting the axis as a slider, our make a custom curve to your liking. Next assign the axis again but without the modifier. Fly and use the modifier to alternate bettwen full range throttle and limited/custom curve range.

Japo32 make sure to select the option O.B. for Vaicom. I think Vaicom will use the old structure for compatibility wih stable if you don't.

You can try power on power off technics. It's mostly how it's done IRL and can be used for formation and AAR. Though personally for AAR and formation I prefer when I can get really established. In that situation with the Warthog (and not trying to shame you on your hardware at all) I do very small movements, I'd say less than 1mm, adding power and taking away as needed. Since I don't belive the x52 and WH have that much diference in total travel (I'm not using curves, but I am using two straight lines set up with TARGET to match my AB detent with the physicak detent)of the throttle, so actually the movement amount you want t be aiming for should be relatively the same. The only diferente is the sensor resolution of each device, but with relatively linear response both should need about the same movement for the same power change, sensor resolution only maters for how small of a movement can be read.

I used to have an X52 (non pro)but that was a long time ago, I really can't remember how good or bad the precision on the throttle was. But my main gripe with it (specially after I had it for a while) was with the joystick it self, as if suffered from a lot of "sticktion".

Also apologize to you Hippo and to Stuartaston as I clearly got you confused in my reply... duh me!

Probably not because the file path and file structure of some files are diferent.

Awsesome stuff @Hollywood_315! Will only be able to try tomorrow. Looking forward to having it work again! Then again I'll have to consider to update or not as I might roll back OB. There's quite a few broken things with 2.5.6, but maybe ED gives us a more or less fast Hot Fix as well.

Hey @stuartaston, I don't know if the spool time in the Hornet is realistic or not as I have no RL experience with it. Like the others have said I think RL pilots have said it's a little too much right now. I only meant that getting used to this spool time delay has probably more to do with the dificulties you are experiencing, than the resolition of your controls axis. As for wheter it's a bad thing or a good thing to use zoom axis. I think it's a bad habit, that will actually throw off your flying, but that is only my opinion in the end of the day you have to do what is best for you. would have to measure the throw in the real hornet vs your saitek. I think the hornet throttle will actually have less angular range but the whole thing is probably able to read a lot more detail out of the range of motion. More throw (longer lever) will allow for easier control of that range of motion as you very well know, and you can theoretically fly more precise in a certain range of the axis if you make that range correspont to more throw, but AAR refueling is probaby not the only ocasion where you will need to be precise in that range and formation flying will also require it, with the added caviat that it will be a lot more dynamic and you will need more range. Using two diferent settings seems to me, other than unrealistic but a way to get around PC periferals real or percived limitations, a way to sabotage your muscle memory. But again in the end you have to find what works for you. I was just adding my opinion. But to more precisely answeer your question. There is really no way of doing what you want in game. You can as you know adjust your curve to give you improvements in one range at the exense of the rest, but it will be permanent for that aircraft and axis. You could bind another axis with the a personalized curve to handle the throttle in just that situation. In theory this could work reasonably well, but I belive it will give you problems because if the axis not in use oscilates even the slightest the moment it moves that will be the value assumed by DCS which will will then have to counter by moving the axis you are actually wanting to use in the situation you are in (assuming a setting of a full range value axis vs a limited but precise value axis). As for a third party solution, only something that creates a virtual device will be able to help you. As that is the only way to have a custom and "changeble" axis response. TM TARGET works just in this way. But since you have a saitek Hotas the only alternative I know is vJoy to create you virtual device and use Joystick Gremmlin to program things the way you want. There may be others but I only know of that one, at least vJoy for the virtual device.

@NineLine I meant the White thing. I would attach a screenshot but I can't util tomorrow. I was on MP though and was not the only one seeing it. Haven't tried deleting the shaders folder, will try that tomorrow as well.

The files on the saved games should be fine, at least for me I haven't had to touch those files. Running a DCS repair is the easiest way to get DCS working. But if you look on Vaicom manual under Manually managing DCS side files you can see the files that are changed by Vaicom. I think only one of the actually stops DCS from starting (see my posts on Vaicom thread) but if you don't fix the others you will still get problems trying to using the comms menus the traditional way. EDIT: Vaicom Updated to 2.5.6 compatibility!

I've seen it in the new right click device behavior, but haven't used it, don't know if it still works. But I could also still see the old export button in the same place as always.

Zip the files.

Lighting needs a lot of work but that's to be expected actually, I think the new system was put in place and now the various light sources cockpit and otherwise need to be adjusted to it. It doesn't take long to think about and realize that this is a big task that spawns every single module and map and effect in DCS. And honestly with so many problems introduced by the new patch ATM I think the lighting issues should remain lower in priority. Invisible planes and AI planes teleporting about and flying 80 degrees nose up lvl flight, should take priority. Not to mention MP instablity, etc.

It's not VoiceAttack, It's Vaicom.

Vaicom installs it's Lua modifications each time you run Voice Attack. There's an option in Vaicom to handle DCS side files manually, but it doesn't appear to work. Haven't tried this yet but I sugest move your Vaicom folder inside VoiceAttack plugins folder to another location to deactivate Vaicom completetly until Hollywood fixes it.

Actually Vaicom is broken for this update. If you reset your Luas DCS will not start. Simple solution is repair DCS and don't run Voice Attack at all so Vaicom won't install it's lua's. As far as I've gathered only 1 file actually stops DCS from starting. But you will have other problems as well.