Aernov

Last time I messed with rockets Q-M-I settings I found out that they aren't reacting properly to those regardless of single or ripple fire set up. Proper QMI settings effects for rockets (and everything else) is described in NWP 3-22.5-AV8B, Vol. I - 1.14.6.3 UFCS Weapon Programming.

In all my time doing A/A refueling I never encountered this somehow. You will start to detach if you get way out of imaginary cone behind the refueling pod while getting fuel, and there's no physics for the basket, so the drogue won't collide with the probe, but that's true for every plane in DCS in my experience.

Yes, now I've found it. Unless newer software eliminated this feature (which is unlikely IMO), markpoint is created at existing designation or beneath the plane.

"A TOO designation is provided to allow low level head-up designation of unplanned targets of opportunity. The pilot presses the TOO pushbutton on the UFC to designate the point directly below the aircraft as the target. This action automatically turns on the radar altimeter (if not operating) to supply target elevation to the system and commands the A/G master mode for immediate attack." (NWP 3-22.5-AV8B, Vol. I) As I understand it, TOO press designates the point under the aircraft (if no designation was present at the moment of button press?) thus creating T0 as any other designation does, and prepares UFC for assigning numbered targetpoint to that designation (T1/2/etc.). At least it should, I'm not sure if it is working currently. I found no evidence of it creating a markpoint at the same moment.

The issues with incorrect HUD range and offsets persist still. And shouldn't TOO create a designation (targetpoint 0)?

At the end of the official manual there is a section about EE describing it's differences and procedures with new systems.

As the title says, circular waypoint marker on EHSD moves when WO/S for that waypoint is boxed. This can be observed in centered EHSD mode too. Screenshot is from Syria, singleplayer. Also, sometimes selected waypoint marker just disappears until it is reselected, I didn't notice exact cause of this, but this occurred when I was messing with NSEQ, offsets and TOT (it disappearing and reappearing with subsequent presses of A/G undesignate HOTAS command without designation present is a different issue).

As seen in the screenshot, HUD shows velocity vector slightly below horizon, meanwhile right MPCD HUD display shows it at around +2° pitch.

Cockpit surfaces illuminated with caution and warning lights and cabin pressure gauge have correct coloring consistent with the light source, but red lamp inside gear lever head shines white (or greenish-white light):

Required RPM varies with speed and altitude, for ground attack keeping RPM at or above 70% will cover all speeds above 0.5 M for altitudes below 5000 ft.

Normal in-flight position is IFA (tightly coupled INS-GPS with constant INS drift correction), in NAV you rely on INS only, which will (at least it should) lose precision in time and needs to be updated. As per HUD heading mark - recently there were reports of it working incorrectly in some cases.

For TO mode - "Water flows when the throttle is set above 105 percent rpm. After takeoff, water continues to flow until airspeed exceeds 250 knots, water is depleted, OFF is selected, or the throttle is moved below 103 percent rpm". For LDG mode - "Water flows when airspeed is below 250 knots, jet pipe temperature exceeds 765 °C, and the throttle is set above 105 percent rpm. Water flow stops only if water is depleted, OFF is selected, or the throttle is moved below 103 percent rpm. After initial water flow, water will flow each time the throttle is set above 105 percent rpm, as applicable, regardless of the JPT until the LDG mode datum is reset by cycling the H2O switch". It does start at 765 C in DCS.

Yeah, Kozhedub's La-7 was blue-gray + dark gray + red nose and white tail, but one can dream ) I always liked АМТ-4 -6 and early 4БО more. Here's a modern photo from Prague (Kbely) aviation museum:

Some non-personal liveries based on historical personal ones would be great (i.e. the liveries with special elements like arrows, slogans or dedications, Guards badges etc., but with customizable numbers and no victory marks). Also, camo variants other than late war grey, like on the pictures below. And, if fictional liveries are acceptable, some famous or widely used ones from previous plane models (La-5 and 5 FN) would be nice.

I tried it in TOT NSEQ mode, but I guess is works the same way for other time functions too. After entering desired TOT and activating CS/T, UFC scratchpad should display desired speed (which it does) and time remaining to reach the point for which CS/T is calculated (time to target). Currently in DCS time to target stays the same as it were at the moment of colonising CS/T on ODU: 1 1) Here I am at W1 to W2 leg, TTT displayed is 19m 40s (TOT NSEQ with ingress as W1-W2-W3(which has a WO/S) and egress as W4-W1) ----------------------------------------------------------------------------------------------- 2 2) And here is W2-W3-WO/S leg, 5 minutes passed yet TTT is still displayed as 19:40. TOT itself works (mostly, in direct and NSEQ modes), it's just UFC TTT display showing static time.

NWP 3-22.5-AV8B, Vol. I, page 2-41, section 2.4.1 "Waypoint and Offset Designation on EHSI/EHSD Display" says: "If there is an offset to the waypoint, the designation may be transferred to the associated offset by pressing the WO/S pushbutton". Currently in DCS pressing WO/S for designated waypoint seems to select the offset as steerpoint (EHSD and HUD symbology starts guiding plane to it), but designation and EHSD markings stay on previously designated waypoint. Only way to designate WO/S is to undesignate W, select WO/S and designate it directly. Also, there's this function: "The pilot can also transfer a designation to an offset from a waypoint by overflying the waypoint and pressing the waypoint overfly (WOF) pushbutton on the UFC. If no waypoint offset is available, the waypoint is designated. This action automatically calls up the A/G master mode if not previously selected, displays attack symbology (if weapons selected), and enables both altitude and navigation update on the UFCS".

It's hard for me to find a single concrete source on the matter, I can't even find the book this illustration is from. Standard S-60 battery (I haven't used KS-19 yet, S-60 is the subject of this post) consists of two sections of 3 guns (so 6 in total), while other sources claim that 4-8 guns were used with 1 SON-9 and 1 PUAZO-6. SON-9 is used in conjunction with ПУАЗО (anti-air artillery fire director unit, not present in DCS, closest thing we have is German Kommandogerat 40), which can remotely aim and set fuze for S-60s. I've found no info on the max quantity of supported guns per unit, majority of illustrations show 4 guns (probably as an example). Photos and videos show 3-4, but who can guarantee that there aren't another dozen of guns out of camera FoV? )

That can be it, this way the battery fires without interruptions for reloading. It would be nice to have an option to enable "full force" fire though.

Here we have an 8-gun AAA position of S-60 + single SON-9. For some reason no more than 4 guns at a time are tracking and firing at targets. "Active" guns are changing (not the same ones stay inactive, changes happen during engagement too). I've tried adding additional SON-9, no effect. This forces to split groups to multiple 4-gun ones, thus the number of SON-9s grow as well and already emitter-rich environment becomes a total mess.

Searchlight and ПУАЗО-6 AAA fire control unit around SON-9 radar. We have German searchlights+KDO for FLAK in WW2 assets pack, so the technology is already in DCS, it would be cool to have versions of these in core DCS, available for all without additional purchases. And the ability to remove on-map light sources (town lights, street lamps etc.) in an area with a trigger zone similar to removal of objects would add a lot to night missions.

On the left - camera is outside of searchlight beam, on the right - inside the beam. The beam and "flare" around the projector itself disappears completely, while cockpit gets "washed out", not really flooded by bright light:

But it has IFF transponder and already clickable switches for it on ACNIP. We also have IFF UFC buttin that is INOP currently.

Arise, topic! The issue returned with last update or with one of hotfixes...

Instability starts to make formation flight almost impossible with intermittent wing drops from depicted distance (flight at 17 000 ft, 0.7 M, about 8 kts headwind). Moving forward doesn't change much, only increasing distance helps.