Jayhawk1971

I'm sorry too for reacting thin-skinned to that, but I was really take aback by Tharos' "tone" to an IMO innocent post (I was in mere conversation mode), and your post was immediately following his which made me perceived that as piling on. I guess I felt I was being put in the same category as the "troll we all know and love".

I'd appreciate if you could kindly refrain from including me in some perceived group of people making such "bold" claims, because I did neither. I mentioned something that was all over the news at that time, with an IMO appropriate expression of skepticism

I was just wondering how much of a discrepancy real life vs. simulation may be. Simulations tend to always take best-case scenarios into account, whereas a lot of things work differently in real life. Even real-life tests with the Luftwaffe MiG-29 vs US Hornets only could give theoretical results. I suppose it's always a problem since (thankfully!) so few air-to-air missiles get exchanged in real life. But when it happens, it can lead to surprising and possibly unexpected results (like that Rhino's AIM-9X seemingly getting spoofed by old-ass Syrian flares a couple of years ago)

How often was the R-73, in real life, fired in anger, how often in HOB-mode, and what was its PK?

I'm wondering whether what Bio said was true for all variants of the Tomcat. I could imagine that at least the latest D-models might have had "better" sensor integration. Although, I have no idea if the LANTIRN system generally was a stand-alone, independent sensor environment, or if it actually was integrated into the avionics suite of the F-15E or those Block 40/42 F-16's that carried the pod. My latest interaction with the Strike Eagle was "Jane's F-15", so what do I know.... If only there was a Strike Eagle Wizzo on these boards that could chime in (if he's allowed to reveal such information, of course)

I get the impression that MS speech recognition is getting worse over time, just like Android autocorrect gets worse and worse. Edit: it's almost like it's unlearning things it already understood. Like "TACAN", for example. Saying TACAN tune used to work flawlessly, but lately I get the odd "tech and tune". OTOH, sometimes Jester says "Roger" (or I get a "confirmation beep") out of the blue (even when there's no background noise like the TV or music). Mostly he is hearing "south", a command to "navigate to waypoint 2", or switching to a different preset channel on the VHF radio. Might be my breathing into the microphone, or scratching noise when I'm looking around (VR headset), or a delayed reaction to a previously given command?

I created shortened versions of the phrase as aliases. That seems to have worked. Took out the "switch" and shortened the phrase to Aspect Nose/Beam/Tail. Still got problems to get it to recognize "tail" instead of "tale". Finally, for the umpteenth time I sad "aspect tail" and suddenly: I don't know how or why, but I ain't complainin'

Hi, maybe I am slurring badly, or my pronunciation is off, but I can't get Vaicom to recognized the three new phrases for the Aspect Switch. I got the update, I clicked "finish" and pasted the list into the Voice Attack profile, as usual. The phrases are there, I can select them for training (which I've been trying for two days now), but somehow they don't get recognized correctly, neither in game nor during training. Either I get nothing, or some weird misinterpretations like the thread title. Normally I don't have problems with Vaicom not understanding my commands and phrases. Just these three new ones. Does anyone have the same problem, or even better, a solution?

Princess? Pah! VR is the Mode of Kings!

Last I've read from the creator was that he was planning (or thinking about) to flesh this out into a fully voice-acted paid DLC-campaign, and add additional missions. Since then he vanished from these forums. Which is a pity, because the campaign is very good, and I certainly would have bought an upgraded version with decent voice-acting.

Well, she's a Cylon, so that doesn't count.

My point was more that it's hard to come back to the Tomcat with the same proficiency as a "FBW-cripple", which I found extensive exposure to the Viper/ Hornet leads to. Especially the Viper basically flies itself, the only real flying challenge seems to be a stiff crosswind on final. Well, that, and the same ground handling characteristics as a Robin Reliant .

I think I'll try that as well. Probably find the switch commands in the RIO controls and bind them to a Voice Attack command?

Late to the party, but IMO pilot body would be great, if arms/legs would move with controller input. Arms and hands need to be animated and correspond with player inputs (reaching for and clicking a switch or pulling a lever). Then it would be an amazing, immersive experience. As it is, the first thing I do when I'm in a Hornet is to disable the pilot body, because his arms get in the way, especially on the left console.

Has the Target Aspect Switch been implemented yet? That was also something that was missing.

That would be fantastic indeed! I've tried that mission, and I loved the atmosphere. Sadly, once I dove below the cloud deck, I could count the individual frames. I'll just have to hope that Santa brings me a new GPU.

Oh, maybe I should have specified that the "lull" is only how I perceive it, due to heavy playing, not in general (there's a ton of great Tomcat content); probably a good illustration of the difference between "relative" and "absolute". So to anyone still on the fence whether to buy this fantastic module: there is a lot of great content available. At least for 20 months of module-exclusive playing. But I do own the Tomcat since March 2020, and have flown it exclusively since then. So I have pretty much played all campaigns, missions, instant actions and training sessions. The only missions I haven't tried yet (but downloaded) are Reflected's "Final Countdown" and "Gulf of Sydra" missions. I've played through Training Day and the other LANTIRN missions as soon as Vaicom Pro was updated with the new Jester LANTIRN commands, and will try the other "branch" of the mission (the - I assume - shorter and less exciting option). I do own Persian Gulf, NTTR and Syria maps as well. Marianas is still a slideshow for me over certain areas (Guam!). If you'll ever find the time to upgrade the other really great single mission (Watching the Devil Dogs) to Forrestal (and/or SC) status, and maybe some of the other single mission, that would really add to their "replayability", IMO. Or some of the interesting quickstart missions such as the Mariana's F-14A/B intercept missions could become really cool "full" missions by adding cold start/ take off features (again, Forrestal or SC) I'd do it myself in the Mission Editor if I only knew how. Probably not a mere two-hour job.

Due to the current "lull" in new Tomcat SP content, I activated my two-week trial license for the Viper (mainly to see how the progress of this model is coming along since the last "trial" period in spring). Again, I found that extensive time in a FBW-aircraft really has a somewhat detrimental effect on my Tomcat handling skills. I also haven't touched the Hornet in over a year (other than to satisfy my curiosity as to how it looks in VR), mostly for the same reason, even though I found the Hornet feels less "digital" than the Viper (which is almost grotesquely easy to handle - which is probably by design, because the pilot needs most of his attention to handle all those weapon systems and avionics: TMS short forward, DMS long right, sacrifice a goat, make coffee maker SOI, yell "Geronimo"....just to mark a steerpoint ). So I made it a point to "end the day" (as in, final flying session of the day) with a flight in the Tomcat to "cleanse my pallet", in the hope of not losing the light touch those Tomcat controls need. And boy is that necessary for me! After doing half of the later Viper training missions (air-to-ground from CCIP to JSOW), I did a Tomcat free flight mission and my muscle memory was already messed up a bit, resulting in somewhat hamfisting the controls into overcorrections. So my question to you folks: how do you juggle with different modules? Or do you also stay module exclusive for a while? Or is switching between the different modules (with or without FBW) as easy as changing your socks?

Allegedly, the term "red light district" goes back the American Civil War, because General Joseph Hooker dedicated a part of the Union camp to that certain trade, and marked it by hanging up red lanterns. His last name also became the colloquial term for practitioners of said trade. Allegedly. And the Tomcat uses a tailhook to land on an aircraft carrier, so the circle is now complete.

I fly in VR, I've played Fear the Bones as dozen times now, so I am one of "those of us". And while it's not ideal, it's manageable, IMO. Instruments at night were never easily readable, but set to "2" I can read altimeter, speed gauge, VVI, engine instruments well enough to operate the plane. Just yesterday I played "Bad Moon RIsing" (from Fear the Bones campaign) and managed to fully complete the mission (without going into spoilers, but you know what I mean if you've played the mission ). Maybe it's because I am relegated to play on dated hardware for the time being (including VR headset) so that I don't have a good comparison to what real high-end hardware could display pre-patch, but for me there's hardly any change in the A. BTW: I never fly with flood lights on, anyway (same when I drive at night, only turn on "flood lights" when entering or exiting the car), because I always found them distracting (the glare on the canopy, and the general brightness in the cockpit). I only use it for startup/ shutdown. Once I'm ready to taxi, I turn both white and red flood lights off.

Flood lights (both red and white) work fine in the F-14A. Just the B is affected. Other lights can be dimmed, so not all that dramatic.

Can't wait! Hopefully by the time the campaign is released performance in general (and some maps in particular) will have been optimized (and/or availability of GPUs will improve).

If the command is not in the game, Voice Attack /Vaicom can not link to it (which is basically what the program does). But apparently not all commands that are available in DCS are accessible via in-game menus. From the Vaicom Pro manual: Nevertheless, if it works in Vaicom, it has to be in DCS.