Hollywood_315

Update on VAICOM 2.5 Many thanks @WhiteGuy for the generous comments You really need to tell us more about those two girls in ###### sometime lol :thumbup: ---- UPDATE ON VAICOM 2.5 ---- Let me briefly share with you all what's currently in the pipeline for VAICOM 2.5. I've been programming in lua and C#/.NET over the last three months. Still much more stuff to do but I've made some great progress in several key areas and all base functions are already up and running. I'm excited about the new release which I hope to get out before end of this year. So what's it all about? Well I can't share all details here but as a preview here are some highlights. VAICOM 2.5 will be a .dll VoiceAttack plugin using advanced interfacing with the DCS core event/fsm engine to really seamlessly integrate into the DCS World experience. Things like UDP network protocol and JSON objects exchange are used for all interfacing under the hood. As a user, things becomes completely transparant. The Menu system is not used at all and is completely bypassed. This allows for an unparalleled immersive experience and the keyboard and menu-free interaction makes VAICOM 2.5 the ideal companion for e.g. VR users. Amongst other things this new foundation makes also for a much simplified installation. There are no more dependencies on any external mods, keyboard language layouts, DCS config settings, Windows configurations, DCS versions etc. VAICOM 2.5 will will be a straightforward install-and-go experience for novices and power users alike. VAICOM 2.5 will come in a FREE edition and a PRO edition. These work automatically with any DCS version. They will share the same foundation where the FREE edition has roughly the same functionality as VAICOM 2.0 with all the advantages of the new architecture. VAICOM 2.5 FREE This version will be free for all to download. It is a complete and full-functional package. Auto-module selection (i.e. single profile) supporting all DCS aircraft modules currently supported by VAICOM 2.0, Support for DCS theatre modules currently supported by VAICOM 2.0 i.e. Caucasus and Nevada, Advanced settings options such as for hiding menus, disabling player voice etc., Seamless JTAC/ATC flow handling using the core DCS fsm directly (no more flow sync issues), Extended command set reach (i.e. include commands not listed in menus), Multiplayer support, etc. VAICOM 2.5 PRO A license key for this version will be around EUR 6,00 (free of charge for VAICOM 2.0 donators). PRO edition has all features of the FREE version with quite a bit more on top: Auto-module recognition supporting ALL DCS modules, including e.g. all WWII aircraft, helos,.. Auto-configuration (self-learning) feature to automatically support any future DCS module releases (such as new aircraft and theaters), Cross-module extended command sets (ever wanted to do JTAC mission in an F-15C? now you can!), Support for future extension pack releases (chatter themes, cockpit voice control pack,..), More advanced settings options such as for voice (keyword) training mode, Extended configuration capabilities e.g. run VA/ICOM on a different PC than DCS World, etc. Details may still change and things will be specified in more detail around release time. I hope this is helpful for now to give you an idea. Of course in the meantime any questions on v2.0 keep 'em coming on this thread - plenty of knowledgeable users who can help you out. Happy flying! :pilotfly: Hollywood

Hey Dooley - no worries. Just to check do you have a US keyboard layout? If not it may be related to that, see note attached to first post. Also make sure to hold the PTT button long enough i.e. do not release until the command is fully executed (you'll hear 2 beeps). Catch me on PM if that doesn't fix it. Verstuurd vanaf mijn SM-G935F met Tapatalk

Ok the issue doesn't sound familiar but I'll see if I can reproduce. VAICOM 2.0 sends virtual key sequences; upcoming new version is built on a different approach. Verstuurd vanaf mijn SM-G935F met Tapatalk

Hey tribundf yes I got the PM thanks. Not quite sure what could be causing the ATC issue. On startup VAICOM defaults to the nearest airfield. With Easy Comms OFF you'll obviously need to select the frequency for the correct tower but you shouldn't end up in any menu if the command is properly recognized. Can you check the log if it's a recognition problem else perhaps check with @sthompson who worked on the NTTR airfields.

Can you check if these URI messages are gone after Start Mission. If not you may need to re-inspect the path in the fetch.cmd script. In the log it sets Easy Comms to false so I'm assuming you changed that in the profile defaults. If you enter a quickstart mission mid-air, try calling 'ATC, airborne' before you proceed with inbound, etc. Also try what happens if you use the airfield name instead e.g. 'Batumi, inbound'. NB as I'm sure you've read in the manual the Select command is not available with Easy Comms OFF. Have a look and let me know how it goes.

@tribundf Yes from the log it seems the settings readout works fine but it concludes that Easy Comms is set to ON. It may have to do which DCS version you're using. Check the note for openbeta users attached to first post and if that doesn't fix it PM me again.

Well from this log it seems that the PTT keys are not being used correctly. If things are well, the log should show something like below when you press/release a PTT hotkey: --:--:-- - Listening suspended --:--:-- - Shortcut : 'Transmit AUTO released' --:--:-- - Listening resumed --:--:-- - Shortcut : 'Transmit AUTO pressed' Since this is not the case here maybe you should check which keys/buttons you have configured for PTT and then try again with using these. Have a look and send me a PM if you need more help with that. Grtz

@Rogue Yes noted thanks - should be tackled in next release version @tribundf Could be something with your PTT setup perhaps? Sounds like the key release may not be properly configured. If you can send me a log screenshot I'll have a look.

Yes I can confirm that is the approach for VAICOM 2.5. It will be a plugin dll linking directly into the DCS lua environments using network protocols. This means it will become independent of the menu system, keyboard layouts, window focus etc. and also of any static mods. The new system will be dynamically updating itself during the mission. Having said that, this is all pretty complex stuff and we're still a while away before VAICOM2.5 will be released. So much appreciated keeping this static ATC mod alive for 2.0 users. It is possible to get a static menu structure in place for the the other recipient types such as JTAC, Tankers, etc. in the same way as done for ATC. However I'm not prioritizing work on that atm as it would be incompatible with VAICOM 2.0 and as mentioned v2.5 will bypass the menu system altogether.

VAICOM roadmap Hi everyone, Good to read the recent exchanges on the thread. I’ve been away for a bit but I’ll do some catching up in the coming days. If you have issues or ideas you want to discuss with me feel free send a PM at any time and I’ll try to answer asap. Also I will provide an update here shortly on what’s in the pipeline for the future of VAICOM. I’ve started work on C#/.NET and lua programming towards what promises to become an advanced next-gen version (working title VAICOM 2.5) with new additional options, simplified setup, and an even richer virtual flying experience with DCS for beginners and (VR) power users alike. All this is still a while away but I thought it would be good to keep you posted. So stay tuned! :thumbup: Thanks Hollywood

Hey guys travelling at the moment but I'll get back to you. In the meantime of course plenty of knowlegeable users on this thread so perhaps they can provide some comments to get you sorted. Cheers Verstuurd vanaf mijn SM-G935F met Tapatalk

With some digging under the hood I come to the following readout for Nevada currently I think we're looking at work in progress still. ID = 5000044, name = TonopathAFB, coalitionID = 0, country = 99(Enemies), LatLongAlt = (37.784040, -116.773303, 1686.814331) ID = 5000029, name = MellanAirstrip, coalitionID = 0, country = 99(Enemies), LatLongAlt = (39.818116, -114.733412, 0.000000) ID = 5000039, name = PahuteMesaAirstrip, coalitionID = 0, country = 99(Enemies), LatLongAlt = (37.094831, -116.315400, 1541.363525) ID = 5000037, name = NorthLasVegasAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.213365, -115.186738, 679.279846) ID = 5000031, name = MesquiteAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.827345, -114.060335, 566.487366) ID = 5000033, name = MinaAirport_3Q0, coalitionID = 0, country = 99(Enemies), LatLongAlt = (38.374547, -118.093499, 1390.512207) ID = 5000003, name = Creech, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.584430, -115.686811, 952.944580) ID = 5000013, name = BeattyAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.868394, -116.786083, 967.133667) ID = 5000021, name = HendersonExecutiveAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (35.967469, -115.133471, 759.436890) ID = 5000026, name = LaughlinAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (35.165905, -114.559864, 200.000198) ID = 5000042, name = TonopahAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (38.058024, -117.075917, 1644.139648) ID = 5000028, name = LincolnCountyAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (37.793390, -114.419237, 1467.689941) ID = 5000011, name = nellis, coalitionID = 2, country = 99(Enemies), LatLongAlt = (36.225662, -115.043808, 561.309143) ID = 5000018, name = EchoBayAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.310471, -114.469338, 472.033691) ID = 5000024, name = JeanAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (35.773786, -115.325703, 860.875854) ID = 5000008, name = LasVegas, coalitionID = 0, country = 99(Enemies), LatLongAlt = (36.076670, -115.162190, 661.430115) ID = 5000016, name = BoulderCityAirport, coalitionID = 0, country = 99(Enemies), LatLongAlt = (35.943682, -114.860552, 646.663635) ID = 5000005, name = groom, coalitionID = 0, country = 99(Enemies), LatLongAlt = (37.219139, -115.785311, 1369.867676)

@mosqui No worries I'll send you a PM later with some things to check. @DE There was an issue or two with VA 1.6 release, but during testing with current version 1.6.2 I didn't encounter any problems so far. Will test some more but unless stated otherwise you can assume VA 1.6.2 is ok to use with VAICOM.

@thompson - fantastic job on that fix! I did some initial tests with Nevada and it seems to work nicely. I've also done some succesful tests with introducing NTTR airfield names. However the current list is some 10 airfields and I don't think it's complete yet. So let's see how that develops. @Joe I recommend setting VA target to Active Window. Of course make sure then that DCS window has focus e.g. during testing do a mouse click somewhere in the DCS window and then test with VA commands. PM me if the issue remains.

Hey Cain The 'other' menu has support in VAICOM but it is basic since the content can be anything depending on mission specifics. It can be accessed using the Mystery callsign over VHF2, i.e. calling 'Mystery, Proceed' will execute the first menu item. Use 'Mystery, Options' to peek at the menu. You could then use F-keys to access listed options. I have also heard of users customizing this further for themselves by creating additional commands in the profile for this section. PM me if you need help with that.

Hi thompson First of all big thumbs up for your essential work on the ATC mod. Highly appreciated, and I speak on behalf of all VAICOM users here. Keep going! :thumbup: Regarding next versions yes I'm definitely considering new features and approach changes and this could be one of them. Currently this is all in early planning stage so not committed yet. Any VAICOM 2.5 release would be after the Merge, so it's still 2.0 for now. Cheers Hollywood

Hey Biggie make sure to use the updated F-15C profile (link in first post) and PM me if the issue remains. Thanks

Guys be aware that a fix exists for this mod for version 1.5 https://forums.eagle.ru/showpost.php?p=2986946&postcount=499 Props to sthompson Cheers Hollywood

Hey Biggie Check out sthompson's fix for Static ATC mod for 1.5 : https://forums.eagle.ru/showpost.php?p=2986946&postcount=499 I'll add this to first post also so it's easier for people to find.

Hey Lynx - congrats on those panels it's just mouth watering to look at the sheer quality of it. I appreciate you may not want to share all your tricks of the trade, but I'm extremely curious. What is the technique to get these white characters, i.e. how do you get the engravings to be so high-contrast white while at the same time having them be translucent for the backlight? Feel free to PM me. Cheers

The Mirage has a somewhat different radio setup as I'm sure you've worked out from the PDF that came with the M-2000C profile. Make sure to verify the Easy Comms setting is recognized correctly and check the PTT setup (VHF1) combined with the HOTAS rocker switch. PM me if you need help.

Hey Vampire, Mojo Make sure to apply the fix for Static ATC mod (for 1.5) here: https://forums.eagle.ru/showpost.php?p=2986946&postcount=499 @LT Check the updated A-10C profile, link in first post. This has the Break Low command fixed. For Request Azimuth etc. bear in mind that the program assumes you have started the mission from the ramp. If you entered a mission mid-air instead e.g. some Quick Start mission you should call 'ATC, airborne' before continuing with things like asking directions, inbound etc.

Hey pynio Question seems pretty specific to the Saitek, no expert myself but plenty of users out there I believe so maybe others can comment. It sounds as if when the Profiler is used the X52 is no longer visible as a DirectX device to Windows. If it was, V.A. would be able to see it also. I'm assuming you're using the refresh circular icon in VA before you config a PTT key. Perhaps this can be a question also for a Saitek/X52 specific thread.

Hi there You may want to check the latest in the VAICOM 2.0 thread here: https://forums.eagle.ru/showthread.php?t=151296 Cheers

Hey Engine They have looked into it. For the Start Mission / unpause a solution has been found, so that appears to be resolved. http://voiceattack.com/smf/index.php?topic=592.0 For the mission.lua readout hang we have the rather frustrating situation that they cannot reproduce the problem. I can accurately reproduce it myself and of course we have users here reporting the same issue also. It could have to do with file corruption from DCS perhaps but the problem was never there before. Need to run some tests with 1.5.12, if the problem persists there also then it may point to some new issue with the mission.lua file generation. http://voiceattack.com/smf/index.php?topic=593.0 The saga continues, for the moment I recommend to use VA 1.5.12 http://voiceattack.com/smf/index.php?topic=293.0