discwalker

Teamasian: https://forums.eagle.ru/showthread.php?t=281728 here reported

The "HUD only" view in su-33

all confirmed for old Kuznetsov ramp start 2-5-6-52437-su33anomalies_rampOldKuznetsov.trk https://cdn.discordapp.com/attachments/543358251694292992/736557705279307776/2-5-6-52437-su33anomalies_rampOldKuznetsov.trk clearly readable HUD poll: https://forums.eagle.ru/showthread.php?t=280991 I would like to add this: things could be red in mirrors Because this is closed: https://forums.eagle.ru/showthread.php?t=281013

the needed track AIs must be smarter: able to land their planes to nearby carrier. AIs started with 30% fuel. 2-5-6-52437-bingoEjectSinceFA18c_release.trk https://cdn.discordapp.com/attachments/543358251694292992/735888594992103424/2-5-6-52437-bingoEjectSinceFA18c_release.trk

And yes: https://forums.eagle.ru/showpost.php?p=4281855&postcount=2 gear structure damage

Yes: https://forums.eagle.ru/showthread.php?t=270567 with illustration:

the clock icon man! working fine ztz96b_HQ7_land_rovers_the_Only_available_rus_fuel_trucks+jf17AI.miz

You almost completely wrong made with vanilla 2.5.6.52196 ATZ-60 the huge fuel truck was never available for user placed object. EDIT2: Even doesn't have damage model in the beginning of the 2.5 series, now has. All other is there, but not the same name as you mentioned. EDIT: Does "historical list of units" tricked you, the clock icon down center with mission date? ztz96b_HQ7_land_rovers_the_Only_available_rus_fuel_trucks.miz

clearly readable HUD poll If you have still problem with actual HUDs, or you feel nostalgic about readability of HUDs of older DCS versions there is a poll in the wishlist section: https://forums.eagle.ru/showthread.php?t=280991

clearly readable HUD poll If you have still problem with actual HUDs, or you feel nostalgic about readability of HUDs of older DCS versions there is a poll in wishlist section: https://forums.eagle.ru/showthread.php?t=280991

This is in DCS from version 2.5.6.52196. Now we can filter "PART OF COALITION IN ZONE" to unit type. Thanks ED!

2-5-6-52196_ewr55g6_red_in_mirror.trk: https://cdn.discordapp.com/attachments/543358251694292992/733443164148596856/2-5-6-52196_ewr55g6_red_in_mirror.trk EDIT: Discovered with MiG-29A, but with F-15C too red in mirrors

Thanks Ironhand for clarification. I practiced landings for a lot of time, mainly with Su-27. But i'm still uncomfortable to land MiG-29 because this huge love to huge bounces at touchdown of the nosewheel at the wrong speed, it's a real punisher. EDIT: My key to a safe MiG29 landing is a big dose of nose up trim, because the plane is not forgiving in sudden pitch changes, early nosewheel touchdown (sink) could happen too easily.

Sirrah, you most of the time fly in perfect conditions.

FYI Not fixed in 2.5.6.52196 Sharjah Intl/PG is named as Novorossiysk/Caucasus when using Persian Gulf map after Caucasus map

Forced repair repair the tyre, but not externally, you levitate above the ground with new tyres: https://cdn.discordapp.com/attachments/543358251694292992/733393118660919296/2-5-6-52196_f15_popped_tyre_forced_repair_only_halfly.trk

We lost this feature in OpenBeta. After version 2.5.6.49798 we must lower drastically gamma to easier read HUD, but that end on gamma 1, with everything else is dark. HUD is useless in fog f.e. when no sun visor exists on a plane. Good old: current state:

loosing patience This random bug introduced in early jun, and still detailed logs are useless to catch this. the attached log made with autoexec.cfg line: log.set_output("dcs", "", log.ALL, log.FULL) Very bad hit every feature that we lost! Seems to me ED is less care about flightsim aspects nowadays. i'm still waiting to response from ED, what does this mean? 2020-07-16 16:41:39.218 WARNING EDTERRAINGRAPHICS41: failed to open "surfaceDetailsHints" section in terrain config dcs.log.noairfieldmarkings52196.txt.zip

trigger condition expanded, bug remained I resaved last mission in 2.5.6.52196 (leaved on the ALL filter the PART OF COALITION IN ZONE conditions), then run again on norender server: on the third connect at first spawn happened again, replayable TwoTriggeredBasesForEnemy-20200715-211630_firstSpawnAnapaSu27BlueAsRED.trk

apply to 2.5.6.50979 and 2.5.6.52196 slightly a different way You can try with a mission created with 1.5.8 or a 2.5.6 factory Su-25T Quickstart mission. Try to place a neutral Portugal F-16CM, airstart with few waypoints. After placement (older missions, newer missions no placement) can switch back to red or blue, then you save, the unit completely disappear and you locked in to ME, only zoom functioning. Errors in the attached logs. (Cuba and South Africa good for testing too because these are relatively new in DCS.) plus: in newer (not fresh) missions wehicles country listing in "all" mode can shows only red and blue portugal-neutral-MElockdownaftersaveanddisappear.zip

Completely random, it not depends on track. My log with your track. 8th try, with one Windows restart in between. More likely to disappear runway markings in the first or the second start of DCS. dcs.log.8thrun.nomarkings.txt.zip

jetski: exclude DCS folder in your antivirus

Warning about repair cleanup state! [REPORTED]Repair tool deletes all hard drive content - ED Forums https://forums.eagle.ru/showthread.php?t=280607

In your case high prf. should be used to closing (hot) target with scan elevation to -1, and you may use predicted target range too.

same loopz for me: april 11 When AI Tomcat was on the groove I landed my Hornet, result: Just disturbing (fly under) AI on the groove is not enough for looping. (For me AI just done today a wave off.) (I have a long tack for 2.5.6.45915 only, not replayable with latest) I have a highly edited scene, for someone is good at arrival timing. Maybe we can pump up the number for landing AIs for greater chance. for_f14a_looping.miz