adirtynurse

Can you screenshot your VAICOM interface

Which commands? About a year ago or so, I had to uncheck Import F10 menu, because after awhile it seemed to confuse VoiceAttack with many similar commands. So I just made a new profile, unchecked the Import F10 Menu function and haven't had a problem since. I too wonder about Hollywood though.

In the Exposure mission, after Fence out checks S4 says "Flight, go Button 14", to which S3 voiceactor replies "Sniper 14, Sniper 3". The subtitles are correct though. Also when RTB and S4 voiceactor says "Sniper 4 flight, go button 6", the subtitles say "Sniper 3 flight"

Dialogue oopsie I think. At first when starting to taxi, the script says "Hold 03 Right", while the voiceactor says "Hold 03 Left" and the all the triggers are set for 03L. The Chevy AI flight can be heard saying their "Rolling" calls on Red Ch2, which hasn't been the case in the campaign up to this point. Twisters RTBd through the container and skipped Charlie entirely. Since my #4 did the same without saying anything, I'm assuming they're Bingo and bugging out. If not then did I miss any dialogue? I went to Charlie as briefed and got to report "Saddled", but didn't hear anything from Twisters after that. I expected a debrief as for the previous flights, but it wasn't there. I was on fragged freqs. Once Metal and Twister flights landed (some of them overtook me on as soon as I was wheels down, still rolling, glad they didn't crash into me) they had parked in random places. Also the two that overtook me on the runway, diagonally crossed the dirt patch between the RWYs from TWY Bravo to get to Ramp Alpha North. Still got a 100%, so over-all I'm happy. Just felt the end got a little weird with the AI going off script. PS! If needed I can provide a trackfile. Currently its almost 10MB, so I couldn't attach it to this post.

Took some off the webs, that looked funny and are easy on the tongue. IRIS – I Require Intense Supervision. Female NFO who would get blackout drunk and wander off to do stupid things. LAMB – Notorious lady pilot who always had something low-cut when in civilian attire, thus LAMB (Look At My Boobs) NAG – Not A Guy First Marine Corps F/A-18 female weapon system office (WSO)

They're reminding people almost daily on discord, that its being worked on and announcements are made when they are needed.

I think this could get a slight overhaul. I understand that IRL only ground crew can change the LGB PRF code. I've heard that WW2 bombs are getting fuzing options in the rearmament menu, so it be great if we could change laser codes on the bombs the same way. Or at the very least make the laser code change condition nearby ground crew (like in HB's F14) and not prior to engine start as it is currently. Unnecessary pain. At the end of the day it inconsistent with the Hornet, being able to change it from cockpit, mid-flight. I might be wrong now, but afaik even the Hornet cannot do that for every LGB. Only JPF equipped older gen LGBs are cockpit-selectable.

Its a MP thing. I have it too. How I got around it is using "Jester Options" command to open the Jester GUI and doing it by way of the menu.

Anyone else getting issues with VAICOM after last OB patch?

Let's be honest. This shouldn't be a "only Supercarrier" thing. It should be a core game mechanic, if at all. Planning a mission, selecting and composing a flight from members for datalink purposes and preplanning waypoints and targets as a game mechanic is needed across the board. The Ready Room and Airboss stations/visalisations can be left for the Supercarrier, sure. But the planning element itself should be all encompassing.

Hopefully once this hits the modern aircraft, we can also pre-set the PRF codes on LGBs and remove the in-flight capability from aircraft that don't have it irl.

Well here's to hoping the madlads over at VAICOM come up with a solution. Iirc ED hasn't released their MC API to 3rd party devs yet, so I don't think we'll see VAICOM support for ED's AI until then. If that's true, then that's probably what's keeping others from developing solutions.

5) Radome on/off in the F10 menu like wheel chocks and NVG/HMD for some a/c

I could be wrong, but I think VAICOM hasn't been updated yet. Most likely it'll happen in a week or two. That's how long it usually has taken. I don't think we'll get VAICOM to action George AI though, solely because Petrovich still isn't supported.

I see this topic going on in circles. Some people seem to dislike GR's videos just based on bias/community stigma. And there are two totally different discussions going on at the same time here. Before I go on, I want to say I try to use everything available when I learn a module. From the ED training events to GR to RedKite to Chuck's guide etc. Each of them have a time and a place for me when learning a new module. In my opinion GR's tutorials aren't on the same quality spectrum as some other's. In a good way. GR does something nobody else does. All of them do what they do very well. Let me explain. I really like GR's guides. They're not "in-depth" by DCS community standards, rather they're a beautiful assortment of quick and dirty 5min mouthfuls of information when you want to learn a specific function of the aircraft and not the gee-wiz stuff of why it functions the way that it does. Now let me finish. Day 1 I want to have fun while learning the module and get some instant gratification while doing it and GR's videos help me to do that. I want to learn how to drop an LGB from an F/A-18? Here's a 4min video. Now you have everything you need to drop LGBs in a Hornet if you just do exactly what was shown in the video. Other creators' videos in comparison have the total info of what GR compiles into a 5min video over the entire 30-60min video (not bashing them, I'm talking about them in the next paragraph). You usually need to watch the ENTIRE thing to get one specific thing to function, because the information of key bindings, terminology and button and menu navigation is all over the place, because the video is meant as a one whole piece, that you read like a book, not like a collection of poems. That's my Day 1. Day 2 Once I'm done with GR's videos (of the functions that actually interest me) and have gotten to do stuff just messing about and my interest is peaked. I start looking into Wags', Redkite's and others' videos that I can find. Now I want to know why am I doing something the way GR showed it to me and are there other ways to do it. What are the actual limitations of the systems etc. After this and a bit of testing I usually take the module out to the MP servers with relative confidence. Everything before this is either SP (maybe training server). Day 3+ Chuck's Guide, Chuck's guide and Chuck's guide. If I can't remember something (haven't played a certain module for a time for example), I usually just open the navigation pane/content list of the guide and look up what I want to know in a couple of easy steps. In essence these guides are the mid-point between the videos above. They're easy to follow, but its more still more cumbersome than a video. And they're not as detailed as some of the videos. And these usually take the longest to get released/updated. That has been my flow of learning modules. Every content creator has a time and a place for me and I watch them all. A big thank you to all of them! Now as for GR being pissy about releasing further guides, while I'm disheartened to hear it, I'm on board with what has been said here already. Its the right move. Every DCS video done by the community should be FOR the love of the game and love of the community. If that doesn't do it for them anymore, than sad to see them hang up their spurs. I just hope there will be someone else to step into their shoes and start doing the quick and dirty specific small piece videos that I need. There are other creators out there already that are not far off, but so far its more like a series than a one-off video with them, so you're still expected to know things before watching their videos. I guess that's what it comes down to. Expectations. GR's videos don't really have any module knowledge expectations from the viewer, while most others do.

I think it would be good to have the FCR mounting on/off function in either the rearmament menu or the F10 ground crew menu.

I'm so glad you guys are at least discussing it. Can't describe my disappointment for not being able to do this from the get go.

Not happy at all. While everything works great, as a singleton MP simmer, not being able to hot switch seats shadows every other thing. I'm missing half of the module, but I paid the full price. As it is there's no point in me setting/learning the CPG controls. I'll never use them at this rate. Was really looking forward to this. My hopes are now on the KW and BS3. Don't get me wrong, there's a lot of cool stuff in the 64 modelled and working to which I say good work devs! But I cannot access them, so unfortunately they might as well not be there for me. George AI is fine, but being forced to use it is more immersion breaking than if I would be able to switch seats mid flight. At least then I could use the full depth of the simulator. We're missing hot switching seats in MP. If we get that. All would be well. As it is now I'm predicting that as with the Hind, once the novelty of the 64 wears off, we won't see it much on the larger MP servers. There will always be some hardcore fans. I hope people have a better experience in the long run than I have had so far. Disappointed

Just had this happen to me as well

Okay it seems to be only an issue on Hoggit's At War servers. Works on Hoggit's Training server. Guess it was server related.

Hey The "Map Marker one to Waypoint one" seems to be acknowledged by VAICOM on Hoggit, but Jester doesn't seem to actually do anything. What am I doing wrong?

I couldn't get the TACAN thing to work as well. Found out its because TACAN isn't a real word and windows voice recognition that VA/VAICOM uses, doesn't recognise it. I just made the word to be TACK AN instead of TACAN and it works. Also in VA/VAICOM you have to say "TACAN X-ray 035" pretty fast. It has to be one fast phrase. As soon I paused for even half a second it goes nuts. I don't think the voice recognition is a VA/VAICOM issue, its more likely windows voice recog issue. VA/VAICOM could use phrasing that is understandable by the bot though. Same goes for the word "Tune". For some reason, my pronunciation most likely, it hears something entirely different, so I just took the word out or replaced it with a synonym. Check out the manual. Teaching/reteaching VAICOM new easier phrases for us to speak and it to understand is incredibly easy.

So after playing around with it I have a noticed a couple of things. 1) Very cool of you to include era-specific brevity. 2) I'd like to make a somewhat selfish request as a VAICOM user. Can you include functions to have Jester slew the pod bit-by-bit. IRL sensor brevity is "slew right one yardstick", "slew up half a screen", "slew left one quarter yardstick", "Zoom in one", "Shadow"/"Track" etc. You get my point. It would be very cool for us VA/VAICOM users to use actually employ sensor brevity in this context. Whether a tandam crew of a single aircraft would actually use this brevity when communicating between eachother over ICS, I don't know. But would still be cool. Also it would cover the "Zoom" request form other users above. 3) Not a huge deal, so feel free to skim over this, but "SPARKLE" is brevity for IR laser marker, not the laser target designator, which would be "LASING" or "LASING 1688". It is funny though how you guys made him say sparkle though. Overall great work HB. Keep it up and thank you! EDIT: Should also mention, that actual sensor brevity will be difficult to use with just the menu.

Are you speaking in full sentences or keyword by keyword? Because I use the keyword by keyword method (basically just piecemeal my sentence) and it works. Didn't used to work if I was blurting out entire sentences though, since voiceattack couldn't recognize keywords fast enough. Afaik any recognition issue is voice attack related, not VAICOM.

Okay. I looked into it and it seems for Helicopters and Airplanes to work the string is different. Instead of {TXT:vaicompro.playerdata.currentmodule.name} we have to use {TXT:vaicompro.playerdata.currentmodule.cat}