Emmy

Thanks for the update 9L...

You're giving the JTAC a head's up that your need for his laser is imminent.

Latest OB, KC-135s appear to be flying blacked out until you’re inside of 0.7nm and the boom drops. They also now immediately re-black out as soon as you’re topped off and the boomer disco’s. Tough on your -2 trying to move to pre-contact.

Yeah, the current animation lacks the slight bit of fore / aft motion as the canopy seats / unseats.

Bumping this hoping it might get addressed please? In the latest OB, it might have now gotten a little worse given the other reported “blooming” hot spots on various displays across the DCS universe.

If you’re flying on a sever that offers TV downloads, absolutely turn off local recording.

When I first got the Viper, the Main Battery switch was bound to the TMWH Flaps handle. Out of Hog Habit, I went to drop a notch of flaps for my first taxi and promptly shut down the jet. Check your bindings...

Plus, a little extra formation flying never hurts!

Are you loading weapons or refueling while running a Stored HDG Alignment? If so, stop. Jostling the jet in any way while doing a SHA will make the alignment go stupid.

There is a script that will detonate missiles before they strike but it still records and reports a kill. Works for A2A and SAMs. It does NOT work for guns. This script in conjunction with a TacView debrief is pretty close to how it works IRL.

So long as it can be disabled server side, meh, why not?

It’s possible you’re suffering the effects of what’s called “Bang Bang Guidance” Note the part about the bombs “over correcting” before settling on the laser properly... “ Paveway II laser-guided bombs use what is known as "bang bang" guidance. This means the bomb's fins deflect fully, rather than proportionally when it is attempting to guide to the laser spot. For example, if it sees the laser spot and determines that it should make a change it deflects its fins until it has over-corrected and then it deflects back the opposite direction, creating a sinusoidal type of flight path. This type of guidance may be less efficient at times, however is more cost effective and allows the use of simpler electronics in the guidance system.” Are you lasing immediately after pickling? If so, I think the bombs are colliding while trying to chase the same spot.

Because if the dumb variants also collide, then it could be a bomb ballistics issue in general and not specific to the laser-guided version. Although I’ve routinely rippled six Mk-82s with default spacing without any bomb collision issues. My money is on premature lasing causing the bombs to steer into each other.

It’s definitely not right in the latest version. Both MFCDs wake up with horrible bloom. The Day/Night does nothing really. The balance between Brightness and Contrast used to require virtually no adjustments in order to read a TAD Map but now the maps appear so washed out that the Brightness needs to be run almost all the way down and the Contrast has to be raised unusually high.

Nope.

You can move an ejected pilot via joystick and pedals.

I use the DOWN arrow on my keyboard which is right in front of and above my stick (on a Monstertech mount) Easy to reach quickly...

“Tap“ it with the left mouse button and then scroll wheel up will raise the brightness.

And maybe more than just Mavericks if we all take a step back and give ED some room to breath... Frankly, I’ll take broader (and I hope more “fully cooked”) updates less frequently over weekly slapdashery that often hurts more than it helps. Spacing out the updates will also allow the Devs to weed out the numerous Operator Errors and other manifestations of pure ignorance that always clog the pipeline after every update. It will also, I think, allow Wags to create feature previews which are more in depth because he won’t be racing to produce a video with only hours to spare before an update is released. On ED’s part though, I expect them to respond to “game breaking” bugs in a timely manner and not let issues fester that could, in fact, be patched with a hot fix.

All of the above has been known to happen in missions we fly. Red Balls requiring you to jump in a different jet, 3 hour Recon flights that come home empty handed, Strike flights that bring their ordinance home, Leads or Wingmen RTB-ing earlier than planned because their wing or lead disco’d, had to eject or got shot down, etc. But I vehemently disagree with your last sentence because it’s not the Sim that makes it fun, it’s the people you fly with who make it fun. Don’t raise your sim. Raise the quality of the people with whom you fly!

No ILS at Incirlik?

Not a guaranteed fix, but try turning “Chimney Smoke” to Zero in your settings. Deleting the FXO and Metashaders folders can also help. This has become an On Again / Off Again issue that nobody seems to be able to solve permanently.

Doesn’t help nearly enough with NVGs on. Even with the slider run all the way down, you’re still blind from your 10 to your 1 o’clock.

+ A Whole Lot! Reported this as well a while ago and asked that night lighting on it be turned WAY down.

LOL