Jayhawk1971

Doing my part for The Cause and *bump* Especially after watching Gonky doing Case I recoveries in a video in November and he lamented that "there isn't a wake to put under my arm".

Thanks. I'll try with the mod later. And I have two copies of the original now, at a "safe house", just in case. In retrospect, I probably really just accidentally deleted the comma after the 7/404 value....the most common as well as most basic mistake when messing with any form of code.

Thanks again, @Flappie and @PLUTON I successfully got it to work again. For posterity: it was the value "7," and I suppose I was merely missing the comma (it's usually such a small detail) after the previous "404" value. Thanks

Thanks guys! I hope it works.

Oh crap! Oh well, guess I'll have to bite that bullet. Thanks, though. Goes to show: don't mess with lua's.

I was kinda trying to avoid the hassle of that. I just got DCS where I needed it to be performance wise (VR). If it's only a simple value in some line of code a full repair seems kinda overkill. I'll probably try to deinstall and reinstall the Supercarrier module. That should "reset" the .lua, right?

Thanks Pluton, much appreciated! Edit: Oh, @PLUTON I just checked. I need the GroundCrew.lua, not the crew.lua. If you could post the groundcrew.lua I would be a very happy camper. Thanks

Hi, I have this problem trying to load missions with the SC....and it is my fault! I messed with the GroundCrew.lua, because I wanted to "fix" the F-14A animation (raise launch bar). Unfortunately, this seems to have caused an error (according to the crash log) that freezes DCS at the mission loading screen. To add insult to injury, I've also accidentally deleted the saved original .lua. Could anyone post the correct original aircraft data values, or the original lua, or would reinstalling the Supercarrier module fix this? I'm referring to CoreMods/tech/USS_Nimitz/scripts/crew.lua Thanks.

I just tried that and made a booboo. I accidentally deleted the original file, and with the changes DCS freezes on loading a mission with the Supercarrier module. Can you, or anyone else, please post the original, none-changed values so that I can change it back? I suppose the "wing_unfold_condition" value before I changed it to 404 is the crux. Update: Got some great help in the customer support section. Got it fixed.

Unless I'm flying straight into the (rising/setting) sun, I don't have any problems reading the HUD projection. There's a HUD brightness knob on the left side of the VDI, and a switch for the red filter for nighttime operations on the right. If none of those settings help you, there's always the VDI and VSI/VVI, which are more accurate anyway, as @lunaticfringe pointed out above. Other than that, maybe your gamma settings are too high?

Event 7, wingman stuck again next to runway. AI seems to have taken a severe blow to the head again during one of the recent updates. Before, the AI waited for the aircraft in front to take off. Now it seems to want to take off immediately, and tries to overtake. Next time I'll try to move to the side and let the AI take off first.

Speaking of the Exposure mission: I don't have the mission showing up in that campaign list, either, but it is in the campaign folder. I did not restart the campaign, however, so I don't know if that needs to be done in order for DCS to add it to the list.

I assume you are referring to the "NTTR Nav points A" list from the briefing documents? If so, I believe it means that ELKXX is on the 359 radial at 100 DME from Nellis (12X). If you are using Vaicom AIRIO instead of the Jester wheel, you'll need to create a custom command to have Jester set DP.

Yep, I've noticed several times (as in, in several missions) that the AI doesn't use the intersection after landing on 21R, but instead turn about 110 degrees and taxi through the grass/ sand. Usually they make it out without getting stuck. But what I've described above was completely new. I only even noticed between HEREM and JUNNO, when Bio was giving his briefing, that Hammer didn't form up on me. I then "F2ed" through all the flights and noticed him sitting right there in the grass at the beginning of 31R, parallel to the runway. I've never, ever seen AI do that before in DCS. Maybe it was a coincidental hiccup. Unfortunately I was so perplexed that I quit without saving the track file. I'll try again tomorrow and see if this is reproduceable.

Event 3 (2v2) is similarly bugged as I've just found out. Wingman is stuck in the grass left of 31R.

Ultra-modern Fox 2 such as IRIS-T, Python 5 and AIM-9X (blocks II and III) have lock on after launch capability, which allows for 360° engagements, which kinda negates supermaneuvrability as a decisive factor. I'd say the winner in current gen WVR fights - with everything including pilot skill being about equal and everyone bringing their A game - is the one with the best countermeasures suite.

Hell, everything should come with a utility knife attached.

Well played, Sir.

Hi, thanks for the detailed reply. Yes, I do have "Action Skip MIssion" (and others, like "skip AAR" and "skip to push time", presumably from "Raven 1" and the Viper Red Flag Campaign) in my keyword list. I did not have debug mode on, until now. Next time I play and it happens, I now have a detailed log to check what's being picked up and executed. I do use VSPX. I wonder whether I could simply delete the command phrases in question? It's weird that Voice Attack recognizes the correct command, but the wrong action is being executed, but only the first time. When I repeat the same command, the correct action is being triggered. It's not even consistently triggering the wrong action. Also weird that this wasn't a problem until relatively recently, long after I've installed Raven 1, Zone 5 and Fear the Bones, yet before I purchased Bunyap's Red Flag Campaign. My Voice Attack/ Vaicom problems (TACAN tuning problems, the above, and the "ghost commands") all started around the same time, and if I am not mistaken they might have been introduced with the November 18, 2021 patch. But who knows. So many variables, and for someone with no previous experience with VoiceAttack, a bit overwhelming.

Hi Max, it doesn't even (visually) bring up the menu. I just get the "mission accomplished" message. The command somehow must work in the background. I don't really have many custom commands (that I know of ). One to access more obscure Tomcat waypoints ("Defense Point") that didn't make it into AIRIO, and added that a year ago, because I needed it for the Zone 5 campaign. The problem I described surfaced around November/December or so. Also weird that it only happens occasionally. I do get a lot of "phantom commands" lately, apparently triggered when breathing too loud through the nose (VR headset and the built in mics are nose-adjacent ). Vaicom either recognizes "south" (whatever that even means) and "Navigate Steerpoint 2". Do you think it might be possible that two commands somehow interfere with each other, resulting in something completely different? Is there a way to check the database integrity in Voice Command? I have no desire to completely start over from scratch. BTW, and this should have been mentioned a long time ago, thank you for taking the time to always try to help out with Vaicom problems! I assume I speak for everyone here that your effort is much appreciated.

The track file is way too large for the forum (>50mb). How can I open it to edit it down? ED probably only needs the last couple of minutes anyway. Or I can email you a "we transfer" link for you to download? Edit: Check PM.

Hi Reflected, I just played Killer Instinct again, most recent patch/hotfix, and when I returned to the carrier, there was a foul deck. The spawned Tomcat AI flight was stuck on cats 2, 3 and 4 (pilots # 5,6 and 7. #3 managed to launch). I did manage to actually squeeze by cat 3 and trap (3 wire, too! ) and take some screenshots. I don't know if it can be seen on those pics, but the Tomcats don't seem to be hooked to the shuttles. Edit: I entered the marshal stack and took my time, and Marshal gave me the "Charlie" signal, despite the foul deck. Also, no wave-off from LSO (although I never called the ball because I was busy setting up my "emergency trap"), so I maybe the carrier AI wasn't even "aware" of the foul deck?

For quite some time now, Vaicom occasionally executes the wrong commands when prompted. Here's the most recent example: 6:09:17.848 TX6 | AUX: [ ] , [ Perform Start Procedure ] 6:09:17.842 Recognized : 'startup' 6:09:10.171 TX6 | AUX: [ F10 Menu ] , [ Perform Start Procedure ] 6:09:10.158 Recognized : 'startup' Note that the first time I tried, it seemed to have executed an F10 menu command, resulting in "mission accomplished" message in Fear the Bones (there's a "skip mission" F10 menu option in that campaign). The same also occasionally happens when I give the navigate steerpoint (usually "steerpoint two") command, in both "Fear the Bones" and "Zone 5"). Which is somewhat annoying when playing a SP campaign. Trying again, the same command worked as it is supposed to. Why does it do that, and how can this behavior be corrected/ stopped?

Sorry 'bout that, LOL. Well, the good thing is, now you have a very good "excuse" for a nice, cold beer ("Nervennahrung").