Firebird1955

Pre ordered through B&H at Oshkosh on 26 July and they still (as of this morning) cannot tell me when they will have them in stock. Just shows backordered.............:(

Voice attack with Vaicom pro add on or similar to reduce keyboard workload. Especially to get away from the Fkey menu issues. It does work, at least for me.:pilotfly:

Just as an FYI it was beta. Thanks for the info.

I have observed recently that when 2 tankers (Texaco=C130 and Arco=S3) are airborne at the same time when I call for intent to refuel, the tanker that is selected is always Arco even when I am very near Texaco. When I say "Texaco" pause till beep then "Approaching to refuel", it will only send a message to Arco. IF I say "Select Texaco" release TX and then say "Approaching to refuel" it will change to Texaco every time (instant selection is checked in preferences). This only seems to apply to the situation with multiple tankers as other aircraft/ATC within the mission are recognized as always, with a simple Callsign, pause, then command. It wasnt this way until the update that changed the key bindings, at least on my end. I tried changing the device to "13" from "38" as in earlier posts, but could not contact anything until I put the "38" back in. This is not a major issue as I can easily say "Select Texaco (or Arco)" prior to intercept, but thought I would throw it out there in case others are seeing the same issue.

BD, It has to be registered like Viacom pro and you should have received a seperate "key" in the email for the chatter. If it is in the app folder as described earlier, then (Assuming that you have a Warthog throttle) you should be able to push the comm button "IN" and it should start/stop chatter as a toggle. Hopefullly this helps.

Chatter key goes in same box as the Vaicom key went in, then email addy. Somehow it knows the difference. Then, if you look C:/voiceattack/vaicom/apps (could vary) there should be a chatter.dll (I believe that is it). If it is not there, then move from the chatter download to that folder.....At least that is what I did to make it work.

I have been playing with it as well with some success. In my case, while I am using 2.5.3, my Vaicom.export.lua had a version of 2.5.0 with no F-18 listed (probably a poorly executed update on my part). I uninstalled vaicom from voice attack as well as the associated export.lua files in saved games and app data (anywhere I found Vaicom.export.lua). I reinstalled 2.5.3 and when I checked the Vaicom.export.lua it had an F-18 listed. It appears to have corrected the failure to send the command to DCS and all went well except for being able to switch between the two tankers I have in game. This could easily have been a failure to set up the VAICOM panel up correctly. I made no changes to any of the export.lua files, just let them regenerate...

Hmmmmmmmmmm... Wonder if MP host had easy comms off (he said he did not, but it could still happen)...

Probably gonna have to be the .lua guru as I had easy comms on and had the issue. Didnt try easy comms off though..........was also using multi to single in the VAICOM setup.

Agreed. I did not try other airframes but DCS did have the following in the changelog from the 18th so something was done to the radios. COMM: Manually entered frequency will no more appears in channels settings Hopefully it will be that simple..

First, let me start by saying this is NOT a flame post, or any other form of Negative observation... This weeks Mini-update (7/13) Update Changelog (7/18 ) and Weekend news (7/20), along with a few other posts has me confused as to what actually did/didn't make the update in relation to the F-18 this week. Wag's notes (7/13 state that the following would be in next update: 1- Aircraft no longer slide on the carrier deck, at any carrier speed. 2- STT track will not switch lock uncommanded. 3- RADAR SIL (radar silence) and STBY mode has been implemented. See image. 4- RWR display logic has been further improved, with critical threat lines added. See image. 5- Option on ME to select single or ripple release (was not in fact merged for last update) 6- DUD cue added for when HT or fuze setting is below current aircraft AGL. See image. 7- RWS page SET and weapon and count added when a weapon is in priority. See image. 8- Night Vision Goggles (NVG) added. See image. 9- Instrumented Carrier Landing System (ICLS) added. See image. 10- Landing gear drag lowered. The Changelog provided on 7/18 said the following made the update: Second (third, fourth) client now can be spawned on 2nd (3rd, 4th) catapult when 1st CAT is busy Radar in STT mode will not jump to another target without players action Radar SIL and STBY modes realized S (single) and R (Ripple) weapons loading options added Selected A/A weapon is no more displayed on radar page in RWS mode Night vision goggles added COMM: Manually entered frequency will no more appears in channels settings Random crash when F/A-18C spawned on carrier catapult in multiplayer fixed Carrier ICLS system realized Radar: roll and pitch stabilization system improved when user changes elevation by discrete button commands Then Today (7/20) The Weekend news says the following: Aircraft no longer slide on the carrier deck, at any carrier speed. STT track will not switch lock uncommanded. RADAR SIL (radar silence) and STBY mode has been implemented. RWR display logic has been further improved, with critical threat lines added. Option on ME to select single or ripple release (was not in fact merged for last update) DUD cue added for when HT or fuze setting is below current aircraft AGL. RWS page SET and weapon and count added when a weapon is in priority. Night Vision Goggles (NVG) added. Instrumented Carrier Landing System (ICLS) added. Landing gear drag lowered. The weekend news is exactly the same as Wag had posted on the 13th yet when questions about the Landing gear drag issue, ED Tester said it did NOT make the update. Additionally, during a MP mission last night, the aircraft were still sliding all over the deck with the speed above 19 kts (we reduced speed from 27 to 19 kts and sliding went away immediately). Now I fully understand that even though some things are mentioned prior to an update that things change and they do not make it. I also know that some things get fixed sooner and are put in. What is confusing is when items pointed out for an update do not show in the update changelog, but DO show up as updated in said update in the weekend news. PLEASE TAKE THIS AS CONSTRUCTIVE CRITICISM AND NOT AS A NEGATIVE POST!! This is an amazing simulation that has so many moving parts it is unfathomable to many of us. Everyone should be proud of producing an outstanding platform with the F-18 release. Thank you all for what you provide...!!!

Having the same issue here as well. Mission last night (MP) where clients both had the issue of VAICOM not sending command through DCS after it shows as recognized in VA. Funny thing is that the host did NOT have an issue. WE checked easy comms, and all of the normal things that cause the issue but nothing changed. It was exactly as the others have mentioned. It cues it up, but unless you hit a transmit key (Interestingly enough the one I had to push wasnt even mapped in voiceattack) it will not transmit it out in DCS. It is as if when they changed the key bindings, it affected the transmit on the radio. Verified that no key was programmed to the Comm1/2 transmit keys in DCS profile. Also noted that simple commands (canopy open, NVG toggle, etc., which have been added to profile work without issue. It seems to only be VAICOM AI Communications commands that are affected (Tanker, Stennis, Crew, Darkstar) I will try the same mission tonight in SP to see if it happens to be a Multiplayer issue.....:joystick:

Ok Thanks for the reply. This was on a private server and it was always the last part. Just so I understand, it delays 10 minutes at the start, so the last 10 minutes are not there for the client. The host seems to have the whole thing always.

I had this same issue when I first started Carrier ops in DCS, and I also had the same issue in P3D using the super hornet. While I cannot verify why it stopped, it stopped when I stopped holding brakes on when pressing the U key. Could be coincidence but I didnt change anything else.

Quick question concerning Tacview playback. When I originally installed Tacview, all worked well, but when I upgraded (at least it was around that time), it always stops recording shortly after the last engagement and does not go to the end of the mission. Am I missing a setting somewhere?

Tab key cycles it off and on

I had a similar issue and it was caused by the export.lua file. On the last update to viacom pro, I believe there was an issue as to how it was put into the export file. He did an updated 2.5.3 and once that was in place, my issue went away.

Ok, not sure I can help much as I am no guru, but here goes. First your .dds files must be 10.6 meg in size I believe (I asked the question but still have no response) so I saved as DXT1 no alpha when converting to .dds. Any other DXT selection made the file larger that 10.6 and did not show in the folder. I used notepad++ to edit the description.lua, used the find and replace feature and placed the old file name in the find and the new replacement file name in replace with and then Replace all. There are several excellent sticky's in the Mod/Liveries section of the forum that go into better detail as this is a very simplified, and hopefully useful explanation

I am looking for CO/XO for VX-9 as line jet is already in the module. I have tried to create them but the ability seems beyond my scope of equipment at this time and was wondering if anyone was doing them. Would be willing to purchase a set of PSD version if someone has available. PM me if someone is willing. Thanks.

Would this be VR compatable?

OK, have tried for a couple of hours and do not seem to be able to find anything in the forums so here goes. What is the process for saving the updated DDS livery file. I have tried DXT5, DXT1, and all show a file size of 21 megs instead of the 10.6 in other files. I am using Photoshop, and have the Nvidia plug-in for DDS, but cannot get them to take. Anything that can be shared would be appreciated. Thanks:helpsmilie:

You guys never met Murphy? He has a law about this sort of thing.

Especially the kids...........Military training just provides the survival skills. LOL

Wonder if this has been fixed in this latest patch? Guess not. At least according to Release notes for AV8

Thanks BIGNEWY. Will try to send when I get home tonight. Knew it had to be something simple