Hollywood_315

Hey sobe - yep guilty as charged [emoji1] Thanks so much man I really appreciate that. Just send me a PM with your issue I'm sure we'll get it to work.

@OverDHill @sobe Excellent stuff guys - I will check this out thanks a lot EDIT: works like a charm.

Hey G3 - many thanks! This looks really cool and promises to be a big improvement over my previous MFCD_FC3 setup for the Eagle. Question: I'm using touchscreen with HELIOS, is there a way to prevent leavu from stealing focus from DCS when I accidentally touch one of the MFDs? I was thinking of maybe there's a trick to have transparency overlays in HELIOS that could cover these leavu screens. I looked around in HELIOS profile editor, but no luck for this yet. If anyone has ideas on this? Cheers

Hear hear :D Thanks again for sharing this useful info - saving others lots of work Will be following with interest

Gotcha - guess there'll be no avoiding the painful hardware route lol Verstuurd vanaf mijn GT-P7300 met Tapatalk

This actually makes me wonder: doesn't some kind of software solution exist to stabilize the DirectX inputs i.e. filter out the noise / spikes from faulty joystick pots?

Thanks for posting this stuff guys - very helpful. My Combat Rudders left toebrake has become noisy and it's jumping all over the place if I inspect it in DCS Config Axis Tune window. No wonder I keep skidding of the runway during landings lately lol. Looks like I'll have to think of some way to dig a way to this pedal stuff deeply buried in my pit which will not be easy considering I forgot to place any kind of maintenance access there for this type of equipment failure :music_whistling:

Notice on DCS 1.5 Hi everyone Since with ED's release version upgrade from 1.2 to 1.5 this can be a source of potential confusion, a small note on the patch for DCS version 1.5 (the note attached to first post): *) If you are on DCS 1.5 RELEASE version (install folder 'DCS World') do NOT apply the patch. *) If you are on DCS 1.5 OPEN BETA version (install folder 'DCS World OpenBeta'), apply the 1.5ob patch (note attached first post). *) If you are on DCS 2.0 OPEN ALPHA version (install folder 'DCS World 2 OpenAlpha') apply the patch following the note, replacing '.openbeta' with '.openalpha' This is where we are at the moment, the idea is that some time from now we will all have a single DCS install folder and the patch will have become obsolete. Hope this clarifies for now. Thanks @figgy Grtz

Hey Enduro - thanks for your kind comments man, I really appreciate it. For the Warthog: yep, you can either use TARGET or Autohotkey, check out the documentation and Davisons 2nd post - I believe you've seen that one already. Feel free to PM me if you need help with that. VAICOM works with 1.2, 1.5 and also with 2.0 alpha A few remarks on 2.0 Nevada alpha at this time: *) ED has not fully implemented all comms yet in 2.0 Nevada, so results may vary a bit there *) notably ATC is not fully implemented yet in 2.0a and the Static ATC mod does not apply properly yet *) I recommend to start with 1.5 first. but if you want to try things out with current 2.0a apply the 1.5 patch (first post), replacing '.openbeta 'with '.openalpha' All of this will evolve of course as ED development of 2.0 progresses and DCS versions converge. Cheers

Yeah that's it: you hold the PTT key until command is executed (i.e. until you hear the beeps). So modifiers may interfere with the sent commands. Of course feel free to experiment but if it doesn't work don't be surprised :D

@Dudikoff No profile error. Use only VA v1.5.8. If you're just toying around this could have all sorts of reasons most obvious one DCS window not having focus. Modifiers should not be used as PTT key is held during command execution. @mr_mojo97 :eek:

Great stuff again there on the Huey captain! Can't wait until the day you'll be starting work on the F/A-18 when it comes out :thumbup: PS donation sent

@Renegade welcome bro :thumbup: @Megatherion PM sent.

Above issue was resolved. Key lesson learned: if using AutoHotKey, run it as admin. :joystick:

Hey Bobby Well not sure I can help you with that... I do see you're installing the beta version, try regular release 1.5.8 instead. Try running the installer as admin, and most of all get the VoiceAttack full version license for 8 USD, as for VAICOM you will need it :-)

@minimi66 You seem to have a setup problem with your HOTAS. "When i key the PTT Mic switches on my TM Warthog throttle, they do bring up the correct radios in sim VHF, UHF etc " These menus should actually not occur. You may need to check the documentation, you likely have the HOTAS MIC joystick bindings in your DCS config not removed. This would also explain the apparent ' toggle' behaviour. Try testing with the keyboard first. If that all works fine, move on to your HOTAS setup. Read the chapter on this in the manual and let me know via PM if you need more help with this. @Megatherion The background chatter volume is intentionally low but should be well audible. Make sure you have DCS master volume set to 50%, see manual.

VoiceAttack: use 1.5.8 release version only. @ Mick no worries :) On a different note as a gentle reminder to everyone: stick to VoiceAttack official release version 1.5.8. and do not use the VA current beta version. There seems to have been introduced a glitch in their latest beta (1.5.8.14), I'm in touch with the VoiceAttack guys on this. So for now: use VA version 1.5.8. only.

Hi there, The double Pause command has given most consistent results during testing. Just a single one may work for the occasional mission but will not work most of the time. Investigations continue on that one :-) For the Select command try the suggestion I gave to Shaz i.e. speak deliberately separate words i.e. Sochi. .... Select. BTW as I'm sure you've picked up in the documentation Select command is only available in Easy Communications ON mode.

Hi, It's my pleasure to announce that a VAICOM 2.0 profile has now become available for the mighty Mi-8! You can now immerse yourself deeply in flying this great helo through realistic AI radio communications. VAICOM uses voice recognition to fully replace the F-key based comms menus, allowing for a realistic experience and fast response times when flying complex missions. More information and download via this thread http://forums.eagle.ru/showthread.php?p=2534446 Video: https://www.youtube.com/embed/kNyJUs3WaNE Enjoy! Hollywood

--- NEW MODULE AVAILABLE: MI8-MTV2 --- --- NEW MODULE AVAILABLE: MI8-MTV2 --- Good news for all you helo lovers out there. The Mighty 8 is now supported! You can download the MI8-MTV2 profile from here: https://www.digitalcombatsimulator.com/en/files/1740703/ Have fun!

Guys All this has already been adressed in this thread earlier. I need you to read the documentation and the info on this thread carefully as I cannot keep repeating myself. To recap: *) There is no typo in any code (the space you see gets generated by the forum editor) *) The URI messages, invalid radio, etc. are NOT RELEVANT on the desktop. Don't stare at the log. You should use Start Mission to get into the game and these messages will be gone. *) If they are not, apply the note on 1.5ob (first post) *) Other issues, check the note on keyboard layout, run VA (and AHK if you use it) as admin. *) Keep the PTT key pressed until you've heard the beeps *) Use MS Speech Library as needed to improve your recognition rates If all else fails feel free to send me a PM. Grtz

@lone82 If you look down this thread you'll find more info on these items, such as regarding Speech Library. PM me if you need more help. @GregP Yes normally it will automatically unpause. This works for the majority of missions. However for reasons still unknown, on some missions you'll need to unpause manually.

Hey sobe This varies a bit per module. For modules with multiple radios and multiple PTT keys, there will be an AUTO function (NUM0) for optional use with Easy Communications ON. For some modules however there is just one radio and/or just a single PTT key. In those profiles, only the NUM1 key is used for PTT and there is no AUTO function. You can check this for each VAICOM profile in the PDF documentation that comes with it. For your situation I recommend to adapt those profiles by editing the push-to-talk commands and change the NUM1 key to NUM0. Send me a PM if you need any help with this.

Hey guys I'm putting the Mi-8TV2 up next, work will start once sufficient funding is in place. In the meantime looking ahead: can someone fill me in on the current status of T-1A Hawk radio comms? Last time I checked this was still WIP. Thanks a lot Hollywood

Hi, I'm pleased to announce that a VAICOM 2.0 profile has now become available for the Mirage 2000C! VAICOM uses voice recognition to provide deep immersion, replacing the F-key based comms menus, allowing for a realistic experience and faster response times when flying complex missions. More information and download via this thread http://forums.eagle.ru/showthread.php?p=2534446 Video: https://www.youtube.com/embed/kNyJUs3WaNE Enjoy! Hollywood