Aernov

Just did VTO with 21000 lbs from 140 ft AGL, I was able to hover at 60-70 ft (50 ft with LIDS retracted) and transition to wingborne left me with 190 lbs of water. Vertical landing at this mass would be kinda difficult with water and probably impossible without it, but again, you have 3100 lbs of fuel to dump before VL. Edit: at 25 deg. C, no wind

I think, life count and OT time in DCS are just random numbers to fill the space on ENG page. Maybe one day there will be life count dissipation varying with engine parameters, and OT time recording. And these numbers will be useful for approximating engine performance margin. One can dream.

Also, doesn't plane's attitude look a bit exaggerated for the indicated AoA? It has relatively small wings, so higher AoA is expected, but it looks like it struggles to fly and holds in the air only by engine power even at decent speeds. On the screenshot altitude is high (VREST Cruise recommended, getting this high is a struggle with heavy and draggy payloads, and maintaining recommended Mach number is sometimes impossible with time-unlimited engine ratings), so AoA is high too, and after measuring the angle (in GIMP and with no real reference for wing axis, so as imprecise as possible) it is pretty close to indicated, but still it looks a bit much for me. Maybe I need to watch more IRL videos to correct my impression.

This example is from instant action mission "Ready on the ramp" W3 is in FH grid, so, according to (my understanding of) provided guide to UTM coordinate system, only 37T zone squares should be available to select for new point entry, while ODU shows three squares from 37U. Interestingly enough, with other waypoints selected grid restrictions were present: From KM square only zone 38T grid was selectable. Also, should UTM grid availability for new point entry be relative to point selected on DATA page earlier, or should it be relative to aircraft position?

I had target point designated (DESG boxed on EHSD) and was going to look up the locations of waypoints to find out which one marks my home base, but DATA page showed same point on the map regardless of selected waypoint, while page symbology changed according to waypoint selection (and aircraft position was shown relative to that selection too, but I am not sure it was correct). Initial DATA page for WYPT, T0 selected W1 selected - symbology changed, but map did not move W2 - same thing and W3 Also, point coordinates are shown in degrees/decimal minutes but can only be accepted by the Harrier in degrees/minutes/seconds (or MGRS/UTM).

Should DAI be kept on horizon during VL on stationary surface? Hover is maintained with it on horizon and nozzles at 82 degrees, but on touchdown nose wheel ends up high above the surface, while IRL videos show almost simultaneous nose- and main wheel touchdown. Should nose be lowered just before landing? Or higher nozzle angle is used IRL?

AV-8B TPod polarity and FoV.trk Here is the track displaying described issue, and two more: 1) WH/BH OSB doesn't toggle polarity, just changes it while the button is held, and changes back when released. HOTAS command (SSS right short in TPod HOTAS mode) works fine and toggles polarity. 2) Sometimes TPod-designated point jumped for some distance closer to the plane position shortly after changing polarity via SSS right short, but this jump thing was inconsistent.

Changing IR polarity for TPod while in narrow FoV sets it in wide with narrow mode "crosshair" symbology (no frame indicating narrow FoV borders in wide view, same yardstick distance indicated etc.). After this occurs, pressing FoV HOTAS command (SSS left short) or WD/NR OSB once switches "crosshair" to wide mode symbology while not changing actual FoV, second press changes FoV to narrow with appropriate symbology, and it stays "synchronized" for consecutive presses.

After SEAD mission my Harrier's snoot looked like that: DMT was blown off completely, but when I opened DMT page (SSS aft), I got LST page with indication of seeker moving in search pattern Should seeker movement be indicated if the majority of DMT assembly is lying somewhere in Beqaa valley? TV page showed black screen with plane attitude symbology, while HUD displayed small circle inside velocity vector (indicating DMT TV as active sensor). I haven't tried to actually find laser spot, or slew TV around though.

On the screenshot: mission year is 1985, so GPS is not operational, yet INS-GPS coupling works (whole flight was in IFA mode, and there were no difference in aircraft position in POS/INS and POS/GPS (so, INS was updating from nonexistent GPS), and horizontal and vertical error values were displayed in the bottom left corner of EHSD and on STRS page (and were relatively small too). I didn't test JDAMs and GPS availability for REDFOR Harrier.

Online mission (on private server) - and the same thing occurred after rearming: 1) Initially I filled all four top dispenser pods with chaff and bottom ones with flares via kneeboard after arming the plane at the beginning of a mission, with engine off. 2) Task changed after startup, and I rearmed for the second time on the ramp with engine running. I didn't touch countermeasures sliders in rearming menu at all (so they were set at 120 flares 60 chaff). And the result is on the screenshot. I didn't check for real CM quantities and pod distribution.

This issue with SA reticle pointing at anything but approximate position of locked emitter was fixed for some (short) time before HUD update in september 2020, then it broke again, and stayed like that since.

There is a quick fix in Razbam discord. It will probably be posted on the forum soon.

The procedure involves only LMAVs, but currently all weapons seems to be affected.

The issue seems to be caused by TPod video feed/HOTAS mode. IR Mavericks and other weapons work fine on their own and with DMT/LST, but, if TPod is in HOTAS mode (SSS down twice) or, maybe, just when TPod video is on the MPCD, all weapons (I have tried Mk.20, GBU-16, GBU-54, APKWS) aren't displaying attack symbology on HUD, stations aren't boxed on STRS (but weapon name stays boxed in the top MPCD border), and when you attempt to select ordnance, attack symbology and STRS selection briefly flashes and drops again, HUD shows only dashes indicating "no ordnance".

AV-8B Flare-chaff experimentation.trk Doing full mission with return/rearm would generate too large of a track, so I placed hot-started Harrier on the ground and experimented a bit: 1) I loaded it with 120 chaff (all in four top dispensers) and 60 flares (in bottom two dispensers) from the editor - and expendables were correctly loaded in mission and indicated in kneeboard page (although I didn't spend all chaff and flares to check the "real" amount). 2) After spending some I have rearmed the aircraft with chaff set to 120 and flare to 60 in rearming menu - and after rearming counters displayed 120 chaff and 60 flares in the same dispenser configuration as was set initially (all chaff on top, all flares on bottom), and kneeboard showed the same (I didn't check for real amount by shooting off all the expendables though). Then, after spending some amount again, I have rearmed with 60 chaff and 120 flares set in rearming menu - and got the same loadout I set in the editor (120 chaff top, 60 flares bottom). This is fine (if we actually getting chaff/flare amounts what is indicated in EW page and kneeboard) because there is no way to control which dispensers would get which CM type in rearming menu, so you'll need to shutdown and use kneeboard to reconfigure (which I didn't try during this test). 3) EW page counters displayed correct amounts, both initially and after rearming, but only in EXP AUT position. In UP position only 90 chaff were counted (while I loaded all 120 in top blocks), and during launch counter sometimes skipped and didn't decrease the number while chaff was deployed. Also, if you try to launch chaff (located only in top dispensers) with DWN selected, nothing will be launched, until knob is positioned in UP, then chaff single or program will be launched (once, regardless of amount of times you pressed CM Chaff with EXP in DWN), same thing with flares in bottom dispensers. For some reason I thought that this UP and DWN selection just set priority to top or bottom CM blocks, launching expendables of desired type from them first, but not prohibiting launch from the other group of dispensers if selected one is empty or does not contain charges of desired CM type.

Switching ext. lights master from normal to NVG increases formation lights brightness (both during day and night), which seems strange. 1) Norm mode: nav lights (set to dim), low formation lights brightness (barely or non-visible during day) 2) NVG mode: nav lights in IR, formation lights somehow a lot brighter (and clearly visible during the day) Seems like formation lights state is switched between NVG and normal modes. Anti-collision beacon is visible in both modes.

Just tested, this issue is fixed. Haven't tested with all bomb types though since everything except for AIR worked fine before.

Is your DCS beta version up to date?

"Experimental features" checkbox is still there, and, even though I have it checked, RWR doesn't show lock direction, all four lights are lighting up anyway.

Max thrust is, probably, reached at max engine rating, which is short lift wet (and a lot of takeoff-related charts use SLW or Dry as requirement). And engine damage or power limiting shouldn't start until allowed time for particular engine rating is exceeded (i.e. you can keep 113.5% RPM and 780 JPT dry for 14 seconds or 111% 750 degrees combat thrust for 9 minutes 50 seconds without consequences aside from life count dissipation). And after VTO (slooow one) and hovering with roughly 18 000 lbs GWT (no armament, just fuel and water) at 107-109 RPM dry I have checked the chart and it was pretty much spot on (with default DCS 29.92 inHg, +20 degrees at 33 ft ASL). So, at this mass (there were over 3000 lbs of fuel) I could have been hovering for 10-15 minutes continuously (fuel flow was around 220 PPM though) with power to spare (to 113.5 RPM, plus wet datum to 120% RPM). There's a lot to relearn and come to terms with, but it is a great change to realism. Life count dissipation and overtemp time recording on ENG page would be great, and can be used in-game for gauging expected engine performance. Life count IRL doesn't necessarily mean engine damage, it's just engine "life expectancy" until next maintenance/change (as far as I know).

Also, what about VSTOL HUD not displaying wet datum RPM/JPT info if those are in range from 109% (normal max thrust rating) to around 113% (start of wet hexagon symbology)? I doubt that real Harrier would leave it's pilot without easily seen important information during VL by stopping display of numerical values from above normal flight ratings to "hexagon values" (less than 6% or 60 degrees from maximum allowed RPM/JPT).

Standard checkflight procedures require to check max RPM - 120.2% for 408 engine, and there are photos/videos with EDP RPM window wisible and showing 120%, so, I guess, it should display 120% for short lift wet rating. There is another issue - as far as I can tell, there are no power increase with throttle movement after engine reaches 116% RPM, you still can move throttle forward, but RPM and, it seems, power, won't rise, and there will be no "15 seconds" warning at full throttle.

It can hover with gross weight up to 22 000 lbs (well, not really at 22k, but close to it) in "default DCS weather conditions" close to sea level, and does it at norm lift wet rating. It would take off vertically at higher masses, but for some reason I was unable to set short lift wet rating during my tests (31.05.2021), engine just didn't go further than 116.8%. Is this a bug?

All bombs, other than AIR, were selectable all at once, TER or not. I have tried same configuration with slick Mk.82s, Snakeeyes, Mk.20s (with 1-2-2-0-2-2-1, there is no three-bomb rack option for 20s).