Callsign JoNay

I guess we are the only two people in the world who change the azimuth this way. :thumbup:

Not sure if this has already been reported, but there has been a bug with the Attack Radar for many updates now. When trying to change the scan width by hovering the cursor over the selected azimuth the text disappears from the MDI. Should be easy enough to confirm during any instant action free flight.

I reported this rain bug two updates ago. Is anyone checking on this? Here's a new side by side demonstration:

87 minutes into my mission: Notice FPM near the center of the HUD, offset only by the small amount of crosswind normally experienced by lining up to the angled deck, yet the rain is coming in like a hurricane almost perpendicular to my path, from the right to left. Rain direction seems fine during start up and first catapult departure, but shifts to directions that contradict wind flow during the course of the mission.

Happens gradually over the course of a mission. Rain falls correctly to the wind on mission start, gradually shifts over the next 30-90 mins.

Persian Gulf. Weather settings: Base 2000 Thickness 3000 Density 9 Rain @ 26K 60kts Dir 311 @ 6.6k 33kts Dir 270 @ 1.6k 29 kts Dir 210 @ 33 ft 14kts Dir 210 Rain doesn't fall in 210 direction at the carrier deck. I think it's falling at the 311 direction set at 26,000 feet.

Tap U about three times and it works. Tapping twice gets the ATC to tell you to taxi back to the ramp. Pressing a 3rd time hooks up to the catapult.

My external lights are on. Probe light still doesn't work. If you go to the external view it shows the light to be working, however no local light is actually being projected into the environment. Fly up close to a basket like the OP's picture and you'll see for yourself.

I also can not get the probe light to work at all in 2.5.6. And it worked only occasionally for me in 2.5.5.

Worked for me. You're a life saver, bro. :thumbup:

Disagree that this is not "THAT big of a deal". It is game breaking for me. I can't stand the default FOV values. I used to edit the max/min FOV with no problem in 2.5.5. ED please fix this ASAP.

For what it's worth it seems the probe light works consistently if I begin my missions from "take off from runway" or "fly over point". However if I "take off from ramp" and go through the process of cold starting the jet myself the probe light rarely works. Seems like something during my ramp start process is causing the bug, but I can't figure out what it is.

Here's a video of a pilot telling a story about how he could see commercial nav lights from 100 miles away with his NVGs. I would think AB would be visible from the same distances, maybe farther. Timestamp- 36:42

I noticed this is still "Checking" status a week later. Any luck reproducing on your end? Here's another video I made to demonstrate the probe light bug: Points of interest are: 04:35 09:23 14:15 However, I included the full video of all three ramp starts in case something is noticed in my startup procedure that might be triggering the probe light bug.

This is true for nav lights as well. I'm so tired of closing in on the TACAN of a tanker at night and it's nav lights are invisible until I get close enough (0.5 miles) to render the highest LOD model. I've heard real life pilots on youtube tell stories about how they can see a person smoking a cigarette from miles away, and how the entire Milky Way and orbiting satellites are visible with NVGs, and we can't see AB or nav lights of another aircraft until we're about to collide with them.

I forgot how truly terrible youtube compression is and how bad night missions look. Here's a direct link to the video file if it helps: https://www.dropbox.com/s/6q2jnwh5aqzbyyb/Probe%20Light%20Text%20Side%20By%20Side%2002.mp4?dl=0

F/A-18C AAR probe light will sometimes not project illumination onto the tanker/basket even though the external view of the aircraft shows the light to be on. Seems to only project illumination about 50% of the time when I attempt AAR with a KC-135, (and 0% of the time with the S-3B). Persian Gulf Single Player My own mission created in mission editor. Specs: DCS Open Beta 2.5.5.431 GTX 1080 Founders, i7, 16 gigs, 4k Video:

I think we've established that it's not a day vs night issue. The light itself works as intended. It's just that some 3D models, (S-3B Viking), don't reflect the light, which sucks because it's the only carrier based tanker in the sim, to my knowledge. I guess it's NVGs for me until the S-3 model is updated. -_-

Well, I figured out the problem. The probe light does not work on the basket of the S-3 Viking. Probe light works just fine on the baskets of the KC-135.

My lights are definitely on, 100%. And I can see the probe light turning on in the external view, but there is no illumination on the carrier deck when I'm parked and nothing illuminates the basket of the S-3 as you can see in my pictures.

Why does it look so different than the NVG screenshot I posted on page 2? My basket is not illuminated at all. You're on the most current build? Edit: Can you share a non NVG screenshot too? I have a feeling the basket will be visible in your sim.

I don't think so. My taxi light works just fine.

Significantly as in zero? I haven't noticed any light on my basket at all. I didn't realize this was a thing that used to work in previous builds. Maybe I should report this as a bug?

Yeah, I just did another round of testing and I don't see any illumination on the basket at all. Tried it with internal lights set to night and NVG mode, as per AG-51_Razor's suggestion, no noticeable difference. What am I missing, guys?

Are you talking about the switch on the interior lighting panel? Maybe that's why I'm not seeing the probe light. I'll do more testing, thanks.