lxsapper

Hard to say when you say you've been torough in your search. I've seen something similar after the 2.5.6 update but I was doing a lot of experimenting, can't remember exactly what I did. But to any one still having problems with Vaicom not working correctly I'd do this: 1- verify the versions of Vaicom Vs DCS as per page 4 of latest Vaicom's manual. 2-run Voice attack go to Vaicom configuration make sure O.B is set as required for your case and that custom path as well. Exit VA. 3-run a DCS repair. 4-goto your DSC/DCS.openbeta savegames folder go to scripts delete Vaicom folder inside that and eighter delete your export.lua or edit it (if you have other things that have added entries to it) and delete the Vaicom entries. 5-enter VA then exit and restart Voice attack 6-only restart DCS now

Try a reset to your lua code.

Plug and play means window recognized and installs the required drivers upon connecting to an USB port. This (perhaps over detailed) explanation is about how to bind them correctly to each DCS aircraft. It's up to each DCS module to have or not default assignments for each controller. But given the amount of controllers available this could be a rather monumental task. So the way it usually works is instead of having default assignments for all controllers on the market. DCS modules follow a strategy of: axis#1-do this... , Axis#2, etc. And the same for the digital inputs.

Only with very old games that don't support more than one controller. Most flight Sims have supported multiple controllers for quite a few years now. Even the warthog or X55,x56 are now two separate controllers. Even if the Warthog can be joined virtually into a single one. But you don't chose anymore which controller to use, you assign DX inputs to your various sim functions.

DCS version?

@Hollywood_315 Found a bug with the Plugin "Select Channel **" command. It won't put the radio back on Preset mode. If you are on Preset and use AIRIO "Tune Radio ***.***" or Vaicom "Select AM/FM ***.***" it will switch to manual mode. But the reverse is not true, the Channel is actually selected but the radio will remain on manual Mode. There's also some strange Buggy Behavior with "Select Channel **" with the F-18, because it will change the frequency of whatever channel you are on, but it won't actually change the channel. If you use Manual tuning with the F-18 "Select AM/FM ***.***" it will change the channel to "M" mode with the frequency you have selected, using "Select Channel **" will also not return you to a preset channel on the F-18. Personally I'm only interested in this commands for the F-14 for the ARC-182, still this is what I found.

Could you clarify pop up? In any case in I'm not sure from your description, but first of all in order for Vaicom to work correctly you must launch VoiceAttack before starting DCS.

Most likely you are using incompatible Vaicom/DCS versions at this point. Check newest Vaicom Manual on page 4 for incompatibilities. And check DCS and VAICOM version.

Hello again @Hollywood_315 Here's my initial findings regarding the new options for SRS Integration: As I stated before I'm really glad for new the functionality, it's definitly the move in the right direction. I thought I would never have use for integration and you made me change my mind. However, and be mindfull that this was after a very basic test of flying alone, issuing AI commands and monotoring SRS states. There are a few things I would like to see changed/added for this to become really an option for me. At present it's certainly usable (for me) but there are things that would make it more friendly/less clunky to use. 1 - All the options regarding dynamic switching are an absolute must for me, you were absolutly bang on when you thought of them. I check all the boxes for them, the only I could probably leave out after a while is the Sound Notification, which is still a must have as an option I think. 2 - At present "Hold AI transmition" works with every TX, I suppose this was easier to implement because of all TX modes supported by VAICOM, but I would like the option to leave some of them out. Using Normal TX mode there is no reason to have it on TX4-6. Even on TX5 for Intercom (at least with present DCS aircraft) I will either have a human or an AI listening on Intercom. Maybe not strictly true since you can speak to Ground crew on Intercom, so maybe have this as an option. In any case the delay on this TXs me feel uncomfortable for my personal use. 3 - A behavior base on what was initial in integration, I believe the plugin would take into account AI vs Human recipients on tuned frequency, would still be useful. There is no need and it's even an inconvenience on having to say "Switch" every-time I want to talk to a Human, even on frequencies that have no AI recipient on it. An alternative, or even better yet an optional increment to this, would be able to select a TX/Radio to exclude from SRS Inhibit altogether. My group and I believe most groups that fly with somewhat real procedures, use a frequency just for own flight or package, there will never be an AI to talk to on that frequency for us. So that's my opinion thus far, I'll try make a full flight with humans latter on, and if I find anything new or change my opinion on anything I'll let you know.

You don't get the Jester wheel with AIRIO atm. The suspend command is a function of the Jester wheel, can't remember what's it's called exactly. It stops jester completly from doing anything. He won't press any buttons, nothing, it will be like he wasn't there. It useful for example if you want to jump back and forth between both cockpits without having Jester do things on his own or change what you,be done. Say you want to do a complete full start of both pits and jump back and forth. If you don't suspend Jester, even if you don't tell him to start up he will still start doing things at one point depending on the state of the jet. This was actually something that Vaicom users asked Hollywood to add to AIRIO that we were missing from the Jester wheel. So thank you again Hollywood!

Lange devices you don't have can be excluded in your profile, again you don't have to edit your .tmh for that.

I was wondering where that function had gone to. I remembered it used to be in DCS. It still is, I had just lost it! :D

Ah well thanks for that. In any case TARGET's percent precision isn't bad at all for my present needs. Beats DCS 10% intervals, and doesn't make the resulting curve a Spline. In fact it very much functions as straight lines between points, which is exactly what I want.

Audio redirect in Vaicom?

https://forums.eagle.ru/showthread.php?t=169387 2- any that works in windows.

Don't forget one of the great things about FF in DCS modules (when it's enabled and working anyway) it's not the effects, but the behavior of trim.

Pikey when I made that comment I was replying to Harlikwin, regarding this: Not sure why else one would think a motion platform would be necessary to convey AoA, but I am not inside his head and I admit I don't actually know what he was thinking. I just assumed that's what he meant.

I meant you can do the Buffet with shaking, I didn't see the need for a motion platform for that. And I assumed it was beeing sugested that AoA should be conveyed to the user through platform absolute pitch, which would not be accurate.

This sounds like the thing that might work for someone who wanted to map an airbrake to the X52 slider, except for the fact they were using an x52... :D Jokes assides I've seen pleanty of times where a funciton like this might be usefull in one Flight sim or another, for a particular function that doesn't suport an axis for some reason etc. So thanks for sharing. On another note, I was wondering if you think it's possible to use something like your "&pro_SD40GP38_ThrZoneList" and use it to make a "SetCustomCurve" more precise by beeing able to define the points down to a tenth of a percent?

If the RiftS is anything like the VIVE (or other sound devices) when you disconect it, the device you had as Default before it, will take back over, and when you connect your riftS it will take preference again. Not sure if that helps or not... As for the TX6 not sure what to tell you... what TX mode are you using? Altough if 1-5 are working, no idea why 6 it's not...

Curious to know what you are cooking... be sure to keep us in the loop! :)

This might be a stupid sugestion as I have no Idea how the RiftS audio works. But why not make RiftS audio your default audio output (when you are using it) and redirect in DCS whatever sound you may want in your speakers (aircraft sounds etc)? Admitidely from someone who knows nothing of the RiftS (but I do have a VIVE) sounds like that should do the trick, SRS/VA and other software should be played on the dafault audio device (RiftS in that case) and your speakers could play whatever you redirected to them in DCS.

It's not a bad advice, but since extra complication is next to nil with using that file (it's just extra DX assignments to play with) and I literally needed this (I keep away from Keyboard strokes as much as possible, even back then, but still like to use programing to do the things I can't by other means) when I started with TARGET (and didn't have it) so... This should have been default with TM TARGET IMO specially when the driver obviously had the ability to do so. Merging at least two devices that have 51 DXinputs + 16Directional Hats positions, and forcing you to take a max of 32Dx inputs + 8inputs in the directional hat. Was a stupid move by TM that put me off of TARGET for a long time.

Well what can I say very surprised in a very good way by today's new's letter. Well done ED, I can only suppot you in comunicating more in this way. Some things in the Reddid milestone tread are not leave me a bit disapointed for now (No it's not that F-16/F-18 are sharing the same team), but when there's expectations there's always bond to be some disapointment. And this new move to be more transparent is definitly a step in the right direction. Again, Well done ED.

The best most realistic indication of AoA (excessive) is buffeting (Shaking) a motion platform to convey AoA (through pitch I presume) would not be representative in the least, of Reality.