AlexCaboose

@NineLine is there an answer on this? It worked previously and now is permanently illuminated. How is it a wishlist item?

It looks like you might be putting the missile in your RWR blind spot when you roll the jet. The beeps also sounded almost like a TACAN or ILS freq. Could you try a longer range SAM and avoid rolling the jet to prevent putting it on your blind spot? Something like an SA-10 near the edge of the WEZ. Well disregard some of that. I noticed at the very end of the YT video the launch indicator is flashing. Could still be partially the reason, but probably not the whole thing.

Why is this listed as wishlist and never stated as added? This functionality not only worked previously, but was also not permanently illuminated. Definitely a bug.

You should hear the lower tone here in Wags' latest video: (3:35) Check out this mod (although I don't know if it's compatible with the latest update). It uses audio from the Goldfein shootdown. https://www.digitalcombatsimulator.com/en/files/3326800/

While I haven't had a chance to download the update and check this out yet, what you should hear is an initial launch warning with 8 beeps, followed by a launch recycle tone 15s later at a lower tone. It should not be continuous, but there's an audible indication to let you know it's the same missile when the recycle is played.

Hey! Check out our post here: https://forum.dcs.world/topic/317585-the-421st-vfs-of-the-476th-vfg-is-now-recruiting/#comment-5135088 I think you'd be an incredible fit in our group! I

The 476th vFighter Group is pleased to announce we are opening our F-16C recruitment for the 421st vFighter Squadron "Black Widows"! If you have always loved the iconic Viper and would like to employ the aircraft with others in a realistic manner, only limited by what DCS offers, then be sure to check out our recruiting process. To learn more about F-16C specific recruiting details and FAQ, please visit this thread: https://www.476vfightergroup.com/showthread.php?8919-421-vFS-Recruiting-Requirements-and-Public-FAQ To apply, create a forum account and follow this link: https://www.476vfightergroup.com/content.php?144-recruiting-main To learn more about general 476 vFG training philosophy check out this video: https://youtu.be/sjk3UrbILTI 29 JAN 2023: Recruitment is now closed, check our website/discord/socials in the future for new opportunities or other squadron openings.

Are there plans to bring the full jamming effects over to client aircraft then?

That's exactly what I want - the most realistic version of the jet possible, and if it turns out I am wrong, so be it. But definitely I had noticed this changed a few times in the last 6 or so months, and there's been zero documentation of it in any of the patch notes. It just seems right now that unless you're pixel on pixel accurate, the bomb isn't coming off. If this is correct behavior, then it really needs to be documented somewhere, and I hope ED will really push to provide more accurate changelogs rather than require us to spend 8+ hours downloading an old version when the new one takes under 2min. The HUD footage I sent them suggests that the release doesn't need to have absolute dead on accuracy as long as it's close.

PM sent. Edit: Added some tracks from DCS OB v 2.8.0.33006 where a similar level of offset off the ASL was releasing the weapon just fine, which also aligns with what I PMed you. Viper G12 #3 2-8-0-33006.trkViper G12 #4 2-8-0-33006.trk

No, I don't have anything publicly available on hand currently other than that this has worked in prev. versions of DCS. It was then broken again sometime around June-August, and then fixed again afterwards before being yet again broken in a recent update. I am trying to downgrade my DCS install to provide you with a track showing evidence of this, but that's going to take some time. Regardless, this is a pretty common sense thing. It's a guided weapon and there's been zero documentation of the change in any of the patch notes. Please pass this forward to the devs for review in the meantime.

Submitting an additional track with less than 1° of offset where the bomb still does not release. Viper G12 #2.trk

The GBU-12 is being forced to release in 5mil constraints, which had been fixed in a previous update. These should be releasing in 3/9 just like the GBU-38. I've attached two tracks showing the GBU-12 and the GBU-38, as well as an overhead view showing the amount of offset. The GBU-12 is a laser guided weapon, and should be easily able to hit the target within these parameters. Viper G12 5mil.trkViper G38 3-9.trk

Yeah, not a bug

Please do, I'd like to see it. I received my unit a few days ago. I think it encourages you to use more force to take advantage of the slightly larger flex/motion of the stick. This in turn makes blending Gs easier, and helps to prevent overshoot.

I had the same experience with the shifting SPI location while hitting CZ a number of times. Unfortunately the track I've had was too long, but I'll definitely submit an additional one soon.

This would be incredibly useful for all sorts of training scenarios. I really hope you guys add this in the future.

Can confirm that doing it with search works just fine. Unfortunately I didn't think to test with RWR off so my track wouldn't be too helpful.

That's better than nothing!

The way it was implemented wasn't even correct. There's a whole process to get to status 6 alignment that involves moving the jet.

I think this is also a difference in service branch as well. I believe the USAF doesn't have switch changes at the range and the Navy will flip the switch before drop. I might have them reversed, but I believe Mover covered this in his CAS video.

This graph doesn't make sense. How would a board upgrade allow greater physical displacement? Surely that must come from the actual base itself, which you're saying won't be out until later in 2023.

No, the FSSB doesn't move. It also has software settings that allow you to adjust the left/right and forward/back force requirements separately.

-- to comment it out

I did a quick repair + commented out the line in export lua and it worked fine.