The Burrito

I don't suppose there's a way to get a 3D-printed CMS top on order for the 4-way, is there?

It is, and I even reinstalled both modules to be sure despite the fact that supercarrier missions appear for me as normal in the F-18 selections.

Some update sometime last year seems to have removed them from my missions lists, but not completely. They're present for landing missions in Instant Action, but they're missing for everything else. I could have sworn the campaigns had Supercarrier variants as well. Would be nice to find out for certain, considering if I search for it I find nothing but rather unhelpful "Supercarrier missing!" "Me too!" posts.

Damn, still no international shipping. Unless you're saying that you can, but it's expensive? Would it be possible for you to direct us to what parts you used so we can order them ourselves, for those of us that can't order from you?

Huh. I remember being told that tools would have to be used to remove supporting walls and the like. This is much better than compromising structural integrity.

So... OTTO buttons of specific sizes and colors are extraordinarily hard to find. I managed to snag two P1s in gray so I can systematically replace the abhorrently cheap switches in my Warthog grip, but I can't use them since they're not going to fit in the gray button areas. (Pinky, Master) Finding P8s, the stubby versions, is near impossible and places like Mouser don't actually stock them, which leads to months of lead time should I order. I need my red murder buttons. :( So! I'm looking for alternatives. This way it'll be less dodgy than hot gluing and soldering an OMRON switch into a comparatively cavernous housing. Of course, patience in ordering $80 worth of buttons is fine, too, I suppose, if it's preferential to go with the OTTOs.

I'm going to replace the buttons on my Warthog grip and throttle with OTTO at some point. I've got two for the master mode and pinky, but apparently everybody buys just the red buttons and they're out of stock until September. I have everything I need, but in case I screw up I'm gonna need more wire to splice in, I think. What's the gauge on the stick's wiring?

How is this a thing in other modules but not the A-10C? Please, add this option. They make my eyes bleed.

Fun fact, including some details without just being a douchebag about it is infinitely more helpful.

Only your second post and you're already sounding whiny.

Bump for great justice, and because I don't know if it's an ED bug or a HB bug. Still an issue as of today, though.

Yeah, I need to replace my joystick's pickle button but don't really feel like sending the grip off and then suddenly having it stuck in one location with the business going around.

Don't suppose you can just send us the parts we need so we can do it ourselves, can you?

My gamma is default. I've never changed it.

I actually just realized that the first three screenshots are in day mode. The rest are definitely in night mode, but I can still clearly see everything pre-2.5.6, even without adjustments. In 2.5.6, switching to day mode just makes it worse. Night mode is what you see in the rest of them.

Observe the very long post showing screenshots. In 2.5.6, the display of the TGP (though not the Maverick, but then again it might only have been minimally affected) has gotten so bright at night it requires tuning of the contrast and brightness when it was never needed prior to the update. This is how they looked in the last 2.5.5 Open Beta build: CCD BHOT WHOT Nothing has been changed, this is all default settings. This is the same settings, looking at generally the same area, but farther away in 2.5.6 and its patch(es). It's the brightness overall that's strikingly different: CCD BHOT (Only usable without MFD brightness/contrast tuning if gain is set to 8 and level is set to 0) WHOT (no appreciable change when setting gain and level) Now, if I were to lower the brightness to 9, set the contrast to 30: CCD BHOT WHOT It becomes a little more manageable, though the CCD mode turns completely black if I set contrast to 32. At stock gain and level settings but with adjusted brightness and contrast, this is what smoke of any kind does to the TGP: BHOT WHOT My gain and levels are up, but if it's at 4L/4G or balanced in any way then smoke completely washes out the TGP video. This is what smoke looked like in 2.5.5 OB: BHOT WHOT [EDIT] I'm told that night mode is actually brighter than day mode. I'll have to check that when I'm able.

Anyone else heard from rel4y lately or has he just been busy?

I don't remember if I replaced that potentiometer or not, though... In any case, watch out for an email from me soon about purchasing a set!

Oh shit, pedal upgrades. I occasionally find myself having to constantly recalibrate to zero the toe brakes and every now and then I'll find it registering a right rudder input without my feet even being on the pedals. Would this mitigate those issues?

Christ, yes, that was exactly my issue. I didn't want to edit via the commands list itself because delving into the root is usually the last option if you have a top-layer alternative. Now if only "Scan sector angels x at x" ****ing worked. "Angels 14" is invariably recognized as "Angels 40" for some reason. I've never had this issue with VoiceAttack.

This is fine. Hadn't even taxied yet, didn't realize I'd actually slid across the deck until I found the deflector clipping through like this. I don't think this was as big of an issue before the latest patch (I'm running open beta on Steam) but there was already a pretty big disconnect between the rolling of the ship and the F-14's relation to it.

VoiceAttack does NOT want to recognize "Radio Tune" command. Like, at all. It'll recognize other things, but not this one. "TACAN Tune" also tends to have some trouble being picked up, but none of these appear in the editor. I feel like adding an alternate command like "set radio" or "set tacan" would help but I don't know what the effect of editing them straight from the VA editor would have. [EDIT] Apparently the "Scan Sector" and "Radio Tune" addon commands have a pretty low chance of activating. VoiceAttack literally reads "scan sector angels 14 at 30" and it wasn't recognized. TACAN Tune is in the editor though (missed it the first time), so there might be a correlation.

Yeah, that did it. I thought since this wasn't being updated to include AIRIO after the fact I didn't have to do that particular step.

Deleted all my custom exports. So far I can now talk to the ground crew, but not my RIO. (Yes, I bought AIRIO.)

Just installed. Everything seems to load plugin-wise when I start VoiceAttack and load the profile, no issues... except when I try to actually do something. The PTT window doesn't update with my current plane and commands recognized by VoiceAttack don't do anything in-game. Setting the custom path to my DCSWorld folder in my Steam directory didn't fix it.