Chain_1

I saw you bug him in the replay, but @_SteelFalcon_ has pointed out the root of your problem. Try it with an STT lock and see what happens.

Worked for me. You need to activate the correct profile. First activate the GBU 10 profile in the DSMS profiles page, then change the settings and save it. GBU 10 should still be highlighted in the profiles page, then you can view it and make sure the settings saved properly. I'm curious as to why the settings didn't save after the first time you set them up, though. Edit: I lol'd at the text pop up that appeared when I hit the target.

There's no countermeasures option based on geographical location. Some weapons, such as mavericks, can be set up to turn on based on position relative to a steerpoint. Maybe that's what you're thinking of.

Because you're posting in the 'Clouds and Weather' section of the 'Bugs and Problems' sub forum. If you have a different topic, you need to go to the correct sub forum.

@FlappieYour top picture is from the KC-46 Dumpster Fire, that's why it looks nice and visible and clean. On the 135, the pdl housings were black at one point, but now they're a bit faded. If you look in the US National SRD, which is publicly available, page 4-17, you can see the visual references for the contact position. Note the faded appearance of the PDL housings.

@GoodHope I've seen a couple of 135 guys in DCS. Maybe we crossed paths at some point. I was Kadena '11-14 and McConnell '14-'18. Cheers.

As a real world KC-135 receiver instructor, they are difficult to see in real life as well. Receivers always ask for them to be turned up during the day when they are already at max brightness. They were supposed to be replaced with LEDs several years ago, but the program got canceled during sequestration. In DCS, they aren't modeled correctly anyway (green when one should be yellow, one light change per foot of movement, etc...). If you consult the ATP 3.3.4.2, a publicly available document, you can see how it really works/looks. If you play a certain other f-16 sim, that is accurate. Edit: I have to call myself out here. I got out my copy of the SRD and apparently I'm too used to flying against KC-10s. 135s do not have yellow PDLs, while 10s do. I guess that shows how difficult they are to see/how long it's been since I had to do that mission. So, DCS is correct on the color, but not how the lights change, while said other sim has the correct light changes, but not the correct color.

Having flown there in the summer and winter IRL, it's always hot. Remember it's roughly 13.5 degrees north in latitude.

It sounds like you tried to map it under the "axis" control group. That section will take only axis inputs. Map the hat using the "HOTAS" group.

They're rendered, just super overswept. Happening to me, too.

The SuperHind was featured in the movie Blood Diamond. To see it in "action," watch this scene.

Anyone who has the F-14 knows that Jester makes references to Star Wars and Top Gun. It would be fun if Petrovich had some lines in this spirit. I propose, therefore, that upon destroying a target Petrovich should say "А ну, чики-брики и в дамки!" For those who can't read Cyrillic, this reads: "Ah noo cheeki breeki i v damké." It would be a nice little Easter egg.

Is your control bound to "Countermeasures Management Switch - FWD" or to "CHAFF/FLARE Dispense Button"? The dispense button (aka the slap switch), on the left wall is something like a panic button that dumps a bunch of chaff and flare. The CMS fwd switch, on the stick, should drop one flare and one chaff if you're in bypass. Edit: I just tried hitting the slap switch and got the same result as you, that's your issue.

It does sound like some kind of interference, but it's probably not from Have Quick, just something on his interphone. I believe fighter guys keep their mics hot for HUD tape recordings, but he probably wouldn't be transmitting constantly, though I'd have to see the video. You only really hear any clicks/skips when your radio is receiving, transmitting you hear yourself normally. Said clicks would also be rhythmic and constant due to the slight timing desync between the radios.

Not sure where the clicks in your clip are coming from because he's not transmitting, but you are correct that you can hear a skipping/clipping sound with Have Quick. That comes from the timing of the different radios being not exactly the same. My source is that I've been using Have Quick for about ten years now.

Have quick is not encrypted, it's frequency hopping. If everyone is on the same timing, it's just like normal radios. For the secure voice beep, SRS comes with that effect, so there's probably a good sound file in its folder.

I'm kind of curious as to what position you're holding. It sounds like you're flying Blue Angel/Thunderbird close. I have no experience with that. In normal fingertip, you should have enough horizontal separation to be clear of wingtip vortices. Stearmandriver is correct though; small aircraft wake turbulence is pretty exaggerated in DCS.

I don't think it works like that. Try saying "Take 10" to select F10, then "Take X" where X is the number of the specific call that you want to make, e.g. when X=3 you're selecting F3 in the radio menu. Doing that has worked fine for me. Edit: changed "option" to "take" x2

It sounds like you're too high. Notice where the basket extends to and how low it is compared to the wing tip and fuselage and try to keep it there. Visually, split the mprs pod with the top edge of the aft hud glass, and that will keep you out of the wingtip vortices. I'm not an IRL Hornet guy (AF FTW), but I can tell you that wake turbulence is no fun to be in. If the size difference between the aircraft is great enough, you won't be able to control your jet. Even if the aircraft are the same type, if you're in the wrong spot it could still be uncontrollable.

In real life, there are antennas, panels, and paint markings that you could use as reference points. Unfortunately, they are not modeled/textured. For left/right, stay behind the yellow centerline stripe. Vertically, when you see the PDLs in the center see where the nacelles intersect your monitor's borders and try to keep them there like probad said.

I don't have a F-16 Dash 1, but I'd guess in the checklist all interior lights are set to off until after engine start, where there's probably a step along the lines of "Interior Lights - As Required." Just a guess though.

Can confirm. Happens with or without LTS test.

The dimmers for those lights are all the way dim, and the AoA lights are the same. They're on the outside of the light housing and you have to move them up. This has gotten me before, too.

For me, at least, it won't trim out if you have autopilot on. Disengage the autopilot, then try trimming. Failing that, bring up your FCS page to see if the controls are reacting normally to your trim inputs.

It sounds like you're too low. What is your agl altitude at which you're trying to drop?