Bentman

Aernov, Thanks for looking at this. You are absolutely right - I was setting interval incorrectly!

Greetings! It's awesome the AUTO release cue is fixed with 2.9.0.46801, but it looks as though QTY is not working, unless I am doing it all wrong. Here's what I expect, based on how I read the AV8bNA Guide: QTY should determine the number of drops (release pulses) per pickle. MULT should control the number of bombs released simultaneously each drop. INTV should determine the distance in feet between where each drop impacts. So if I want to drop a string of 8 high drag bombs impacting one after the other every 500 ft, I believe I should be setting QTY to 8, MULT to 1, and INTV to 500. Or if I wanted to drop 8 bombs in 4 drops of 2 bombs each, with each pair separated by 200 ft, I believe I should be setting QTY to 4, MULT to 2, and INTV to 200. However, it seems that no matter what I'm allowed to set QTY to, as far as the jet is concerned, it remains effectively fixed at a value of 1. I can drop multiple bombs per pickle by increasing MULT. Of course those drops occur simultaneously, making INTV irrelevant. I've tried this both in AUTO and CCIP with no difference in behavior (that I can detect). Tracks attached. Of course it's entirely possible that I have just not grasped QTY/MULT logic and everything is working as intended. In which case, never mind. Thanks! AV8BNA_AUTO_QTY_MULT_INTV..trk AV8BNA_CCIP_QTY8_MULT1_INTV500..trk

Still getting the flickering black box when looking in certain directions relative to sun location. Open Beta 2.7.10.18996 Processor - Xeon W-2140B 3.2GHz Ram - 32.0 GB GPU - Radeon Prof Vega 64 - 16 MB - Driver - 20.45.40.10 Windows Version - Short_Black_Flicker.mp4 10.0.19042 Build 19042 black_flicker.trk

I also think it is sun angle. Attached are a couple of track files - the 1st starts at 0455, flickering starts a minute or so in, apparently once the sun gets close enough to the horizon. The 2nd starts at 0520, and once the sun is high enough above the horizon, the flickering stops. I noticed this a couple days before the patch to 2.7.9.17830, and see the same thing after it. Emptied the contents of the fx and meta2 folders, no change. av8bNA_black_box_0455-0500.trk av8bNA_black_box_0520-25.trk

Thanks for the response. Yup, problem persists with today's update. New .trk attached. av8bNA_sidearm_debug_OB_59398.trk

In open beta, after Sidearms lock on, the reticle projected onto the HUD no longer centers on the emitter (it does in stable). For me at least, the weapon itself seems to be acquiring, locking, and homing as expected, both caged and uncaged. I'm attaching a track file. I do appreciate that waypoints now display on the HUD in A/G mode! av8bNA_sidearm_debug_OB.trk

Thanks for the update!