Chief Instructor Posted September 20, 2016 Posted September 20, 2016 Hi, I have just discovered Voice Attack (and VAICOM which I love the look of). I only really fly around Nevada at the moment. I can't see a definitive answer as to whether VAICOM works in DCS 2.0. Does it? Also, as importantly, has anyone created an F-5E profile for it, or can i easily mod an existing one? Cheers! :thumbup: CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System
colyoap Posted September 20, 2016 Posted September 20, 2016 As far as I know voice attack is not yet compatible with 2.0 due to there not being a static ATC menu yet. I'm also excited for this to be implemented soon, hopefully Callsign: "Milkman" I7-8700k@4.8--Corsair H115i pro--EVGA FTW3 1080ti--GB Aorus Z370--256GB M.2 SSD--16GB ram--Win10--1000wGold Rate PSU--CV1 Rift--TIR5--X55 HOTAS--TM pedals--TM MFDs--Custom UFC
colyoap Posted September 20, 2016 Posted September 20, 2016 My guess would be we won't have a static list until all airfield are added to NTTR Callsign: "Milkman" I7-8700k@4.8--Corsair H115i pro--EVGA FTW3 1080ti--GB Aorus Z370--256GB M.2 SSD--16GB ram--Win10--1000wGold Rate PSU--CV1 Rift--TIR5--X55 HOTAS--TM pedals--TM MFDs--Custom UFC
Slick Fork Posted September 21, 2016 Posted September 21, 2016 I'm using it with limited success in 2.0. If defaults to the closest airfield so sometimes that bit's ok. Wingman commands etc. work just fine.
Chief Instructor Posted September 21, 2016 Author Posted September 21, 2016 I'm using it with limited success in 2.0. If defaults to the closest airfield so sometimes that bit's ok. Wingman commands etc. work just fine. Did you have to modify anything to make it work in DCS 2.0? I'm finding that when I speak "start mission" to start the mission once loaded, it tries to initialise but suspends listening because it can't the temp files it wants. On closer inspection I can see that it's running a cmd batch file which is trying to copy .miz files from my users directory which don't exist. I'd certainly like to find a way of making it work :-) CPU: Intel i9 13900KS @5.8GHz | MB: ROG Strix Z790 Gaming-E | GPU: Asus ROG Strix RTX3090 OC | RAM: 32Gb Corsair Dominator DDR5 @6200MHz | Cooling: Custom CPU/GPU cooling loop | PSU: Supernova 850G2 @ 850W | OS: Windows 10 Home Premium 64Bit Storage: 3x Samsung EVO 970 Plus M.2 1Tb + 3x Samsung 850 EVO SSD 250Gb | Input: TM HOTAS WH Saitek Combat Pedals | Output: Samsung 50" OLED TV | VR: HP Reverb G2 | Audio: Realtek + Z906 5.1 Surround Sound Speaker System
Tic-Tac Posted September 21, 2016 Posted September 21, 2016 there's a fix for the same issue with beta which might apply to the Alpha also, this fix is at the beginning of the VAICOM 2.0 thread, except change to the relevant 'Alpha' location - not tried it myself " In the mean time if you're on 1.5ob you can try this. With a text editor (notepad or Notepad++) edit the file called 'VAICOM_fetch_data.cmd' in VAICOM\Tools folder and change this line 'COPY /Y %USERPROFILE%\AppData\Local\Temp\DCS\tempMission.miz TEMP\tempMission.zip' into: COPY /Y "%USERPROFILE%\AppData\Local\Temp\DCS.openbeta\tempMission.miz" TEMP\tempMission.zip "
Slick Fork Posted September 24, 2016 Posted September 24, 2016 Did you have to modify anything to make it work in DCS 2.0? I'm finding that when I speak "start mission" to start the mission once loaded, it tries to initialise but suspends listening because it can't the temp files it wants. On closer inspection I can see that it's running a cmd batch file which is trying to copy .miz files from my users directory which don't exist. I'd certainly like to find a way of making it work :-) No, I didn't do anything to it. "start mission" works fine as do all the wingman commands and if the airfield I want is closest that works ok too. I'm trying not to mess with it too much as once the merge hits (hopefully by Christmas) it'll all change again anyway.
Recommended Posts