BMGZ06

You have to go mil or burner before you hit the deck and over the wires. You dont want to slam the gas forward just start easing it in as you get close to the wires. I got an _OK_ 3 wire last night on case 1 Persian gulf mission again and as I get over the ramp I start adding power in and go MIL and burner on the deck just for good measure.

yes it says f18. it even shows the name of the airfield when I hit PTT but the command then changes the frequency as if easy comms is on with instant select nearest atc. this is in multiplayer so it must be a server side setting. It works ok in SP with easy comm off.

YA it shows easy comms on even in the cockpit and I tried using select after and before the name. I was flying a mission last nigh with some guys and two of them had very similar issues with vaicom, and it caused crashes so they uninstalled it and just stuck with VA only and stopped having crashing issues. I deactivated it last night after it was somehow causing every radio channel to read as Guard and I couldnt fix it. Once I deactivated it everything went back to normal with voiceattack and had no issues with crashes or radio channels being switched when trying to transmit calls to in game AI with the comms menu. I mean it is really a pain when even in single player and not using SRS, the program is clearly what was causing the radio channels to switch to a different frequency after manually inputting them. I input the frequency for Batumi manually, and then give the inbound command and it automatically switches to another frequency for either the carrier or another airfield close by. This happened with easy comms off and instant select unchecked. After deactivating vaicom I can input frequencies and then do the normal in game commands with voiceattack I did before without this issue. I am just going to stick with Baileys VA profile as it works well and provides a lot of great functions. Maybe I will give vaicom another go in a couple months to see how things progress. Perhaps it is just due to the open beta updates and suppercarrier module causing some conflicts right now. The plugin is great when I can get it to work properly.

So I have easy comms unchecked in my DCS options. I go into servers that say no easy comms(local) or easy comms no and the radio is constantly forcing to the wrong frequency no matter what I manually select. The radios are really confusing to get work properly and the manual is not clear on how to fix this issue. I have Select tunes radio checked and extended command set checked in vaicom pref. If I am just in the DCS main page and not in any server or single player mission at all easy comms is still saying ON. What settings do I need in order for easy comms to remain off and get vaicom to work properly in a server with SRS as well? I checked the SRS integration box and nothing changes. The radio I tune manually still forces to some random freq based on I guess the closest tanker or airfield still. Sometimes I can get it to work but if go to change the frequency again for something else then I am right back into the same situation. Is this ultimately a screw up on the server owners part? I just went into another one and tuned into ARCO1-1 tanker that said 253mhz. It called Texaco. I looked up in their mission briefing and 3 tankers are have the same frequency??? The same went for the carriers. They were sharing the frequencies with two other airfields. It was Through the Inferno Socal server. Why on earth would they do this? They use SRS as well but if three airfield and tankers share the same frequency how is that even going to work with SRS alone?

It was obvious from the fact that it is no larger that the FOV was still going to be the same. Reading about wider FOV and pixel per degree then you give up a lot of PPD for FOV. The GPU power is not currently there to drive a human or near human FOV with super sharp res like the Reverb has. The manual IPD though is going to allow more people to get the actual FOV of 114 without seeing the black boarders. I see them because my IPD is 67 so I see boarders a lot but I like the sharpness. The new G2 will have overall more clarity and sharpness as well due to new lenses and they are kicking up the brightness as well which will be great for night missions. Less mura is going to really add more immersion as well.

You link the other profiles by going to the profile screen for vaicom where all the commands are listed then in the upper left hand box where the name of the profile is displayed there is an option button net to it. Click that option button and then there is an option to link other profiles right there.

That video is of now retired Captain Richard "Twig" Labranche when he was still a young LT. He went on to fly Tomcats and Hornets and was an LSO as well. He is a very highly regarded aviator. This was not a cold cat shot. There was an engine failure. Here is the accident report. He was also on the 1995 Carrier Fortress at Sea documentary where he talks about this crash. There was an Super Tomcat that lost and engine on super sonic flyby in the documentary as well. https://aviation-safety.net/wikibase/57190 Here is the documentary. It is a good watch. I started it at the point where he talks about the crash.

It would be nice to have failures like this modeled in somehow. Not sure how they would do it so it would happen not too much or not too little. Being able to bust a cable would be a nice touch but I know they are going to put the barrier net into the works so that means they must be planning some sort of failure process maybe with cables and also if a plane has a gear or engine failure. I think most people tend to turn off random failures though in the options.

Yup my Voiceattack has crashed 4 times today. I am also having random issues with easy comms off when i manually tune a frequency it will force back to a default radio frequency on the manual radio channel. It is not working well when SRS is active either. It is like it is getting confused. The only way vaicom works normally is in single player with easy comms off. I noticed that since i have easy comms off that when I get into a server that has it on it forces vaicom into that mode and it shows in the vaicom config window in the PTT tab that easy comms is on. This was causing the radio to revert to the Manual channel and a default frequency when I try to tune to specific airfield, carrier or tanker. It was reverting to a channel for the closest ATC which it says was a Hazard class ship that of course cant respond and just say go to alternate. As soon as I left the server and went into single player then it said easy comms was off. Still had some weird issue where the same frequency that was being forced in the multiplayer server was forcing in single player manual radio channel. I had to close VA and start it up again then it started to work and I could tune manually and get the airfields to respond normally.

Never mind I figured out why speech recognition was not working and coming up with vaicom.

When I activated VSPX I did the finish process and pasted the new commands in and looked in there and the airfield names are there. I am still trying to figure out how to get the keyword training to work also. When I click on the microphone button in vaicom to open speech training it just opens up my windows speech training screen which I already did. I do not get that small pop up like it shows in the manual that is just for specific words you want to train. I cant open the speech recognition dictionary. I spent awhile trying to figure it out.

Ya I will do that for sure. Have you had issues contacting the airfields on Persian Gulf map? None of them respond at all. In SP or servers with easy comms on I see the frequency tune in automatically or when I have to manually tune if easy comms are off but zero response through vaicom. They respond with in game menu comms though.

Yes I figured all that out last night but for some reason airfield calls on PG map dont work. There is no response at all and I see the radio tuning to the proper frequency for that field since I am using easy comms. In multiplayer that are not using easy comms I know I have to use SRS or tune it manually and the calls to carrier work for the most part but often times I have to say the command multiple times. "See you at 10" tends to be the biggest issue for some reason. I like the plugin a lot so far.

Be sure to first say the name of the Carrier then inbound or Name of Carrier then Marking moms. Works well. Same goes for airfields on caucasus map. The airfield inbound calls do not work for me on persian gulf. I also found that using the VSPX option works better for me also. I am using easy comms and have the preferences in vaicom selected for it also.

I actually figured it out finally. With easy comms you cant rely on just saying Inbound for carrier or Marking Moms, Marshall etc. I had to say the name of the carrier and then inbound and it works better with VSPX enabled. The only thing I noticed now is that calling into the airfields on Gulf map doesnt work at all. I call the airfield and it makes the call but doesnt say the name, just has some abbreviations that start with "O" and they are all the same for every airfield, then there is no response. The calls into all the airfields on Caucasus map works perfect. Have not tried Nevada since I hate that map. I updated all the commands for the VSPX switch over as it says to do with everything that gets copied to the clipboard. Calling the ships works just fine by saying the carrier name then inbound or marking moms. tested it with two carriers in ME and called into both just fine.

I had the same issue. You need to say "Carrier Name, then Inbound" or vice versa. You can also do it with marking moms call. Speak really clearly or turn on VSPX mode per instruction manual. It helps you to be able to speak faster but you have to update the AI COMMUNICATIONS commands as prompted when you click the VSPX option in Vaicom preferences then go to editors tab and click finish and follow what the popup dialog tells you to do. It will copy all the commands to windows clipboard for you. The manual tells you how to update the commands in the vaicom profile. look under "VA profile has very long list of separate commands" section of this link: https://forums.eagle.ru/showpost.php?p=4311067&postcount=5

Sorry I should have been clear. That is the way I did it actually. I just checked it. I linked the profile in that options menu as you stated. Still only 76 commands show, but all the Baileys commands work fine.

Anyone know why the number of commands in the profile screen would now be saying there are only 76 commands? There was around 500 before. I cant search for a lot of commands to see the voice command and key binds for the missing ones now. I also have Baileys F18 profile imported to it and there was almost 900 commands then. Those still work but I have to switch to that profile to see any of them now and make edits where I was able to see them all in the Vaicom profile after I imported them.

I am sure it was a brighter in real life but the camera they used was likely not adjusted properly to show it how is actually looks in real life.

To give a decent idea of what it looks like in real life but it is an old video and the camera is likely showing it a bit darker than it actually is. Still though it aint like coming into land at LAX for sure:)

Ya I posted about this in the VR subforum but no response from anyone at ED. I think they are trying to iron out the lighting issues from another post I saw from Bignewy or Nineline. Lighting is not uniform in 2d vs 3d gaming it seems. So right now the view distance of deck lights and ball is bad but the ball is super bright once you do see it making it hard to tell if it is high or low. Then in 2d monitor gaming I have seen people say the ball is not bright enough but deck lighting can be seen from much farther away. I just don't bother with night ops right now even though it is fun. In my VR with gamma 2.5 It is still like flying in an ink bottle it is so black. I think if some of the real life carrier pilots on the board chimed in they will say it is in fact really dark out there especially on moonless or cloudy nights. Also I do not think the deck lights are bright at all and are hard to make out to begin with. It is scary stuff I would think. Nothing like coming into land on a airfield in a city at night which I have done in real life and it is not a big deal. You can see a lot due to the light pollution. We just need to be patient and realize that they are going to sort these things out at some point, and it is early access. People tend to forget that early access means we have to put up with weird stuff for awhile.

Yes this is a weird bug for sure. I have voiceattack set to trigger this but when you land wha tyou need to do is bring up the comms menu and it will likely be on the ATC menu with nothing there. You have to hit F11 or say F11 if you are using voiceattack and go back to previous menu then you can trigger launch again. It works for me but it is annoying that they are stuck in recovery mode.

Ya Vaicom will allow you to force a lot of the commands you normally have to go through the entire inbound call process after wave off or bolters. It can be a little tough to understand how to get up and running at first. I am having issues with it recognizing my inbound to carrier calls. Sometimes it works and others it doesn't mostly due to speech recognition limitations that I think has to do with my microphone quality and speech training within windows. I need to be deliberate with every word. You can also combine Vaicom with Baileys F18 V2.0 profile which is awesome and provides a ton of other voice commands with actual audio responses he programmed in. The install of Vaicom is shown in a youtube video but the res of the more intricate setup and programming is not shown and you have to read through the manual to understand a lot with how it works. Just a side note: Buy the Pro version with realistic ATC and AIRIO for the F14 but dont bother with the Chatter extension since it is just a novelty. It just gives you a bunch of canned radio chatter background on the radios contently. It is fun for about 5 minutes but I should have save the money.

It looks like with easy comms on I have to slowly say "Inbound...Roosevelt" and it works most of the time. Still some issues here and there. I am going to try it in the VSPX mode to see if it works better later. I am also turning on the ARC-210 radio in the cockpit. It will not work for me without doing that which I did not think was needed unless using SRS. So I have some more training to do I guess. Normal voiceattack commands worked just fine for me and using Baileys F18 2.0.vax profile is also nice with Vaicom. It provides a lot of missing commands to make life easier. It is also easier to tune to different radio channels and set tacan, ils, and radio frequencies with his profile I find. They both seem to work together without issue though.

The inbound call works randomly and there is no clear reason as to why. Makes no sense.