discwalker

+1 and the units name

@fitness88 Believe me, the max gamma of 3.5 is enough dark when you try to land at night to an unlit runway in Caucasus, unlit because of DCS 2.5.0 inherited MP incompleteness (bug https://forums.eagle.ru/showthread.php?t=201610) If you miss to spot the runway threshold markings, landing is impossible. Cockpit displays of Su-25T are almost unreadable at 3.5 gamma, very rude. Visibility only improve slightly in external view.

DCS need an option to all planes to HUD only view show only the HUD. I using one monitor and therefore i don't want to export the MFDs.

I need the "cheat". Thank you very much.

+1 But currently unwantedly or without a proper conception working on all client aircrafts in the same manner if same kind with the placed "player" A/C to multiplayer mission with preprogrammed system failures.

My odd takeoffs caused by accidental auto flaps at takeoffs with the last landings pitch trim settings. Why not trim pitch automatically in air in all circumstances at flaps auto settings? It can kill you. In this case manual trim is not working but applied the latest setting, until half flaps and back to auto: https://cdn.discordapp.com/attachments/551106084157390874/669609225827123210/25541962_deadly_Trim_TO_edition-flaps_auto.trk I am curious to Stubbies2003 odd takeoffs stabilators position at takeoff roll.

My rig passed memtest86 twice I still got IC failure in MP F14 spawn today at first time, second start was all ok. dcs.log.misc.hlsl.txt.zip

research Added South Africa: DCS 2.5.2.20601 Update 9 https://forums.eagle.ru/showpost.php?p=3603492&postcount=5 Added Cuba: DCS 2.5.4.27314 Open Beta https://forums.eagle.ru/showpost.php?p=3797108&postcount=44

Country listing is often abundant in "NEW AIRPLANE GROUP" and "NEW HELICOPTER GROUP" in case of editing older missions. In older DCS versions there was fever known countries, the difference is added to these editing modes to the list box. In case of 1.5.8 lastest (and early 2.5.0): Cuba and South Africa. If a known country is not added to the mission file neutrals section it will be listed unwantedly. ["coalitions"] = { ["neutrals"] = { You can experience more with the by hand prepared "usafa_vs_usa_2-5-5-prepared.miz", in which only Russia is listed on neutrals side. Or with the mission from 2013. previous attachment, which is created with DCS 1.5.8: 1,5_usa_vs_usafa_coalsample.miz https://forums.eagle.ru/attachment.php?attachmentid=219361&d=1571181586 (the year 2013 Ka50 mission is free, unlimited distribution: https://www.digitalcombatsimulator.com/en/files/345629/) This imprefectness will generate more confusion when new countries will be added. usafa_vs_usa_2-5-5-prepared.miz Live Fire Ground_ka50-2013may.miz

we need to live with that

odd takeoffs is not exclusively for you Next time use the rightCtrl+ENTER view for watching trim status when gear is up and flaps on auto. Maybe we can record it one time on video. I fly MP too almost every time. For me the Hornet produced **twice** scary takeoff with full bomb loadout. The plane tried to kill me with forced climb to stall. I needed to release gear and flaps to manually correct the TRIM! (The odd takeoffs was not the first.)

Usable gears "down lock override" for completeness. (DCS Hornet has this function from day one.)

from cockpit Belorechensk

Trouble areas on caucasus @Boosterdog: not Metsia, but Mestia: i cannot find here the diggers in air Your Belorechensk coordinates are wrong. Look around from my ground vehicles in the attached mission. explore_diggers_and_sukhumi_fence_vs_searchlight.miz

To report a memory leak ( ) you need MS systinternals processexplorer utility as written here at the end section https://www.digitalcombatsimulator.com/en/support/faq/710/ because DCS not crashed the crash reporter not create a minidump

My results of quick investigation: (You need su-33 module to play back correctly. EDIT: and the main version of DCS used in january) The screenshot for the first MP track, shot in play time: https://cdn.discordapp.com/attachments/543358251694292992/666367154345738280/unwantedpopups-20200113-203109_singleMainCommMenuAtAWACSrep.trk https://cdn.discordapp.com/attachments/543358251694292992/666367157634072586/unwantedpopups-20200113-203421_multiple_flares.trk

Track replay fail in outside view at 8:55:04 when A-10C not installed. Uncommanded popup of communication menu in main section can occur 99% at allied flight reports. Even open in main when you in your tanker menu, and you begging for the basket. I hate the uncommanded behaviour since introduction. ED need to count F12 hits. And very unwelcome to the newbies when popup under f10 map view and NOT visible. I can not count in one hand how many of our newbies struck to this situation.

I downloaded your logfile. Your 14 GB of paging memory is tiny to DCS. You use several mods, those can behave differently in an updated DCS. Maybe your F-14 module need a uninstall / reinstall.

When I had crashes at loading stage last time my SSD was faulty. It is worth a penny to try to copy the whole DCS installation to an another folder. To see all files are readable in whole or not. EDIT: I exactly got a lot of IN_PAGE_ERROR as you are

Yes, communication menu causing pain many times. Just one case: if you tune in to the station and unreachable in menu.

track and video This behaviour is examineable almost anytime on 104th server. Since long ago. https://cdn.discordapp.com/attachments/599576363837423619/660570041930088449/8_Op_Fire_Shield_16-20191228-204039-missiles.trk There is no need to wait to spawn to plane just hit the F6 numerous times. You can see dead missiles alive.

ED should consider to shut down auto popup communication menu, for everyone at least an option, so annoying, not just folks like me without any headtracking solution. So many times i must hit F12 with frustrated mind. It's a bad thing since introduction. Except when opening in the right page at aerial refueling for Ready to contact - to spam to the not helpful tanker. But sometimes automatism change that page too :-(

I play rarely with F14B in multi But IC false alarms is frequent. After restart the failed file magically healed. What is the common in F-14 and fog?: fogcommon.hlsl 2019-12-07 20:48:38.083 ERROR SECURITYCONTROL: Manifest hash check failed for file 'bazar/shaders/common/fogcommon.hlsl' IC fail and disconnection is 99% sure for the first time. EDIT: DCS files are excluded in my antivirus real time scanner dcs.logf14_and_fog_THE_common.txt.zip

When I in single player tested, I cannot restrict; but multiplayer the restriction is working in our Aerobatic server. EDIT: Nevermind, In Multiplayer the warehouse change by update restricted the LAU-127 attached sidewinders, with updated stock restriction not possible.

i tought it was fixed long time ago mergeable with this finally reported one: https://forums.eagle.ru/showthread.php?t=232681