Callsign JoNay

≡☆≡ JOIN THE 51st VFW ≡☆≡ ■ABOUT US■ We are a North American based group operating primarily in the evening hours between the PST-EST time zones, but we accept applicants from all over the world as long as they can adapt to our schedule. We currently have 70+ active pilots, some active/former military, some commercial aviators, and others just sim pilot gamers. We consider ourselves MilSim-Lite. We do have a rank structure, but do not enforce anything too extreme like virtual saluting or adhering to strict chains of command. We are self aware, and know that at the end of the day we are all just nerds who enjoy the same video game. In the air, we do try to fly seriously. Learning about, and adopting, real world standard operating procedures and tactics is one of the things we enjoy. Our main wing missions usually occur on Saturday or Sunday evenings. We typically have 40+ pilots in attendance, flying a variety of airframe types all assigned with parallel objectives that work toward a larger win condition. We primarily play PVE, but will occasionally organize PVP events, complete with OPSEC channels, encrypted COMMS, and back end espionage. ■SERVERS■ We have several dedicated servers, enhanced with MOOSE, Tactical Paddles, and other back end goodies that bring the simulator to life and enhance immersion. ■REQUIREMENTS■ Fluent in English. Availability in the evening hours of North American time zones. Over 18 years old. Have some form of HOTAS. Have some form of head tracking. Latest version of DCS Open Beta. Simple Radio / SRS. Not an active member of any other 4th gen DCS virtual squadrons. ■AIRFRAMES■ A-10C AH-64D, and/or other Blue helos F-16C F/A-18C F-15E AV-8B (Decommissioned, but we would love to see the Harrier in our skies again. If you are an experienced Harrier pilot interested in starting a squadron under the 51st VFW banner, or if you are part of an established Harrier group looking for a home, we would love to hear from you.) RedFor (We don't have an official RedFor unit yet, but we are collecting lone wolf mercenaries who are interested in participating in our occasional PVP scenarios.) ■FAQs■ Question: Are you a zero to hero training group? Answer: Not quite. Some skills in DCS can be practiced in single player, such as take offs, landings, aerial refueling, basic avionics, navigation, and weapon usage. We hope that any 51st VFW applicants have those types of single player skills mostly squared away with reasonable competency. Everything else that involves other human players, such as tactics, 51st VFW standard operating procedures, and COMMs/brevity, can all be taught in a zero to hero style. TL;DR, just know your aircraft, and we'll teach you how to be part of our team. ARE YOU READY TO TAKE ON THE NEXT CHALLENGE? ■APPLY■ https://discord.gg/51stvfw ■WATCH■

ED, please fix. The whole point of a PB shot is to have a HARM in the air, 3/4 of the way to the target when it switches on it's radar. We can't have our PB mode HARMs veering off the intended target before it even has a chance to start emitting.

Sure thing. Here is the trimmed down 7.5 minutes of when the JSOW+HARM attack happened. PB Mode HARM TacView Trimmed.zip.acmi

Ahh thank you. I did a search to see if this was already discussed, but I didn't find any hits. Hopefully it gets addressed. Edit/Add: Just to further contribute to this, here's a HUD view from the HARM the moment before it veered onto the incorrect target. The intended target is the pink grouping directly below the HUD (you can see the JSOWs inbound), and the green box to the right is the SA-15 that the HARM veered on to. In the top middle of the image the distance is reading 38.72 nm to that incorrect SA-15 target.

I've been noticing a behavior with AGM-88 HARMs in PB mode, that I think might be unrealistic. Last night my virtual wing hosted a mission that involved multiple flights performing DEAD on several different SAM sites arranged in a wall from NW to SE. I was attacking the Northern most SA-11 site that was protected by an SA-15 SHORAD. My tactic was to create markpoints on the SA-11 TELs, deploy JSOWs to those MPs, give them a healthy head start, and then launch a PB Mode HARM in trail with the SA-15 code (119), and one of the TEL markpoints selected, with the intention of suppressing the SA-15 if it goes active and tries to shoot down the JSOWs. (My HARM shot was too late, but that's not the point.) About midway through the HARM's flight to the designated WP at the SA-11 site, it veered hard to the right. ...Distracted by a different SA-15. The HARM ended up splashing down over 23 nm away from it's intended location. I don't have any documentation to prove otherwise, but I have a hard time believing that this is accurate PB mode behavior. Wouldn't the HARM have some kind of narrowed FOV in PB mode? Or perhaps some kind of delay on it's seeker activation, so that it only activates closer to the designated WP, and not get distracted by something over 20 miles away? I know if I was the weapon designer, I would have some kind of features in place to prevent it from being so easily distracted by unintended targets so far away. I could understand it getting distracted by a similar target within 5 nm of the intended one, but 23 nm away? Really? The current implementation seems to defy logic and common sense, and makes coordinated SEAD very difficult in DCS. Can someone at ED review? Thanks.

Update: We are continuing to recruit Hornet pilots for our early 2025 class. In addition to our usual requirements listed on page 1, we are looking for the following traits: •A relatively high level of participation, once per month minimum during busy periods of your life, once per week, or every other week, during normal periods of your life. •A relatively high level of activity on discord. We need pilots who follow the discord daily, who participate in discussions, exchange questions and techniques regarding the Hornet, who engage in planning for our various operations, and most importantly we need individuals who reply to @checkmates pings. •Some mid week availability. If you are never available mid week, only weekends, it might be an issue. •Interested in EVERYTHING the Hornet can do. Our next generation of Hornet pilots needs to be equally interested in WVR dogfighting, BVR in both PVP and PVE scenarios, precision strikes, SEAD, DEAD, anti-ship warfare, close air support, even FAC-A, recon, air policing, and carrier ops. •Applicants should be able to CASE-1 recover with decent scores on Bankler's CASE-1 trainer, and should be able to take fuel quickly and reliably on all basket-equipped tanker types. As far as comms, tactics, and SOPs go, don't worry about any of that stuff. We can train and develop you from the ground up, as long as you can get those single player skills squared away, like CASE-1 and AAR. Join our discord to apply: https://discord.gg/51stvfw

Bump. Please add these bindings.

Our Viper squadron, the 66th BlackKnights, is re-opening recruitment for an early 2025 cadet class. This squadron only recruits a few times per year, so don't delay, apply now!! Applicants must be over 18, English speaking, have relatively good gear, and availability in the evening hours of North American time zones. Join the 51st Discord: h55ps://discord.gg/51stvfw and look for the main applications in the public area: https://discord.com/channels/713888090003079228/1188169559342063717

See this clip for how BMS handles the angular size of the NVGs: https://www.twitch.tv/callsignsqueak/clip/EphemeralSwissCaribouUWot-UMhlSHWrxItyZluQ This is the proper way to do it. Why are the NVGs a fixed angular size in DCS? Can someone at ED please acknowledge this? The way it's currently implemented is highly inaccurate, and needs to be fixed.

Please consider instead of just removing the flare feature, also include an option to be able to recover properly without any AI comms at all. Many of us fly with other people who handle the ATC and LSO duties, and it's annoying to have to trigger scripted player/ATC comms from the menu while also talking to real human beings. This is especially annoying in Case III, since you have to go through the entire comms menu dance just to get the lights in the LA to come on, (established, commencing, check in, platform, ball, etc).

Big +1. I shared the same thoughts on my virtual wing's discord after I saw Wags' preview video:

Ahh, I figured it out. On passes 1 and 3 I didn't call the ball, and it gave me the flares. On pass 2 I did call the ball, and no flares. It seems like it's tied to the comms. Can we please have an option to disable the necessity for comms? Some of us like to do this zip lip, or with human controllers/LSOs.

Here was pass 2 of 3, no flares: https://www.twitch.tv/51st_callsignjonay/clip/CheerfulRelievedGerbilOneHand-lxWaoMBQyotdzxUO and pass 3 of 3, flares again: https://www.twitch.tv/51st_callsignjonay/clip/ThoughtfulKindShrewPipeHype-2emnFO-mTzqYAKX_

https://www.twitch.tv/51st_callsignjonay/clip/SplendidBlindingClipzTheRinger-ceJAu0ojeB_WbRLO Same here. I was testing today, and the LSO shot flares at me in 2 out of 3 passes.

It's night vision, so it should be able to. To me it sounds like regular NVGs with the HMD symbology inserted into the right eyepiece. The DCS Warthog already has it, but the FOV is borked as per what I posted above. When you zoom the FOV in the symbology gets larger but not the green circle fixed area of the post processed night vision. https://youtube.com/clip/UgkxD2cWj06AAKG28ZBx5ubFygkbjHvDVoFl?si=ss8cQoV0_w937qoQ We really need ED to fix this.

I wonder if the lack of implementation has something to do with the incorrect way the NVG FOV is implemented in DCS: The green circle should be a fixed FOV, 40-degree, or 100-degree for QuadEye. It should not be a fixed area/size on our monitor. It should expand if we use FOV zoom the same way our HMD expands in size when we zoom our view. I believe the way the way this should be working is that if we choose the to equip the HMD option, we get the monocle version that is incompatible with NVGs. And if we equip the NVG option, we should have the HMD symbology in our right night vision scene (right eye), but only when the goggles are down and on. We should not have the ability to turn on HMD symbology without NVGs turned on, if we have NVGs equipped. Can anyone from ED comment? It would be great to get these things fixed. The current NVG scene seems to be a post processing effect which is probably why its a fixed size and not a fixed FOV the way it should be, but this is unrealistic and strides should be taken to come up with a better solution that is more true to life.

In a September 2023 newsletter ED revealed development progress of the new pilot model, specifically the helmet. I highlighted a point of interest to me, which is the mention of NVCD. After some quick and dirty google research I found this website: https://www.collinsaerospace.com/what-we-do/industries/military-and-defense/displays-and-controls/airborne/helmet-mounted-displays/joint-helmet-mounted-cueing-system My question is, are we eventually getting HMD symbology in the NVG attachment for our DCS Hornet? I haven't seen any discussion or chatter about it within the community.

RIP. I had another disconnect last night. Issue still exists.

Thinking back more, I think it was only a Throttle Grip firmware update, but I don't recall having a single in-flight disconnect from my stick base since, and I used to get them reliably 1-3 times per flight. Maybe there was some conflict.

Update: I updated the stick base and throttle firmware through SimApp about 3-4 weeks ago, and I don't think I've had an in-flight disconnection since. Anyone else noticing more reliability lately?

The 51st VFW has re-opened recruitment for the F-15E Driver and WSO slots. Apply at: https://discord.gg/51stvfw