Deezle

You know, I've had this happen to me once or twice years ago. Steep high altitude dive with idle throttles, didn't go negative G, engines flamed out.

IIRC one the unlabeled buttons on the CDU is a markpoint delete button on the newer A-10s. It appears we didn't get that feature with the upgrade, perhaps @Snoopy could chime in if it's something it should have and hopefully ED could implement it someday.

FWIW I'm pretty sure those are RWR antennas. The MWS sensors are on the wingtips and tail.

Never experienced this. If you adjust controls while flying it will forget about switches that are already on, but I've never had them "time out" while just flying for hours.

They are plain Eaton brand toggle switches with caps that I made and glued on.

It's supposed to stay centered, just like the real one stays centered over your eye.

I don't see how that would be correct in the future either, because it doesn't describe how to stop or start programs...

You can make it a JSGME mod like any other mod, it's really no trouble at all.

I know how the controls and settings work. Since I haven't tried it in years, I just set up a quick test against a Tor, with no jamming it fired on me at 8 miles, with jamming (SAM2) it fired at 6.9. Jamming by itself, without chaff, didn't appear to disrupt the missile guidance at all. Perhaps when used with chaff it works better than just chaff or jammer by themselves? I maintain an extra 2 AIM-9s is more useful in a typical MP threat environment. If I find myself messing with the bull where I shouldn't be, I'd much rather terrain mask to get close to my target than using a jammer up high to get slightly further into the threat envelope without a good place to hide.

IME the jammer pods are total junk. They will let you get slightly closer, so the threat can more easily kill you :rolleyes: Haven't hung that dead weight under my aircraft in years.

Been a while since I made the video so maybe it isn't clear, but instead of "device_commands.Button_4", you need "3004", instead of "device_commands.Button_6" you need 3006, ect. You also don't need multiple bindings for a 2 way switch, it should be a single binding that tells it to turn off when your toggle switch is off. In the same folder you find clickabledata, you will find a list of cockpit device IDs.

This has been known about forever, the devs have just ignored it.

I don't care about the new theme/design. However the layout is horrifically bad.

Those commands are not compatible with value_up and value_down. I go over this exact problem and how to create commands that are compatible in this video.

Of course. Do you know if it's possible on our end to create a left and right keybind though? Like many other modules that support keybinds to move knobs left or right one step at a time like he would need for using an encoder. I'm pretty well versed in the clicakbledata and default.lua stuff, but I've never tried to do this type of command.

That's a good find, it appears in addition to setting the TGP into laser search mode, CHAS also resets the SPI to the steerpoint. This method is faster and more fluid that using TMS aft long to reset the SPI to steerpoint first if you were used to always using CHAL to slave to steerpoint.

Nope, it slaves TGP to SPI and CHFL slaves all to SPI, per my experience and per the manual. For example if you're generating the SPI with your TGP and wish to slave it to a steerpoint, you must TMS aft long to set the steerpoint as SPI before the TGP will slave to it. This is an unfortunate change that's going to take a while to get used to.

I don't know what's correct, I just know what works.

In the past, many claimed that lasing too early with LGBs would cause them to miss. I never once encountered that. While I haven't confirmed it with the GBU-12 lately, I can say with certainty the GBU-54 will fly waaaay long if you lase too early.

Roll in the opposite direction of the arrow. I've had limited success with this. I usually just standby the TGP and deploy it again.

FWIW you can edit some lua files to configure the MFCDs to your preferences from a cold start. I had no idea this was even changed since I've run that mod forever.

Depends on mission, but on a typical MP mission with enemy fighter threats I would take: 1. (2) AIM-9M (jammer is useless) 2. GBU-12 3. AGM-65G 4. APKWS M282 5. GBU-54 6. GBU-12 7. GBU-54 8. APKWS M282 9. AGM-65G 10. LITENING Pod 11. (2) AIM-9M Never take any triple racks, and sometimes go lighter depending.

I've used them on slow moving, very low helos in the past, that strikes me as somewhat plausible. Using them against a flying plane is definitely not realistic.

I will be trying this, thank you!

A few years later, still going strong. I finally combined the lighting panel with the other right side panel and converted it over to a single Leo Bodnar board. No more Arduino stuff in my pit, everything is working pretty smoothly now.