Jayhawk1971

All I can say after 17 pages of more or less pointless debate, is that I feel pretty smug with my old G940 right now. Force feedback and more than enough bindable buttons and axis are great for the Apache (and other modules that need to be actively trimmed, like the Tomcat). It's about time some manufacturer gets its act together and comes out with a new generation of (affordable) FFB HOTAS.

The Apache is a dream to fly, but I use a FFB stick, and VR, and that seems to help a lot. I find it a lot easier to handle than the Huey. Trim is your friend.

Obviously ED felt that the type of content on that particular channel does not align with ED's preferences enough to warrant offering them early early access. Instead they chose to work with other content creators who they felt were more compatible. That's all. It's a business decision that I can absolutely understand. Apparently this decision bruised some egos.

Yes, please make them clickable, at least from OFF to IDLE. Playing in VR, it's just so convenient in the Tomcat to simply click the throttles to idle (and off during shutdown), whereas I have to fumble for the keyboard in the Hornet or Viper.

Yep, I'd say Top Gun > Iron Eagle (first one) > Fire Birds. Iron Eagle had the best soundtrack, though, IMO: Queen, Ronnie James Dio, Adrenalin, Twisted Sister, Spencer Davies Group > Kenny Loggins, Harold Faltermeyer and Giorgio Moroder anytime, any day. Top Gun did have Steve Stevens, though.... So yeah, I agree with the Tomcat probably having had more "hype" going on. Viper pre-EA-release wasn't without anticipation, either.

Codewords for the day like "tulip" or "rose" are referenced in the mission-specific kneeboard cards. Baltic Dragon also included a glossary in his campaign documentation where some abbreviations are being explained. All of the terms can be googled, and many can even be deduced from their context. If you know what the word "alibi" means, you can probably guess what "no alibis" within the context of a fence check may refer to. Or when you see a whole bunch of contacts grouped together on your radar screen, what could "Gorilla group" mean?

Relax, people. I'm certain all of us will figure out how rockets work - along with everything else - as soon as we have access to the module. There may even be dedicated training missions. If you've ever managed to learn any module with MFDs in DCS, I'm positive you'll learn the Apache in the appropriate amount of time required.

I'm still not clear about for whom this briefing room is meant. Is this a multiplayer only feature, for online squadrons? Or can single player creators use the briefing room in their campaigns? I mean it would add tremendous immersion to any campaign if mission briefings and debriefings could be held in an actual briefing room.....

I wanted to avoid that, and in the end it worked out great, thanks to the help of some great, helpful simmers. It was a single .lua value I had to change back. Took all but 30 seconds.

I guess from here: People who can't wait to have this module probably are grasping at every straw they get. Personally, I'm not in a particular hurry, as there most likely won't be any content beyond basic training missions anyway, for quite some time I assume. I'm SP only. My advice: hope for the best, plan for the worst.

Yes, the "tally wildcard" command has been imported. The downside of this function seems to be that Vaicom Pro tends to misinterpret voice commands. For example, I had incidents where I gave the AIRIO "startup" or "navigate steerpoint X" commands, but Voice Attack executed "skip mission" from the imported F10 menu. From the log I could tell that the correct command phrase was recognized, but the wrong action was triggered. I still haven't found an acceptable solution, because I'd like to keep some of the "special action" commands (like "tally wildcard", because that's useful in a couple of Zone 5 missions). But since I've bought a couple of scripted SP campaigns, the the "action" lists get's longer and longer and clogged up with one time, mission-related events that aren't useful beyond that.

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.