Aernov

Edit: EHSD TGT and STP symbology is correct as is, my mistake. Trying self-lased LMAV attack, I have encountered the following: after marking target and firing my laser, I used SSS forward long (in TPOD HOTAS mode) to switch to LMAV from TPOD screen, which worked. Then Maverick uncaged, locked on laser spot and launched without any problems, and lasing continued, but when I tried to return on TPOD page with SSS press twice, lasing stopped as soon as the page was opened. Maybe this is caused by TPOD being deselected or reselected as SOI, but it seems wrong. Is it? AV-8B TPOD + LMAV.trk

As NATOPS says, correct idle RPM for our version of Pegasus is 28.4% - 29%, and it should move the Harrier on idle, taxi procedure is done with idling engine, and speed is maintained by nozzle deflection, so this behaviour is correct. Kind of. Right now in-game idle engine thrust is exaggerated, as recommended nozzle angles for taxi speed control (45-60 degrees) aren't enough to cease acceleration.

By default carb heat lever is set to "cold" (forward) and air filter is off (aft).

I have started first flight with top 4 CM dispensers filled with chaff and bottom 2 - with flares, spent some during a mission and returned to base to rearm/refuel. After rearming with engine on I can't use kneeboard to configure CM loadout (which is as intended), and adjusting chaff/flare quantities in rearming menu seems to have no effect, Aircraft is loaded with 120 fares and 60 chaff regardless, and EW page displays incorrect CM values (for chaff only in this case).

Also, flare interval can be set to whole seconds only, no 0.300 and such, just 1, 2 etc. Is this correct?

It's there, right under arming/jettison panel. If you lean slightly left and back it is visible enough to determine it's position.

AV-8B MFD symbology visibility.trk I've placed AV-8B (air start with WP 1 marked as AAR zone) and KC-130 with TACAN 14Y on an empty Caucasus map. Symbology from right MFD could be seen on the left one (but not vice versa). Here you can see AAR zone circle from EHSD on the right MFD on the left one. Symbology is placed "correctly" according to EHSD scale (increasing scale moves symbology from the left MFD). Also, there was a report about TPOD 2D Yardstick being visible on the left MFD from the right one, seems like the same problem.

Is there a HOTAS function for Sidearm selection in AV-8B? I have never heard about it. And currently Sidearm selection puts it in caged mode, which can lock emitters close to boresight line (or velocity vector, it seems that caged Sidearm is slaved to it) and does it very inconsistently. Pressing cage/uncage button lets it search and lock off-boresight radars (but not very reliably too, one time it locks SA-11 from 15 nm at 45 degrees off-course, and in the next attack it doesn't see anything at all, while RWR plays intricate songs about 4 SA-11 launchers and two SA-15s tracking you). Also, Sidearm lock crosshair shows incorrect emitter location (not even close) since HUD was redone in september(?) 2020.

Better seen at night.

Does turbo lever operates some kind of automated regulator that maintains set MP, or is it just mechanically (via hydraulic/oil piston) closes/opens exhaust waste gate thus regulating amount of gases directed to the turbosupercharger bucket wheel, increasing/decreasing it's speed in near-linear fashion? Is there any info on turbo automatic MP regulation system?

Hot nozzles are glowing although the engine wasn't running in this mission (cold start). Looks like glow intensity is independent from JPT (which was around 8 at the moment I took this screenshot).

Maybe, but it looks like we see the inside of storage and gun pods through that gap, with transparent textures and everything. And this bridge is shaped like it is supposed to be flush with the fuselage. Here we can see part of the middle section with exposed rivets and no paint, it looks like the contact surface of the pod itself. (I couldn't find a better photo)

There is a pretty big gap.

As you can see on the screenshot, TACAN symbol can be seen just above right Sidearm box on STRS page on left MFD while EHSD is displayed on the right. This is an old issue, it was reported many times but it is still there.

Learn it slowly, begin with Chuck's, majority of info in it remains correct, and update is coming sooner or later. Or you can get NATOPS for (T)AV-8B and learn from it, but this way you will encounter and acknowledge all the bugs and errors in system modeling, and it will make you a little sad. But Harrier is an interesting plane and a great module still, and it is complete enough (for the most part) to be very capable in DCS, so don't get discouraged.

1) External model canopy slide rails seem to be modeled incorrectly - canopy sides do not touch them and red lock lever head can be seen in the gap where the rail should be (in cockpit view all is good). 2) While flying formation online I saw lead's intercooler shutters flap back and forth a few times and then stay in fully open position, he denied any input on them when I asked. No track or video, sadly. 3) After getting hit I saw black smoke behind me, which I identified as oil leak (I could not identify the "source" of that smoke, but it definitely did not come out of oil cooler outlets, and all cylinders were good, RPM were stable). Sure enough, oil pressure dropped soon, and did it in a moment, from normal to zero in like one second. Is that correct behaviour? shouldn't oil pressure drop gradually as it leaks out? Also, after oil pressure dropped there was no easily identifiable lubrication loss effects (CHT rise, gradual change in engine noise, RPM instability and eventual engine death) for nearly 10 minutes, I was able to RTB and land, and engine was working fine. And the smoke did not stop. Is this correct or damage model is still WiP?

What I got from manuals and 1943 introduction video for P-47 is: boost is optional for all takeoffs, majority of takeoffs are performed without turbosupercharger, and takeoff MP is 52''. From this I assumed that this MP can be achieved without boost. With turbo this setting can be reached easily at high elevation fields too. And I also assumed that P-47 can climb to 7000 ft without applying boost, and DCS one requires turbo to maintain 42'' as soon as 4000 ft. Also, I was flying A2A Simulations P-47 for a long time and got some "habits" and preconceptions about plane's operation, which did not "dissipate" for three years since I have moved from FSX to DCS. So, my questions are based on assumptions made from lack of definite info in manuals basically. I just want to know if DCS P-47D works as the real one made in 1940s, and I can start to learn stuff and form new habits without relearning it later when flight model or system operation gets updated.

Is there an explanation for this CB behaviour?

Almost no P-39 or P-63 mentions, why is that? It has some unique flight characteristics, was used and liked by Soviet pilots (looks like we won't get any USSR-made aircraft in observable future anyway), has decent A/G capability, looks good...

Shouldn't P-47 be able to reach 52'' manifold takeoff power with throttle alone? Our P-47 reaches maximum of 46'' - 47'' at near-sea level altitude with "default" DCS weather conditions (29.92 in Hg, something like +15 deg. C, no wind). Is this correctly modeled? And should it lose manifold pressure with increase in altitude as fast as it does now? Shouldn't regular geared supercharger provide enough boost to climb to 7000 ft at 42'' manifold?

I'd love to get a late razorback modification in DCS (D-22 or -23, or both). How much difference is there between late razorbacks and already modeled bubble canopy P-47s systems-wise? Will it be too much work to make them? (3D model, aerodynamics, prop controls)

You'll have rockets, not only S-8 with HE and HEAT warheads which already can kill most things (except tanks, usually), but bigger ones as well, including S-24 (those can kill a tank or two, a building, concrete bunker...). Later you'll get R-60s, so air won't be safe around the Hind either. 30 mm cannon, while not as effective as GAU-8, still capable of doing some bad things to a lot of vehicle types. Apache "gameplay" will probably be very similar to Ka-50: hover above tree line and launch missiles from a distance. Mi-24 will do strafing (or even bombing) runs at relatively high speeds in addition to launching guided rockets. And infantry support missions can be done, it just requires more planning and editor work.

We could use some missions which require cold start and takeoff from FARP, road base (possibly with trees in the way), short runway (like the one on the famous Georgian "cross" unmarked airfield). Those will force us to use RVTO or even VTO, increase the value of in-air refueling and somewhat limit possible payloads. Also, strong crosswind, bad weather and night variations of the same missions (although in it's current state (no proper DMT contrast lock and incorrect slew behaviour, no FLIR hostpot tracker, incomplete NVG features) Harrier is not much of "N/A" yet). Also, some missions can be made with random target placement, so they will be slightly different each time (and a lot different if the random placement area includes mountains), searching for targets can be interesting after Razbam introduces (and fixes) hotspot tracker.

Your rudder axis may be assigned to multiple devices, one of which causes constant input to one side, you can check that in axis commands. Harrier can spin with strong "rudder" input (which translates to activation of reaction control system nozzles while Harrier is in hover mode or has enough duct pressure), but it can be stopped easily if you manage to hold the plane horizontal during this spin and recovery.

The damage is there, but ENG page and engine life count stays the same regardless of engine status. It should dissipate at a rate dependent on JPT, from less than 0.1 "points" per minute on <645 deg. C to more than 1000 PPM at temps greater than 800 C. It is not as important as DMT and other stuff described above, but it would be nice to have still. Also, they could program some power loss proportional to life count (more wear on the engine - less power allowed by DECS/JPTL), if it's not already implemented.