GumidekCZ

Here, read:

+1 Waiting to be designated as W.I.P. or "will be implemented soon"

Thank you!, quick response and positive one

Simple question for ED team, as the topic title indicates. Will it come with GPS/INS rework? which is planned to do. From early DCS Hornet Manual (page 110; Hornet NAVIGATION): MODE Option. ... SLEW (slew map with TDC when TDC assigned to the display).

Another proof of max 28 FLARES count, NOT! 32 as DEKA claims.

@Swift. In Super-Hornet and T-45 O/S (OAP) works same as for DCS Hornet, except two things, bith which make absolute sense to work like that: 1) if Range set to 0.0 nm, AOP returns back to original WP indication on HSI page 2) when WP coordinates (not elevation) is changed, AOP values are zeroized. Screen from un-official T-45 documentation - (same description can be found in NAVY P-821 T-45 document): Other un-official SuperHornet sim page documentation: The offset (O/S) is created the moment the range from the waypoint is greater than zero. Destroying an offset works in exactly the same way, by setting the offsets range back to zero. @BIGNEWY PLEASE, can you send this info about OAP reset to the team, if they can ivestigate this?

As title says: Roads into shelters are too close, the sharp turn shoul begin around 2m from shelter wall. Exmaple picture from H4 airbase.... but this can be seen at almost any airbase with such shelters. Another bad example - H3 North-West airbase: Google Map: RUWAYHID airbase is WELL MADE - Good example:

Why it must be this way @Harker? Colors represent MPRF bricks which are shown at the time corresponding HPRF brick is shown: Why it is not show this better way, so the HPRF and MPRF bricks are in result CLOSER - only half of current HPRF bin:

Sorry: THERE IS ONE GHOST BRICK FAR (2 NM) IN FRONT OF ALL OTHERS BEHIND IT (REAL ONES OR MC EXTRAPOLATED) AND IS NOT GENERATED EVERY SWEEP. The GHOST jumping BRICK is made by HIGH PRF sweep and the rest by MED PRF. The problem is as @Tholozor reported, that HIGH PRF brick is NOT coolocated with MED PRF and is show like 2 nm in front. Which now seems like two fighter jets in Trail formation - very stupid to give such not true and misleading information to Hornet pilot for proper SA at life threatening BVR situation. OK - the cant be NOT coolocated and this is because of HIGH PRF range radar BINS, but ... next post

Im more than sure, that these are NOT two same things we are reporting. Please check my Track file again if you didnt.

On radar screen, we now how extra strange dectection "GHOST" BRICK, which is jumping closer as soon a real detection brick will catch it. Will be still there, no matter how many BARS, azimuth scan angle, RWS or TWS... PG-73_radar_bricks_BUG.trk

AI descent angle wrong calculated, which results in unable to fly through its end of descent waypoint. AI_descent_profile_BUG.trk

After a Year, nothing Fixed ... even if Reported. Im adding tracks with "M" Sparrow version, missiles fired aprox at same distance: LOW - Target placed at lower portion of FLOOD cicle will miss target HIGH - Target placed at upper portion of FLOOD cicle will guide on target AIM-7_FLOOD_LOW.trk AIM-7_FLOOD_HIGH.trk

@FlankerKiller its not about if the Flares work in DCS and how they work (we all know about that stupid "random" game). Please take your time and read carefully what I have written above. Look at the weights.. now the Honet is using M206 like flares - lighter and lower aproximated lower efficiency than what it should have in DCS

Bump Hello ED? Mustang need some LOVE

COVERT selector knob - basicaly selects, which lights the pilot wants to be switched from "naked eye visible" into INFRARED SPECTRUM (same spectrun as LITENING pod IR designator) - VISIBLE THROUGH NVG (Refuel, Lower wingtip lights, Low formation light are not capable of IR emission). By switching between BRIGHT and DIM the pilots can set intensity of Covert lights IR emission. WHEN? ED, WHEN? we are waiting.... (:o)

Bump We still don't have any tool how to setup fighter to fighter Tacan for AI pilot in mission editor with proper +63 channel difference rule. I still have to set same Tacan CH to get Yardstick on my AI lead aircraft. We all know that it's wrong. We are patiently waiting for this feature in ME since A-10C was released.

May be you can help here, @NineLine PLEASE!!!

Thats because these two effects are STUPIDLY connected by single switch in DCS options. Wake turbulence set to off = Badly modelled Burble off

NOT IN SINGLE RW VIDEO of any airplane landing on carrier can be seen similar effect we STILL have now in DCS. THERE SHOULD NOT BE ANY NOSE PITCHING UP when reaching the deck before and hitting it with hook. I was hoping that yesterdays Hornet FM update would fix this idiotic behavior, but unfortunately not Im still patiently waiting, for fix. Then, and only then I will turn Turbulence effect in settings back to ON - so stupid than vortex behind big aircraft and burble effect behind ship is bound together and not divided into 2 separated setting switches.

YEAH, on of biggest mistake Western countries did in WWII ... together with selling plans by Brithish of their jet engine to Russia.

As title say: , I want to get rid of RU skins in any default ED missions RU skins ONLY for RUSSIA MADE PLANES PROPER SKINS BY NATION WHO MADE THE PLANE (not in licence)

Generaly Rockeye (MK 20) have fron fuze modelled for every module here in DCS, not just F-15E. IRL for MK 339 MOD 1 fuze, you can load two separate values of Arming Delay corresponding to the primary (AD1 - NOSE) or secondary (AD2 - NSTL) option timers - both timers set on ground. As you cycle inflight between NSTL and NOSE, the function times change to reflect this. TAIL select = DUD. Rockeye was fitted only with a primary and secondary timed delay fuze, which had to be both preset on the ground. Settings from 1.2 to 100 seconds. The fuze is preset at 1.2 seconds for primary delay, and the option delay is preset at 4.0 seconds. If you want the munition to function at a particular burst altitude (BA) to optimize coverage, you need only load that altitude in the SMS and the pull-up anticipation cue will function to let you know when you reach that (minimum) altitude. In this sense, the pull-up anticipation cue is not trying to satisfy a minimum fuze arm constraint, but is trying to indicate the optimum release point to ensure the correct function altitude. https://info.publicintelligence.net/USNavyRocketBombFuzeManual.pdf

As title say When RBL selected, after few seconds it will switch to BOL because of some instability. If you watch the HSI page, Harpoon symbology will flicker there. Track: Harpoon_RBL-unstable__BUG.trk

Because My June 2020 report still not solved and I found even more strange BUG behaviour, Im opening new report topic. Old one: Me flying MAG 270° (Caucasus map 276,2° TRUE), Harpoon set by UFC to fly MAG 270°, but instead of that, Harpoon fly its TRUE HDG 270° New find: Me flying MAG 260° (Caucasus map 266° TRUE), (Avionics set to MAG) Harpoon in BOL mode set by UFC to fly bearing 260° Than I switched avionics to TRUE and on HSI the line of Harpoon flightpath is correct ... 260° of TRUE, but after launch, the Harpoon will fly 254° TRUE. Thats radiculous! The missile should fly on type of bearing (MAG or TRUE) selected in avionics in time of bearing enterd in UFC. If MAG/TRUE changed in A/C HSI page after that, nothing should change - the bearing is already in memory of Harpoon INS. There is no command that should change it. track attached Harpoon_BOL_bearing_BUG.trk