Nealius

What triggers the cool-down cycle? A certain switch position? Pressing and holding the lock button for up to 30 seconds with the bandit 30-45 degrees, radar in ILLUM, HMS selected, and nada. However I was practically in formation with the target drone, so would lack of relative velocity mess with the radar's ability to lock?

Trying to but I cannot achieve lock until the bandit crosses within my canopy frame which is something like 10-20 degrees (estimating). Manual switch doesn't appear to do anything for me. I can press and hold the missile fire button but it still won't fire.

Is there a launch authorization override somewhere? Reason I ask is for two scenarios: 1. High-aspect R-27ET engagement gives me launch tone at around 18nm but I cannot get launch authorization until 3-4nm, preventing me from getting any range out of the "extended range" missile. 2. HMS off-bore shots with R-73: I can only employ the HMS in conjunction with radar or IRST, which in my experience will only acquire targets within the canopy bow; I am completely unable to achieve an off-bore lock on targets outside my canopy bow. Particularly point number 2, a recent Spudknocker video shows him engaging targets off-bore with HMS without locking a target at all, but there is no explanation for how he is doing this.

PACAF standard load notation makes a bit more sense tbh. For example: 4A 2W x2 = 4 AMRAAM, 2 Sidewinder, 2 wing tanks.

I had my reticle offset while level. I wonder if it's shifted by wind.

I've noticed the same with the cannon, but mainly when using IRST with radar in dummy mode. Using an IRST track the gun symbology is offset an entire reticle length to the right.

Continuation of this issue: In some situations the issue has been resolved, but it still exists with certain unit/livery combinations.

Are these planned for public release? I spent a few weeks in Czechia and love their aircraft paint schemes.

I'll check out your vid when I have time. Typically I avoid videos since I need written text and ctrl+F capability to find the info I'm looking for; also cellular data consumption

The real-world Luftwaffe manual has much more understandable wording for explaning this system: In TAC the remaining flight distance is calculated based on current fuel flow and ADC data. In OPT the remaining flight distance shows the max possible range "with an optimized calculated fuel flow." I believe this would be referenced through charts, however my manual is incomplete and missing said charts.

Happens 100%, every flight, including training missions, on my system (7800X3D, 4070Ti Super, 64GB DDR5, all SSD).

If we can get a system of localized weather, yes that solution is better. currently weather is global to the whole map, meaning a timed setting is more practical within the current engine.

A pattern I've noticed on my end has been that the 109 and Anton seem to be opposite what they should be in terms of robustness. I can sink a lot of ammo into a 109, pop his radiators, and he will still somehow climb away from me with damage that would have seized the engine on a player. The Anton, which should be capable of taking a lot of hits (and indeed does when I'm flying as a player), always drops the left landing gear after getting hit with a burst of .50 and the pilot bails immediately.