lxsapper

Well to be honest you received some experienced knowledge, and what you got from TM is the run of the mill answer and nothing new that hadn't been said to you before. But if it makes you happy...

Yes the Tools that An Ant0ine linked. And no The Calibration tools will do absolutely nothing for the AB stop. But the Will allow your axis to start before Idle (Get full axis range basically), absolutely useless for DCS, but useful for other flight sims. To set your AB region you can use the User Curve settings in DCS as you mentioned. You can also use Target Script Editor to set it precisely. But you have to go the TARGET programming route and not everyone wants to.

Well if only we could get @Victory205 to chime in some more... He'll know! :smilewink:

I think people are missing the OPs point. He's not asking for flight lessons, he's asking if the ball behaviour is correct or needs to be reviewed.

Missed that one somehow.

You must have that set initialy yes. You may turn it off later on if you always fly on the same server missions with the same F10 menu. But the you must go into the editor and click "finish" and follow the steps to add those commands to the profile. Read the Vaicom manual on the keyword editor if you need clarification on how to do this. As for editing the keywords for the F10 menu you'll have to have a look yourself, as I said I never dabbled into this.

You do in the Tomcat...

I think, and I might be talking out of my ass here... That the ball is only good for coordinating the turn when you are already on the turn with neglectible roll. I belive when rolling the ball will always be spun to the outside because of centrifugal forces, even though what you should do is use inside, into the roll, to counter adverse yaw.

Just like Ant0ine said, usually you won't need to calibrate the WH stick or throttle. However when I bought my set second hand the Joystick drifted to the side on the X axis and that's how I knew it needed calibration. If you have any such issues if will fix it. do not ever calibrate them using windows tools. The WH devices hold their calibration in hardware you don't want to add a layer of driver calibration to that. You seem to be confusing adjusting your axis resposes with calibration, they are not the same. TM calibration tools do allow you to do some "wrong" calibration that can be very useful for some uses, but I'd stay away from that for now. I do have my throttle calibrated to something a little different from the instructions for such a reason. TARGET actually allows you to trim (or do all sorts of crazy stuff with them) your axis and even do it on the fly, for example for AC or simulators that don't have this feature. But refering to this as TRIM as opposed to CALIBRATE is more accurate.

So if I understand you correctly, you want to use Vaicom normally and then add your own commands to control DCS, cockpit functions, etc. And have those commands on a open mic setting, correct? If that's the case add the new commands to either Vaicom profile or make a new profile and append it to Vaicom profile. Then in each of those commands you are going to add in the "when I say this command execute" section: 1- Voice attack function- start listening 2- whatever you want executed, key presses etc. 3- Voice attack function- stop listening So we can conclude that in really VA is always listening... Anyways it works.

This is not a function of Vaicom, but yes you can do it with VoiceAttack and there is more than one way to set it up.

But if you need to set curves deadzones etc. Either will do the job. But Target, specialy target script, will give you more control.

No, as there is no command for that in DCS. 1- If you are trying to use F10 Menu commands you have to let Vaicom import them then add them to your profile, with the finish button on Vaicom's editor tab. Then each command is precceded with the word "action", other than that I can't be of much help I've never dabbled much into using Vaicom for F10 menu items. I just use the "Options" command for that. 2- "Status" is a AOCS command, has to be used in Crystal Palace frequency, and only works as far as I can tell with normal TX mode. Other than that I think your question is also regarding the same as point 1. 3- Vaicom recognized as you saying one of the New commands for the SuperCarrier comms. It doesn't mater that you have Pre-Purchassed the SC, since the module is still not in DCS, this commands will not be available to you. This is something I believe Hollywood is still working on, and getting some work done prior to SC release, probably so he can get Vaicom up to speed ASP after SC release. 4- If you use recipient in your wording yes, there i a delay, I don't think it's no where near 3 seconds, but there is a delay. You skip it and just say "Request Taxi".

I don't know what is wrong in your case but as a tip, you can't really leave a pause between "Radio Tune" and the Frequency numbers, you have to say it in one go, because the whole thing is one command and VA will "stop looking" for words to form a command if you leave it too long to speak the next word. I find that speaking quite fast works very well for radio tuning commands even using standard Windows Voice Recognition Engine.

Sorry can't agree with most of what you wrote. Ranging from the "not realistic goal" to the "actually more work to module developers" to the "you don't understand the scope of it".

Thank you BIGNEWY, we appreciate it!

As per latest(2.5.17) manual:

Debolestis also has HAT Switches shafts, should be able to replace yours with a little work if you need.

The reason all pedals I know of have this behavior by defaul with all aircraft, it's because the break axis resgister in windows and X and Y, and DCS assigns them automatically to control aircraft pitch and roll, but to make things worst these axis are not centered at rest but at max value in one direction. Z axis usually is assigned correctly to rudder. So you need to reasign them correctly to left and right toe brakes. And this is where the inversion is often needed as most pedals have their electronic response set one way, but DCS considers this position should be max breaking rather than no breaking. If this is the case for you and you don't invert your toe breakes you will be fully breaked when you let go and unbreak when you press them in.

Maybe someone more technical can help you. I understand what you need... and I don't think it's possible without ED adding this ability on their end.

Every option? Only the relevant ones certainly. But this isn't just up to ED, this is up to every module developer to implement individually.

Generating S&R missions, ok nice idea. Improving the models and have the crew on life rafts good idea. Penalizing the pilot who ejected? What sort of penalty? Sitting in external view for two hours until another player is able to pick him up? No? What then?

Hello @sthompson I can't be sure from memory but I think it's normal that you don't see TX6 available to in those images. I think only TXs associated with radios will show as available. But TX6 can't use "options" in normal mode and can't use "select" on any. In normal mode to use options you still have to key the radio you wish to transmit on. And "select" by it's very nature requires you to key the radio you want to tune. Even the if your aircraft only has 1 radio. If you don't want other players to listen in on that try integration, becoming a very interesting option IMO. I'll try to further explain the TXs mode within my knowledge, even though I think the manual covers it reasonably well. Normal mode is well... Normal. TX1, 2 and 3 will each transmit on a radio and only in that radio. Multi is for allowing you to use multiple PTTs in aircraft that have multiple radios and one PTT. i.e. the KA-50 and the Huey, in normal mode they will only have TX1 mapped, and to talk on the other radios you have to turn an in DCS cockpit knob. Multi allows you to bypass this by always having each radio mapped to one TX, just like normal mode, but regardless of aircraft. Single is like an auto mode. You can select whatever TX6 you want and regardless of what radio your intended recipient is. If you have their frequency tunned in one of your radios they will get the message, the plugin recognizes it and knows where it needs to send it to. A bit like easy Comms except you still have to tune your radios to the frequency of who you want to talk to. Inverse is like Single but instead of selecting a TX to use, you can use any and all of them. Hope this helps

Rgr that, The whole steps shouldn't be needed by everyone. I just included them because according to my knowledge, if you do all of that it should clear any problems you have regarding your VAICOM/DCS installation and get you running. But yes, not all steps are necessary for everyone.

So did that work for you or not? You were are actually supposed to check that box if you were running Open Beta(unless you were on STEAM). It's how the plugin knows if it should install .lua modifications for Release or Open Beta. I say you were lucky in the past because in the last few months there were no significant difference in structure from Release and Open Beta. That of course changed a lot with 2.5.6.