Jayhawk1971

And still no joy? Did you do the whole "update dance"? My mistake at first was that I assumed I already had the most recent update installed (it already said 2.5.11.1 when I checked, or I thought it did), but nevertheless redownloaded and reinstalled and it worked.

First try downloading the latest AIRIO version from the website and copy/paste it into your "extensions" folder. Even if it says that you are already on the latest version. That's what finally got that command working for others and myself.

I pretty much followed what's in the manual and the readme files: - Downloaded and installed most current Vaicom Pro version. - Downloaded most recent AIRIO extension (2.5.11.1)...twice. - Did the "dance": Vaicom Pro config tab: export (this creates new AIRIO profile) Voice Attack: Import new AIRIO profile Edit profile, manually copy all 9 entries to VAICOM PRO to DCS World profile Delete "temporary AIRIO" profile - Start Vaicom Pro first, then DCS. Close and restart Vaicom Pro. Press "finish" in editor tab and paste updated command list into Voice Attack. - Put the downloaded airio.dll in the extension subfolder folder of the vaicom plugin in the voice attack folder. Edit: oh, and trained the new keywords and phrases. Restarted PC. Now it works.

QWP ("track steerpoint 123") works now after copy/pasting the latest AIRIO version. Thanks.

Same

This ^^ Everything else I've tested seemed to work: "eyeballs", "look for [target]" , set map marker to steerpoint. Tried with the mission "Training Day". I now did everything again as specified in the manual. Will test later. Just to recap the procedure (in case I've missed a step): Vaicom Pro config tab: export (this creates new AIRIO profile) Voice Attack: Import new AIRIO profile Edit profile, manually copy all 9 entries to VAICOM PRO to DCS World profile Delete "temporary AIRIO" profile

I did train them, they are now correctly recognized by voice attack, however somehow not "connected" to the respective Jester action?

I can't get any of the new LANTIRN commands to work. Either Voice Attack does not understand the command (like "Track Steerpoint One"), or if it understands it, does not recognize it (like "eyeball"). I downloaded and installed the newest version, clicked on "finish" in the editor tab, copy+pasted the new commands as usual, even deleted the Vaicom entry from the export.lua. Did anyone get the new lantirn airio commands to work? Update: I downloaded the most recent AIRIO plugin again and copied the .dll in the extensions folder. Now I get voice attack to recognize the commands. Yet, as I am trying to tell him to "track steerpoint 1" (12:17:17.946 TX2 | VHF/UHF ARC-182: [ ] , [ LANTIRN Track Steerpoint 1 ] all he does is switch to waypoint 1. However he's not pointing the Pod onto that area. (come to think of it, why ARC-182 when I talk to Jester?) Edit 2: The command "Track Marker [1..10] to track a map marker also does not seem to be present. Command is not recognized, and it's also not listed under "select keywords".

Here's what I did: I'm master arm on, PH selected, TWS Auto. As the Floggers turn hot, I keep extending to either their left or their right, forcing them to keep turning into me, but still creating some offset. Once I get the launch warning, I fire the AIM-54 right into his face (in TWS), which will go pitbull shortly after launch, which gives the Flogger something to worry about while I beam his missile, drop altitude and have Jester (hopefully) put out some chaff. Simultaneously, I order my wingman to engage bandits. Usually my Phoenix takes out the first MiG while his missile gets trashed, so I aggressively reengage with Sparrows /Sidewinder if wingy failed to take number two out.

VR is not TrackIR. Head movement is 1:1, while your field of view (peripheral vision) is narrower than "real live" (unless you're using a Pimax). So you either have to live with uncomfortable head positions, or get something like Necksafer (that apparently acts more like TrackIR in translating actual head movement into exaggerated head movement - not using that myself, as using VR is my effort to make my flight sim experience more "realistic", not less). Some things that come to mind that may help: make sure you are "sitting" correctly in the cockpit (meaning your head position is where it should be; if not: re-center with the "5" key on the numpad). Also, leaning back while looking left/right helps to reach the switches that are farther back (like oxygen - which actually is the only one in the Tomcat). The F-14 pilot seat is rather "tame" compared to the Viper, where you really have to reach behind you. Using a swivel chair helps, too, IMO. Also, neck problems are realistic:

Same.

That would depend on how far you are so far, but I'd say yes, there are spoilers. There's some radio banter and "CNN news update" shortly after launch which progress the story. Didn't know you were on your first playthrough, so of course please do take your time and enjoy the campaign without skipping ahead! The issue is not that urgent. You're in for quite a ride. It's a great campaign. Maybe someone from HB will take a look at it, or someone else who's already finished the campaign

Could you check Mission 11 (Dawn Patrol) whether you too experience that everything inside the cockpit - including displays, most notably the VDI - get dim when flying under a cloud? Just to verify that it's not just me. One would think backlit gauges and especially displays should seem brighter when the outside light sources get dimmer.

No argument there. Was just sharing my experience as it was similar to what MBot experienced. Should Heatblur or ED find a solution that most can live with - without breaking immersion for the majority of users (those playing flatscreen or with better headsets/GPUs) - it would be great. If not, well, I'll adapt, as always. (echo sounding out the carrier by making clicking noises with my tongue, like a bat? Should look into that...... )

Yup. Influencer marketing - and by extension, the whole trend towards "access media" (websites, blogs, even formerly respectable "legacy" media outlets) - has become a huge factor in the marketing mix...and highly annoying for consumers. It's cheap (production costs are miniscule compared to final market price), you get instant metrics (via social monitoring tools) and since the "reviewers" basically would sell their own mother for access, a guaranteed fluff piece (to be fair: not all, a select few still give somewhat honest reviews) . It's the same (if not worse) with camera gear channels.

I wish this were what I was seeing when playing in VR. It's not nearly as crisp and clear in my headset, unfortunately. Still managed to trap (3 wire, even, according to Jester), but it wasn't pretty. Then again, if the AI LSO is suffering from the same aliasing as me, he probably didn't notice.

Thanks!

Concur. Worked on the ground post patch for me.

Subjectively speaking, at least for me it was more a texture issue rather than a brightness issue. The low contrast between "deck coating" and "weathered" markings make it harder to discern details when rolling out, at least in VR with the Vive. Generally a LOD problem, I suppose.

I was experiencing the same problem in VR: the Forrestal's flight deck was a dark gray blob until late in the groove, which made lineup rather difficult, especially since the smaller flight deck takes getting used to as well. Not to mention the (for my pathetic system specs) severe drop in fps which made it harder still.

Actually I don't really know exactly. I did turn off the computer, though, and when I later got back to DCS I simply tried again, and it worked. Didn't do anything else.

I can not reassign wingsweep axis, the hat input is being ignored by DCS. --disregard-- figured it out.

I have three F-14 folders in that config folder: F-14, F-14 RIO and F-14B. So do I have to delete all files (joystick, keyboard, mouse, trackir) from each folder? And then what?

That's why I hope that Eagle Dynamics and Heatblur can come to an arrangement where owners of the SC module will get a Forrestal-class ship with the same fidelity, while those who don't own SC get a "low-fi" version that's comparable with the basic "Stennis". That would be fair IMO. Anyway, back on topic: this looks absolutely amazing. I hope that us Vaicom-AIRIO users get a timely implementation of all of that as voice commands.

And, of course, it had to be the one that I started.... The problem with that feature is that posters who still insist to feed the obvious troll tend to also quote said troll, so that you are still confronted with its garbage.