GumidekCZ

Dont be frustrated @Bowie . Be cool and patient. If you cant help yourself on your own, here are some of my advices: 1) FIND ANOTHER GAME with which you can forget how bad you feel about ED and DCS. 2) NEVER EVER use DCS AI units in your / your friends mission 3) NEVER EVER be campaign or mission creator - I know some of them and they are speachless of ED's inability to maintain DCS bugless.

If "RTB on Bingo Fuel" option is set to "NO RTB ON BINGO FUEL", AI refuse to AAR if commanded to by action trigger. AI_refuse_AAR_BUG.trk null

Without track file, your bug report is USELESS!

nullI did set two triggerd actions with TACANs set for LEADER (after 10 secondsand) also fow WINGMEN (after 30 secondsand). After 30 seconds, nothing happens. TRIGGERED_TACAN_ACTIVATION_BUG.trk

@NineLine This is still and issue - Especialy now when GAMBLERS campaign is out! Can you please check, if team is working on fix? this example track with AI Hornet: AI_Descent_BUG.trk

@NineLine I can confirm this BUG. I have flown as a GAMBLERS campaign tester AI formations for hours and hours ... ALL OK! But after recent patch in Mission 01, Weasel 12 (Formation Echelon left) is NOT STABLE and is doing small side waves. - THIS LOOKS AND I CAN NOT FLY CLOSE FORMATION WITH SUCH AI

If AI Later spawned in shelter set, another live AI is refusing to park in. Instead will taxi into shelter which is located in farthest distance from current shelter on the opposite side of airfiled. CONFIRMED JUST ON SYRIA MAP (multiple airfields) SO FAR: AI_REFUSE_PARK_IN_SHELTER_BUG_Syria_H4.trk

DCS 2.9.5.55918 @BIGNEWY this bug is not only about snap views, but about DCS not reading Lua file with user saved view values. F-16 default values from my SnapViews.lua - C:\Users\Gumidek\Saved Games\DCS.openbeta\Config\View\ The values were created by pressing RAlt+Num0 [13] = {--default view viewAngle = 78.268605,--FOV viewAngleVertical= 53.910793,--VFOV hAngle = 0.000000, vAngle = -20.316243, x_trans = 0.021000, y_trans = 0.083000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, The data are there, but DCS will NEVER LOAD these data! According my test DCS is using saved FOV or angles only till the quit of DCS game. After that DCS is unable to read or return to these vaulues. If you delete this file and DCS will create new one after saving FOV, but will NEVER use it/read it ANYMORE!

"using" or just they had in amunition store, but decided not worth of using it, (due to power Hornet have available or other reasons)?

Thanks, Poor CAA performance may be also the reason, why I cant found ANY YT vid with CAA ACM mode explained and shown in practice. I hope that next update will fix this to be realistic, but still usable at some good conditions.

Have anybody same problem as me, that this Auto Acquisition is constantly locking ground or some imaginary ghosts, simply anything else then target in front of me? I dont have a track now - I will add it tonight.

+1 good idea! We need it.

Most, if not all DCS F-16 liveries looks like this one: Not only the panels in Mid Fuselage, but also other panles on fuselage are reaised - NOT CORRECT! This way are done only the fuslage structure reinforcements seen on some other F-16 blocks. Real F-16 picture (NO panels height offset, just reinforcements) : What Im seeking is just shallow bumb in the middle of these panels - outer edge of panels in level with fuselage ... as such can be seen in real pitures with specific sun light direction:

+1 I would like to know the limitations! Which signs are forbidden? or if there are some non usable combinations of letters and numbers...

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