lester

К сожалению, он разучился это делать уже давно, с 2.9 (если в миссии есть ветер). Пока вынужденно запрашиваю контроль на упавление(C) сразу после того, как преключаюсь с заднего на переднее сиденье и вывожу на висение вручную, а потом задействую автомат удержания положения ATT HOLD (и высоты ALT HOLD) - благо его пофиксили в этом патче.

Looks like George is still unable to hover when there's a wind in the mission after switching from the backseat. When in the backseat I bring it to hover with no issues (with or without ATT HOLD mode engaged), then after switching to the front seat George immediately turns aside, can't align. The only workaround for now it seems is to request control right after switching to the front seat then hover manually. Attached track just in case, can someone confirm please? I could have put too strong wind, but again I have no issues to hover when doing it manually. apache_george_wind_29.trk

Подтверждение карты Афганистана от Ника Грея (не помню, было ли официальное подтверждение от ED, были координаты в прошлогоднем and beyond видео), работы ED по ней продвигаются очень быстро, ожидается в 2024 (цитата: "coming next year"). Также в работе карта "еще одной страны поблизости" в начале 2024 (цитата: "but also coming early next year is another one nearby"), пока воздерживатся от названия: будет в 2-х частях и поспособствует тому, чтобы регион был представлен в симуляторе. Обе должны быть представлены в новом видео "2024 and beyond".

А вот и официальный видос от HB:

Very sad news. RIP

Имеется в виду в 2.9 vs 2.8? https://github.com/Quaggles/dcs-charts#changelogsummary-dcs-290

Hey @Flappie. Now with pagefile settings set to default for sure, I got crash in 2.9 MT while flying in a Viper on a multiplayer server. Looks like it's familiar ACCESS_VIOLATION memory error. Please find the logs attached (also sent crash report), hope it might help. dcs.log dcs.log-20231031-061115.zip

I wasn't able to reproduce it in singleplayer mission: both with hot start in the air and with cold start and take off, with my usual startup routine. But it's definitely reproducible for me in multiplayer. Unfortunately can't provide track because of that. This is how this effect looks like: Note that I didn't touch rudder pedals after switching to CPG seat.

Same here. Makes working with TADS after switching really uncomfortable.

А ЭПР Maverick достаточна для перехвата Тором?

Хотел еще уточнить, помимо ATT HOLD наблюдаю проблему при переключении с места пилота на CPG в 2.9: вроде оттримировался, но после переключения вертолет под управленем Джорджа начинает осциллировать влево-вправо, что делает работу с TADS очень некомфортной. Может это быть как-то связано или я что-то делаю не так? До 2.9 я обычно переключался на CPG только после установки ATT HOLD и ALT HOLD, но сейчас ATT HOLD сломан, поэтому просто стараюсь переключиться из максимально стабильного положения. Если необходимо, могу записать короткий трек. И большое спасибо разработчикам за постоянную работу над модулем. UPD: пользователи на англоязычной части форума сообщают о такой же проблеме: UPD2: с коротким треком я поторопился, не удается воспроизвести в простой миссии со стартом в воздухе. этот эффект воспроизводился в мультиплеере, причем каждый раз когда я перключаюсь с пилота на CPG. UPD3: не смог воспроизвести и после холодного старта, с мой обычной процедурой запуска и настроек и последующим взлетом в однопользовтельской миссии. На сервере воспроизводится, снял короткий ролик как это выглядит: Педали естественно не трогаю после переключения.

Если его нет, то его нужно создать. Проблема в том, что даже при наличии файла с ключом и значением как указано в патч ноутс не возвращает прежние точки. Есть несколько сообщений на англоязычной части форума с такой же проблемой.

@Flappie I wasn't able to disable new dots in VR the way it described in the patch notes: There are other reports about it too. Maybe I did something wrong or maybe sharpening affects it as you wrote? I do have DLSS and DLAA enabled and sharpening set to 0.5 as suggested. Checked 2D with just DLAA too: new dots are still there

Same here: wasn't able to disable new dots by setting DotRendererExperiment = False in the autoexec.cfg file I created under \Saved Games\DCS.openbeta\Config folder in VR (HP Reverb G2).

Shoot, I did change the pagefile settings back to default as you suggested, but it looks like they haven't not been actually applied until the OS restart (which I thought I did at the time of error, but it obviously didn't happen looking at the logs). My apologies and thank you for your time @Flappie !

Just got interesting OOM error on MP Syria server flying Viper, there was a dialog notifying that game crashed (and suggested to send report, which I did later), but the DCS process continued to run until I left the server. dcs.log-20230917-062313.zip dcs.log

@Flappie After upgrading to 64GB of RAM got first OOM error on multiplayer server Syria map flying Apache. Pagefile settings are the same as above. dcs.20230912-063313.crash dcs.20230912-063313.dmp dcs.log

Okay, I got a lot of OOM crashes recently, I even tried a different multiplayer server. No errors in single player so far. The bad part of it is: it made DCS unplayable in multiplayer for me, the good part: my new 64GB RAM arriving tomorrow so hopefully these OOM errors should be gone. It's probably caused my RAM given that I don't see a lot of other reports, the only thing disturbing me is that number of these OOM errors grew exponentially for me since the latest OB. Attaching two recent crash logs when I flew on 2 different servers just in case (first Apache on PG map, second Strike Eagle on Caucasus map), because in both cases proper zip files were generated and they probably contain more information than in previous messages. For the second one it seems DCS process was still alive even after error message had been displayed until I pressed the button to send crash report. dcs.log-20230728-004708.zip dcs.log-20230728-021820.zip dcs.log

And just got another OOM error flying Apache on Syria map on the same server (I was switching between looking at F15SE on F2 view flying overhead and F10 map at the moment of a crash). I'm curious can it be a problem with physical RAM on my machine... I see other reports about crashes in the most recent OB though: I did delete fxo and metashaders2 folders (I do it every time after the update). dcs.20230726-043434.crash dcs.log

@Flappie Got another OOM error on the same MP server flying Strike Eagle on Marianas map. Wanted to confirm: in both this log and the one in the previous message I see log entries related to Heatblur F-14 like: Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_<something> interleaved with out-of-memory errors. Are they unrelated? It's also interesting that I don't get such errors flying on the same server, but on maps different from Marianas (which is indeed resource-heavy map). UPDATE: actually just got another OOM error flying Apache on Syria map on the same server (see my message below). I checked both my disks with chkdsk as you suggested, no issues found (see attached output). I have 32 GB RAM of physical memory and 64GB pagefile (see screenshot). I thought it should be enough even for Marianas? Thanks! dcs.log dcs.20230726-030837.crash dcs.20230726-030837.dmp chkdsk_output.txt

Interesting. I definitely have ~300GB free on both of my M2 NVMe drives. But as you wrote maybe it's my local thing (also it seems it's time to upgrade 32GB RAM -> 64 GB RAM). Thanks for checking!

Hey @Flappie . Decided to post another OOM crash I got on MP server flying Hornet on Marianas map as I think looking into log this error is a bit different from the previous one. 2023-07-24 03:06:48.849 ERROR DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_HELMET_NORMAL.dds. Reason: Not enough memory resources are available to complete this operation. 2023-07-24 03:06:48.864 ERROR DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_HELMET_RoughMet.dds. Reason: Not enough memory resources are available to complete this operation. 2023-07-24 03:06:48.876 ERROR DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET.dds. Reason: Not enough memory resources are available to complete this operation. 2023-07-24 03:06:48.893 ERROR DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET_NORMAL.dds. Reason: Not enough memory resources are available to complete this operation. 2023-07-24 03:06:48.906 ERROR DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET_RoughMet.dds'. Reason: The request is not supported. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): More out of memory in ed_malloc for 16777444 bytes. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): More out of memory in SharedBuffer for 16777412 bytes. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): Not enough memory to decompress: HB_F14_LOD1_3in1.dds 2023-07-24 03:06:48.906 ERROR DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_LOD1_3in1.dds'. Reason: The parameter is incorrect. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): More out of memory in ed_malloc for 16777444 bytes. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): More out of memory in SharedBuffer for 16777412 bytes. 2023-07-24 03:06:48.906 ERROR EDCORE (18824): Not enough memory to decompress: HB_F14_LOD1_3in1_RoughMet.dds 2023-07-24 03:06:48.907 ERROR DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_LOD1_3in1_RoughMet.dds'. Reason: The parameter is incorrect. 2023-07-24 03:06:48.921 ERROR DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_SUIT.dds. Reason: Not enough memory resources are available to complete this operation. 2023-07-24 03:06:48.925 ERROR EDCORE (18824): More out of memory in ed_malloc for 22369828 bytes. 2023-07-24 03:06:48.925 ERROR EDCORE (18824): More out of memory in SharedBuffer for 22369796 bytes. 2023-07-24 03:06:48.925 ERROR EDCORE (18824): Not enough memory to decompress: HB_F14_TF30_A.dds 2023-07-24 03:06:48.925 ERROR DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_TF30_A.dds'. Reason: The parameter is incorrect. 2023-07-24 03:06:48.926 ERROR EDCORE (18824): More out of memory in ed_malloc for 22369828 bytes. 2023-07-24 03:06:48.926 ERROR EDCORE (18824): More out of memory in SharedBuffer for 22369796 bytes. 2023-07-24 03:06:48.926 ERROR EDCORE (18824): Not enough memory to decompress: HB_F14_TF30_A_RoughMet.dds 2023-07-24 03:06:48.926 ERROR DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_TF30_A_RoughMet.dds'. Reason: The parameter is incorrect. 2023-07-24 03:06:48.954 ERROR EDCORE (30100): More out of memory in ed_malloc for 12198088 bytes. dcs.log-20230724-030646.zip dcs.log

Думаю, насчет HOTAS и интерфейса дело практики и личных предпочтений. Как по мне, именно интеграция с HOTAS в Хорнете не самая удачная по сравнению даже с Вайпером, в Страйк Игле и особенно в Кабане (что неудивительно, т.к. ЕМНИП его HOTAS создавался на основе опыта полученного в других платформах) она еще более продвинутая. Да, сейчас ситуационная осведомленность SA ограничена, но даталинк будет реализован (у Хорнета SA page тоже не сразу появилась) и у Страйк Игла будет что-то типа HSD Вайпера. При этом радар у Страйк Игла самый мощный и дает много информации, хотя к интерфейсу надо привыкнуть. Думаю, если есть звено Иглов, то они могут достаточно хорошо контролировать пространство распределяя высоты и.т.п для обзора. А насчет экранов помнится еще в The FPP подкасте один из пилотов/wso Страйк Игла говорил, что хотелось бы чтобы обновили.

Hey @Flappie. Look like I got memory error (ACCESS_VIOLATION) on MT Syria map on multiplayer server when flying Apache. Attached both generated zip and log file. dcs.log-20230703-063100.zip dcs.log